#rnash
1 messages ยท Page 1 of 1 (latest)
Hi ๐ making MOTO (Mail Order/Telephone Order) payments requires special permission, it is not something you can just do.
Additionally, you shouldn't be marking payments as MOTO unless they are a mail or telephone order.
Hmm...
I did mention that a few times
It doesn't make sense to me either
I just want to be able to make a card payment passing the raw card data
because my client wants to use a generic card swiper to fill out the customer's card information and I can't do that with the Card element
However, I was specifically given that document link and told to use the MOTO parameter
is there another option?
It sounds like you don't need or want MOTO. If you have toggled the switch in the Stripe dashboard acknowledging that you understand that handling raw card details mean your systems have a higher compliance burden, then you should be set:
https://dashboard.stripe.com/settings/integration
What behavior do you see when you don't use moto?
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Did you toggle the setting in the dashboard?
Can you share the ID of a request (req_123) that encountered the error you're referring to?
sure
one moment
sorry
i need to recreate it
just a little bit longer
req_bbjmQn2nQp2y2t
that's the request id
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
there's the log link
Here's the specific error message: "Sending credit card numbers directly to the Stripe API is generally unsafe. We suggest you use test tokens that map to the test card you are using, see https://stripe.com/docs/testing."
Thank you, taking a closer look.
ok thanks
While I do, have you by chance tried processing a test payment directly on your Platform account using this approach, and if so was the same error encountered?
I have not tried that
as it's not something we ever do
all of our charges are direct charges to our client's connect account with application fees
Makes sense, I'm just trying to think through what could be happening here, and am wondering if it's specific to Connect.
Hello ๐
Hopping in as toby needs to step away soon
Yes, can you try creating a PaymentMethod with raw PAN on the platform to see if that returns a different result?
NP! Take your time ๐
that seems to have worked
Ah interesting!!
is it safe to share the payment intent id?
yup
pi_3MC31iCLzmUGuqoM0rOeIHjJ
yeah I wonder if the toggle for the PCI compliance on the connected account needs to be turned as well
Reaching out to some of my colleagues to see if I missed something minor here
but to me it seems like the request should've worked and not errored out
ok thanks
Ah okay, just checked with a couple of my teammates
It looks like that toggle only affects payments created on the platform account
It won't affect PaymentIntents created on the connected accounts
You'd want to write in to our support team via
https://support.stripe.com/?contact=true
so that they can enable support for raw PANs on direct charges for you.
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
hmm..
I have had several chat sessions with support
but maybe they just didn't know they needed to enable support for direct charges?
Yeah not sure why that happened. I'd recommend writing in again just to make sure.
Only thing I'd flag is that you'd need to maintain PCI compliance on your end if you integrate this flow.
we understand
this is a temporary "fix"
we plan to migrate to Stripe supported card readers asap
I see ๐