#bk_ach-sources-paymentmethods

1 messages · Page 1 of 1 (latest)

fiery violetBOT
#

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

📝 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.

opal fox
#

Here's the log ID: req_CyNmXDLkwiYVoE

#

Some more context on this. As I have been trying to fix some errors we were getting, I noticed that our code was trying to grab sources from the customer object by trying to expand sources when we called the customer. So I am trying to re-work that to use paymentMethods instead now, but running into the above error.

half carbon
#

Hi there 👋 seems like you're talking about this legacy flow, where you need to work with Sources instead of a Payment Methods:
https://docs.stripe.com/ach-deprecated#manually-collecting-and-verifying-bank-accounts

Is this a new integration you're building? If so, I'd recommend exploring our current approach for handling ACH Debits:
https://docs.stripe.com/payments/ach-direct-debit

ACH Direct Debit

Learn how businesses can accept payments with ACH Direct Debit.

ACH Direct Debit with Charges

Legacy guide for accepting ACH payments with our older Charges API.

opal fox
#

SO this all started when we migrated off of charges to payment intents so we could implement wallet payments. But I keep finding bits and pieces of legacy code everywhere still relying on old pieces of Stripe, like sources.

fiery violetBOT
opal fox
#

So let me make sure I am understanding this. In order to utilize paymentIntents, we can no longer go through Plaid for ACH payment setup?

half carbon
#

Correct. The Plaid integration was build for Sources and Charges. To process ACH payments on Payment Intents with Payment Methods, with bank account linking similar to Plaid, you'll want to use our Financial Connections solution.

opal fox
#

Gotcha. Thanks for the clarification.

half carbon
#

Any time!

opal fox
#

One follow-up question: Does the current API version with paymentIntents also allow us to still use legacy sources? We use the NodeJS package where you specify a version by date. If I can "fix" our current issue by simply splitting ACH payments from card payments on the backend, I'd like to go that route for now and then migrate us off the older flow later.

cedar galleon
#

Hi 👋

I'm stepping in as my colleague needs to go

#

Existing Source based payment methods will still work but we strongly encourage migration to new Payment Method-based flows

opal fox
#

thank you. I'll try to use the legacy for now, but we'll migrate off of Plaid here shortly. Thanks for the info!