#ml74_api
pearl emberBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1254809225130020936
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
wintry wind
Hello, yes that sounds like a permissions issue which you would need to work with our Support team to get MOTO properly enabled on your account.
And yes, you can use Stripe.JS to collect the PaymentMethod here and then pass server-side to create/confirm the PaymentIntent with MOTO
That does work just fine
shy hare
I've just spent 2 hours on the phone with a support agent telling me that the Card Element is a form and forms aren't APIs, so that's why it won't work 😭
I think my question is more on whether the permissions are split? i.e. can MOTO be enabled without the raw data API being enabled (which seems to require all of the PCI compliance paperwork)?
wintry wind
Yeah MOTO is passed when you create/confirm a PaymentIntent
Versus you can create a PaymentMethod client-side using Stripe.JS + Card Element without MOTO involved at all at that point
shy hare
Yes, I understand this. By permissions here, I mean the actual account permissions - like feature access to MOTO.
wintry wind
You should not need raw PAN permissions for the MOTO permission, if that is what you are asking?
Those are separate afaik
shy hare
Ok, perfect
One last thing... do you know if MOTO can be enabled platform-wide for Connect?
Assuming we don't need raw PAN. I know that's up to each Connect account to figure out their own PCI compliance docs if that's the case.
wintry wind
Yes it can be enabled so that your platform can use it for any Connected Account (as long as your platform is the one creating the request)