#unibit - payout
1 messages · Page 1 of 1 (latest)
hi
Could you specify what form or element you are using? Do you mean Stripe Checkout?
we need to automate this process and prefill our clients card details and do the checkout automatically
Quoting here so we have all the contect
yes stripe checkout
Great, thanks.
let me explain our case in detail
we have a PWA web app
and we are using a form to store our clients card details in his phone local storage
Okay so you won't be able to pre-fill the Checkout form with that data.
what we need is when it comes to checkout, we need to pull this info from local storage and fill your payout form
You CAN set up the Checkout session to save the payment method and that will prefill the next time the customer uses Checkout.
yes but we also want this form to auto submit
we do not want any user interaction, is that possible?
This use case doesn't really fit the Checkout product workflow. Can you describe what your ideal payment flow would look like?
very simple
we ask our client his email and then ask him to pay a specific amount, then we move him directly to checkout
at the moment during checkout using your payment form
we dont need our client to see this process at all
Okay, that is a legacy checkout product. We do not recommend using it. Here is a guide for migrating: https://stripe.com/docs/payments/checkout/migration
However, if I am understanding you right, you want your customers to only see this once where they enter their card information and then have it all automatic after that. Right?
yes
Okay so first step, you'll still want to configure your Checkout session (new Checkout, not legacy) to configure the payment intent for future usage as I linked above.
ok then?
Unfortunately you can't fully automate the process with Checkout. And I know this isn't exactly what you want but I do think it's a good idea to allow the customer to provide new payment information.
Sorry, still digging through docs
sorry for the trouble but i think am asking a very simple think😆
But I think offering the single click pay option does go a long way to reducing friction but still provides the customer the chance to update payment methods if, for instance, they got a new card with better rewards
client is register his card on our system
then he fills a box with value to pay and thats it !
next time he logs in, he only have to fill the payment
So when do they register their card in your system? What does that mean? Do you save the card info yourself?
yes
So...are you saying you are storing raw card numbers in your own system?
no, the cards are only stored in customers local storage mobile phone
Still not clear on exactly what you mean. Raw PANs? GoogePay/ApplePay, kind of curious how this works
Well what I would do is use the current version of Checkout, configure it to set up payment methods for future use and allow the customer to save their card, and have them see that screen briefly as they click through the flow.
so, there is now way to bypass the PAY NO button?
Well... you could store the payment method ID that is generated by the Checkout method and generate a paymentIntent in your code using that same payment. method.
ok, thanks for your support
Legacy checkout, what you are using in the screenshot, utilizes card tokens https://stripe.com/docs/api/tokens/create_card
and the Charges API https://stripe.com/docs/api/charges
This is how you could achieve the same thing but it would be much more brittle and prone to failure IMHO.
I know the migrating to a new version of checkout would take some work but you'd be saving yourself a lot of technical debt.