Stripe is retiring a legacy ACH Direct Debit payment fallback on August 24, 2026. After that date, payments that relied on this fallback will fail. If you use Stripe with Zapier to create subscriptions, invoices, or payments, some of your Zap runs could start failing.
This is a change Stripe is making to its own platform. It is not a Zapier product change, and Zapier cannot turn it off or delay it for you.
What is changing
Today, if a Stripe customer does not have a payment method explicitly set on a subscription or invoice, Stripe can fall back to a bank account already stored on the customer's record. This is a legacy ACH Direct Debit mandate.
After August 24, 2026, Stripe removes that fallback entirely. Any payment that would have used that fallback will fail.
August 24, 2026 is Stripe's enforcement date. Zapier cannot adjust it.
Why this might affect you
Zap actions that create or collect payment on subscriptions and invoices could start failing after the deadline. This happens when a Stripe customer pays through this legacy bank-account method and no default payment method is set on the customer, the subscription, or the invoice.
Whether this affects your account depends entirely on how your own Stripe customers are set up. Zapier cannot determine this for you. Check your Stripe Dashboard or contact Stripe Support for account-specific guidance.
What to do in your Stripe account
The fix lives in your own Stripe account, not in Zapier. It applies to everyone using Stripe with Zapier, whichever Stripe app version your Zaps use.
- Migrate your existing customers. For any Stripe customer still relying on the legacy bank-account fallback, set an explicit default payment method on their Stripe record. Stripe's documentation explains how legacy ACH payments are identified and how to migrate existing bank accounts.
- Set payment methods explicitly going forward. Even after you migrate existing customers, any new customer created without an explicit default payment method can fail the same way. Set an explicit default payment method on new customers as you create them.
Zapier cannot determine which of your customers are affected. Contact Stripe Support for account-specific questions.
Additional steps for your Zapier setup
Select the option that matches the Stripe app version or custom action your Zap uses. These steps supplement the two steps in your Stripe account. They do not replace them.
Not sure which app version you are using? In the Zap editor, click your Stripe step and check the app name. Learn how to identify your app version and what app tags mean.
You are on this version if the app name reads Stripe with no version number and no app tag.
The Create Subscription action has an optional Default Payment Method field. Map this field to set the payment method explicitly for new subscriptions created through your Zap.
This only covers Zap runs where you map the field. It does not retroactively fix existing customer data, so you also need to set an explicit default payment method on your existing Stripe customers, and on new customers as you create them.
You are on this version if the app name shows a version number in parentheses and no app tag.
Set an explicit default payment method on your existing Stripe customers, and on new customers as you create them. This applies whether or not you update your app version.
Separately, if you want the option to set a payment method explicitly for new subscriptions created through a specific Zap, update that Zap to the latest Stripe app version.
In the Zap editor:
- Click the Stripe step.
- In the Setup tab, click Change next to the app name.
- Select Stripe, without a version number or the Legacy tag, to move to the latest version.
- Click Test step to confirm the step works.
- Turn your Zap back on if it was paused.
For most accounts, your existing connection carries over automatically and you do not need to reconnect it.
For full instructions, read how to update to the latest app version.
You are using this app if the app name carries a Legacy tag.
The Stripe (Legacy) app does not have an equivalent field to update. The fix lives entirely in your own Stripe account.
Set an explicit default payment method on your existing Stripe customers, and on new customers as you create them. For account-specific questions, contact Stripe Support.
Custom actions send exactly the request you configured. Zapier cannot detect or adjust this for you the way it can for built-in actions.
If your custom action creates or finalizes Stripe subscriptions, invoices, or payments:
- Check the custom action's request body.
- Set a payment method explicitly in the request rather than relying on the customer's stored default. Use
default_payment_methodon a subscription or invoice, orpayment_methodon a payment intent. - In your Stripe account, set an explicit default payment method on your existing customers, and on new customers as you create them.
Still need help?
- Questions about your Stripe account, or which of your customers are affected: contact Stripe Support directly. They can confirm your account's specific exposure. Zapier does not have access to this information.
- Questions about a Zapier step, app version, or connection: contact Zapier Support.
NoteThis information was accurate at the time of publication. Check the latest product update notes for any updates or changes.