Stripe Checkout Sessions restrict card funding types

Introduced 2026-08-26 · score 0.96

HOW TO USE IT

When creating a Checkout Session, set `payment_method_options.card.restrictions.funding_types_blocked` to block specified card types; Stripe says a customer attempting to use a restricted type sees an error.

curl https://api.stripe.com/v1/checkout/sessions \
  -u "<secret_key>:" \
  -H "Stripe-Version: 2026-08-26.dahlia" \
  --data-urlencode success_url="<success_url>" \
  -d "line_items[0][price]"="<price_id>" \
  -d "line_items[0][quantity]"=1 \
  -d mode=payment \
  -d "payment_method_options[card][restrictions][funding_types_blocked][]"=prepaid

WHY THIS HELPS

When implementing checkout payment restrictions, configure a Checkout Session to block specified card funding types.

REQUIREMENTS AND LIMITATIONS

payment_method_options[card][restrictions][funding_types_blocked]: List of card funding types to block: `credit`, `debit`, and/or `prepaid`. The release note documents the setting and allowed values; create-session request example documents the other required fields shown.
mode (required): Checkout Session mode; `payment` accepts one-time payments.
line_items (required): List of items being purchased; required for `payment` and `subscription` mode.
success_url: Redirect URL after payment or setup; required for embedded or custom UI mode when redirect-based payment methods are enabled, and disallowed for those UI modes.
Prerequisite: To use this parameter, requests must use API version `2026-08-26.dahlia` (or the corresponding SDK/API version upgrade); the Stripe changelog says to set the `Stripe-Version` header for REST requests.
Applies to Checkout Sessions.
Restricted card funding types cause the Checkout Session to show an error.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card

Tools change faster than your agent’s training data.

Changes

Stripe Checkout Sessions restrict card funding types