Community News

 View Only

Stripe ACH Direct Debit Migration

  Thread closed by the administrator, not accepting new replies.
  • 1.  Stripe ACH Direct Debit Migration

    Posted 5 hours ago
    No replies, thread closed.

    Important Update: Stripe ACH Direct Debit Integration Migration

    To comply with modern security standards and ensure your payment processing remains uninterrupted, you must migrate to Stripe's updated Payment Intents workflow by August 6, 2026.

    Ref: https://docs.stripe.com/payments/ach-direct-debit/migrating-to-new-apis

    Why is this happening?

    Stripe is deprecating its legacy Charges API and moving entirely to the modern Payment Intents API. This industry-wide upgrade provides a more secure, reliable foundation for bank transfers and introduces mandatory tracking for customer authorization (mandates).

    As a result, legacy ACH payment structures (where bank accounts are labeled as ach_debit or source) are being replaced by modern payment methods (labeled as us_bank_account and payment_method).

    Determining if your integration is affected

    Evaluate your existing payment records to identify your status:

    • Action Required: If your payment method identifiers begin with the prefix ba_, you are utilizing an outdated format and must proceed with the migration.

    • No Action Needed: If your identifiers already feature the pm_ prefix, your system is already compatible with the current Payment Intents framework.

    How to Complete Your Migration

    To maintain processing continuity before the August 6, 2026 deadline, identify your current integration pathway and finalize testing in your sandbox environment:

    Scenario A: Users on Stripe v1

    1. Required Upgrade: You are required to move your current setup from Stripe v1 to the modern Stripe v2 framework.

    2. Migration Activation: If your upgrade to v2 is finalized prior to July 1, 2026, our system will automatically enable the migration for your tenant on that date. For upgrades completed after July 1, please submit a request to Zuora Support to manually trigger the migration process.

    Scenario B: Users on Stripe v2 (with legacy ba_ identifiers)

    1. Automated Update: Zuora will begin managing the conversion for these tenants starting July 1, 2026. No manual intervention is necessary for this group.

    Following sandbox validation, we will deploy a similar automated enablement across all production environments for Stripe v2 by July 15.

    Impact of the Update

    The update process is intended to be friction-free. Once our team activates the necessary tenant property:

    • Legacy ba_ IDs will be automatically converted by our system to the modern pm_ model during the next payment initiation, ensuring your checkout flow remains uninterrupted.

    • A mandatory legal mandate, representing the customer's debit authorization, will be generated automatically with its unique Mandate ID stored securely.

    We are here to help

    We strongly recommend reviewing your Stripe ACH setup and initiating this migration as soon as possible to prevent any payment failures after the August 6 deadline.

    If you are unsure which version you are using, need help upgrading to Stripe v2, or are ready to enable your tenant property, please contact Zuora Support and our team will guide you through the process.



    ------------------------------
    Megan Aaron
    Zuora, Inc.
    ------------------------------