#lowell_revetize-bank-accounts
mild spade
Hello! Just starting a thread for you
We made some recent changes to our ACH bank accounts so that they can now be compatible with Payment Methods (hence the "pm" prefix). For the most part, these two flows should be compatible with each other and you can see a bit more detail on the difference between the two here (https://stripe.com/docs/payments/ach-debit/migrations)
What is the error you're hitting?
tropic tundra
Gotcha - so if I'm creating a destination charge - there shouldn't be any issues?
Here's the error:
Raw error: { "error": { "code": "resource_missing", "doc_url": "https://stripe.com/docs/error-codes/resource-missing" , "message": "No such source: 'pm_1Kz5jJGGE3miL3DnZ1GEXyNC'", "param": "source", "type": "invalid_request_error" } }
mild spade
Do you have the request ID as well? (req_xxx)
tropic tundra
req_lSNRu07S2Wsded
Pretty sure that's it
req_JEUe5BmwM3HGmw
You could look at this one actually
mild spade
Instead of setting source: "pm_1Kz5jJGGE3miL3DnZ1GEXyNC" have you tried payment_method: "pm_1Kz5jJGGE3miL3DnZ1GEXyNC" instead? Since these are Payment Method objects, not Sources, we'd expect you to pass them in to payment_method
You can see an example in the docs I linked earlier: https://stripe.com/docs/payments/ach-debit/migrations#create-payment-intent
tropic tundra
What about the customers that have "sources" instead of "payment methods"?
Looks like those docs say that it will work in the payment method parameter?
Is that right?
tight tusk
It can, in some cases (though not all), but here you've got the reverse scenario sending newer payment method IDs on the source parameter. This will never work, it is not supported.
tropic tundra
In what cases will a source not work in the payment method parameter?
Right, okay - so that's why it didn't work - sending a payment method into the source parameter will never work - gotcha
red prism
correct! pm_123 only works as a PaymentMethod on PaymentIntent and SetupIntent.
tropic tundra
And ba_123 or card_123 won't always work in the payment method parameter?
red prism
payment_method: 'card_123' should always work
payment_method: 'ba_123' works as long as 1/ the Bank Account is verified. 2/ You have a proper mandate: https://stripe.com/docs/payments/ach-debit/migrations
tropic tundra
are mandates applicable with destination charges?
I don't know what a mandate is - never done anything with one before. Is it new? Or does it not apply for destination charges?
red prism
Yes they are applicable. It is not new, we've had them for a few years but it is new that they apply to ACH Debit. It's for the PaymentIntent integration which shipped a few weeks ago
tropic tundra
I see
What about if we're manually adding bank accounts through our dashboard and not through the api
?
mandates are still applicable?
obsidian plume
Hello! Taking over and catching up...
Mandates would still apply in that case, yes. You need to collect mandate acknowledgement as outlined here: https://stripe.com/docs/payments/ach-debit/migrations#mandate-acknowledgement