#ben-curthoys_docs
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1345003420938928159
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
In an ideal world, there would be a flag I could set somewhere on the Payment Element integration to say "this transaction is MOTO", and then inappropriate payment method types would be hidden, and the SCA checks would be skipped.
yes
demo site is at https://www.starkadder.org.uk/sales
and you're using the same site internally and externally right?
yes
so in the old version, the same payment form was used for the public in eCommerce mode and by staff for telephone orders with the MOTO flag set.
it seems that with the payment element version, MOTO transactions are not possible. I just want that confirmed before I spend any more time trying to make them work ๐
yes MOTO is not supported on the paymentElement
I'm thinking of a better solution for this give me a few minutes please
ok!
I believe that Stripe Terminal can be used to process MOTO transactions, but people don't want to have to buy hardware for people working in the back office away from customer present transactions.
yes that's correct
I think there's a way to combine both
I'm testing this out and will let you know
that's great
I'm sorry what I had in mind didn't work
ok well
the old card element works fine, so no big problem
if there's a feedback form can you add a note to say that better MOTO integration for the payment element would be nice?
i understand the barriers are largely regulatory rather than technical.
pesky SCA laws etc.
yes I don't think this is something we're looking to change in the PaymentElement as it is suppose to be used by end customers directly