#hendie_mytime

1 messages · Page 1 of 1 (latest)

rugged estuaryBOT
true kettle
#

Hi, that is correct. With MOTO payment, SCA is waived, https://support.stripe.com/questions/mail-order-telephone-order-(moto)-transactions-when-to-categorize-transactions-as-moto. On your second question, handling raw pans is not recommended, https://support.stripe.com/questions/manually-entered-card-payments. We talk about both of these here, and after reviewing these documents please let me know if you have any further questions. Also, we are happy to help with any integration related questions and anything outside of this, you would need to write in to our support team.

elder burrow
#

I will read what you linked to, but fwiw I did not mean PAN, rather a one-time-pin.

#

the two articles you linked me to does not answer my questions, please advise

true kettle
#

Do you have an example where a MOTO payment persists in asking for SCA?

elder burrow
#

no, I am reacting to a statement on one of your YouTube videos that said a bank may not honout MOTO - so my question is about that. What response can we expect from the bank in such a case?

#

and is it a flat decline then, or is there another way to mitigate in such a case?

#

.. and I would also welcome an answer to 2. above please

true kettle
#

I see, let me look through some documents on my end. Thank you for your patience.

elder burrow
#

thanks

true kettle
#

If a payment intent needs SCA, they fall in 'requires_action' status and provides next action, https://stripe.com/docs/payments/3d-secure#manual-redirect. In cases where SCA is required even with MOTO because the bank requires it, you'd need to handle this on your end. SCA emails only work for Stripe Billing, https://stripe.com/docs/billing/migration/strong-customer-authentication and for one time payments, there is not such a setting to send emails to complete 3DS.

For your second question, are you able to reword it? I do not think I fully understand the question.

elder burrow
#

For the second question, the customer is at the web page, on a web store, and keying in their card, in those cases we do not want it to be classified as a MOTO transaction. What flag if any can be set in the API call to create the PI, to indicate that SCA and not MOTO rules should be followed?

#

so it's a customer vs. merchant initiated charge

true kettle
#

Ahh I see what you're asking. To flag a MOTO payment, you'd need to pass in specific paratmeters aftering contacting support to enable this feature on your account. Once your account has access to this, you'd flag MOTO payments with this parameter:

payment_method_options: {
card: {
moto: true,
},
},

If they are not MOTO payment, you would not pass this and that tells us that these are not MOTO payments.

#

Does that answer your question?

elder burrow
#

yes! absolutely. Thanks!

#

here's a follow-up

#

if in the case of the merchant entering the card, we get requires_action, we send the client an email/sms with a link to our own app, with a button to verify - which will do the client-secret driven sca follow-up, now on the client's browser

#

make sense - and could it work?

true kettle
#

Yep, that works.