#jasonj-moto-paumentintent

1 messages · Page 1 of 1 (latest)

ionic lava
modest totem
#

Amazing, thanks for this, not sure the business would want me turning it off if I don't have to. I will try it in test mode though! I did contact support and they said they would get back to me and suggested i asked here. I will try your solution and let you know how it goes. Thanks

#

it seems turning it on in test mode also enables it in live mode

ionic lava
#

yeah that warning is mostly to avoid many people just sending raw PANs and not realizing the risk. But I assume you're going to send raw PAN's in Live mode too if you want to do MOTO and collect card details yourself right?

modest totem
#

If there is no other option, the documentation says i have to do it all in one API call and send the card details (as they may be one off customers)

#

it worked perfectly, thanks for your help!

ionic lava
#

yay!

modest totem
#

i've turned it off until the business can make a decision. but i all depends if there are any other options

ionic lava
#

How are you collecting card details for MOTO? Do you have agents in a call center entering card details dictated on the phone?

modest totem
#

yep, and recently the payments require sending a code to the customers phone, which is not great

ionic lava
#

So you should build a UI using Elements to collect card details and your agents at the call center enter card details in our internal payment page. And the PaymentIntent is configured for MOTO and it all works

#

so really you never need to send raw card details in that case

modest totem
#

yes, we have it currently using our ui which then creates a paymentIntent, the stripe 'box' (card element?) then loads and the card details are entered into that and then the paymentIntent is confirmed. But now we have to do it all in one call (for MOTO payments), so i am going to collect the card info in our ui and send the api call to stripe with the card details

#

can i load the stripe 'box' without creating the paymentIntent first?

ionic lava
#

you don't have to do it all in one call at all, this is a misunderstanding really

modest totem
#

if i am using moto, then i must use confirm=true?

ionic lava
#

The docs clearly cover this
1/ Create a PaymentMethod client-side for the card details
2/ Create a PaymentIntent and pass the moto flag + payment_method: 'pm_123456' + confirm: true

#

You have to build it custom for this flow, where you use the card Element for this to collect card details entered by your support agents

#

but the flow works the same and you really don't want to handle raw card details since it'd drastically change your PCI compliance requirements

modest totem
#

OK, I will try this, thanks. If i create the payment method, do i need to give it the id 'pm_123456'?

ionic lava
#

not sure what you mean?

#

but step 1 creates a PaymentMethod and that PaymentMethod has an id (we generate it) and then you pass that id when you create/confirm the PI at step 2

modest totem
#

gotcha, i will try tomorrow, you've been a great help, thanks!

ionic lava
#

Of course, sorry for the confusion, I know our MOTO docs could be a bit more concrete/explicit