OxaPay Web3 Pay

Overview

OxaPay Web3 Pay is an invoice-payment feature that lets customers connect a compatible external wallet and approve a blockchain payment directly from the OxaPay invoice interface. It reduces manual address copying and QR scanning, but the wallet still signs an on-chain transaction whose asset, network, recipient, amount, fees, and execution result must be verified.

OxaPay’s current product description covers major EVM-compatible networks and selected non-EVM networks including Bitcoin, Solana, Tron, and Toncoin. Wallet compatibility does not mean every asset or network is available for every request. The choices shown on the specific crypto invoice remain authoritative, and the customer may need to switch networks or use a different wallet.

The payment flow normally starts with an active invoice and a current quote. After the customer connects a wallet, the interface prepares the appropriate transfer or contract call. The wallet displays the transaction for approval, broadcasts it, and returns control to the invoice page. A successful connection, signature, or transaction submission is not final payment; OxaPay must detect the transaction and update the invoice according to its payment-status rules.

Web3 Pay is distinct from Pay by OxaPay. Web3 Pay uses an external wallet and blockchain transaction, while Pay by OxaPay uses an eligible OxaPay wallet balance inside the platform. Merchants should keep these methods separate in analytics, support procedures, fee reporting, and failure recovery.

Material risks include wallet-connection phishing, malicious or misleading signing prompts, wrong-network selection, stale invoice data, unsupported tokens, duplicate submission, failed contract execution, and a frontend showing completion before the authoritative payment state. The customer must be able to review the exact recipient and economic effect before signing.

Merchant systems should retain the invoice and order identifiers, selected asset and network, wallet address where appropriate, quoted amount, transaction or user-operation reference, execution result, timestamps, fees, OxaPay status events, and any fallback instructions. Callbacks must be authenticated and processed idempotently, and fulfillment should follow the merchant’s documented acceptance policy rather than the browser return state alone.