Skip to main content

Webhooks

Information on the endpoints for managing notifications by the receiving PSP to the receiving end user.


Receiving Callbacks

This service has two security protection methods:

  • mTLS Authentication: In your server's domain representing, you should configure the requirement of the public key (mTLS) that we are providing, for mutual authentication to occur. It is necessary for your server to have a minimum TLS version of 1.2.

    To configure your server, you can follow the examples mentioned in the Pix API.

    Callbacks are sent by Efí via POST url-webhook-registered when there is a change in status.

  • Validation by hash registered in webhook: An HMAC (a unique identifier) will be appended to the end of the URL when sending the callback. This hash registered in the webhook will be used to validate the notification's origin. Thus, all webhooks sent to your server will have this final identification, and your application must confirm its presence.

    Callbacks are sent by Efí via POST url-registered-webhook?hmac=registered-hash when there is a change in status.

Information

If you need to test the Payment endpoints of the Open Finance, we have a functional testing environment that allows simulating all the statuses returned by our API and webhook.

If the payment amount is R$ 0.11:
The payment will be rejected, and the information will be sent via webhook.
If the payment amount is different from R$ 0.11:
The payment will be accepted, and the information will be sent via webhook.


Request