/debit-auth/create returns HTTP 500 for intent RECURRING_CHARGE

Questions
1

We cannot create recurring ACH authorizations. The Web Payments SDK call to
POST /debit-auth/create returns HTTP 500 every time when tokenizing with
intent RECURRING_CHARGE. The SDK surfaces UnexpectedError, and its own Sentry
receives “Error: No error message” from ach-authz-sdk/enclave.js.

Key evidence: using the same stored bank account, same amount, same currency,
same application and same location, and changing ONLY the intent:

intent CHARGE works, BAUTH token returned
intent RECURRING_CHARGE HTTP 500, before any UI renders

So bank-on-file works for this application. Only the recurring path fails.

Application ID: sq0idp-2n6VeCiSZoBmCzE6V8t4ng
Location ID: LAEEK07SYKB5E
SDK: web-payments-sdk 1.85.0
Sentry project 3478832, event_id 1cd9a3b1cbbe4facbe61c32244ecda9f
Cf-Ray a403bfd10de45609-BOS, 24 Sep 2026 18:11:02 GMT, us-west-2

Already ruled out: frequency shape (also fails with the daily form from your
docs), start date (today and future), three different verified debitable bank
accounts, two unrelated merchants, amounts from 1.00 to 175.00, production
environment. This has never worked. Card recurring plans work normally.

Is RECURRING_CHARGE enabled for this application? If it needs separate
enablement, please tell us what to request. If it should already work, please
check the Sentry event: your enclave reports exceptions with no message.

3

Since charge works but recurring charge does not, I’d like to check if you application has access to the bank on file flow and investigate the request.

Could you DM me the following:

  1. Square app id: sq0idp-2n6VeCiSZoBmCzE6V8t4ng
  2. Environment: production
  3. Charge amount use case: fixed amount/varying amount/both
  4. What is the expected amount/cadence/approximate volumes?
5

  1. Square app id: sq0idp-2n6VeCiSZoBmCzE6V8t4ng

  2. Environment: production

  3. Charge amount use case: FIXED AMOUNT.

    Each plan authorizes one fixed total per charge. The amount is frozen at
    authorization time and verified against the stored authorization before
    every charge; if the amount needs to change, we require a new buyer
    authorization rather than reusing the existing one. We do not debit
    variable amounts against a recurring authorization.

  4. Expected amount / cadence / volumes:

    Amounts: - USD per charge, averaging about USD.
    Our platform limits a single recurring charge to between 0.50 and
    50,000.00 USD.

    Cadence: monthly in practice. The product also supports daily, weekly,
    biweekly, quarterly and yearly, all as fixed-amount schedules.

    Volume: ACH recurring plans across merchants, roughly
    USD per monthly cycle today. These are small US service
    businesses billing their own customers (professional services, tax
    preparation and similar).

    Note: this is our current ACH footprint, which is small because the
    recurring authorization has never worked. Card-based recurring plans run
    normally and are the larger share of our volume today.

    We are a platform integration: merchants connect their own Square
    accounts to our application via OAuth, and each merchant bills their own
    customers. The two merchants in the reproduction are unrelated to each
    other.

6

Your app should be added, it may take a few days for the flag to roll out.

8

I’ll wait to see what happens.

9

Wanted to follow up and check if it is working for you now!

10

Yes, all good. Thank You!