Card webhook events

Card events use the same subscription, envelope and signature as other Endl webhooks, with the object in data.

Event	When	Object in `data`
`card_enrollment.updated`	An individual’s or a business’s enrolment status changes	Enrolment
`cardholder.updated`	A cardholder’s status changes, for example `pending` to `active`	Cardholder
`card.created`	A card is issued	Card
`card.updated`	Status, controls or name change, including freeze and unfreeze	Card
`card.canceled`	Canceled, a single-use card spent, or expired — see `closedReason`	Card
`card_transaction.authorized`	A new authorisation	Card transaction
`card_transaction.updated`	The amount changed	Card transaction
`card_transaction.completed`	Settled	Card transaction
`card_transaction.reversed`	Fully reversed	Card transaction
`card_transaction.declined`	Declined	Card transaction
`card_transaction.refunded`	A refund arrived	Card transaction, `type: refund`
`card_deposit.completed`	Money reached the card balance, by either method	Deposit
`card_deposit.failed`	A deposit from the Endl account failed	Deposit
`card_withdrawal.completed`	Money left the card balance	Withdrawal
`card_withdrawal.failed`	A withdrawal failed	Withdrawal

The objects are the same ones the endpoints return: the Enrolment, Cardholder, Card, Card transaction, Deposit and Withdrawal.

Events arrive at least once and in any order. Ignore an event id you have already processed. When two copies of an object arrive, keep the one with the newest updatedAt; for deposits and withdrawals, keep the final status (completed or failed).

Introduction

Endpoints

Card webhook events