#manyalawy_api
clear bisonBOT
👋 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/1278667213091504212
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- manyalawy_ach-migration, 10 hours ago, 9 messages
hidden mango
hi! note there are two "ACH" integrations, ACH Debit(customer gives your their bank details, you charge them), and Credit(you provide a bank number to the customer, they do a wire to them).
But in any case we are deprecating the older ACH Credit implementation yes, hence the email.
clear bisonBOT
terse bear
Still a bit confused here, what are the changes I need to do here 😅
vapid fern
Start here essentially: https://docs.stripe.com/payments/payment-methods/transitioning
ACH Credit overall is not a PM that has migrated to the new APIs though
terse bear
This page says that I need to integrate to the payment methods or payment intents API in general. I need the exact scope of changes that I need in order to changes without a large regression
vapid fern
The doc has links to various migration option guides that use our new APIs and UIs. But, as stated, ACH Credit overall is not available on the new APIs – Bank Transfers are likely the most comparable (e.g. customers send money to you): https://docs.stripe.com/payments/bank-transfers
terse bear
If ACH Credit is not available on the new APIs how am I supposed to migrate it ?
vapid fern
You'd migrate to use Bank Transfers which is fundamentally the same
terse bear
Okay so we can't use ACH credit transfers anymore is that correct ?
What I did was that I used the payment intents API instead of the Charge API and thought that this was the only change I had to do
vapid fern
Okay so we can't use ACH credit transfers anymore is that correct ?
After the deprecation date mentioned, yes
vapid fern
What I did was that I used the payment intents API instead of the Charge API and...
No, Source objects are being deprecated entirely. ACH Credit is built on top of that API and we haven't re-built it
terse bear
So I need to migrate completely from the Sources API even for cards right ?
vapid fern
No, cards are not being deprecated (yet). They're still backwards compatible with the newer APIs as the doc outlines
terse bear
So all I need to do know is to migrate the usage of ACH credit transfers
Also I have another question, I am currently using plaid to generate a token when the customer tries to add ACH as a payment source. Since we don't want to depend on the sources API, what should I migrate to given that I use Plaid.
gloomy monolith
hi! I'm taking over this thread.
if you follow our new ACH Direct Debit documentation, then you no longer nee dot use Plaid: https://docs.stripe.com/payments/ach-debit
terse bear
Hello, isn't this documentation for debit? The email sent to me is regarding Credit transfers
gloomy monolith
sorry I may have misunderstood your question. in the past, to accept ACH debit you need to use Plaid, but it's no longer the case.
so can you clarify why you want to use Plaid?