Send a cross-asset swap between own wallets
Cross-asset variant of POST /v1/payments/p2p/own: identical body plus a required receivingAssetCode that must differ from sendingAssetCode. Executed as a strict-send Stellar path payment — amount is denominated in sendingAssetCode and the received amount depends on the live rate at execution time. The destination may be the same wallet (a self-swap). Returns 202.
Authorizations
Access token issued by POST /v1/auth/token.
Application secret (the apiKey issued at registration), validated at the Kong edge.
Body
Same-asset transfer between two of the caller's own wallets. Beneficiary fields are not accepted; use POST /v1/payments/p2p/beneficiary instead.
Unique key for safe retries. Replaying it returns the original result.
Your own transaction identifier.
Your own reference, echoed on the transaction record.
Source wallet.
Destination wallet in your own association.
Asset to send — bare code (e.g. USDZ). The gateway resolves the issuer from the asset registry.
"USDZ"
Amount to send
Asset to receive — bare code. Must differ from sendingAssetCode.
"ZARC"
Optional Stellar memo.
Optional sender phone number.
Response
Swap accepted for asynchronous processing.
A 202 means the submission was accepted for asynchronous execution, not that it settled. Track completion with the Transactions routes or webhooks.
The transaction record id, used with GET /v1/transactions/{transactionId}.
Submission status; not a terminal transaction status.
"accepted"
Downstream intent id, when present.
True when this response replays a prior submission with the same idempotencyKey.