OxaPay Merchant Service

Overview

OxaPay Merchant Service is the set of tools and APIs used by businesses to accept cryptocurrency payments through invoices, white-label payments, static addresses, and related integrations. Merchants create payment requests, receive tracking identifiers and instructions, monitor statuses, and reconcile received or converted funds.

The service covers payment acceptance, while payouts, wallet operations, swaps, and donation links can use separate OxaPay products and permissions. Related operational concepts include OxaPay Swap Service and OxaPay Payout Service. They should remain connected through identifiers and evidence without being treated as the same payment state, control, or financial result.

Implementations should link OxaPay Merchant Service to OxaPay Swap Service and OxaPay Payout Service through auditable references. Although the records can share a customer or transaction, OxaPay Merchant Service retains its own authority, lifecycle, and recovery rules. The authoritative record for OxaPay Merchant Service should also show the rule version, responsible system, permitted state transition, and any downstream action such as fulfillment, settlement, refund, or manual review.

Important risks include API-key compromise, incorrect callback handling, duplicate requests, unsupported currencies, premature fulfillment, and misunderstanding payment-status semantics. Operational procedures for OxaPay Merchant Service should cover duplicate requests, unavailable services, delayed status updates, mismatched currencies or networks, staff intervention, and customer disputes. 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.

Operational ownership for OxaPay Merchant Service should cover configuration changes, access, monitoring, customer treatment, accounting, and escalation. This supports the central requirement that oxaPay Merchant Service supports several acceptance models, each requiring secure API keys, accurate status handling, callbacks, order mapping, and reconciliation.