List currencies
List supported currencies with networks, directional transaction limits
(inbound / outbound), capability flags (can_onramp, can_offramp,
can_deposit, can_convert), and current conversion fees (fees) keyed by
settlement network. Flag meaning depends on type — see the API overview.
Each fees.payment_methods entry describes the tiered fee ladder and
per-chain network fees for its settlement network, split by offramp /
onramp when both directions are supported. fees is null for crypto
currencies and when fee data is unavailable.
Each row is unique by code plus country_code (for example every WAEMU
country has its own XOF entry with its own networks and limits). Use filters
to find currencies that support a given operation or network, then paginate
with page and per_page.
For which countries and networks we cover, start with GET /v1/countries. For
banks and mobile money operators (provider_id on fiat beneficiaries), use
GET /v1/countries/{country_code}/providers — not this resource.
Platform view vs customer view
Without customer_id, the capability flags answer “can this be done on the
platform” — they are the same for every caller.
Pass the optional customer_id query parameter (a customer id, cust_…) and
the same flags answer a narrower question: can this customer do this right
now? Capabilities that depend on the customer’s state are downgraded — today,
fiat can_deposit reads false when the customer’s KYC is not approved. The
capability filters (can_deposit=true, …) are then evaluated against the
customer’s view too, so a filtered listing never advertises an operation the
customer would be blocked from.
Every downgraded row carries a customer_restrictions array explaining the
downgrade. Each entry has:
capability— the capability that was removed (e.g.deposit).reason— a stable machine code (e.g.customer_kyc_not_approved).next_steps—{ action, docs_url }with what to do about it.
customer_restrictions entries are the exact diff between the platform view
and the customer view: they appear only for capabilities the platform
supports (true at platform level) that the customer’s state removes. A
capability that is false at platform level is never annotated, and the field
is omitted entirely on rows with no downgrade and in the platform view.
An unknown customer_id, or one belonging to another integration, returns
404 not_found; a malformed one returns 400 invalid_input. See the full
customer restrictions reference
for all restriction reasons.
Filter behavior
code— filter by ISO currency code (e.g.XOFreturns all WAEMU country rows).type—fiatorcrypto.country_code— filter by ISO 3166-1 alpha-2 country code.customer_id— customer id (cust_…). Switches the listing to that customer’s view (see above).can_onramp— boolean. Currencies that can participate in onramps. For fiat, usable as onramp source; for crypto, as onramp destination.can_offramp— boolean. Currencies that can participate in offramps. For fiat, usable as offramp destination; for crypto, as offramp source.can_deposit— boolean. Currencies that can participate in deposits (typically crypto only).can_convert— boolean. Currencies that participate in wallet-to-wallet conversions.network— only currencies that include this network in theirnetworksarray.min_inbound_amount— decimal string. Only currencies where at least one network has inbound min less than or equal to this value.max_inbound_amount— decimal string. Only currencies where at least one network has inbound max greater than or equal to this value.min_outbound_amount— decimal string. Only currencies where at least one network has outbound min less than or equal to this value.max_outbound_amount— decimal string. Only currencies where at least one network has outbound max greater than or equal to this value.page— integer, 1-indexed page number.per_page— integer page size (max 200).
Example
GET /v1/currencies?type=fiat&can_offramp=true
Authorizations
API key issued during merchant onboarding.
Query Parameters
Response
Supported currencies fetched successfully