#danitoyy
1 messages ยท Page 1 of 1 (latest)
Hello ๐
Yes just give me a moment to catch up
Oh, no worries ๐ I am just new to the DC
We have a guide on how you can save a payment method during payment process here
https://stripe.com/docs/payments/save-during-payment?platform=web
Have you had a chance to read through it?
I read it through
To be honest with you, I had 0 problems with everything except this one
I didn't understand much
I just need the concrete steps, not that much text ๐
Because at one point it becomes more confusing than helpful
HI ๐
I'm stepping in as @deep sedge needs to go. This document is a series of concrete steps and about as step-by-step as we get. Can you explain what part is confusing you?
Where exactly is the method gonna get saved and after it is saved, lets say I have an endpoint on my backend which retrieved the saved payment methods by email. How do we use them later on
The Payment Method is saved to the Customer
And we have a section of this doc specific to how to charge this payment intent later on here: https://stripe.com/docs/payments/save-during-payment?platform=web#charge-saved-payment-method
Okay, but the idea here is that we don't want to charge the customer without him knowing about it. We want him to pay by himself, but we don't want him to type his card again
Its not a monthly automatic subscription funcionality, it is just a normal purchase, but with a saved card
Okay
So that would be up to your integration
You could have a "Buy" button that just re-uses the payment method ID created from the previous transaction. That would still involve the Customer choosing to pay again but would not require them to enter card information
Thats the part I dont quite understand
So I have to retrieve the paymentMethods, make him choose
Then we send the payment method id to the backend and then what ? I create a payment intent with that ID?
And after that the Element will know that he does not have to write down card data again ?
Then we send the payment method id to the backend and then what ? I create a payment intent with that ID?
That is exactly what is show in the documentation section I shared above
And after that the Element will know that he does not have to write down card data again ?
If you are not collecting card information, you don't need the Payment Element
But all of this is up to you to design currently