Transaction Events
TRANSACTION_AUTHORIZED
Fired when a card purchase is authorized. Funds are reserved but not yet settled.
WEBHOOK
Fires when a cardholder makes a purchase and the authorization is approved. The funds are reserved on the card but not yet permanently settled — a subsequent
TRANSACTION_CLEARED event confirms final settlement.
This is the earliest signal that a transaction has occurred. Use it to show pending activity to the cardholder in real time.
Event Type
Payload
Payload Fields
| Field | Type | Description |
|---|---|---|
transactionId | string | Unique transaction identifier |
cardId | string | The card used for the transaction |
cardholderId | string | The cardholder (best-effort — may be absent if not resolvable) |
externalId | string or null | Your internal user ID from the cardholder profile |
type | string | Always AUTHORIZATION for this event |
status | string | Always APPROVED for this event |
amount | number | Transaction amount in dollars |
currency | string | Transaction currency (ISO 4217) |
billingAmount | number | Amount in the card’s billing currency, in dollars |
billingCurrency | string | Billing currency — may differ for cross-border transactions |
merchant | object | Merchant details — may be absent for non-purchase transactions |
merchant.name | string | Merchant name |
merchant.id | string | Merchant identifier from the network |
merchant.city | string | Merchant city |
merchant.country | string | Merchant country (ISO 3166-1 alpha-2) |
merchant.mcc | string | ISO 18245 Merchant Category Code |
merchant.mccDescription | string | Human-readable MCC description |
Common Use Cases
- Show a “Pending” transaction in the cardholder’s transaction history
- Send a real-time push notification: “$29.99 at Amazon — pending”
- Implement MCC-based spending controls
Authorizations
API key from the FYATU CaaS portal. Pass as Authorization: Bearer <key>.
Body
application/json
Response
200
Acknowledge the event.

