Invoice Pay Currency
Pronunciation: IN-voys PAY KUR-un-see
Definition
Invoice pay currency is the specific currency or cryptocurrency the payer uses to settle an invoice. It can differ from the invoice denomination and merchant settlement currency. In crypto checkout, the field should identify both the asset and blockchain network because symbols such as USDT or USDC are operationally incomplete without a contract or native representation. The effective allowlist, network, precision, limits, quote source, and settlement route should be versioned with every payment request.
Overview
Invoice pay currency is the specific currency or cryptocurrency the payer uses to settle an invoice. It can differ from the invoice denomination and merchant settlement currency.
In crypto checkout, the field should identify both the asset and blockchain network because symbols such as USDT or USDC are operationally incomplete without a contract or native representation. The effective allowlist, network, precision, limits, quote source, and settlement route should be versioned with every payment request. The pay amount is derived from the invoice amount using a quote when currencies differ. Related operational concepts include invoice currency and Invoice Denomination. They should remain connected through identifiers and evidence without being treated as the same payment state, control, or financial result.
The payer can change currency before transaction submission, but the system should create a new quote and payment instruction. Automatic conversion can settle the merchant in another asset. The authoritative record for Invoice Pay Currency should also show the rule version, responsible system, permitted state transition, and any downstream action such as fulfillment, settlement, refund, or manual review.
Risks include wrong contract or network, stale quotes, transfer-tax tokens, insufficient liquidity, unsupported exchange withdrawals, and refunds in an unintended currency. Documenting those handoffs keeps duplicate events, delayed updates, and manual corrections for Invoice Pay Currency traceable to the correct object. Testing should cover duplicated and out-of-order events, incorrect asset or network data, late transactions, provider outages, retries after uncertain responses, and manual intervention after one subsystem has already changed state.
Teams should document the policy version, responsible service, approval limits, exception route, and reconciliation evidence for Invoice Pay Currency. In practical terms, invoice pay currency identifies how the payer transfers value and must include network, contract, quote, amount, fees, settlement, and refund treatment.
Key Takeaway
Invoice pay currency identifies how the payer transfers value and must include network, contract, quote, amount, fees, settlement, and refund treatment.
Sources
- ISO 4217 Currency Codes — ISO (2026-08-01)
- OxaPay API Reference: Accepted Currencies — OxaPay (2026-08-01)