OxaPay Payout API

Overview

The OxaPay Payout API lets authorized applications generate cryptocurrency payouts and retrieve their status, details, and history programmatically. A generate request sends supported payout details such as destination, currency, network, and amount, while the returned track_id identifies the payout for later information and status retrieval. OxaPay’s payout service uses a Payout API Key for authentication. Applications should restrict payout credentials, use approval and destination controls, assign stable internal references, and reconcile uncertain requests before resubmission. A payout can remain processing, fail validation, wait on operational conditions, or later receive a transaction hash. They should validate network and memo requirements, monitor documented status, record fees and transaction hashes, and maintain an auditable exception process. Retrying after a timeout without checking the original result can create an unintended duplicate transfer. The OxaPay Payout API contract should define identifiers, validation, authorization, status semantics, errors, limits, and version behavior at the same boundary. Observability for OxaPay Payout API should record operation, version, principal, request ID, latency, retry count, error code, and final state without exposing secrets. Data handled by OxaPay Payout API should use documented types, units, timestamp rules, nullable fields, and enum behavior to prevent silent interpretation errors.

Request acceptance does not equal final blockchain settlement.

Testing OxaPay Payout API should cover malformed input, denied access, rate limits, timeouts, duplicates, asynchronous completion, and version changes.

The OxaPay Payout API owner should publish stable error semantics and guidance on whether correction, retry, status lookup, or escalation is appropriate.

For OxaPay Payout API, the application should preserve a correlation path from request construction through response, asynchronous completion, and final business state.