# Create a Checkout Session ## Prerequisites Before you can run the following code snippet, you need to call these APIs with the provided parameters to set up the prerequisite API object(s). 1. createPrice POST /v1/prices {"currency":"usd","unit_amount":1000,"recurring":{"interval":"month"},"product_data":{"name":"Gold Plan"}} ## Request ```curl curl https://api.stripe.com/v1/checkout/sessions \ -u "<>" \ -H "Stripe-Version: 2026-10-28.endive" \ --data-urlencode "success_url=https://example.com/success" \ -d "line_items[0][price]={{PRICE_ID}}" \ -d "line_items[0][quantity]=2" \ -d mode=payment ``` ### Response ```json { "id": "cs_test_a11YYufWQzNY63zpQ6QSNRQhkUpVph4WRmzW0zWJO2znZKdVujZ0N0S22u", "object": "checkout.session", "after_expiration": null, "allow_promotion_codes": null, "amount_subtotal": 2198, "amount_total": 2198, "automatic_tax": { "enabled": false, "liability": null, "status": null }, "billing_address_collection": null, "cancel_url": null, "client_reference_id": null, "consent": null, "consent_collection": null, "created": 1679600215, "currency": "usd", "custom_fields": [], "custom_text": { "shipping_address": null, "submit": null }, "customer": null, "customer_creation": "if_required", "customer_details": null, "customer_email": null, "expires_at": 1679686615, "invoice": null, "invoice_creation": { "enabled": false, "invoice_data": { "account_tax_ids": null, "custom_fields": null, "description": null, "footer": null, "issuer": null, "metadata": {}, "rendering_options": null } }, "livemode": false, "locale": null, "metadata": {}, "mode": "payment", "payment_intent": null, "payment_link": null, "payment_method_collection": "always", "payment_method_options": {}, "payment_method_types": [ "card" ], "payment_status": "unpaid", "phone_number_collection": { "enabled": false }, "recovered_from": null, "setup_intent": null, "shipping_address_collection": null, "shipping_cost": null, "shipping_details": null, "shipping_options": [], "status": "open", "submit_type": null, "subscription": null, "success_url": "https://example.com/success", "total_details": { "amount_discount": 0, "amount_shipping": 0, "amount_tax": 0 }, "return_url": null, "ui_mode": "hosted_page", "url": "https://checkout.stripe.com/c/pay/cs_test_a11YYufWQzNY63zpQ6QSNRQhkUpVph4WRmzW0zWJO2znZKdVujZ0N0S22u#fidkdWxOYHwnPyd1blpxYHZxWjA0SDdPUW5JbmFMck1wMmx9N2BLZjFEfGRUNWhqTmJ%2FM2F8bUA2SDRySkFdUV81T1BSV0YxcWJcTUJcYW5rSzN3dzBLPUE0TzRKTTxzNFBjPWZEX1NKSkxpNTVjRjN8VHE0YicpJ2N3amhWYHdzYHcnP3F3cGApJ2lkfGpwcVF8dWAnPyd2bGtiaWBabHFgaCcpJ2BrZGdpYFVpZGZgbWppYWB3dic%2FcXdwYHgl" } ``` - `payment_method_options` (object, optional) Payment-method-specific configuration. - `payment_method_options.acss_debit` (object, optional) contains details about the ACSS Debit payment method options. You can’t set this parameter if `ui_mode` is `elements`. - `payment_method_options.acss_debit.currency` (enum, optional) Three-letter [ISO currency code](https://www.iso.org/iso-4217-currency-codes.html), in lowercase. Must be a [supported currency](https://docs.stripe.com/currencies.md). This is only accepted for Checkout Sessions in `setup` mode. Possible enum values: - `cad` Canadian dollars - `usd` US dollars - `payment_method_options.acss_debit.mandate_options` (object, optional) Additional fields for Mandate creation - `payment_method_options.acss_debit.mandate_options.custom_mandate_url` (string, optional) A URL for custom mandate text to render during confirmation step. The URL will be rendered with additional GET parameters `payment_intent` and `payment_intent_client_secret` when confirming a Payment Intent, or `setup_intent` and `setup_intent_client_secret` when confirming a Setup Intent. - `payment_method_options.acss_debit.mandate_options.default_for` (array of enums, optional) List of Stripe products where this mandate can be selected automatically. Only usable in `setup` mode. Possible enum values: - `invoice` Enables payments for Stripe Invoices. ‘subscription’ must also be provided. - `subscription` Enables payments for Stripe Subscriptions. ‘invoice’ must also be provided. - `payment_method_options.acss_debit.mandate_options.interval_description` (string, optional) Description of the mandate interval. Only required if ‘payment_schedule’ parameter is ‘interval’ or ‘combined’. The maximum length is 500 characters. - `payment_method_options.acss_debit.mandate_options.payment_schedule` (enum, optional) Payment schedule for the mandate. Possible enum values: - `combined` Payments can be initiated at a pre-defined interval or sporadically - `interval` Payments are initiated at a regular pre-defined interval - `sporadic` Payments are initiated sporadically - `payment_method_options.acss_debit.mandate_options.transaction_type` (enum, optional) Transaction type of the mandate. Possible enum values: - `business` Transactions are made for business reasons - `personal` Transactions are made for personal reasons - `payment_method_options.acss_debit.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `on_session` Use `on_session` if you intend to only reuse the payment method when your customer is present in your checkout flow. - `payment_method_options.acss_debit.target_date` (string, optional) Controls when Stripe will attempt to debit the funds from the customer’s account. The date must be a string in YYYY-MM-DD format. The date must be in the future and between 3 and 15 calendar days from now. - `payment_method_options.acss_debit.verification_method` (enum, optional) Verification method for the intent Possible enum values: - `automatic` Instant verification with fallback to microdeposits. - `instant` Instant verification. - `microdeposits` Verification using microdeposits. - `payment_method_options.affirm` (object, optional) contains details about the Affirm payment method options. - `payment_method_options.affirm.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.affirm.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.afterpay_clearpay` (object, optional) contains details about the Afterpay Clearpay payment method options. - `payment_method_options.afterpay_clearpay.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.afterpay_clearpay.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.alipay` (object, optional) contains details about the Alipay payment method options. - `payment_method_options.alipay.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.alma` (object, optional) contains details about the Alma payment method options. - `payment_method_options.alma.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.amazon_pay` (object, optional) contains details about the AmazonPay payment method options. - `payment_method_options.amazon_pay.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.amazon_pay.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `payment_method_options.au_becs_debit` (object, optional) contains details about the AU Becs Debit payment method options. - `payment_method_options.au_becs_debit.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.au_becs_debit.target_date` (string, optional) Controls when Stripe will attempt to debit the funds from the customer’s account. The date must be a string in YYYY-MM-DD format. The date must be in the future and between 3 and 15 calendar days from now. - `payment_method_options.bacs_debit` (object, optional) contains details about the Bacs Debit payment method options. - `payment_method_options.bacs_debit.mandate_options` (object, optional) Additional fields for Mandate creation - `payment_method_options.bacs_debit.mandate_options.reference_prefix` (string, optional) Prefix used to generate the Mandate reference. Must be at most 12 characters long. Must consist of only uppercase letters, numbers, spaces, or the following special characters: ‘/’, ‘_’, ‘-’, ‘&’, ‘.’. Cannot begin with ‘DDIC’ or ‘STRIPE’. The maximum length is 12 characters. - `payment_method_options.bacs_debit.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `on_session` Use `on_session` if you intend to only reuse the payment method when your customer is present in your checkout flow. - `payment_method_options.bacs_debit.target_date` (string, optional) Controls when Stripe will attempt to debit the funds from the customer’s account. The date must be a string in YYYY-MM-DD format. The date must be in the future and between 3 and 15 calendar days from now. - `payment_method_options.bancontact` (object, optional) contains details about the Bancontact payment method options. - `payment_method_options.bancontact.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `payment_method_options.billie` (object, optional) contains details about the Billie payment method options. - `payment_method_options.billie.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.blik` (object, optional) contains details about the BLIK payment method options. - `payment_method_options.blik.mandate_options` (object, optional) Additional fields for Mandate creation - `payment_method_options.blik.mandate_options.expires_at` (timestamp, optional) Date when the mandate expires and no further payments will be charged. If not provided, the mandate will be set to be indefinite. - `payment_method_options.boleto` (object, optional) contains details about the Boleto payment method options. - `payment_method_options.boleto.expires_after_days` (integer, optional) The number of calendar days before a Boleto voucher expires. For example, if you create a Boleto voucher on Monday and you set expires_after_days to 2, the Boleto invoice will expire on Wednesday at 23:59 America/Sao_Paulo time. - `payment_method_options.boleto.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `on_session` Use `on_session` if you intend to only reuse the payment method when your customer is present in your checkout flow. - `payment_method_options.card` (object, optional) contains details about the Card payment method options. - `payment_method_options.card.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.card.installments` (object, optional) Installment options for card payments - `payment_method_options.card.installments.enabled` (boolean, optional) Setting to true enables installments for this Checkout Session. Setting to false will prevent any installment plan from applying to a payment. - `payment_method_options.card.request_extended_authorization` (enum, optional) Request ability to [capture beyond the standard authorization validity window](https://docs.stripe.com/payments/extended-authorization.md) for this CheckoutSession. Possible enum values: - `if_available` Use `if_available` if you want to extend the capture window when eligible for extended authorization. - `never` Use `never` if you don’t want to extend the capture window. - `payment_method_options.card.request_incremental_authorization` (enum, optional) Request ability to [increment the authorization](https://docs.stripe.com/payments/incremental-authorization.md) for this CheckoutSession. Possible enum values: - `if_available` Use `if_available` if you want to increment the authorization on the PaymentIntent when eligible. - `never` Use `never` if you don’t want to increment the authorization on the PaymentIntent. - `payment_method_options.card.request_multicapture` (enum, optional) Request ability to make [multiple captures](https://docs.stripe.com/payments/multicapture.md) for this CheckoutSession. Possible enum values: - `if_available` Use `if_available` if you want to use multicapture when eligible. - `never` Use `never` if you don’t want to use multicapture. - `payment_method_options.card.request_overcapture` (enum, optional) Request ability to [overcapture](https://docs.stripe.com/payments/overcapture.md) for this CheckoutSession. Possible enum values: - `if_available` Use `if_available` if you want to overcapture the payment when eligible. - `never` Use `never` if you don’t want to overcapture the payment. - `payment_method_options.card.request_three_d_secure` (enum, optional) We strongly recommend that you rely on our SCA Engine to automatically prompt your customers for authentication based on risk level and [other requirements](https://docs.stripe.com/strong-customer-authentication.md). However, if you wish to request 3D Secure based on logic from your own fraud engine, provide this option. If not provided, this value defaults to `automatic`. Read our guide on [manually requesting 3D Secure](https://docs.stripe.com/payments/3d-secure/authentication-flow.md#manual-three-ds) for more information on how this configuration interacts with Radar and our SCA Engine. Possible enum values: - `any` Use `any` to manually request 3DS with a preference for a `frictionless` flow, increasing the likelihood of the authentication being completed without any additional input from the customer. 3DS will always be attempted if it is supported for the card, but Stripe can’t guarantee your preference because the issuer determines the ultimate authentication flow. To learn more about 3DS flows, read our [guide](https://stripe.com/guides/3d-secure-2#frictionless-authentication). - `automatic` (Default) Our SCA Engine automatically prompts your customers for authentication based on risk level and other requirements. - `challenge` Use `challenge` to request 3DS with a preference for a `challenge` flow, where the customer must respond to a prompt for active authentication. Stripe can’t guarantee your preference because the issuer determines the ultimate authentication flow. To learn more about 3DS flows, read our [guide](https://stripe.com/guides/3d-secure-2#frictionless-authentication). - `payment_method_options.card.restrictions` (object, optional) Restrictions to apply to the card payment method. For example, you can block specific card brands. You can’t set this parameter if `ui_mode` is `elements`. - `payment_method_options.card.restrictions.brands_blocked` (array of enums, optional) The card brands to block. If a customer enters or selects a card belonging to a blocked brand, they can’t complete the payment. Possible enum values: - `american_express` Include `american_express` to block American Express cards. - `discover_global_network` Include `discover_global_network` to block all cards within the Discover Global Network. This encompasses the following card brands: - Discover - Diners Club - JCB - UnionPay - Elo - `mastercard` Include `mastercard` to block Mastercard cards. - `visa` Include `visa` to block Visa cards. - `payment_method_options.card.restrictions.funding_types_blocked` (array of enums, optional) Card funding types to block for this Checkout Session. Supported values are `credit`, `debit`, and `prepaid`. Possible enum values: - `credit` Include `credit` to block credit cards. - `debit` Include `debit` to block debit cards. - `prepaid` Include `prepaid` to block prepaid cards. - `payment_method_options.card.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `on_session` Use `on_session` if you intend to only reuse the payment method when your customer is present in your checkout flow. - `payment_method_options.card.statement_descriptor_suffix_kana` (string, optional) Provides information about a card payment that customers see on their statements. Concatenated with the Kana prefix (shortened Kana descriptor) or Kana statement descriptor that’s set on the account to form the complete statement descriptor. Maximum 22 characters. On card statements, the *concatenation* of both prefix and suffix (including separators) will appear truncated to 22 characters. The maximum length is 22 characters. - `payment_method_options.card.statement_descriptor_suffix_kanji` (string, optional) Provides information about a card payment that customers see on their statements. Concatenated with the Kanji prefix (shortened Kanji descriptor) or Kanji statement descriptor that’s set on the account to form the complete statement descriptor. Maximum 17 characters. On card statements, the *concatenation* of both prefix and suffix (including separators) will appear truncated to 17 characters. The maximum length is 17 characters. - `payment_method_options.cashapp` (object, optional) contains details about the Cashapp Pay payment method options. - `payment_method_options.cashapp.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.cashapp.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `on_session` Use `on_session` if you intend to only reuse the payment method when your customer is present in your checkout flow. - `payment_method_options.crypto` (object, optional) contains details about the Crypto payment method options. - `payment_method_options.crypto.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.customer_balance` (object, optional) contains details about the Customer Balance payment method options. - `payment_method_options.customer_balance.bank_transfer` (object, optional) Configuration for the bank transfer funding type, if the `funding_type` is set to `bank_transfer`. - `payment_method_options.customer_balance.bank_transfer.type` (enum, required) The list of bank transfer types that this PaymentIntent is allowed to use for funding. Possible enum values: - `eu_bank_transfer` eu_bank_transfer bank transfer type - `gb_bank_transfer` gb_bank_transfer bank transfer type - `jp_bank_transfer` jp_bank_transfer bank transfer type - `mx_bank_transfer` mx_bank_transfer bank transfer type - `us_bank_transfer` us_bank_transfer bank transfer type - `payment_method_options.customer_balance.bank_transfer.eu_bank_transfer` (object, optional) Configuration for eu_bank_transfer funding type. - `payment_method_options.customer_balance.bank_transfer.eu_bank_transfer.country` (string, required) The desired country code of the bank account information. Permitted values include: `DE`, `FR`, `IE`, or `NL`. - `payment_method_options.customer_balance.bank_transfer.requested_address_types` (array of enums, optional) List of address types that should be returned in the financial_addresses response. If not specified, all valid types will be returned. Permitted values include: `sort_code`, `zengin`, `iban`, or `spei`. Possible enum values: - `aba` aba bank account address type - `iban` iban bank account address type - `sepa` sepa bank account address type - `sort_code` sort_code bank account address type - `spei` spei bank account address type - `swift` swift bank account address type - `zengin` zengin bank account address type - `payment_method_options.customer_balance.funding_type` (string, value is "bank_transfer", optional) The funding method type to be used when there are not enough funds in the customer balance. Permitted values include: `bank_transfer`. - `payment_method_options.customer_balance.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.demo_pay` (object, optional) contains details about the DemoPay payment method options. - `payment_method_options.demo_pay.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `payment_method_options.eps` (object, optional) contains details about the EPS payment method options. - `payment_method_options.eps.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.fpx` (object, optional) contains details about the FPX payment method options. - `payment_method_options.fpx.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.giropay` (object, optional) contains details about the Giropay payment method options. - `payment_method_options.giropay.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.grabpay` (object, optional) contains details about the Grabpay payment method options. - `payment_method_options.grabpay.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.ideal` (object, optional) contains details about the Ideal payment method options. - `payment_method_options.ideal.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.kakao_pay` (object, optional) contains details about the Kakao Pay payment method options. - `payment_method_options.kakao_pay.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.kakao_pay.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `payment_method_options.klarna` (object, optional) contains details about the Klarna payment method options. - `payment_method_options.klarna.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.klarna.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.klarna.subscriptions` (array of objects, optional) Subscription details if the Checkout Session sets up a future subscription. - `payment_method_options.klarna.subscriptions.interval` (enum, required) Unit of time between subscription charges. Possible enum values: - `day` - `month` - `week` - `year` - `payment_method_options.klarna.subscriptions.next_billing` (object, required) Describes the upcoming charge for this subscription. - `payment_method_options.klarna.subscriptions.next_billing.amount` (integer, required) The amount of the next charge for the subscription. - `payment_method_options.klarna.subscriptions.next_billing.date` (string, required) The date of the next charge for the subscription in YYYY-MM-DD format. - `payment_method_options.klarna.subscriptions.reference` (string, required) A non-customer-facing reference to correlate subscription charges in the Klarna app. Use a value that persists across subscription charges. The maximum length is 255 characters. - `payment_method_options.klarna.subscriptions.interval_count` (integer, optional) The number of intervals (specified in the `interval` attribute) between subscription charges. For example, `interval=month` and `interval_count=3` charges every 3 months. - `payment_method_options.klarna.subscriptions.name` (string, optional) Name for subscription. The maximum length is 255 characters. - `payment_method_options.konbini` (object, optional) contains details about the Konbini payment method options. - `payment_method_options.konbini.expires_after_days` (integer, optional) The number of calendar days (between 1 and 60) after which Konbini payment instructions will expire. For example, if a PaymentIntent is confirmed with Konbini and `expires_after_days` set to 2 on Monday JST, the instructions will expire on Wednesday 23:59:59 JST. Defaults to 3 days. - `payment_method_options.konbini.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.kr_card` (object, optional) contains details about the Korean card payment method options. - `payment_method_options.kr_card.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.kr_card.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `payment_method_options.link` (object, optional) contains details about the Link payment method options (Link is also known as Onelink in the UK). - `payment_method_options.link.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.link.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `payment_method_options.mobilepay` (object, optional) contains details about the Mobilepay payment method options. - `payment_method_options.mobilepay.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.mobilepay.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.multibanco` (object, optional) contains details about the Multibanco payment method options. - `payment_method_options.multibanco.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.naver_pay` (object, optional) contains details about the Naver Pay payment method options. - `payment_method_options.naver_pay.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.naver_pay.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `payment_method_options.oxxo` (object, optional) contains details about the OXXO payment method options. - `payment_method_options.oxxo.expires_after_days` (integer, optional) The number of calendar days before an OXXO voucher expires. For example, if you create an OXXO voucher on Monday and you set expires_after_days to 2, the OXXO invoice will expire on Wednesday at 23:59 America/Mexico_City time. - `payment_method_options.oxxo.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.p24` (object, optional) contains details about the P24 payment method options. - `payment_method_options.p24.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.p24.tos_shown_and_accepted` (boolean, optional) Confirm that the payer has accepted the P24 terms and conditions. - `payment_method_options.pay_by_bank` (object, optional) contains details about the Pay By Bank payment method options. - `payment_method_options.payco` (object, optional) contains details about the PAYCO payment method options. - `payment_method_options.payco.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.payco.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.paynow` (object, optional) contains details about the PayNow payment method options. - `payment_method_options.paynow.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.paypal` (object, optional) contains details about the PayPal payment method options. - `payment_method_options.paypal.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.paypal.preferred_locale` (enum, optional) [Preferred locale](https://docs.stripe.com/payments/paypal/supported-locales.md) of the PayPal checkout page that the customer is redirected to. Possible enum values: - `cs-CZ` Czech - The Czech Republic - `da-DK` Danish - Denmark - `de-AT` German - Austria - `de-DE` German - Germany - `de-LU` German - Luxembourg - `el-GR` Greek - Greece - `en-GB` English - United Kingdom - `en-US` English - United States of America - `es-ES` Spanish - Spain - `fi-FI` Finnish - Finland - `fr-BE` French - Belgium - `fr-FR` French - France - `fr-LU` French - Luxembourg - `hu-HU` Hungarian - Hungary - `it-IT` Italian - Italy - `nl-BE` Dutch - Belgium - `nl-NL` Dutch - Netherlands - `pl-PL` Polish - Poland - `pt-PT` Portuguese - Portugal - `sk-SK` Slovak - Slovakia - `sv-SE` Swedish - Sweden - `payment_method_options.paypal.reference` (string, optional) A reference of the PayPal transaction visible to customer which is mapped to PayPal’s invoice ID. This must be a globally unique ID if you have configured in your PayPal settings to block multiple payments per invoice ID. The maximum length is 127 characters. - `payment_method_options.paypal.risk_correlation_id` (string, optional) The risk correlation ID for an on-session payment using a saved PayPal payment method. The maximum length is 32 characters. - `payment_method_options.paypal.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). If you’ve already set `setup_future_usage` and you’re performing a request using a publishable key, you can only update the value from `on_session` to `off_session`. Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `payment_method_options.payto` (object, optional) contains details about the PayTo payment method options. - `payment_method_options.payto.mandate_options` (object, optional) Additional fields for Mandate creation - `payment_method_options.payto.mandate_options.amount` (integer, optional) Amount that will be collected. It is required when `amount_type` is `fixed`. - `payment_method_options.payto.mandate_options.amount_type` (enum, optional) The type of amount that will be collected. The amount charged must be exact or up to the value of `amount` param for `fixed` or `maximum` type respectively. Defaults to `maximum`. Possible enum values: - `fixed` The amount is the exact amount that will be charged. - `maximum` The amount is the maximum amount that can be charged. - `payment_method_options.payto.mandate_options.end_date` (string, optional) Date, in YYYY-MM-DD format, after which payments will not be collected. Defaults to no end date. - `payment_method_options.payto.mandate_options.payment_schedule` (enum, optional) The periodicity at which payments will be collected. Defaults to `adhoc`. Possible enum values: - `adhoc` Payments will be made ad hoc - `annual` Payments will be made annually - `daily` Payments will be made daily - `fortnightly` Payments will be made fortnightly - `monthly` Payments will be made monthly - `quarterly` Payments will be made quarterly - `semi_annual` Payments will be made semi-annually - `weekly` Payments will be made weekly - `payment_method_options.payto.mandate_options.payments_per_period` (integer, optional) The number of payments that will be made during a payment period. Defaults to 1 except for when `payment_schedule` is `adhoc`. In that case, it defaults to no limit. - `payment_method_options.payto.mandate_options.purpose` (enum, optional) The purpose for which payments are made. Has a default value based on your merchant category code. Possible enum values: - `dependant_support` Transactions are made for dependant support reasons - `government` Transactions are made for government reasons - `loan` Transactions are made for loan reasons - `mortgage` Transactions are made for mortgage reasons - `other` Transactions are made for other reasons - `pension` Transactions are made for pension reasons - `personal` Transactions are made for personal reasons - `retail` Transactions are made for retail reasons - `salary` Transactions are made for salary reasons - `tax` Transactions are made for tax reasons - `utility` Transactions are made for utility reasons - `payment_method_options.payto.mandate_options.start_date` (string, optional) Date, in YYYY-MM-DD format, from which payments will be collected. Defaults to confirmation time. - `payment_method_options.payto.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `payment_method_options.pix` (object, optional) contains details about the Pix payment method options. - `payment_method_options.pix.amount_includes_iof` (enum, optional) Determines if the amount includes the IOF tax. Defaults to `never`. Possible enum values: - `always` The IOF tax is included in the amount. - `never` The IOF tax is not included in the amount. - `payment_method_options.pix.expires_after_seconds` (integer, optional) The number of seconds after PaymentIntent confirmation when the Pix expires (between 60 and 1209600, inclusive). If unspecified, defaults to 14400 seconds (4 hours). - `payment_method_options.pix.mandate_options` (object, optional) Additional fields for mandate creation. - `payment_method_options.pix.mandate_options.amount` (integer, optional) Amount to be charged for future payments. Required when `amount_type=fixed`. If not provided for `amount_type=maximum`, defaults to 40000. - `payment_method_options.pix.mandate_options.amount_includes_iof` (enum, optional) Determines if the amount includes the IOF tax. Defaults to `never`. Possible enum values: - `always` The IOF tax is included in the amount. - `never` The IOF tax is not included in the amount. - `payment_method_options.pix.mandate_options.amount_type` (enum, optional) Type of amount. Defaults to `maximum`. Possible enum values: - `fixed` The exact amount for future payments. - `maximum` The maximum amount for future payments. - `payment_method_options.pix.mandate_options.currency` (enum, optional) Three-letter [ISO currency code](https://www.iso.org/iso-4217-currency-codes.html), in lowercase. Only `brl` is supported currently. - `payment_method_options.pix.mandate_options.end_date` (string, optional) Date when the mandate expires and no further payments will be charged, in `YYYY-MM-DD`. If not provided, the mandate will be active until canceled. If provided, end date should be after start date. - `payment_method_options.pix.mandate_options.payment_schedule` (enum, optional) Schedule at which the future payments will be charged. Defaults to `monthly`. Possible enum values: - `halfyearly` The future payments will be charged half-yearly. - `monthly` The future payments will be charged monthly. - `quarterly` The future payments will be charged quarterly. - `weekly` The future payments will be charged weekly. - `yearly` The future payments will be charged yearly. - `payment_method_options.pix.mandate_options.reference` (string, optional) Subscription name displayed to buyers in their bank app. Defaults to the displayable business name. The maximum length is 35 characters. - `payment_method_options.pix.mandate_options.start_date` (string, optional) Start date of the mandate, in `YYYY-MM-DD`. Start date should be at least 3 days in the future. Defaults to 3 days after the current date. - `payment_method_options.pix.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `payment_method_options.revolut_pay` (object, optional) contains details about the RevolutPay payment method options. - `payment_method_options.revolut_pay.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.revolut_pay.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `payment_method_options.samsung_pay` (object, optional) contains details about the Samsung Pay payment method options. - `payment_method_options.samsung_pay.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.samsung_pay.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.satispay` (object, optional) contains details about the Satispay payment method options. - `payment_method_options.satispay.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.scalapay` (object, optional) contains details about the Scalapay payment method options. - `payment_method_options.scalapay.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.sepa_debit` (object, optional) contains details about the Sepa Debit payment method options. - `payment_method_options.sepa_debit.mandate_options` (object, optional) Additional fields for Mandate creation - `payment_method_options.sepa_debit.mandate_options.reference_prefix` (string, optional) Prefix used to generate the Mandate reference. Must be at most 12 characters long. Must consist of only uppercase letters, numbers, spaces, or the following special characters: ‘/’, ‘_’, ‘-’, ‘&’, ‘.’. Cannot begin with ‘STRIPE’. The maximum length is 12 characters. - `payment_method_options.sepa_debit.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `on_session` Use `on_session` if you intend to only reuse the payment method when your customer is present in your checkout flow. - `payment_method_options.sepa_debit.target_date` (string, optional) Controls when Stripe will attempt to debit the funds from the customer’s account. The date must be a string in YYYY-MM-DD format. The date must be in the future and between 3 and 15 calendar days from now. - `payment_method_options.sequra` (object, optional) contains details about the SeQura payment method options. - `payment_method_options.sequra.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.sofort` (object, optional) contains details about the Sofort payment method options. - `payment_method_options.sofort.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.sunbit` (object, optional) contains details about the Sunbit payment method options. - `payment_method_options.sunbit.capture_method` (enum, optional) Controls when the funds will be captured from the customer’s account. Possible enum values: - `manual` Use `manual` if you intend to place the funds on hold and want to override the top-level `capture_method` value for this payment method. - `payment_method_options.sunbit.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `payment_method_options.swish` (object, optional) contains details about the Swish payment method options. - `payment_method_options.swish.reference` (string, optional) The order reference that will be displayed to customers in the Swish application. Defaults to the `id` of the Payment Intent. - `payment_method_options.twint` (object, optional) contains details about the TWINT payment method options. - `payment_method_options.twint.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `payment_method_options.upi` (object, optional) contains details about the UPI payment method options. - `payment_method_options.upi.mandate_options` (object, optional) Additional fields for Mandate creation - `payment_method_options.upi.mandate_options.amount` (integer, optional) Amount to be charged for future payments. - `payment_method_options.upi.mandate_options.amount_type` (enum, optional) One of `fixed` or `maximum`. If `fixed`, the `amount` param refers to the exact amount to be charged in future payments. If `maximum`, the amount charged can be up to the value passed for the `amount` param. Possible enum values: - `fixed` If `fixed`, the `amount` param refers to the exact amount to be charged in future payments. - `maximum` If `maximum`, the amount charged can be up to the value passed for the `amount` param. - `payment_method_options.upi.mandate_options.description` (string, optional) A description of the mandate or subscription that is meant to be displayed to the customer. The maximum length is 20 characters. - `payment_method_options.upi.mandate_options.end_date` (timestamp, optional) End date of the mandate or subscription. - `payment_method_options.us_bank_account` (object, optional) contains details about the Us Bank Account payment method options. - `payment_method_options.us_bank_account.financial_connections` (object, optional) Additional fields for Financial Connections Session creation - `payment_method_options.us_bank_account.financial_connections.permissions` (array of enums, optional) The list of permissions to request. If this parameter is passed, the `payment_method` permission must be included. Valid permissions include: `balances`, `ownership`, `payment_method`, and `transactions`. Possible enum values: - `balances` - `ownership` - `payment_method` - `transactions` - `payment_method_options.us_bank_account.financial_connections.prefetch` (array of enums, optional) List of data features that you would like to retrieve upon account creation. Possible enum values: - `balances` Requests to prefetch balance data on accounts collected in this session. - `ownership` Requests to prefetch ownership data on accounts collected in this session. - `transactions` Requests to prefetch transaction data on accounts collected in this session. - `payment_method_options.us_bank_account.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method. - `off_session` Use `off_session` if your customer may or may not be present in your checkout flow. - `on_session` Use `on_session` if you intend to only reuse the payment method when your customer is present in your checkout flow. - `payment_method_options.us_bank_account.target_date` (string, optional) Controls when Stripe will attempt to debit the funds from the customer’s account. The date must be a string in YYYY-MM-DD format. The date must be in the future and between 3 and 15 calendar days from now. - `payment_method_options.us_bank_account.verification_method` (enum, optional) Verification method for the intent Possible enum values: - `automatic` Instant verification with fallback to microdeposits. - `instant` Instant verification only. - `payment_method_options.wechat_pay` (object, optional) contains details about the WeChat Pay payment method options. - `payment_method_options.wechat_pay.client` (enum, required) The client type that the end customer will pay from Possible enum values: - `android` The end customer will pay from an Android app - `ios` The end customer will pay from an iOS app - `web` The end customer will pay from web browser - `payment_method_options.wechat_pay.app_id` (string, optional) The app ID registered with WeChat Pay. Only required when client is ios or android. - `payment_method_options.wechat_pay.setup_future_usage` (enum, optional) Indicates that you intend to make future payments with this PaymentIntent’s payment method. If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.stripe.com/payments/save-during-payment.md) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still [attach](https://docs.stripe.com/api/payment_methods/attach.md) the payment method to a Customer after the transaction completes. If the payment method is `card_present` and isn’t a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead. When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication.md). Possible enum values: - `none` Use `none` if you do not intend to reuse this payment method and want to override the top-level `setup_future_usage` value for this payment method.