Skip to main content
POST
Send an own-wallet P2P transfer

Authorizations

Authorization
string
header
required

Access token issued by POST /v1/auth/token.

x-zeam-auth
string
header
required

Application secret (the apiKey issued at registration), validated at the Kong edge.

Body

application/json

Same-asset transfer between two of the caller's own wallets. Beneficiary fields are not accepted; use POST /v1/payments/p2p/beneficiary instead.

idempotencyKey
string
required

Unique key for safe retries. Replaying it returns the original result.

transactionId
string
required

Your own transaction identifier.

externalReference
string
required

Your own reference, echoed on the transaction record.

walletId
string<uuid>
required

Source wallet.

destinationWalletId
string<uuid>
required

Destination wallet in your own association.

sendingAssetCode
string
required

Asset to send — bare code (e.g. USDZ). The gateway resolves the issuer from the asset registry.

Example:

"USDZ"

amount
number
required

Amount to send

memo
string

Optional Stellar memo.

senderPhoneNumber
string

Optional sender phone number.

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.

transactionRecordId
string<uuid>
required

The transaction record id, used with GET /v1/transactions/{transactionId}.

status
string
required

Submission status; not a terminal transaction status.

Example:

"accepted"

intentId
string

Downstream intent id, when present.

isIdempotent
boolean

True when this response replays a prior submission with the same idempotencyKey.

message
string