Supported Currency

Overview

Supported Currency describes provider capability. OxaPay’s common-currencies endpoint returns asset symbols, names, status, network details, required confirmations, withdrawal fees, minimums, and static-address fee information.

The term differs from Accepted Currencies. A merchant can enable only a subset of the provider’s supported assets. Support also can vary by product, so an asset available for payout may not have identical invoice or static-address behavior.

Network context is essential. A stablecoin can be supported on several networks with different confirmation requirements and fees. Applications should retrieve the current network list and avoid matching an asset solely by its ticker.

Support can change during maintenance, risk review, or product updates. A cached configuration should have a refresh policy, and checkout creation should fail safely if the requested asset or network is no longer active.

Operational records should store the provider’s currency and network identifiers used at payment creation. This allows later reconciliation even if display names, aliases, fees, or confirmation settings change after the transaction.

A provider can expose the same asset through several supported networks, each with separate confirmation and fee settings.

Provider support should be interpreted as a structured capability matrix. An asset may be enabled for invoice payments, disabled for withdrawals, unavailable on one network, or subject to different minimums and confirmation thresholds. Applications should cache the matrix only briefly, handle temporary unavailability, and show users the exact combination currently accepted for the operation they are performing.

Operational monitoring should compare successful payment creation with the advertised capability matrix. A currency marked supported but failing repeatedly on one network should be treated as degraded until the provider confirms normal service.