Only authorize the purchase. This will not actually capture the payment.(default: false)
Coinflow Types *
Configuration for zero authorization flow. The presence of this object indicates the checkout is in zero auth mode.
Two mutually exclusive modes:
{ disableSavedPaymentMethods: boolean } - show or hide saved methods{ cardToken: "token" } - verify a specific saved cardIf true, pre-checks the partial USDC payment checkbox when USDC balance is available. If false or undefined, maintains default behavior (unchecked).
The DeviceID gotten from the Coinflow SDK: https://docs.coinflow.cash/guides/checkout/fraud-protection/chargeback-protection/implement-chargeback-protection#how-to-add-chargeback-protection
nSureSDK.getDeviceId()
If rendering the Coinflow component within multiple nested iframes, all ancestors in the chain must be provided as a comma-separated list.
Example: Primary origin that will be interacting with the Coinflow iFrame: foo.com Subsequent origins that will render foo.com: bar.com The origin array would then be: [https://foo.com,https://bar.com]
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.
(Solana only) if your transaction requires a known amount of Rent to be paid, you can pass it here.
(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.
3DS Card Authorization Data
On initial payment submission - Device3DSInfo needed: 3DS device information - required if 3DS is enabled
After card challenge complete: 3DS challenge transaction id - required after prompted for challenge
(Solana only) If a transaction involved in the purchase, should payment be checked for redemption
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.
(Optional) Idemptotency Key to pass to prevent multiple purchases with the same checkout link. If not passed, a random one will be generated for you automatically.
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
The API key of the merchant - 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