#yilber_achv1-deprecation-plaid

1 messages · Page 1 of 1 (latest)

woeful wraithBOT
#

👋 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/1470459506956960018

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

tribal vigil
#

Hello can you send your account ID here? I'm not sure if I can see what our criteria were for sending that email but I will look

#

My guess is that you are using the legacy sources API in some way. A common way for that to happen is if you are passing the payment method ID (pm_ or ba_) to the source parameter for an endpoint (rather than the payment_method parameter, which uses the newer API)

dim lily
#

give me a second please, I'm looking for it

woeful wraithBOT
dim lily
#

Where i can find the account ID?

twin pike
#

Hi 👋

I'm stepping in as my colleague needs to go.

#

Once you log into your Stripe dashboard, the Account ID should be in the URL. It will start with acc_. You can also go to your Profile page and that will show you all the accounts you have access to.

dim lily
#

Here it is: 17jYIrFt57mGFjZQ

twin pike
#

That is not an Account ID. We need the full string that starts with acct_

#

It's all part of the ID

dim lily
#

In the url I can see: acct_17jYIrFt57mGFjZQ

twin pike
#

And this is for the business Zinkerz Inc., correct?

dim lily
#

Yes

twin pike
#

Okay, thank you. And the email you received was specifically about legacy ACH debits, correct?

dim lily
#

Yes, Can it help if I share the content email I receive?

twin pike
#

Not really. I'm just trying to understand where you may be using legacy bank debit payment methods. Those Ids start with ba_

dim lily
#

The email provides a series of steps recommending a migration to Checkout Sessions. However, in one part it indicates that the charges.create method will be deprecated (at least that is my understanding).
As I mentioned when creating this request, we do not use this method in our server-side code. This is why we are confused about what exactly we are expected to migrate.

twin pike
#

In that case you need to review the guidance and see what parts apply to your integration.

dim lily
#

Specifically, based on that email, what exactly is going to be deprecated?

twin pike
dim lily
#

We link ACH bank accounts using Plaid, but we only use it for user authentication and to generate the bank account token. That token is then passed to the Stripe API. is this flow valid?

twin pike
#

I think that is what is being deprecated. We mention that here and that flow is what we are recommending you replace with Checkout Sessions

dim lily
#

Well… my question is not fully resolved yet, considering what is mentioned in the documentation: “If you create ACH Direct Debit payments using the Charges API through the API, Invoices, or Subscriptions, you must migrate to the Payment Intents API or Checkout Sessions API.”

As I mentioned, I understand that the charges.create method will be deprecated, which we do not use in our integration. So why are we receiving this email if the ACH account integration itself is not mentioned as being deprecated (in our case, using Plaid)

twin pike
#

Unfortunately, that isn't something I can provide insight into. You will need to reach out to Support here: https://support.stripe.com/contact

They can provide more details about exactly what prompted this email.

dim lily
#

Ok, Thanks, i will be contact they

twin pike
#

Happy to shed what 💡 I can 🙂