Stripe | Financial Infrastructure to Grow Your Revenue

Stripe | Financial Infrastructure to Grow Your Revenue

4466 articles

Adds ability to schedule debit payments for a specific date


Adds ability to schedule debit payments for a specific date

What’s new

The target_date parameter is now available for all bank debit payment methods (including ACH, the related setting, the related setting, AU the related setting, and the related setting). You can use this parameter to specify a future date (3 to 15 days ahead) to debit funds from the user’s bank account when you create or update a Checkout Session; or when you create or update a Payment Intent.

Impact

The target_date parameter helps you manage your financial planning and customer expectations. You can synchronize your debit transactions with your cash flow needs by scheduling payments more strategically. For example, you could align payments with billing cycles, customer payment habits, or other financial considerations.

Changes

ParameterChangeResources or endpoints
target_dateAddedCheckout.Session#create.payment_method_options.acss_debit Checkout.Session#create.payment_method_options.au_becs_debit Checkout. Session#create. payment_method_options. bacs_debit + 27 more Checkout. Session#create. payment_method_options. sepa_debit Checkout.Session#create.payment_method_options.us_bank_account Checkout.Session.payment_method_options.acss_debit Checkout.Session.payment_method_options.au_becs_debit Checkout. Session. payment_method_options. bacs_debit Checkout. Session. payment_method_options. sepa_debit Checkout.Session.payment_method_options.us_bank_account PaymentIntent#confirm.payment_method_options.acss_debit PaymentIntent#confirm.payment_method_options.au_becs_debit PaymentIntent#confirm. payment_method_options. bacs_debit PaymentIntent#confirm.payment_method_options.sepa_debit PaymentIntent#confirm.payment_method_options.us_bank_account PaymentIntent#create.payment_method_options.acss_debit PaymentIntent#create.payment_method_options.au_becs_debit PaymentIntent#create. payment_method_options. bacs_debit PaymentIntent#create.payment_method_options.sepa_debit PaymentIntent#create.payment_method_options.us_bank_account PaymentIntent#update.payment_method_options.acss_debit PaymentIntent#update.payment_method_options.au_becs_debit PaymentIntent#update. payment_method_options. bacs_debit PaymentIntent#update.payment_method_options.sepa_debit PaymentIntent#update.payment_method_options.us_bank_account PaymentIntent.payment_method_options.acss_debit PaymentIntent.payment_method_options.au_becs_debit PaymentIntent. payment_method_options. bacs_debit PaymentIntent.payment_method_options.sepa_debit PaymentIntent.payment_method_options.us_bank_account

Upgrade

  1. View your current API version in Workbench.
  2. If you use an SDK, upgrade to the corresponding SDK version for this API version.
  • If you don’t use an SDK, update your API requests to include Stripe-Version: 2025-02-24. acacia
  1. Upgrade the API version used for webhook endpoints .
  2. Test your integration against the new version.
  3. If you use Connect, test your Connect integration .
  4. In Workbench, perform the upgrade . You can roll back the version for 72 hours.

Learn more about Stripe API upgrades.

Last verified 2026-09-24

Is this helpful?