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.
When route.required is true, an enabled Vault source can fund a cross-chain send; confirm the Payment with the returned managed authorization. A connected-wallet send still requires a direct transfer. Receive Payments do not need a preview.
See Sending payments.Authorizations
Headers
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 keep the same Payment ID end to end.
Response
Canonical Payment preview