Webhook Event Codes
Use the Webhook Event Codes pages to understand and configure the webhook notifications available through Thredd's Event Delivery Service.
Webhook Event Codes
Thredd’s Event Delivery Service uses event codes to identify the type of webhook notification being sent. Each event code has its own payload structure, example request, example notification response, and field descriptions.
Use this page to find the event code you want to configure or understand.
Available event codes
| Event code | Event name | Description |
|---|---|---|
| 101 | Fraud Rule Triggered by a Transaction | Sent when a fraud rule is triggered by a transaction. |
| 102 | Fraud Acknowledgement Notification | Sent when a fraud alert is closed, acknowledged, or times out. |
| 103 | Card Status Change | Sent when a card status changes. |
| 104 | Custom PAN Creation | Sent when a card with a custom PAN has been created. |
| 105 | Payment Manual Review Outcome | Sent when a pending payment has been reviewed in Scam Transaction Monitoring. |
| 106 | Tokenisation Authorisation Request (TAR) | Sent when a Tokenisation Authorisation Request is received. |
| 107 | Activation Code Notification (ACN) | Sent when an activation code notification is generated. |
| 108 | Tokenisation Complete Notification (TCN) | Sent when tokenisation has completed. |
| 109 | Tokenisation Event Notification (TEN) | Sent when a tokenisation lifecycle event occurs. |
| 110 | Tokenisation Status Update Failure Notification (TFN) | Sent when a token status update fails. |
| 111 | Apata Finalised Event | Sent when Apata sends a finalised 3D Secure event. |
| 112 | Transaction Confirmation Event | Sent for transaction confirmation notifications. |
| 115 | FTM Alert Creation | Sent when a new alert is created in Fraud Transaction Monitoring. |
| 117 | Open Banking Registration | Sent when a customer interacts with an Open Banking registration session. |
| 119 | Card Lifecycle Notification | Sent when a card is created or activated, allowing clients to receive asynchronous card lifecycle updates. |
| 121 | Card Creation Failure | Sent when there is a card creation failure during the customised card creation process. |
NoteEvent Code 103 (Card Status Change) sends notifications asynchronously only, as messages are processed in batches. Clients will not receive notifications in a specific order. If a client requires ordered processing, you must use the notification timestamp provided in the payload to ensure proper sequencing.
How webhook event pages are structured
Each event code page includes:
- when the event is sent
- any onboarding or configuration requirements
- an example webhook configuration request
- an example notification response
- field descriptions for the response payload
Updated 2 days ago