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 the related setting Debit in payment_method_details.acss_debit.expected_debit_date.
This property is available for all direct debit payment methods: the related setting Debit, AU the related setting Debit, the related setting Debit, NZ Bank Account, the related setting Debit, and US Bank Account.
The expected_debit_date property returns a date string in the related setting-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
Upgrade
- View your current API version in Workbench.
- 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
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
- In Workbench, perform the upgrade . You can roll back the version for 72 hours.
Learn more about Stripe API upgrades.