Skip to main content
Use this page to map card-specific statuses into order and fulfillment behavior.

​
Typical lifecycle

  1. pending: the transaction was created.
  2. three_ds_required: the customer must complete authentication.
  3. authorized or processing: the issuer or acquirer is still working.
  4. captured or paid: the payment is final enough for fulfillment.
  5. refused, canceled, refunded, or partially_refunded: stop or reverse fulfillment.

​
Example response that requires customer action

{
  "id": "tr_2001",
  "status": "three_ds_required",
  "method": "credit_card",
  "amount": 2490,
  "currency": "BRL",
  "next_action": {
    "type": "three_ds_challenge",
    "challenge_session_id": "3ds_1001",
    "client_secret": "sec_1001",
    "expires_at": "2026-03-16T14:20:00.000Z"
  }
}

​
Status handling guidance

  • Do not fulfill on pending or three_ds_required.
  • Fulfill only once when you reach a settled state such as captured or paid.
  • If the browser flow ends unexpectedly, reconcile with GET /v2/transactions/{id}.
  • Treat refund and chargeback states as separate finance workflows.