Choose Which Payment Methods Appear at Checkout

When a connected processor like Stripe supports many payment methods — cards, digital wallets, bank debits, buy-now-pay-later — you don't have to show all of them everywhere. You can control which methods appear on invoices, payment links, stores, funnels, forms, and subscriptions.

Where the toggle lives

1. Go to Payments > Integrations and click Manage next to your connected processor.
2. Select Manage Payment Methods.
3. You'll see the payment options available for each area of the platform — invoices, payment links, stores, forms, and subscriptions each have their own list.
4. Toggle individual methods on or off for each area, and repeat separately for Test and Live mode.

Subscriptions have their own dropdown, since recurring charges support a narrower set of methods than one-time payments. Some methods — Apple Pay, other digital wallets, and bank transfers — only become available after your account passes the processor's own verification for that method.

Typical defaults

Out of the box, most checkout areas show cards plus digital wallets (Apple Pay, Google Pay) and a couple of alternative methods. Invoices tend to support the widest range, since they're often used for larger, less time-sensitive payments — including bank debits and buy-now-pay-later options alongside cards.

If a method isn't showing up for a customer

Even when you've enabled a payment method on your end, the processor makes the final call on whether to display it to a specific shopper. That decision depends on things outside your control:

• The customer's location, IP address, and the transaction currency
• The order amount — some methods have minimum or maximum limits
• Regional availability and eligibility rules for that method

So if a customer reports a missing option, first confirm the method is actually toggled on for that checkout area. If it is, the most likely explanation is the processor itself decided not to offer it to that particular customer or transaction — that's normal behavior, not a bug. Your processor's own dashboard will usually show the eligibility requirements for any method that seems to be underperforming.