Skip to content
Create account or Sign in
The Stripe Docs logo
/
Ask AI
Create accountSign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
APIs & SDKsHelp
Overview
Versioning
Changelog
    Overview
    Clover
    Basil
    Acacia
    Previous versions
Upgrade your API version
Upgrade your SDK version
Essentials
SDKs
API
Testing
Stripe CLI
Sample projects
Tools
Stripe Dashboard
Workbench
Developers Dashboard
Stripe Shell
Stripe for Visual Studio Code
Features
Workflows
Event Destinations
Stripe health alertsFile uploads
AI solutions
Agent toolkit
Model Context ProtocolBuild agentic AI SaaS Billing workflows
Security and privacy
Security
Stripebot web crawler
Privacy
Extend Stripe
Build Stripe apps
Use apps from Stripe
Partners
Partner ecosystem
Partner certification
United States
English (United Kingdom)
HomeDeveloper resourcesChangelogClover2025-12-15.clover

Adds expected debit date for bank debit payments

What’s new

You can now access the expected_debit_date for bank debit payments under payment_method_details for Charges. For example, you can find the expected debit date for ACSS Debit in payment_method_details.acss_debit.expected_debit_date.

This property is available for all direct debit payment methods: ACSS Debit, AU BECS Debit, BACS Debit, NZ Bank Account, SEPA Debit, and US Bank Account.

The expected_debit_date property returns a date string in YYYY-MM-DD format indicating when funds are expected to be debited from the customer’s bank account. This information is available in API responses and charge.updated, charge.succeeded, and charge.failed events when the debit date can be determined.

Impact

You can now provide your customers with visibility into when funds are expected to be debited from their accounts, which helps with cash flow forecasting and customer communication. The expected_debit_date property returns null when the debit date can’t be determined, so make sure your integration handles both scenarios.

Changes

ParameterChangeResources or endpoints
expected_debit_dateAdded
Charge.payment_method_details.acss_debitCharge.payment_method_details.au_becs_debitCharge.payment_method_details.bacs_debit
 + 15 more
Charge.payment_method_details.nz_bank_accountCharge.payment_method_details.sepa_debitCharge.payment_method_details.us_bank_accountPaymentAttemptRecord.payment_method_details.acss_debitPaymentAttemptRecord.payment_method_details.au_becs_debitPaymentAttemptRecord.payment_method_details.bacs_debitPaymentAttemptRecord.payment_method_details.nz_bank_accountPaymentAttemptRecord.payment_method_details.sepa_debitPaymentAttemptRecord.payment_method_details.us_bank_accountPaymentRecord.payment_method_details.acss_debitPaymentRecord.payment_method_details.au_becs_debitPaymentRecord.payment_method_details.bacs_debitPaymentRecord.payment_method_details.nz_bank_accountPaymentRecord.payment_method_details.sepa_debitPaymentRecord.payment_method_details.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-12-15.clover
  3. Upgrade the API version used for webhook endpoints.
  4. Test your integration against the new version.
  5. If you use Connect, test your Connect integration.
  6. In Workbench, perform the upgrade. You can roll back the version for 72 hours.

Learn more about Stripe API upgrades.

Related changes

  • Adds Mollie as a supported iDEAL issuer
  • Adds additional card payment method details to Payment Records
  • Adds support for the PayTo payment method
Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc