OxaPay Swap Service

Overview

OxaPay Swap Service lets users or businesses exchange supported cryptocurrency assets through the OxaPay dashboard or API. The service uses available balances and a quoted conversion to move value from a source currency into a destination currency. A swap differs from payment settlement, payout, or blockchain bridge transfer and can have its own rate, fee, liquidity, and completion states. When implementing OxaPay Swap Service alongside Pay by OxaPay, current capabilities and request parameters should be verified against the relevant OxaPay documentation and preserved with each resulting transaction.

OxaPay’s current Swap Service uses a General API key. Applications can query supported swap pairs and minimums, calculate amounts and rates, submit a swap from one account currency to another, and retrieve swap history. The quoted or calculated result should be linked to the executed swap because supported pairs, minimums, and market rates can change.

Important risks include stale quotes, wrong currency selection, insufficient balance, slippage or spread, duplicate requests, provider outage, and accounting that hides conversion results.

Systems should store source and destination currencies, amounts, quote, rate, fee, request ID, execution status, resulting balances, and accounting entries.

The workflow for OxaPay Swap Service commonly touches OxaPay Payout Service and Pay by OxaPay. Documenting those handoffs keeps duplicate events, delayed updates, and manual corrections for OxaPay Swap Service traceable to the correct object.

Operational procedures for OxaPay Swap Service should cover duplicate requests, unavailable services, delayed status updates, mismatched currencies or networks, staff intervention, and customer disputes. When OxaPay Swap Service interacts with OxaPay Payout Service, current capabilities and parameters should be checked against the relevant OxaPay documentation because supported options and service configuration can change.

Use of OxaPay Swap Service should preserve the relevant OxaPay service context, tracking or request identifier, merchant-side order or account reference, effective configuration, timestamps, fees, and resulting balance or transaction evidence. When OxaPay Swap Service interacts with OxaPay Payout Service, the merchant should process OxaPay callbacks or API responses idempotently and reconcile them with its own commercial and accounting records.