The end-to-end webhook sequence for a standard card purchase, from authorization through settlement.
This is the standard flow for a card purchase that is approved and later settles normally, with no reversal or refund. It walks through every webhook Altery sends along the way.
Sequence
sequenceDiagram
participant Cardholder
participant Scheme as Card Scheme
participant Altery
participant Partner as Your System
Cardholder->>Scheme: Presents card at merchant
Scheme->>Altery: Authorization request
Altery->>Partner: CardAuthorizationRequest (sync, 2s timeout)
Partner->>Altery: authorize: "true" / "false"
Altery->>Scheme: Authorization decision
Altery-)Partner: CardTransactionApproved (notification)
Note over Altery,Partner: 1-3 days later, or longer
Scheme->>Altery: Clearing / settlement received
Altery-)Partner: CardTransactionCleared (notification)
Webhooks in this flow
| Step | Webhook | Type | Description |
|---|---|---|---|
| 1 | CardAuthorizationRequest | Request | Sent in real time; your response approves or declines the transaction |
| 2 | CardTransactionApproved | Notification | Sent once the authorization is approved and the transaction is created |
| 3 | CardTransactionCleared | Notification | Sent when the processor confirms settlement |
If the authorization is declined instead of approved, see CardTransactionDeclined — the flow ends there and no further webhooks are sent for that authorization.
Amount across the flow
The amount authorized, the amount approved, and the amount cleared are not guaranteed to be identical — see Non-Standard Transaction Scenarios for cases like partial approvals, tips, and foreign-currency exchange-rate differences. Each webhook's contract page explains what its own amount field represents; treat the clearing event as the source of truth for reconciliation.
See also
- Reversal flow — when an authorization is cancelled before settlement instead of clearing
- Refund flow — when a settled transaction is later returned to the cardholder
- Non-Standard Transaction Scenarios