Webhook Definition
Webhooks are used to notify your system the moment an end-user completes a payment. Instead of polling for updates, your server will receive an HTTP POST request with the transaction details automatically.
Please remember that the nature of webhooks is asynchronous, no payload is expected as a result of sending you the event, only a 200 Status Code. Any code different from 200 will be interpreted as a failed attempt to inform you and will enter into a repetition cycle, please read the next section to acknowledge the amount of repetitions and spacing between them. Set up your callbackUrl through /v2/merchants/{merchantId}/webhook endpoint.
Data Structure
| Field | DataType | Description | Length |
|---|---|---|---|
| authorizationId | string | Blokko's authorization Id | 8 |
| transactionUuid | string | Blokko's unique identifier for the transaction | 36 |
| merchantId | string | The id you created for the transaction | 36 |
| merchantReference | string | Your internal purchase reference | 36 |
| transactionStatus | string | "P" for pending "E" for Executed (finished) | 1 |
| createdAt | string | The date time UTC when the transaction was created | 19 |
| completedAt | string | The date time UTC when the payment was completed | 19 |
Repetitions Pattern
Upon failure of the Webhook interface of the Customer (different from SC 200) Blokko will follow a repetition pattern to inform the customer of an event.
| Attempt | Seconds |
|---|---|
| 1 | 0 |
| 2 | 30 |
| 3 | 60 |
| 4 | 90 |