Card Transaction Lifecycle

​

Typical lifecycle

1. pending: the transaction was created.
2. three_ds_required: the customer must complete authentication.
3. authorized or processing: card processing is still in progress.
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": "018f1f2e-7b43-7c9a-8d3e-1a2b3c4d5e70",
  "status": "three_ds_required",
  "method": "credit_card",
  "amount": 2490,
  "currency": "BRL",
  "next_action": {
    "type": "three_ds_challenge"
  }
}

​

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.

​

Read next

• Payment Element for Cards
• 3D Secure
• Transaction Statuses