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

# Fiat account lifecycle

> How a customer's fiat (beneficiary) account moves through its states, why only one account can be active per payment method, and how a suspended account is reactivated.

A **fiat account** is your user's destination bank account — where fiat is sent on an off-ramp payout (for example a CBU/CVU/alias in Argentina, a CLABE in Mexico, or a PSE/BRE-B account in Colombia). Each account moves through a lifecycle driven by two things: its **validation** (does the account exist and belong to the customer) and an **activation rule** that keeps a single account active per payment method.

## Account states

| Status                  | Meaning                                                                                                                                      |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| `processing`            | Validation/registration in progress (asynchronous providers).                                                                                |
| `unconfirmed`           | Validated, waiting for confirmation. Applies to Argentina and Colombia (BRE-B) accounts, which must be confirmed before they can be enabled. |
| `enabled`               | Confirmed and ready to receive payouts.                                                                                                      |
| `suspended`             | Was `enabled`, then deactivated because another account for the same payment method was enabled. It can be reactivated.                      |
| `disabled`              | Validation failed permanently. The account cannot be used.                                                                                   |
| `revalidation_required` | The account must be re-validated before it can be used again.                                                                                |
| `deactivated`           | The account was deactivated and is no longer usable.                                                                                         |

A fiat account must be `enabled` before it can receive a payout.

## One active account per payment method

A customer can have only **one active (`enabled`) fiat account per payment method** at a time. When a fiat account becomes `enabled`, any other account that was previously `enabled` for the **same customer and the same payment method** is automatically moved to `suspended`.

The rule is scoped per payment method: enabling an account of one payment method does **not** affect the customer's accounts registered under a different payment method.

<Note>
  Suspension has no dedicated event or webhook. To detect that a previously active account was suspended, poll [List Fiat Accounts](/ramps-api/fiat-accounts/list-fiat-accounts) or [Retrieve Fiat Account Requirements](/ramps-api/fiat-accounts/retrieve-fiat-account-requirements) and read each account's `status`.
</Note>

## Reactivating a suspended account

A `suspended` account is not gone — it can be brought back to `enabled` in either of these ways:

* **Re-register the same account.** Submitting [Create Fiat Account](/ramps-api/fiat-accounts/create-fiat-account) again with the same account details re-enables the existing account instead of creating a duplicate.
* **Use it in a new off-ramp.** Referencing the suspended account's `fiatAccountId` when you [create an off-ramp order](/ramps-api/off-ramp/create-off-ramp-order) or [off-ramp session](/ramps-api/off-ramp/create-off-ramp-session) reactivates it.

In both cases the account returns to `enabled`, and — following the rule above — the account that was active before it is moved to `suspended`.