Pay by OxaPay

Overview

Pay by OxaPay is an invoice-payment option that lets an authenticated OxaPay user settle an eligible invoice from available OxaPay wallet balance. The payer selects a supported balance and authorizes an internal platform payment associated with that invoice instead of broadcasting a separate transaction from an external blockchain wallet.

OxaPay currently states that this internal payment path does not charge the payer a blockchain network fee. It is therefore distinct from OxaPay Web3 Pay, where the customer connects an external wallet and submits an on-chain transaction. The two methods can appear on the same invoice but create different authorization, fee, and evidence records.

The payer must authenticate, choose an eligible currency balance, review the invoice amount, and confirm the payment. OxaPay then applies the internal transfer to the invoice and produces a service-side payment record. The merchant should rely on the authenticated invoice status rather than the payer’s confirmation screen or an unverified client-side message.

The underlying OxaPay Wallet is a platform account wallet. Availability can depend on the user’s balance, currency, account access, security settings, and current service configuration. An internal wallet balance should not be presented as proof that the payer directly controls an on-chain private key or that a public blockchain transfer occurred.

Operational risks include account takeover, insufficient or unavailable balance, wrong-currency selection, duplicate authorization, invoice-session mismatch, stale status, and fulfillment before the internal payment is finalized. Sensitive account sessions and credentials must remain outside merchant frontend code, screenshots, support chats, and ordinary logs.

Merchant records should preserve the invoice and order identifiers, payer authorization result, selected balance and currency, amount, fees, internal transaction reference, timestamps, final OxaPay status, and any refund or exception. Status events should be authenticated, handled idempotently, and reconciled with the merchant’s order and accounting records before irreversible delivery.