Endpoint
Authentication
All requests must include a valid bearer token in theAuthorization header, or a pay3_session cookie obtained during wallet authentication.
Path parameters
string
required
The UUID of the transaction to approve. Obtain this from the
transactionId field in GET /api/approvals/pending.Request body
No request body is required.Response
Returns the updated transaction record after submission. The shape mirrors the objects returned by GET /api/transactions/:id.string
required
UUID of the transaction.
string
required
Updated transaction status. Will be
SUBMITTING immediately after approval while the Stellar network processes the payment, and will eventually transition to SUCCESS or FAILED.string
The Stellar transaction hash. Populated once the transaction reaches
SUCCESS. May be null if the network confirmation has not yet been received at the time the response is returned — poll GET /api/transactions/:id to retrieve the final hash.string
required
Always
TRANSFER for transactions that pass through the approval queue.string
required
Asset code transferred.
string
required
Transfer amount as a decimal string.
string
required
Destination Stellar G-address.
string
required
Always
PENDING_APPROVAL for transactions that went through the approval queue.string
ISO 8601 timestamp when the transaction reached
SUCCESS. null if network confirmation is still pending.Error responses
Example request
Example response
Example error response — expired approval
If
stellarTransactionHash is null in the response, the Stellar network confirmation is still pending. Retrieve the final state — including the hash once confirmed — via GET /api/transactions/:id.