A payment method is missing from the Stripe Payment Element, or the call to exclude it fails
The Payment Element shows only card, although other payment methods are enabledShort answer
With automatic payment methods, Stripe decides which methods the Payment Element shows. A method disappears when it is off in the Dashboard, when your code still hard-codes payment_method_types, or when the currency, amount, customer country or flags such as setup_future_usage rule it out. Retrieve the PaymentIntent and read its payment_method_types field first.
Fix it fast
1Find out which cause you have
Retrieve the PaymentIntent that the page uses and read payment_method_types. The Payment Element can only show the methods in that list, so the list tells you whether the problem is on the server or in the front end.
curl https://api.stripe.com/v1/payment_intents/pi_XXXXXXXX \ -u "$STRIPE_SECRET_KEY:"2Match what you see, then jump to its fix
- 1
payment_method_types in the PaymentIntent does not contain the method you expectThe payment method is not turned on in the DashboardFix - 2
The PaymentIntent lists exactly the methods hard-coded in your server codeThe server still passes a fixed payment_method_types listFix - 3
The method is enabled, and it appears for some orders and customers and not for othersThe currency, amount or customer country rules the method outFix - 4
The method shows up once you remove setup_future_usage or capture_method from the creation callsetup_future_usage or manual capture filters the method outFix - 5
The create call fails after you add excluded_payment_method_types with one of those three valuesapple_pay, google_pay or link was excluded with the wrong parameterFix
- 1
What does the error look like?
The Payment Element shows only card, although other payment methods are enabledExcluding apple_pay, google_pay or link with excluded_payment_method_types returns an error
Cause 1 of 5
The payment method is not turned on in the Dashboard
1Check
Only methods you enabled in the Dashboard can be shown to customers. With Connect direct charges or on_behalf_of, the settings of the connected account decide instead.
curl https://api.stripe.com/v1/payment_intents/pi_XXXXXXXX -u "$STRIPE_SECRET_KEY:" | grep -A4 payment_method_types2Fix
Turn the method on there. If it is not listed at all, it is not supported in the country your Stripe account is registered in.
# Dashboard > Settings > Payment methods > turn the method on3Verify
Create a new PaymentIntent and read payment_method_types again.
curl https://api.stripe.com/v1/payment_intents \
-u "$STRIPE_SECRET_KEY:" \
-d amount=2000 \
-d currency=usd \
-d "automatic_payment_methods[enabled]=true"Confirmed by docs.stripe.com
Cause 2 of 5
The server still passes a fixed payment_method_types list
1Check
Stripe's guide says that to manage payment methods from the Dashboard you remove payment_method_types from your integration code. A list written in code keeps the methods fixed. Search the server for it.
grep -rn "payment_method_types" server src2Fix
To manage methods from the Dashboard, remove payment_method_types from the code. If your account uses an API version older than 2023-08-16, send automatic_payment_methods[enabled]=true instead.
curl https://api.stripe.com/v1/payment_intents \
-u "$STRIPE_SECRET_KEY:" \
-d amount=1099 \
-d currency=eur \
-d "automatic_payment_methods[enabled]=true"3Verify
Retrieve the new PaymentIntent. Its payment_method_types now follows the Dashboard.
curl https://api.stripe.com/v1/payment_intents/pi_XXXXXXXX -u "$STRIPE_SECRET_KEY:"Confirmed by docs.stripe.com
Cause 3 of 5
The currency, amount or customer country rules the method out
1Check
Each method supports certain currencies and countries, and some have their own minimum and maximum. The final amount, with tax and discounts, is the one that counts. ACH Direct Debit needs USD, SEPA Direct Debit is only offered below 10,000 EUR, and BLIK is for customers in Poland.
curl https://api.stripe.com/v1/payment_intents/pi_XXXXXXXX -u "$STRIPE_SECRET_KEY:" | grep -E "amount|currency"2Fix
Create the PaymentIntent in a currency the method supports, check the amount against its limits, and test with a customer in a supported country.
curl https://api.stripe.com/v1/payment_intents \
-u "$STRIPE_SECRET_KEY:" \
-d amount=2000 \
-d currency=usd \
-d "automatic_payment_methods[enabled]=true"3Verify
Read payment_method_types on the new PaymentIntent.
curl https://api.stripe.com/v1/payment_intents/pi_XXXXXXXX -u "$STRIPE_SECRET_KEY:"Confirmed by docs.stripe.com
Cause 4 of 5
setup_future_usage or manual capture filters the method out
1Check
Some methods cannot be set up for future use, and some do not support manual capture. Stripe removes them automatically when you set those parameters.
grep -rn "setup_future_usage\|capture_method" server src2Fix
Drop the parameter if you do not need it, or accept that the method is unavailable for that flow.
curl https://api.stripe.com/v1/payment_intents \
-u "$STRIPE_SECRET_KEY:" \
-d amount=2000 \
-d currency=usd \
-d "automatic_payment_methods[enabled]=true"3Verify
Create a PaymentIntent without the parameter and compare payment_method_types.
curl https://api.stripe.com/v1/payment_intents/pi_XXXXXXXX -u "$STRIPE_SECRET_KEY:"Confirmed by docs.stripe.com
Cause 5 of 5
apple_pay, google_pay or link was excluded with the wrong parameter
1Check
excluded_payment_method_types removes methods for one PaymentIntent. Stripe's guide says that excluding apple_pay, google_pay or link this way generates an error, because wallets have their own switch in the Payment Element.
grep -rn "excluded_payment_method_types" server src2Fix
Remove those three values from the exclusion list. Turn wallets off with the wallets option of the Payment Element on the front end instead.
curl https://api.stripe.com/v1/payment_intents \
-u "$STRIPE_SECRET_KEY:" \
-d amount=1000 \
-d currency=usd \
-d "automatic_payment_methods[enabled]=true" \
-d "excluded_payment_method_types[]=affirm"3Verify
The call returns a PaymentIntent with the remaining methods.
curl https://api.stripe.com/v1/payment_intents/pi_XXXXXXXX -u "$STRIPE_SECRET_KEY:"Confirmed by docs.stripe.com
How do I stop it coming back?
- Manage payment methods in the Dashboard and keep payment_method_types out of the code, unless a flow truly needs a fixed list.
- Log payment_method_types from each created PaymentIntent, so a missing method is visible in your own logs.
- Test with the currency, amount and country of a real customer, not only with a default test order.
- Check the Dashboard payment methods page after every account or country change.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Payments
Stripe Elements shows console warnings or errors in a Next.js checkout
Could not find Elements context; You need to wrap the part of your app that calls useElements() in an <Elements> provider.
Most React Stripe.js warnings come from four mistakes: calling loadStripe inside a component, using useStripe or useElements outside the Elements provider, using the objects before they have loaded, and a Content Security Policy that blocks js.stripe.com.
4 causes, each with a fixPayments
firebase deploy fails because the Stripe client has no API key
Neither apiKey nor config.authenticator provided
The Stripe client is built from a key that is empty at that moment.
3 causes, each with a fixPayments
Metadata you set on a Stripe Checkout Session is empty when you read it
event.data.object.metadata.order_id is None in the webhook handler
Stripe does not copy metadata between objects on its own.
3 causes, each with a fixPayments
Stripe says No such checkout.session when you retrieve a session
resource_missing
A resource_missing error means the ID is not visible to the key you used.
3 causes, each with a fixPayments
Stripe says there is no such token when your server uses it
livemode_mismatch
Stripe answers with a missing-resource error when the ID you send does not exist for the key you use.
3 causes, each with a fixPayments
A Stripe webhook to a Vercel function fails with a 308 redirect
HTTP/2 308
Stripe treats every redirect from a webhook URL as a failure and does not follow it.
3 causes, each with a fix