One payment, many transactions. A card payment that is authorized, then captured, then partially refunded will have three transactions:
AUTHORIZE, CAPTURE, and REFUND. If the first provider declined the authorization, there may be an additional AUTHORIZE transaction from the fallback provider.Object Fields
The unique identifier of the transaction (UUID).Example:
txn_f47ac10b-58cc-4372-a567-0e02b2c3d479The parent payment identifier. Links to the Payment Object.Example:
8546df3a-b83e-4bb5-a4b3-57aa6385924fThe transaction type, indicating the action performed against the provider.Values:
PURCHASE, AUTHORIZE, CAPTURE, CANCEL, REFUND, VERIFY, CHARGEBACK, FRAUD_SCREENING, SALEPURCHASE. Single-step payment (charge + capture in one call).AUTHORIZE. Places a hold on funds without capturing.CAPTURE. Captures a previously authorized amount.CANCEL. Voids an authorization before capture.REFUND. Returns funds to the customer after capture.VERIFY. Zero-value card verification (e.g., for enrollment).CHARGEBACK. Dispute initiated by the cardholder’s bank.FRAUD_SCREENING. Fraud analysis performed before processing.SALE. Combined authorization and capture in a single step (provider-specific).
PURCHASEThe transaction outcome status.Values:
CREATED, SUCCEEDED, PENDING, DECLINED, REJECTED, FAILED, CANCELLED, EXPIRED, ERROR, WON, LOSTCREATED. Transaction initiated, awaiting provider response.SUCCEEDED. Provider approved the transaction.PENDING. Awaiting asynchronous confirmation (common for PIX, Boleto).DECLINED. Provider declined (soft decline, retryable).REJECTED. Provider rejected (hard decline, do not retry).FAILED. Processing error on the provider side.CANCELLED. Voided before completion.EXPIRED. Timed out waiting for customer action or provider response.ERROR. Unexpected system error.WON. Chargeback dispute resolved in merchant’s favor.LOST. Chargeback dispute resolved in cardholder’s favor.
SUCCEEDEDName of the provider that processed this transaction.Example:
ADYENThe provider’s own transaction reference, used for cross-referencing on the provider’s dashboard.Example:
8835562831897070Yuno-normalized response code from the provider. See Response Codes for the full mapping.Example:
00Human-readable response message from the provider.Example:
ApprovedThe transaction amount. May differ from the payment amount in partial captures or partial refunds.
3DS authentication details. Present only for card transactions that underwent 3D Secure verification. See 3D Secure.
ISO 8601 timestamp of when the transaction was created.Example:
2026-03-01T14:31:01.000ZStatus by Transaction Type
Not all statuses apply to every transaction type. The following matrix shows which statuses are valid for each type:| Status | PURCHASE | AUTHORIZE | CAPTURE | CANCEL | REFUND | VERIFY | CHARGEBACK | FRAUD_SCREENING | SALE |
|---|---|---|---|---|---|---|---|---|---|
CREATED | Yes | Yes | Yes | Yes | Yes | Yes | — | Yes | Yes |
SUCCEEDED | Yes | Yes | Yes | Yes | Yes | Yes | — | Yes | Yes |
PENDING | Yes | Yes | — | — | Yes | — | — | Yes | Yes |
DECLINED | Yes | Yes | — | — | Yes | Yes | — | Yes | Yes |
REJECTED | Yes | Yes | Yes | Yes | Yes | — | — | Yes | Yes |
FAILED | Yes | Yes | Yes | Yes | Yes | Yes | — | Yes | Yes |
CANCELLED | Yes | Yes | — | — | — | — | — | — | Yes |
EXPIRED | Yes | Yes | — | — | — | — | — | — | Yes |
ERROR | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
WON | — | — | — | — | — | — | Yes | — | — |
LOST | — | — | — | — | — | — | Yes | — | — |
WON and LOST are exclusive to CHARGEBACK transactions and represent the final dispute outcome. All other transaction types use SUCCEEDED or DECLINED/REJECTED as terminal states.Example
Related Concepts
- Transactions. How transactions relate to payments and routing
- Payment Statuses. How transaction outcomes map to payment statuses
- Response Codes. Provider response code mapping and MAC codes