Webhook Definition
Please remember that the nature of webhook 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 missing 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.
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 | strin | The date time UTC when the payment was done | 19 |
Repetitions Pattern
Upon failure of the Webhook interface of the Customer (different from SC 200) Blokko will attempt to inform in a repetition pattern to inform the customer of an event.
| Attempt | Seconds |
|---|---|
| 1 | 0 |
| 2 | 30 |
| 3 | 60 |
| 4 | 90 |
Updated about 5 hours ago
