#lovelock
1 messages ยท Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- lovelock, 5 days ago, 5 messages
๐ happy to help
MOTO is only available when the customer isn't on session
so basically without using the Payment Element form
Ah okay, so we don't want to give these users access to our Stripe dashboard to take these payments - we want to keep them in our own CRM.
What do people normally do here? Stil use the API but create their own method of collecting the card details?
Which is the reason for using Stripe elements really. Okay thanks,
Stripe Elements is targeted for end-customers
I'm just thinking whether there's a way of using MOTO with Stripe Elements in the deferred flow
give me a couple of minutes would like to try that
Thansk!
๐ stepping in as tarzan needed to step away
I'm not sure I understand... MOTO is used when a customer gives you their card details over the phone or basically isn't present in the flow to enter it themselves.
Why do you need MOTO in the flow you are describing?
We have a method of taking payments over the phone, but wish to use the stripe elements form so we can use our existing flow.
The Stripe form provides lots of benefits over us rolling our own
What flow are you using right now?
The intent-first flow?
So you create the PaymentIntent and then send client secret to your frontend to render Payment Element?
Create Stripe Customer
Create Payment Intent
Return the view with the payment intent into Stripe elements
Customer fill in card details
Place order into our system
If no errors with our system, Capture the full amount of the payment intent. If an error, cancel the intent
Gotcha, if you want to use MOTO then you would need to switch to this flow: https://stripe.com/docs/payments/finalize-payments-on-the-server
I thought it would be a case of changing the flow, thank I'll take a read
๐
The simpler thing might be to just render Card Element (https://stripe.com/docs/js/element/other_element) and then use createPaymentMethod() https://stripe.com/docs/js/payment_methods/create_payment_method and then send the PaymentMehtod to your backend for this flow.
So you would technically have two different flows, but this may be simpler than actually changing your whole flow altogether.