Requested Payment Currency
Pronunciation: ree-KWES-tid PAY-muhnt KUR-un-see
Definition
Requested Payment Currency is the fiat currency, coin, token, or unit in which the merchant expresses the amount due in the payment request. In a production payment system, the record should identify the relevant obligation, payer or customer context, asset, network, amount, authoritative identifiers, current status, and timestamps. Teams should validate inputs, preserve original evidence, prevent duplicate actions, and route ambiguous or unsafe cases to controlled review. The concept should not be interpreted from a wallet screenshot or provider message alone; it must be reconciled with blockchain observations and the merchant’s documented acceptance, fulfillment, refund, and accounting rules.
Overview
Requested Payment Currency is the fiat currency, coin, token, or unit in which the merchant expresses the amount due in the payment request. In a production payment system, the record should identify the relevant obligation, payer or customer context, asset, network, amount, authoritative identifiers, current status, and timestamps.
Teams should validate inputs, preserve original evidence, prevent duplicate actions, and route ambiguous or unsafe cases to controlled review. The concept should not be interpreted from a wallet screenshot or provider message alone; it must be reconciled with blockchain observations and the merchant’s documented acceptance, fulfillment, refund, and accounting rules. Related operational concepts include Received Payment Currency, Payment Amount Conversion, and Payment Quote. They should remain connected through identifiers and evidence without being treated as the same payment state, control, or financial result.
Its scope should be stated precisely because blockchain evidence, gateway status, merchant acceptance, fulfillment, settlement, and accounting can occur at different times. The implementation should define which system is authoritative for each decision, what evidence is required, and whether the result permits acceptance, fulfillment, settlement, refund, customer communication, or only further monitoring. Specific scope: the fiat currency, coin, token, or unit in which the in the payment request.
Teams should validate inputs, preserve original evidence, prevent duplicate actions, and route ambiguous or unsafe cases to controlled review. Clear boundaries reduce premature fulfillment, duplicate actions, unmatched funds, and inconsistent support responses. 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. Specific scope: the fiat currency, coin, token, or unit in which the in the payment request.
Governance should connect Requested Payment Currency to the original obligation, payment instructions, observed transaction, internal state, financial posting, and any fulfillment or refund. The decisive principle remains that requested Payment Currency should be governed by authoritative evidence, explicit rules, idempotent processing, and reconciliation before irreversible business action. Specific scope: the fiat currency, coin, token, or unit in which the in the payment request.
Key Takeaway
Requested Payment Currency should be handled according to the fact that the fiat currency, coin, token, or unit in which the merchant expresses the amount due in the payment request, with the corresponding validation and exception controls.
Sources
- Generate Invoice — OxaPay (2026-08-02)
- Accepted Currencies — OxaPay (2026-08-02)
- Payment Processing — Bitcoin Developer Guide (2026-08-02)