Payment Methods
Capability matrix of Admin API payment methods by flow type, express checkout, upsell, and subscription support, with links to each guide
Guides for creating Admin API orders with each supported payment method. The matrix below summarizes each method's flow type and capabilities — see the individual guide for request details and payment-specific data.
Capability matrix
| Payment Method | Flow | Express | Upsells | Subscriptions |
|---|---|---|---|---|
card_token | Direct & Redirect (3DS) | Yes | Yes | Yes |
apple_pay | Redirect | Yes | Yes | Yes |
google_pay | Redirect | Yes | Yes | Yes |
paypal | Redirect | Yes | Yes | Yes |
klarna | Redirect | No | Yes | Yes |
link | Redirect | Yes | Yes | Yes |
twint | Redirect | No | Yes | Yes |
swish | Redirect | No | No | No |
affirm | Redirect | No | No | No |
afterpay | Redirect | No | No | No |
bancontact | Redirect | No | No | No |
ideal | Redirect | No | No | No |
sepa_direct | Redirect | No | No | No |
Upsells (post-purchase, one-click) are added via ordersAddLineItemsCreate, which reuses the order's initial payment method to collect payment. This requires the payment method to support merchant-initiated charges — see each guide's Upsells section.
Redirect payment flow
Every method except direct card tokenization completes payment through a redirect flow:
Below is a high-level overview of the user flow when creating orders on the Admin API that utilize the payment method redirect flow.