#jacob_rino_5
1 messages · Page 1 of 1 (latest)
All of our payment UIs and APIs handle 3DS/auth as standard. How are you integrating?
@sick stag
I access via the stripe api on php.
When I try to make a code on the subscription of a monthly product, every month, do we have to create our own confirmation interface?
Does stripe require you to confirm the card if it is in 3DS only?
Or does stripe ignore the 3DS, and the payment is made correctly without a confirmation event?
How are you collecting payment information from your customers?
First I created a payment interface, to retrieve the user's card and link it to a customer, then I created a subscription specific to this user, with the default card.
My question is just simple, on the 3DS, if we have a card that can only be used in 3DS, every month, does that require authorization from the customer every month?
@sick stag
Which 'payment interface'? You need to give me details of which APIs/UIs you're using
My question is just simple, on the 3DS, if we have a card that can only be used in 3DS, every month, does that require authorization from the customer every month?
Not necessarily, but it can happen that off-session payments will require 3DS/auth. Our APIs are optimised to prevent that but banks determine whether auth/3DS is required on each payment. Your integration needs to account for that
A sessionless payment is a payment that is just on the back-end side? so no need for a front interface?
@sick stag
Please don't @ me, I'll come back to your questions when I have a moment
An off-session payment is a payment initiated by you (the merchant) when the customer is not present/online in the checkout/payment flow
So they're common in recurring/subscription payments
You should be able to test this 3DS/auth off-session scenario with a test clock: https://stripe.com/docs/billing/testing/test-clocks
Thanks, i will resend you another question if i have..