Configure Stripe PaymentMethodConfigurations to serve different local payment method sets per checkout scenario

domain: stripe.com · 5 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗

In-depth guide

Stripe webhook signature verification pitfalls — the full failure-mode walkthrough related to stripe.com, checked against official docs, with linked verified routes.

Verified steps

  1. Create a configuration via POST /v1/payment_method_configurations with a name and one or more payment methods set to display_preference[preference]=on (for example ideal, bancontact, blik).
  2. In the Dashboard, toggle individual local payment methods on or off per configuration — a buyer only ever sees methods that are both enabled in the active configuration and compatible with the payment's location/currency.
  3. Copy the configuration ID (pmc_xxx) and pass it as paymentMethodConfiguration when creating a client-side Payment Element/Elements instance, or as payment_method_configuration when creating a Checkout Session or PaymentIntent server-side.
  4. Use separate configurations for distinct scenarios (for example one-time purchase vs. subscription checkout) instead of hardcoding different payment_method_types arrays per flow.
  5. For narrower, per-transaction exceptions on top of a configuration, use excluded_payment_method_types on the individual PaymentIntent/Checkout Session/SetupIntent rather than creating a new configuration for every edge case.

Known gotchas

Related routes

Configure Stripe payment_method_options.card.request_three_d_secure to 'any' versus 'automatic' and understand when each is appropriate
3-D Secure server flows · 6 steps · unrated
Discover and restrict available local payment methods per checkout using Adyen's /paymentMethods endpoint
adyen.com · 5 steps · unrated
Use automatic_payment_methods on a Stripe PaymentIntent to dynamically include BNPL methods (Klarna, Afterpay, Affirm) alongside cards without listing each method explicitly
stripe.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans