felipe-borges_api | Stripe Developers | Page 1

strange hareBOT Apr 20, 2026, 12:46 PM

#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1495767495498268722

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

icy rock Apr 20, 2026, 12:49 PM

#

hey there 👋

a 'legacy Bank Account' refers to the type of object (bank_account) used to represent a customer's bank account in the legacy integration, which has an ID like ba_12345 (i.e. legacy ach_debit)
https://docs.stripe.com/api/customer_bank_accounts

#

on the other hand, when using the newer us_bank_account integration, the equivalent object is a payment_method, with an ID like pm_12345
https://docs.stripe.com/api/payment_methods

#

Now looking at the registered bank accounts, all of them are "type": "us_bank_account"

that means that you're using the current integration

ocean mesa Apr 20, 2026, 12:51 PM

#

mmm thanks, that's clarifying

#

but still all my charges are legacy

icy rock Apr 20, 2026, 12:52 PM

#

what do you mean exactly?

ocean mesa Apr 20, 2026, 12:52 PM

#

as per the doc: "On a Charge object, the payment_method_details.type property is ach_debit for the legacy integration and us_bank_account for the newer integration."

#

"payment_method_details": {
        "ach_debit": {
          "account_holder_type": "individual",
          "bank_name": "WELLS FARGO BANK NA",
          "country": "US",
          "fingerprint": "fCqjXPc15wR2Vi0J",
          "last4": "3799",
          "routing_number": "121042882"
        },
        "type": "ach_debit"
      },

example charge ☝️

#

and the migration dashboard is complaining

icy rock Apr 20, 2026, 12:54 PM

#

yeah that suggests the charge was created with a legacy bank account (i.e. ba_1234 rather than pm_1234)

can you share the charge ID?

ocean mesa Apr 20, 2026, 12:54 PM

#

ah got it
py_3TOHHkJmq474uon80XGxI952

icy rock Apr 20, 2026, 12:56 PM

#

thanks! yeah checking on my side I can see that example was created through the legacy path

ocean mesa Apr 20, 2026, 12:56 PM

#

you're right, I can see some charges using the newer integration

#

meaning I basically have to migrate all the legacy bank accounts

icy rock Apr 20, 2026, 12:58 PM

#

yeah that's correct - sounds like you already have it, but here's the doc for that: https://docs.stripe.com/payments/ach-direct-debit/migrating-from-charges

strange hareBOT Apr 20, 2026, 12:59 PM

#

ocean mesa Apr 20, 2026, 1:00 PM

#

if I can ask something slighly unrelated, do you know what's that "Dashboard" row in the migration ss?

fathom reef Apr 20, 2026, 1:01 PM

#

Hello
I assume it is referring to the charges you create directly from the dashboard

ocean mesa Apr 20, 2026, 1:23 PM

#

just noticed ACH Direct Debit payment method is disabled on the dashboard, whereas the doc explicitly says we have to enable it. so wonder if the newer integration should even be working

#felipe-borges_api