#özgür
1 messages · Page 1 of 1 (latest)
hello @thin lake, it looks like that sample is creating Tokens which doesn't support 3DS. Note that Tokens and Charges API is deprecated and you should use PaymentMethods and PaymentIntents instead. We don't have any official documentation for using it Stripe with Vue, but here's a general guide : https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements
hey alex, tnx for reply. I have stripe.subscriptions.create function in server-side. However, the approach you sent is want me to fill amount and currency i. that's why, it is not what I want.
actually, if there is a way to enable 3d secure to paymentMethods.create method. It would be really awesome.
are you already using PaymentMethods and PaymentIntents?
I'm using paymentMethods
alright, and how are you collecting the card details to accept payment for the subscriptions?
client send raw credit card details to server and they passes as parameters to paymentMethods.create
We actively discourage you from using the Stripe API directly to tokenize the cards because by handling raw card numbers directly you become subject to the full PCI compliance standards. In your case this means you’d have to submit a SAQ D form annually to prove that you are PCI compliant : https://stripe.com/docs/security/guide#validating-pci-compliance. It’s a 40 page form and that's not a headache most people want to be dealing with.
Are you already PCI compliant?
Usually, you should use Stripe Elements / Checkout instead. The library creates an iFrame which points to a Stripe domain, meaning that the raw credit card numbers never hit your system so you don’t need to be PCI compliant, Stripe does all that for you. You still get back the tokenized card for use on your backend.