RON WAFFLE

[tender mural]

Payment Element has collected card details for you. Why do you need it in MOTO?

[patent bone]

It's for certain scenarios in my business. I was just wondering if it's possible to tell the payment element it's a MOTO payment and get then use that for my process. I just wanted to use it for ease of use with card validation etc

MOTO is exempt from SCA and therefore 3ds as I'm sure you know, so we use it for certain things

[tender mural]

If the customer is in the session to fill in the card details, you shouldn't set it as MOTO to exempt SCA

[patent bone]

They are not in the session

This would be used by our staff, it's a breakdown/accident recovery business so sometimes payments have to be taken over the phone. We cannot ask customers to enter a checkout flow when they are in a car accident or broken down

so take those payments over the phone

I was just wondering if the implementation was possible using the iframe, for validation etc

[tender mural]

I see! In this case, you may set the Payment Intent to moto as how you integrate MOTO without Payment Element. There shouldn't be any difference between Payment Element and direct API integration

[patent bone]

Ah I see

so just pass the payment intent without payment_method_data?

and then use that client_secret in the payment element to capture/charge the payment method

[tender mural]

Yes!

[patent bone]

and obviously without 'confirm => 'true' anymore?

I will test it out anyway, thanks for the help

[tender mural]

yup, without confirm: true