US Wire Domestic Payments Checkout (Saved Account)
Initiates a US Domestic Wire Payments payment order with a saved account. Returns destination account info. Must be paid before the returned expiration date (5 minutes).
Authentication
The session key generated for the end user - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-key
The web3 wallet of the end user - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-key
The blockchain associated with the end user - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-key
The external identifier of the end user - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-key
The API key of the merchant - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-key
Request
If this purchase is for a seller/submerchant where the marketplace takes a fee, this is the % fee which is taken from the subtotal amount.
(EVM only) if you want to execute an EVM transaction on a successful purchase, you can pass a transaction request here.
Gas fees for the transaction will be automatically calculated and added to the total charged to the customer. Optionally the merchant can opt to pay for these gas fees.
(Stellar only) Base64 XDR transaction string for executing a merchant contract call on a successful purchase.
For transaction purchases, pass the base64 XDR string created using .toXDR() on a transaction
built with generated TypeScript bindings (e.g., NftClientWrapper.buildNftPurchaseTx).
For direct USDC transfers (no merchant transaction), omit this field or pass undefined.
Gas fees for the transaction will be automatically calculated and added to the total charged to the customer.
Customer signed USDC transferWithAuthorization data for dual-source payments Used for combined USDC + Credit Card payments on EVM chains
V2 of CustomerUsdcTransferData — replaces the (v, r, s) triple with a single
signature bytes string, matching USDC FiatTokenV2_2's bytes-overload
transferWithAuthorization. All other fields unchanged from V1.
End-user geographic coordinates captured at the moment of the withdrawal
request. Consumed by BlockingRuleMethod.GEOLOCATION enforcement.
Replay-of-different-coords bypass is prevented server-side: the first resolved {country, state} for a given (merchant, user) pair is pinned in Redis, and subsequent requests are evaluated against that pinned value regardless of the lat/lng they submit.