Preview a send payment
Resolve the fee, funding options and next action for a send Payment without creating it.
intent: send). It resolves the sender, destination, fee, available funding options and next action without creating a Payment. For a crypto send, proceed only when the selected payment source is available.
An enabled Vault source can fund a deposit-address Routing order when route.required is true; confirm that Payment with its returned managed authorization. A connected-wallet send still requires a direct transfer. Receive Payments do not need a preview.
See Sending payments.Authorizations
HTTP Basic auth. Username is the Stableyard app ID. Password is the app secret. The optional Stableyard-Version request header must match the environment pin.
Headers
Optional contract-version assertion. Omit it to use the app environment's pinned version. A different supported version is accepted only after that environment is explicitly migrated.
2026-09-09 Body
Move funds from an existing UPA payment source to another UPA, payment handle, or external crypto wallet. Crypto Send supports direct transfers and, when enabled, Vault-funded cross-chain or cross-token Routing. The paymentAmount identifies the exact destination asset and amount. Commercial fees are calculated on the quoted source input and added on top; sourceAmount shows the total sender debit. Routing uses exact_output and does not reduce the authorized destination amount for slippage. Preview first and stop when the selected source is unavailable. Routed Vault sends retain the same canonical Payment ID through source funding, destination verification and refund recovery; the routing deposit address is an internal execution detail.
"send"Identify a UPA using either its Stableyard account ID or your own external user ID.
- Stableyard account ID
- External user ID
Send to another UPA, a payment handle, or an external crypto wallet. External QR and bank rails use their dedicated request variants below.
- UPA account
- Payment handle
- External crypto wallet
Recommended for business integrations. For example, 10.00 USDC.
- Decimal amount
- Atomic amount
"deliver_exact"Optional active Vault mandate authorizing this outgoing occurrence. A mandate constrains Vault spending; it does not schedule recurring Payments.
1 - 64"vault_mandate_123"
1 - 5001 - 25660 <= x <= 86400Response
Canonical Payment preview
Total sender debit in the source asset, including commercial fees added to the required routing input. Null when the route is unavailable and the source input cannot be quoted.
- UPA account
- Payment handle
- External crypto wallet
- External merchant QR
- External bank beneficiary
- Verified linked bank account