itadmin

[outer belfry]

Do you have an example payment (pi_xxx)?

[civic plover]

pi_3N6UzKLmSbVG4LEH0BsVDwzQ

Yes here is a recent one i was provided this morning - i can see about others as well.

Our API version is 2018-11-08 as well if this is useful.

[outer belfry]

You need to be processing MOTO payments if over the phone: https://support.stripe.com/questions/mail-order-telephone-order-(moto)-transactions-when-to-categorize-transactions-as-moto

Your integration isn't set up for that so 3DS is being triggered

[civic plover]

Another example: pi_3N5mM8LmSbVG4LEH1CoA5b3J

[outer belfry]

MOTO payments are exempt from SCA so if you integrate correctly 3DS will never trigger

[civic plover]

Make sense - i assume this isn't something we can do on our stripe account but will need to get our developers involved?

[outer belfry]

You will first need to speak to support to have that enabled on your account, and then yes your will need to make adjustments to your integration (pass additional parameters, for example)

[civic plover]

OK - we integrated a few years ago and this has only really popped up recently - the reasoning makes sense however. Suspect a poor integration here.

[outer belfry]

Yeah, SCA enforcement has been steadily rolling out over the past few years

[civic plover]

Yea makes perfect sense - surprised its taken this long for it to crop up tbh. Annoying haha assumed this is something that would have been done appropriately - cheers for the support.

[outer belfry]

np

[civic plover]

One last thing sorry - is there a resource for SCA I can look at with regards to additional parameters that can/should be passed?

[outer belfry]

The MOTO documentation is hidden until your account has been given access. Reach out to support and they should enable it for your account

[civic plover]

Right so parameters to pass is in the MOTO documentation?

[outer belfry]

Correct yep