The Payment methods section is required. Pass paymentMethods as a list of method names in the render order you want.
Enable methods
Supported names:
'card'
'bank'
'applePay'
'googlePay'
Render order
The array order controls render order. Methods that fail a runtime check (a wallet on http://, a wallet unavailable on the device, a misconfigured merchant) are hidden without shifting siblings.
Default selection
The first available method is selected on mount unless you set defaultPaymentMethod:
If the default is not available at runtime, the first available method wins.
Per-method options
Configure a method using its top-level key on the Checkout options. The options match the standalone element’s options.
See:
Submitted value
onSubmit carries the authorize-ready payload under the matching key. Each shape:
value.card: encrypted card envelope — encryptedCardNumber, encryptedExpiryMonth, encryptedExpiryYear, encryptedSecurityCode (empty string when hidden), plus riskData and browserInfo. Optional holderName / postalCode when configured.
value.bank: discriminated union { mode: 'manual', manual: { … } } | { mode: 'plaid', plaid: { … } }.
value.applePay / value.googlePay: { walletToken, walletType: 'applePay' | 'googlePay', … }.
Forward value to your server. See the authorize a payment API reference for the authorize request shape.
See also
Last modified on July 29, 2026