Accepted Currencies
Pronunciation: ak-SEP-tid KUR-un-seez
Also known as: Merchant-Accepted Currencies, Allowed Payment Currencies
Definition
Accepted currencies are the cryptocurrencies a merchant has chosen to make available to payers for a specific payment service. They are a merchant-configured subset of all currencies supported by the provider. A currency can be technically supported but not accepted by that merchant, and acceptance can also depend on network, payment type, account settings, maintenance status, and current operational policy.
Overview
Meaning and scope
Accepted currencies are the cryptocurrencies a merchant has chosen to make available to payers for a specific payment service. They are a merchant-configured subset of all currencies supported by the provider. A currency can be technically supported but not accepted by that merchant, and acceptance can also depend on network, payment type, account settings, maintenance status, and current operational policy.
Mechanism and operation
Accepted Currencies define what a payer can select at checkout or through an API-created invoice. OxaPay exposes an authenticated endpoint that returns the currencies enabled for that merchant’s payment processing. A provider may support an asset across one or more networks, while the merchant accepts only a smaller list because of treasury, volatility, liquidity, accounting, or customer-demand considerations. Configuration can change, and a currency can be paused or removed. The resulting payment record should preserve the selected Pay Currency, network, and any conversion target. User interfaces should filter invalid combinations before presenting them.
Practical payment example
An online store accepts BTC and two stablecoins but only on specified chains. Its checkout lists eligible asset-network pairs, because accepting an asset name does not imply support for every issued representation.
Operational checks
A payer should not be allowed to choose an asset on a network the merchant or provider cannot process. Symbols alone are insufficient because tokens with the same symbol can exist on different networks. Unexpected changes can affect conversion exposure, customer experience, and reconciliation.
Distinctions and limits
They are merchant-facing configuration, not a complete description of provider capability. Acceptance should be checked when the payment session is created, not assumed from a cached website list. Reports should distinguish currencies offered to customers from currencies actually used, settled, or converted.
Related reading
Related definitions: Supported Currency, Pay Currency.
Example
An online store accepts BTC and two stablecoins but only on specified chains. Its checkout lists eligible asset-network pairs, because accepting an asset name does not imply support for every issued representation.
Comparison
Acceptance should be checked when the payment session is created, not assumed from a cached website list. A payer should not be allowed to choose an asset on a network the merchant or provider cannot process.
Key Takeaway
Accepted currencies are the merchant-enabled payment options, so they must be retrieved and validated separately from the provider's broader supported-currency list.
Sources
- OxaPay API Reference: Accepted Currencies — OxaPay (2026-08-02)
- OxaPay API Reference: Supported Currencies — OxaPay (2026-08-02)
- OxaPay API Reference: Generate Invoice — OxaPay (2026-08-02)