#_obo_
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- obo-indiarbi-setupintent, 2 days ago, 34 messages
and I guess a follow up, all of other cards in that testing block simulate an initial acceptance / verification of a mandate / 3ds, yes?
The description for that card is as follows:
Simulates a cardholder receiving a pre-debit notification for an off-session payment either cancelling or pausing the payment for a mandate of any amount.
all of other cards in that testing block simulate an initial acceptance / verification of a mandate / 3ds, yes?
I don't think that is true since the card ending in 0263 states
all of other cards in that testing block simulate an initial acceptance / verification of a mandate / 3ds, yes?
For context here, we're using 3ds as a security mechanism for our platform as payment gates some features that bad actors have abused, so we want to make sure that all payment mechanisms are "legit"
and the bad actors have almost universally used stolen Credit Cards
I think really what I'm asking here is "if they get past the "complete 3ds verification" part of any of these cards, the card has a VERY low chance of being fraudulent or stolen
I cannot speak to fraud risk but one of the reasons for using 3DS is the liability shift that occurs. We mention that here: https://stripe.com/docs/issuing/3d-secure#liability-shift
Basically, after a customer successfully authenticates, it is the issuing bank that is liable for any fraud. But if you want more guidance about securing your payment integration from fraud I would recommend reaching out to Support here: https://support.stripe.com/contact
Thanks for the links. One follow up rephrasing of my question.
Is it possible for stripe to set up a subscription for a 3ds payment method that has not yet been confirmed? (by using the subscriptions.update api endpoint)
I'm not sure I understand how that would work. You would need to attach the payment method to the customer, at which point an authorization with the issuer would be attempted that should surface any additional authentication.