#mursk_api
vital wolfBOT
đ 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/1272905318690586685
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
umbral bramble
Correct, in that call you are passing the token to the source parameter on the Customer. That will create a Sources API source, so we do reccommend migrating your flow to one of our PaymentMethod/PaymentIntent based flows.
And you aren't seeing /v1/customers/cus_123/source because this call uses a different path. It will show up in your logs as POST /v1/customers
jolly ledge
@umbral bramble Got it! That makes sense - thank you. Have a couple follow-up questions if you don't mind:
1.) My solution to the above was to instead call stripe.confirmUsBankAccountSetup from the client using a SetupIntent provided by the server. My understanding was this would result in the creation of a payment method rather than a source. However, I'm getting a bit confused on the terminology here. The docs say that method is for creating an ACH Direct Debit payment method, while the documentation for migrating (https://docs.stripe.com/payments/customer-balance/direct-sources-migration) says I should be using USD Bank Transfers. Am I on the right track here or would my solution implement the incorrect payment method type?
2.) With regards to removing ACH Credit Transfer (the legacy one that results in a Source) from our Stripe generated invoice payment pages, that's just completed in the Dashboard settings right?
umbral bramble
The confirmUsBankAccountSetup solution is the correct one for ACH DD. That doc is actually for a slightly different push-based payment method (for both the source and the payment method version mentioned in that doc) where you would give the user virtual bank account info and they would send money to the virtual account. This is the closest doc that I can find for ACH DD but it isn't an exact match
https://docs.stripe.com/payments/ach-debit/migrating-from-charges
It may just be easier to follow our doc on saving ACH DD payment methods from scratch
https://docs.stripe.com/payments/ach-debit/set-up-payment
jolly ledge
Okay cool, but just to confirm, is ACH DD essentially the same thing (maybe a subset) of "USD Bank Transfers" outlined in the migration guides?
umbral bramble
Unfortunately not. ACH DD is a pull-based payment method. Kind of like a credit card where you charging the user results in Stripe reaching out to the bank and asking for them to send us $X. The bank transfer-flows are push-based, so the one where the customer logs in to their bank website and puts in a bank and routing number to transfer their funds to.
And to be clear, both of these exist in the sources API as well, it isn't a payment methods vs sources thing. ACH DD is the payment method equivalent of the flow that was being used in the API calls that you sent me
And wow I actually never realized that it is kind of confusing that banks are transferring funds in all of these scenarios but only one of them (and a lesser used one at that) is actually called bank transfers
jolly ledge
I see what you're saying, thanks. These types of payment methods exist in both APIs. I just need to get off the Sources API specifically, but whichever payment instrument we choose is up to us.