OxaPay White Label API

Overview

The OxaPay White Label API lets merchants create a cryptocurrency payment experience integrated into their own interface while using OxaPay’s payment processing. Callback processing needs authentication, idempotency, and legal state transitions. White label changes presentation, not the asynchronous nature of blockchain payment. Implementations should keep the API key server-side, validate all session parameters, store OxaPay tracking identifiers, and protect the client from tampering. Observability for OxaPay White Label API should record operation, version, principal, request ID, latency, retry count, error code, and final state without exposing secrets. The OxaPay White Label API owner should publish stable error semantics and guidance on whether correction, retry, status lookup, or escalation is appropriate.

For OxaPay White Label API, metrics should separate transport success from business success. OxaPay’s Generate White Label endpoint is authenticated with a Merchant API Key and accepts payment-session details in JSON. It supports a merchant-controlled presentation flow while the provider returns the information needed to complete and track the payment. Authoritative payment information and reconciliation should resolve uncertain or missed events. The merchant remains responsible for accurate asset and network instructions, status handling, customer messaging, and deciding when confirmation is sufficient for fulfillment. For OxaPay White Label API, the application should preserve a correlation path from request construction through response, asynchronous completion, and final business state.

Data handled by OxaPay White Label API should use documented types, units, timestamp rules, nullable fields, and enum behavior to prevent silent interpretation errors.

The OxaPay White Label API contract should define identifiers, validation, authorization, status semantics, errors, limits, and version behavior at the same boundary.