Integration Guide
Last updated
Last updated
The notification body contains the type of notification and its payload:
The content of notification is encrypted to protect data from fraud attempts. When converting human-readable string to hexadecimal format, we use UTF-8.
Format of body: Hexadecimal Format of Initialization Vector: Hexadecimal
When your service receives a webhook notification, it must return a 2xx HTTP status code. Otherwise, the webhook service considers the notification delivery as failed, and will retry to send the notification later.
Parameter
Description
Format
Required
type
Type of the notification
• PAYMENT This type of notification is sent when a payment is created or updated in the system.
• REGISTRATION This type of notification is sent when a registration is created or deleted.
(PAYMENT|REGISTRATION)
required
action
Indicator of status change. This field is available only if the type is REGISTRATION.
• CREATED when registration has been created.
• UPDATED when registration has been updated.
• DELETED when registration has been deleted.
(CREATED|UPDATED|DELETED)
conditional
payload
Content of the notification. If the notification type is payment or registration, the payload's content will be identical to the response you received on the payment or registration.
JSON
required
Parameter
Description
Encryption algorithm
AES
Key
[secret of listener] (64-character-long hexadecimal string in configuration)
Key length
256 bits (32 bytes)
Block mode
GCM
Padding
None
Initialization vector
In HTTP header (X-Initialization-Vector)
Authentication tag
In HTTP header (X-Authentication-Tag)
Protocol
HTTPS (HTTP is allowed on test systems only)
HTTP method
POST
Content type
text(text/plain)