Legacy webhooks and event types
For the current workflow with webhooks, see theWebhooks topic.
Webhooks allow you to retrieve real-time information about payment and payout events.
When webhooks are set up, Nexio sends a POST
request with event information to the specified endpoint.
NoteYou may also choose to receive a signature header—allowing you to verify the webhook's authenticity.
Event types
Below are the possible values for webhook event types.
Event Type | Description | Example Webhook Body |
---|---|---|
| Webhook will be sent when the account associated with the card has been closed | Account closed example |
| Webhook will be sent when the card brand advises you to contact the cardholder | Contact cardholder example |
| Webhook will be sent when card data has been updated | Card updated example |
| Webhook will be sent when card data has been saved | Card saved example |
| Webhook will be sent when echeck data has been saved | Echeck saved example |
| Webhook will be sent when any of the following happens:
| Payout event example |
| Webhook will be sent when any of the following happens:
| Spendback event example |
| Webhook will be sent when a subscription has been processed | Subscription example |
| Webhook will be sent when a transaction is authorized | Transaction event example |
| Webhook will be sent when a transaction is captured | Transaction event example |
| Webhook will be sent when a transaction is marked as pending | Transaction event example |
| Webhook will be sent when a transaction is refunded | Transaction event example |
| Webhook will be sent when a transaction is settled | Transaction event example |
| Webhook will be sent when a transaction is voided | Transaction event example |
Next steps
Updated 1 day ago