Skip to main content
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

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.
Suspension has no dedicated event or webhook. To detect that a previously active account was suspended, poll List Fiat Accounts or Retrieve Fiat Account Requirements and read each account’s status.

​
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 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 or 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.