> ## Documentation Index
> Fetch the complete documentation index at: https://developer.pagou.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Card Transaction Lifecycle

> Handle authorization, 3DS, capture outcomes, and terminal states in a predictable card payment flow.

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`: 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

```json theme={null}
{
  "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](/payments/cards/payment-element)
* [3D Secure](/frontend/payment-element/three-d-secure)
* [Transaction Statuses](/payments/transaction-statuses)