#shaitan1126-cards
1 messages · Page 1 of 1 (latest)
if you want to save and reuse cards in Stripe, you must create a customer. The cards have to be attached to a customer to be "saved" and "reusable"
Ok, i don't want to be used that card again
Just need to save that card and display to ther somewhere on the website
could you elaborate a bit more on your use case?
Actually, when user pay on the platform for some services then we can show the card list to them and just need to ask to re-enter the cvv only
not the full card detail
in such a scenario, we would require a customer to be created. Otherwise how would you know that it is that particular user's card?
you could be presenting user A's card to user B
If stripe a card Id then we can save that card into our database and later we can fetch full info from that card id from stripe to the detail to user.
It would be a good approach
in Stripe, your use case is what we would typically name as saving and reusing a card
it requires a customer to be created, and the card attached to a customer in Stripe
if you don't want to create a customer, i'm afraid that use case isn't something we support
Yes we know to save cards in customer Id
As in our terms an policy we are not saving user confidential info on our platform
Pleaser concern on this in future, as it would be very helpful to store card using a unique token or a card Id
ah if that's what you're referring to, then yes, you will be PCI compliant if you use Stripe Checkout or Elements. Checkout and Elements host all form inputs containing card data within an iframe served from Stripe’s domain—not yours—so your customers’ card information never touches your servers
you can take a look at this if you want to know more : https://stripe.com/docs/security/guide
No, this not what i am talking about
the card details are tokenized
Where is the exact link of that?
https://stripe.com/docs/api/payment_methods/create - when you create a payment method, the response is a payment method id
you're welcome