Event Notifications (Webhooks)
Receiving Event Notifications
Notifications are Event objects pushed to the merchant server. Trustly will send a POST request to the notification endpoint that you provide. A notification indicates changes to the object referenced in the event, such as changes to the transaction status (authorized, canceled, denied). See Get Transaction for more information.
Info
You must return HTTP status
200 OKin less than 3 seconds. If Trustly does not receive a200 OKresponse in 3 seconds, we will retry the notification every 5 minutes for 12 hours.
Info
Ensure you validate the Notification was sent by Trustly and has not been tampered with by Securing Requests.
Example Header
Authorization: Basic TThSYUhnRWpCRTU0enVGWU1SUXE6RVlOM0dYYXNyVlUxdlExdXlZejIyTk5RZHk0PQ==
An Event notification contains the following headers:
| Parameter | Type | Description |
|---|---|---|
| Authorization | String | A Base64 encoded string that can be used to validate the request. |
Example Request
merchantId=1002463580&merchantReference=cb180040-7210-4ab9-97b7-415824754802&paymentType=2&transactionType=3&eventId=1002593570&eventType=Authorize&objectId=1002593555&objectType=Transaction&message=&timeZone=Etc%2FUTC&createdAt=1556234040954&accessId=M8RaHgEjBE54zuFYMRQq&paymentProviderTransaction.status=AC100&paymentProviderTransaction.statusMessage=AC100&status=2&statusMessage=Authorized
An Event notification body is an application/x-www-form-urlencoded string with the following parameters:
| Parameter | Type | Description |
|---|---|---|
| merchantId | String | A unique ID that identifies the merchant. |
| merchantReference | String | A unique identifier from the merchant’s systems such as order ID. |
| paymentType | String | Identifies the type of Payment this notification is associated with. This is provided in the establishData when the Authorization is created. |
| transactionType | String | Type of Transaction that this notification is associated with (Authorization, Capture, etc). |
| eventId | String | A unique Trustly event identifier. |
| eventType | String | Type of Event included in this notification. |
| objectId | String | A unique ID that identifies this transaction. This will be the transactionId that is returned from the Trustly API or SDK. |
| objectType | String | The type of object this Event is related to. See Object Types. |
| message | String | Optional event message. |
| parentObjectId | String | The unique ID of the parent object if existent. |
| timeZone | String | Time zone used for createdAt. This will always be Etc/UTC. |
| createdAt | Unix Timestamp | The notification creation date and time |
| accessId | String | accessId that was used when generating the Transaction. |
| paymentProviderTransaction.status | String | |
| paymentProviderTransaction.statusMessage | String | Payment provider transaction status message. |
| status | String | |
| statusMessage | String | Status message. |
| errorCode | String | Error code related to the current status. |
| splitToken | String | Only sent if enabled for the merchant. Only sent if transactionType = 1 and status = 2. Merchant must store the value and send it back on Capture API calls. |
| paymentProviderTransaction.reasonCode | Enum | The reasonCode should reflect more detailed information about why the transaction was not accepted successfully. |
| paymentProviderTransaction.reasonCodeMessage | String | A more descriptive description of the event that generated the reason code. |
To see a list of Event Types, visit Type Definitions
Updated 6 months ago