#Reformedot - fraud protection

1 messages · Page 1 of 1 (latest)

ocean osprey
#

You want to prevent someone from disputing a subscription payment?

shy sequoia
#

Yes, I want the protection on my subscription

ocean osprey
#

You can't prevent someone from disputing a payment

shy sequoia
ocean osprey
#

Oh I see

#

You want to force 3ds?

shy sequoia
#

It's possible to get that?

#

I already have a setup intent that asks for 3ds

#

not sure if its "forced"

#

but that message is not available on the subscription that I create after my setup intent, using the same payment method

ocean osprey
#

Yeah that will only show on transactions where 3ds was used

#

So if 3ds was used on the setupintent but not the sub payment, it won't show

shy sequoia
#

I charge the subscription off_session

#

That's why I use the setup intent via frontend that already needs 3ds

ocean osprey
#

Yeah I understand

#

You can't get that same protection notice though if 3ds isn't used on the transaction

shy sequoia
#

The problem is that I can't verify the subscription with 3ds, cause I charge via backend

#

there's no workaround for that? Like using the setup intent 3ds as protection for the future payments?

#

It makes no sense to show 3ds for setup intents if I can't use the 3ds protection for the future payments

ocean osprey
#

You want the user to have to come back on session and auth with 3ds for future payments?

shy sequoia
#

I already do that with the setup intent right?

#

to avoid users to come back for each subscription charge

ocean osprey
#

It can help but it's still possible for the bank to require 3ds for future payments

#

Let me ask a colleague about the dispute protection though

shy sequoia
#

Okay thanks

ocean osprey
#

I dont' think future payments are protected but want to confirm for sure

shy sequoia
ocean osprey
#
Payments made with saved cards when the customer is not present in the checkout flow (sometimes called “off-session”) may qualify as merchant-initiated transactions. These payments technically fall outside the scope of SCA. In practice, marking a payment as a “merchant-initiated transaction” will be similar to requesting an exemption. And like any other exemption, it is still up to the bank to decide whether authentication is needed for the transaction.```
#

Overall I recommend reaching out to support about this: https://support.stripe.com