#wayo-ach-verification
1 messages · Page 1 of 1 (latest)
wayo-ach-verification
hello!
What is the context of this, like are you only collecting ACH details or can the customer choose another payment method?
yes card and ach .
But at the same time? Or do you have a special UI? Sorry I don't fully grasp your flow and we don't really discuss "secret features" like the micro-deposit skip so I don't even know if it works with the Subscription flow
Have you tried creating the Subscription, looking at the first Invoice's PaymentIntent and then configuring that one to skip micro-deposits?
Currently I only have card with the card element and i'm not using payment intents. I am trying to add ACH and move to payment intents.
Are you trying to completely skip FinancialConnections and just collect raw bank account details yourself? I'm still not really following the overall goal/design
Yes that's it.
Okay so you don't use PaymentElement at all?
you just have your own form for bank account routing number and account number collection?
I am prototyping at the moment. I was hoping I could use payment element since it can support many payment methods.
I am using ACH with Plaid, but I want to switch to Stripe.
Okay so what's the problem? Like what happens if you create a PaymentIntent with the skip value and then show it in PaymentElement?
That works fine. It only shows the account number and routing number which is what I want. The issue comes when I try to collect the payment details .
Using the function collectBankAccountForPayment throws an error about using the value skip for the PI.
The function that seems to work is confirmPayment seems to try and charge the customer immediately but I use subscriptions which I create in the following page.
but there's no reason to call collectBankAccountForPayment at all. So I'm trying to figure out what you're doing
The flow should be
1/ Create the Subscription and look at the first Invoice's PaymentIntent
2/ Client-side, collect the payment method details to confirm that PaymentIntent.
That's the canonical flow for integrating Billing today
So I'm struggling a bit with what you are describing. Like if you move to PaymentElement for card payments too you have to completely change your integration first to map to that
Could we keep this chat's history open? I want to read up more on this and get back to you, probably tomorrow.
No, threads are short lived. I'd recommend that you work directly with our support team for long running 1:1 help, especially to use a secret feature like this one. They will be better equipped to help you
Sounds good, thanks!