Webhooks Configuration
Overview
Configuring Webhooks
1.
2.
3.
4.
5.
Webhook Headers
{
"Content-Type": "application/json",
"X-Webhook-Security-Fields": "id,status",
"X-Webhook-Security-Hash": "0f52db1b460e50b6684de069176da48a2f9fe20b1b97336cc7eb550f19bbf805",
"X-Webhook-Request-UUID": "fa8ff1ec-8eed-44fc-a84b-5a6ffc2b531f"
}
Header Details
Content-Type
: Specifies that the payload is in JSON format.X-Webhook-Security-Fields
: Lists the payload fields used for security hashing.X-Webhook-Security-Hash
: A hash for verifying webhook integrity.X-Webhook-Request-UUID
: A unique identifier for debugging requests in webhook logs.Webhook Security
Obtaining Webhook Secret
1.
2.
3.
4.
Hash Generation Process
1.
X-Webhook-Security-Fields
from the webhook payload.2.
3.
4.
5.
X-Webhook-Security-Hash
to verify webhook authenticity.Available Webhooks
Technical Name | Title | Description |
---|---|---|
BusinessKycStatusChanged | Merchant KYC Status Changed | Triggered when the Know Your Customer (KYC) status of a merchant changes. This webhook helps track compliance and verification status updates. |
BusinessExternalAccountStatusChanged | Receiver Account Status Changed | Triggered when the verification status of a receiver account changes. |
BusinessRequestStatusChanged | Transaction Status Changed | Triggered when the status of a transaction changes. It allows you to monitor and respond to updates regarding transaction status updates. |
BusinessRequestPayoutConfirmationStatusChanged | Transaction Payout Confirmation Status Changed | Triggered when the status of a payout confirmation (telex) request changed. It allows you to track when the request is completed and the document is available. |
Webhook Log
Accessing the Webhook Log
1.
2.
3.
4.
Best Practices
Modified at 2025-03-04 13:00:08