#omah-Intents
vivid torrent
👋 happy to help
you could use Checkout in setup mode
when you say application do you mean a mobile app?
urban notch
Hi, can you just take a quick look at this https://application.kafene.com/applications/new
When someone can creates an application, he add their routing and account number, after clicking on create application, we create the customer and save the bank details on the server side.
vivid torrent
you are creating Custom Connect Accounts and not customers right?
or am I missing something here
ok nvm what I said, I misunderstood the form you sent me.
how are you creating the payment method?
urban notch
The customers can manually input their bank details in the form along with other data e.g, email, first name, etc. We call create customer API to create that customer on stripe with their name and email.
We then use the customer Id returned from the stripe to create a customer source with the bank details sent from the client stripe.customers.createSource
This adds the customer's payment method (bank number and routing number) to the customer's file on stripe
vivid torrent
what seem to be the issue for you?
urban notch
We now want to use setupIntent to add the customer payment method to the customer file so we can use payment intent API subsequently to bill the customer with the payment method saved. The flow of the setupIntent requires that the server creates a customer, and gets the client's secret key which will be sent to the Client to add the payment method.
To follow this flow, we might have to change our flow and this is something we are not ready to do.
Is there a way to save the customer's bank info without setupIntent, and then use paymentIntent API to bill the customer in the future with the saved payment method.
flat narwhal
no, there's not, you'd have to migrate to the current flow. If you're not ready to do that you can continue use your existing integration of creating Customers with Sources and charging them later with the Charges API until you migrate.