Accepted Currencies

Overview

Accepted Currencies define what a payer can select at checkout or through an API-created invoice. They are merchant-facing configuration, not a complete description of provider capability. OxaPay exposes an authenticated endpoint that returns the currencies enabled for that merchant’s payment processing.

The concept differs from Supported Currency. 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. Supported does not automatically mean offered.

Acceptance should be checked when the payment session is created, not assumed from a cached website list. 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. 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.

Operational teams should version and monitor accepted-currency settings. Unexpected changes can affect conversion exposure, customer experience, and reconciliation. Reports should distinguish currencies offered to customers from currencies actually used, settled, or converted.

Merchants should define why each asset is accepted and what happens after receipt. A volatile coin may be accepted only with immediate conversion, while a stablecoin can be retained for settlement. The configuration should also state whether mixed payments, auto-withdrawal, and network-specific restrictions apply. Customer-facing options, treasury policy, and accounting treatment should be reviewed together.