#chris-payment-failed
1 messages · Page 1 of 1 (latest)
pi_3LAND8KaApx60PlP0qrUvvq4
Okay so this is an ACH Debit payment, which is legacy ACH/old. We don't really have docs for that integration path anymore where you pass the undocumented source parameter with ba_123
I would highly recommend migrating to the newer integration via us_bank_account. See https://stripe.com/docs/payments/ach-debit/migrations
And then you can use https://stripe.com/docs/payments/ach-debit/accept-a-payment?platform=web&ui=checkout#test-integration
ah, from Plaid
yeah I mean it's not really Plaid specific, you could still move over to the new API, you just use a deprecated integration path and you'd get a better experience overall with the newer integration
it's deprecated? it's the only way to integrate Plaid that I was aware of
we get a btok from Plaid then exchange it for a ba_ I believe
is there a cleaner way to do that?
or should we consider replacing Plaid with Stripe's ACH?
cc @dim nest who is taking over
(but basically you can pass payment_method: 'ba_123' instead of source: 'ba_123'
or should we consider replacing Plaid with Stripe's ACH?
You should definitely consider this, as it's an easier all-around experience. For the most part, everything from the API to the support experience is better on Stripe ACH