Send an own-wallet P2P transfer
Sends a same-asset transfer between two of your own wallets, executed asynchronously as a Stellar payment. The recipient receives exactly amount; no fee is charged. A 202 means queued, not settled. Replaying the same transactionId returns the original result with isIdempotent: true.
Authorizations
Access token issued by POST /v1/auth/token.
Application secret (the apiKey issued at registration), required on every request.
Body
Same-asset transfer between two of the caller's own wallets. Beneficiary fields are not accepted; use POST /v1/payments/p2p/beneficiary instead. transactionId is the only identity field — it is the idempotency key and the reference recorded on the transaction.
Your transaction id. Replaying it returns the original result.
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, denominated in sendingAssetCode.
Optional Stellar memo.
Optional sender-side transaction reference, shown on the sender's statement. When supplied: 1-16 characters, letters, digits, and hyphens only. Omit it or send null for no reference.
16^[A-Za-z0-9-]{1,16}$Optional recipient-side transaction reference, shown on the recipient's statement (for withdrawals it is also printed on their bank or mobile-money statement). When supplied: 1-16 characters, letters, digits, and hyphens only. Omit it or send null for no reference.
16^[A-Za-z0-9-]{1,16}$Response
Payment 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"
Execution intent id, when present.
True when this response replays a prior submission with the same transactionId.