Payment URI
Pronunciation: PAY-ment YOU-AR-EYE
Definition
A payment URI is a standardized or application-specific link that encodes payment details so a compatible wallet or application can prepare a transaction. It can include scheme, recipient, amount, asset, network, label, memo, invoice, and callback or request references. The URI prepares a payment but does not prove the payer reviewed, signed, broadcast, or settled the transaction. Payment URI records should preserve pricing, authorization, transaction evidence, confirmations, fees, settlement, and any exception or refund as separate states.
Overview
A payment URI is a standardized or application-specific link that encodes payment details so a compatible wallet or application can prepare a transaction. It can include scheme, recipient, amount, asset, network, label, memo, invoice, and callback or request references. The URI prepares a payment but does not prove the payer reviewed, signed, broadcast, or settled the transaction. For teams linking Payment URI to Token URI, the payment record should preserve pricing, authorization, transaction evidence, confirmations, fees, settlement, and any exception or refund as separate states.
Important risks include malicious recipient substitution, unsupported schemes, ambiguous networks, unsafe query parameters, encoding errors, stale amounts, and wallet interpretation differences.
Applications should validate scheme and fields, show decoded details before authorization, preserve the original URI, bind it to the payment request, and verify settlement.
The workflow for Payment URI commonly touches Token URI and Bitcoin URI (BIP21). Documenting those handoffs keeps duplicate events, delayed updates, and manual corrections for Payment URI traceable to the correct object.
For Payment URI, risk controls should be proportional to payment value and reversibility. When Payment URI interacts with Token URI, useful controls include allowlisted assets and networks, server-generated instructions, authenticated callbacks, independent transaction monitoring, confirmation or finality thresholds, duplicate detection, rate expiry, exception queues, and reviewed manual decisions. In the relationship between Payment URI and Bitcoin URI (BIP21), merchant fulfillment policy should specify exactly which verified state permits delivery or account credit.
A reliable implementation of Payment URI separates intent, authorization, network or provider processing, confirmation, settlement, and accounting. When Payment URI interacts with Token URI, a submitted transaction or customer-facing success message is only an intermediate signal until the expected asset, network, amount, recipient, execution result, and finality policy have been verified. In the relationship between Payment URI and Bitcoin URI (BIP21), the commercial order should advance through idempotent state transitions tied to durable external identifiers.
Key Takeaway
Payment URIs improve wallet handoff but require secure decoding, exact recipient and network review, expiry handling, and independent transaction verification.
Sources
- OxaPay API Reference: Payment — OxaPay (2026-08-01)
- Bitcoin Developer Guide: Payment Processing — Bitcoin.org (2026-08-01)
- FATF Guidance on Virtual Assets — FATF (2026-08-01)