#k.shitara
1 messages · Page 1 of 1 (latest)
We suport almost all card companies, as long as they issue cards on major card network like VISA/MASTER/Discover/Amex and other networks per countries like JCB....
As a merchant you don't need to worry about it
I think that often when you make a payment, you may jump to the screen of the credit card company and request a screening, but with the above credit card companies, does that mean that a screening is not required?
Probably you refer to 3D Secure? There are a lot of companies using it and Stripe supports 3DS verification indeed
Above is card network, not credit card companies
Yes.3D Secure.
If I want to implement 3D Secure with Stripe, is there a description in the Stripe documentation on how to do so?
It's automatically handled by most of our SDK. You can just continue implement as you do normally
ie Checkout or PaymentElement, will take care of 3DS in case the card requires
OK. Since we are planning to implement it with a card element this time, it will be handled automatically if implemented as usual.
the legacy Card Element not Payment Element?
Sorry, I'm in the middle of research and don't know the details, but what is the difference between the two?
Are the implementation methods very different?
Quite different. Payment Element is newer, recommended and will auto-handle 3DS
We are planning to integrate it with laravel cashier, and we have heard that if we use laravel cashier, it will be a card element.
Is it possible to support the payment element?
It depends on laravel cashier really
If I use the card element, is it possible to manually insert the 3DS without it being automatically processed?
As a merchant no. It will be displayed automatically based on the card. And we (Stripe) decide it