#remonh87-ach
1 messages · Page 1 of 1 (latest)
yes sure: pi_3Kpp1zKNps8ESOf71qYU5deg
the error happens when I call confirmpayment
also made a video of collecting the account
Not seeing any confirmation attempts on that PI
Can you share your code where you call confirmPayment?
I think it is the stripe mobile sdk that throws the exception
my code is :
await Stripe.instance.confirmPayment(
paymentIntentResult['clientSecret'],
PaymentMethodParams.usBankAccount(
billingDetails: billingDetails,
),
I am one of the maintainers of the Flutter Stripe lib and we use the react native sdk as base.
But I can figure out what happened but I want to get the flow right for ach and that is :
- create payment intent
- Retrieve bank account
- Confirmpayment (without providing the routing number + bankaccount since it is retrieved in step2?)
- When needed confirm with microdeposits
or did I miss sth here?
I haven't looked at this in React Native/mobile yet unfortunately, but I don't think "retrieve" is the exact way it works, that's supposed to get handled inside of confirmPayment
I'd have to actually build an ACH integration with our React Native SDK myself(which is on my todo list, sorry) to properly answer you, but in general we'd really need to see your full code, can you share that? Not sure it will mean much since we don't know Flutter but I can look.
no problem at all it is open source : https://github.com/flutter-stripe/flutter_stripe/blob/sync/example/lib/screens/regional_payment_methods/us_bank_account.dart
I want to create a proper flow because else all our consumers of the flutter lib will use ACH incorrectly
if you have an example on ios or android that is a good example I can check that out as well.
yeah I'm just building this on React Native, give me a while
like I said, I don't speak Dart, but that code seems normal enough, there's probably some specific issue like the state is not persisted(since it looks like it's meant to be that you call collectBankAccountForPayment and the Stripe SDK keeps some state which is then used later in confirmPayment)
so probably some specific bug there or something