#kieran-mackison_api

1 messages · Page 1 of 1 (latest)

rigid smeltBOT
#

👋 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/1429780413873918012

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

vagrant flare
#

Do you have an example payment you can share? pi_abc ID preferably

echo plinth
#

Probably should add that both us and the client are UK based, as are all transactions with customers, so it is an SCA region

vagrant flare
#

MOTO payments are SCA exempt so assuming that the parameter is set correctly they should bypass need for auth

#

But need an example to see how you're creating/confirm the intents

echo plinth
#

2 secs, let me grab that. I think we have examples through the checkout approach, but not real ones through the paymentIntent approach. Would test card payment IDs still work for you to check?

vagrant flare
#

Hmm I think a live example from an actual customer can help so I can look at exactly why 3DS/auth was triggered

#

When you say 'checkout approach', does that mean Checkout Session?

echo plinth
#

Yeah that was the approach taken originally, which having read the docs now I don't think makes sense, hence the new attempt at paymentIntent

vagrant flare
#

Not sure why you'd init a MIT payment with Checkout as it requires the customer be on-session. You can't set/pass MOTO there

#

Payment Intent should work though, but assuming it's being done correctly of course

echo plinth
vagrant flare
#

Go ahead and share a test one if you have it to hand

#

At least then I can see the parameters you're setting

echo plinth
#

Test Payment plan - pi_3SJGgcPsm2Exc1pK045fzm9h

vagrant flare
#

Hmm, this is a PI created in test mode but used a real card?

echo plinth
#

That should have just used the 4242 4242 4242 4242 card

vagrant flare
echo plinth
#

Grabbing a real one shortly, just waiting on them to come back with the OTP

vagrant flare
#

In any case, I don't see the MOTO param on either create or confirm?

echo plinth
#

Okay bear in mind I'm not a pureDev, and I'm picking this up from someone who has done the work and left midway through so I apologise if I don't get everything. I'm assuming a real example will have the same issue then?

pi_3SKGj7LiFNhGHNik1HImcDdc

vagrant flare
#

Yep, not set there either. FWIW, that account (acct_188QGxLiFNhGHNik) doesn't have the required access for MOTO. So you'll need to speak to support about that

echo plinth
#

Damn, I thought that was done as a pre-req prior. Okay thank you, so I need to get that setup as a pre-req first and make sure the payment_method_options[card][moto]: true param is passed as well and then it should work?

rigid smeltBOT
royal wagon
#

Yes, that's correct, along with confirm: true as described in those docs

echo plinth
#

While I've got you, because the client account manager believes he asked for MOTO to be enabled on all of their accounts, are you able to confirm which of these have the pre-req setting enabled and then I can get him to pass it to support:

acct_1LDQYDLmEGunLtqQ
acct_188QGxLiFNhGHNik (Confirmed not working above)
acct_16BWmwDWdyZXKPET
acct_1PG0KpFmURsFLQZg

royal wagon
#

It looks like just the first account (acct_1LDQYDLmEGunLtqQ) is enabled for MOTO

echo plinth
#

OK brilliant, thank you so much for all of your help! Have a great day

royal wagon
#

Thanks, you too!

echo plinth
#

Is there any way to ask those to be enabled from here or do I need to get our client account manager to go through the support channel for that?