Skip to main content
A destination defines where fiat funds land when an off-ramp completes. Each destination is tied to a customer and holds:
  • Account holder details and banking information for the receiving bank.
  • The relationship between the customer and the account holder (see below).
Supported rails depend on the destination’s country and currency — see Coverage.

​
Holder relationships

When you add a destination to a customer, you have to specify the relationship between the customer and the account holder.

​
Self payments

If the customer is sending funds to their own destination, use:

​
Third-party payments

If the customer is paying a third party (suppliers, employees, family members, etc.), use one of these relationships: Example: a Brazilian company paying a supplier in the United States would create a destination with SUPPLIER as the holder relationship and provide the supplier’s US bank details.

Transactions

Route payouts to a destination.

Customers

The legal entity that owns the destination.

Nested Payments

Why holder relationships have to be disclosed and accurate.

Coverage

Supported rails by country and currency.