OxaPay API

Overview

The OxaPay API is OxaPay’s RESTful interface for integrating cryptocurrency payments, payouts, swaps, account data, and related operational workflows. OxaPay organizes API capabilities into payment, payout, swap, common, and error-related areas. Applications use service-specific API keys to call documented endpoints, exchange JSON data, and receive structured status, data, message, and error information. Creating an invoice or payout does not mean its financial outcome is complete. Observability for OxaPay API should record operation, version, principal, request ID, latency, retry count, error code, and final state without exposing secrets.

Developers should use the current OxaPay documentation, keep Merchant, Payout, and General API keys separated, validate all parameters, and store returned tracking identifiers. Payment and payout status should be reconciled through authoritative endpoints, while inbound webhooks require documented verification and idempotent processing. Network delays, confirmation requirements, callback delivery, validation errors, and ambiguous timeouts must be handled by the integrating application. For OxaPay API, the application should preserve a correlation path from request construction through response, asynchronous completion, and final business state. The OxaPay API owner should publish stable error semantics and guidance on whether correction, retry, status lookup, or escalation is appropriate.

Different operations use different credentials and lifecycle rules.

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

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

A successful transport result from OxaPay API should not be interpreted beyond the exact API state documented by the provider.