Webhoook Event Notification
Notifications, often referred to as webhooks, provide a mechanism for applications to receive real-time updates about specific events. Within this API, webhooks are used to inform your server about a range of events, including transactions, refunds, or card tokenization, allowing your system to react promptly to these occurrences.
Security
To validate the authenticity of requests, we use a signature process. The API key is hashed using SHA-256 to generate a key, which is then used in a HMAC-SHA-256 operation to sign the timestamp (Sec-Timestamp header) and request body. The signature is then compared to the value sent in the Sec-Signature header. Additionally, after verifying the signature, you must retrieve the session object to ensure the accuracy and legitimacy of the event before further processing. Note that you should expect to receive multiple events and handle each one accordingly.
Webhoook Event Object
id
string
Unique identifier for the event object.
type
enum
The event type is either “session.created”, “session.expired”, “session.completed”.
created_at
int
The timestamp at which the Session was created.
data.status
enum
The status of the session is either “open”, “expired”, or “completed”.
data.session_id
string
Unique identifier for the session object associated to the event.
Session Creation Notification
The "session.created"
notification informs your system that a new session has been successfully created
The above event type returns JSON structured like this:
Session Complete Notification
The "session.completed"
notification informs your system that a new session has been successfully completed
The above event type returns JSON structured like this:
Session Expire Notification
The "session.expired"
notification informs your system that a new session has been expired
The above event type returns JSON structured like this:
Last updated