#Mohammed-3DS
torpid cliff
payment intents while charging and adding card
in some rare cases I may need the charges api
payment method api can solve this matter?
by saving this payment instead of depending on the source api to store cards
waxen axle
The Charges/Sources API can't handle 3DS, you need to migrate to the PaymentIntents/SetupIntents API to handle 3DS properly
torpid cliff
but my system don't really handle the normal e-commerce website
I don't have cart .... etc
my system you should add the card and using in future services but 3ds prevent this?
can you just tell me the difference between payment methode api and card(resource api)
?
waxen axle
So you want to collect the payment methods first before creating charges to your customers?
torpid cliff
yes my idea instead of saving cards , I save payment method for most of the cars because my payments considered (off session payments)
than I retrieve the payment method and do the payment
but can't see if this will work or no
because most of cards auth once than you can use
but some specific cards require auth on each payment (depend on bank)
*cards not cars
waxen axle
I see. Even though you can use SetupIntents API to collect payment method for future off_session payments, the bank can still request for 3DS. So your application need to handle this scenario and bring your customer on session to confirm the payment
torpid cliff
so technically there is no way to only authenticate once the user add the card, than use the card without authentication (if there 3DS required on each payment)?
waxen axle
No unfortunately.