CreateBankAccount Beta: production availability outside Square Invoices and BANK_ACCOUNTS_WRITE

Questions
1

Hello Square Developer Team,

We are integrating customer bank-account enrollment for BlueLine Trailer Leasing LLC. Our current scope is enrollment only, without initiating any payment or debit.

The customer personally completes the Square/Plaid linking and consent flow using Web Payments SDK with intent: “STORE”. Our server submits the resulting bnon: token and Square customer ID to CreateBankAccount. We do not manually collect or enter bank credentials.

This exact flow succeeded in Sandbox:

  • CreateBankAccount returned a reusable bact: bank-account ID.
  • A subsequent GetBankAccount request confirmed VERIFIED.
  • We disabled the test account afterward and confirmed DISABLED.
  • No payments or debits were submitted.

Our production credentials successfully connect to Square, and our configured location is active in the United States with USD currency.

However, RetrieveTokenStatus does not report BANK_ACCOUNTS_WRITE in either production or Sandbox, even though Sandbox enrollment succeeded. We checked with API versions 2026-07-15 and 2026-09-16.

Could the Square team please clarify:

  1. Is this customer-initiated STORE/CreateBankAccount flow available in production outside Square Invoices?
  2. Does our application or seller account require Beta approval or additional enablement? If so, how do we request it?
  3. How should we obtain or confirm BANK_ACCOUNTS_WRITE, given the token-introspection results?
  4. Are there additional production requirements for enrollment without a charge?

We need to preserve our existing production card integration.

API reference:

Square Customer Support directed us to this forum for Developer/API assistance.

Thank you.

3

Validating tokens and checking production permissions for bank account storage without immediate charges can be tricky. Have you checked if your Square developer account requires specific feature flags enabled

4

Hi @blueline,

Would you be able to send your Production Application ID (not your access token!) here. Happy to take a look into this to confirm production eligibility outside Invoices, any required beta enablement, and the permission/introspection behavior for your enrollment-only use case.