#KEITH LARD
1 messages · Page 1 of 1 (latest)
I think so with this flow: https://stripe.com/docs/payments/build-a-two-step-confirmation
i.e. use createPaymentMethod with the Payment Element and then create the PI
Ah I see, so go through that flow to create the payment method, then make the subsequent MOTO api call with that payment method
Yes, as you'd pass the pm_xxx to the payment_method parameter when creating your MOTO PI
sure, np. Hope it works
Do I always have to send an amount through, when collecting the details?
Can you elaborate?
So in this step here, it shows adding the amount, but in my case would I not just want to collect the details, then the amount is determined after in the MOTO call
Ah, I understand now. Yeah Payment Element requires some concept of a payment before it can be initialised (i.e. currency, amount). I forgot that part, my bad
Actually thinking about it I suppose it makes sense in case of insufficient_funds, I was just worried it would charge my customers
Generally we recommend MOTO flows to use the Card Element
Okay cool, is it not possible through the payment element then?
I should be doing this instead? https://stripe.com/docs/terminal/features/saving-cards/save-cards-directly
Not without passing some payment parameters, which is counter intuitive I guess
That's for in-person payments? I thought you were doing MOTO?
I am I just re-read it apologies
I basically want to use MOTO but I want the flexibility of the payment element, for card validation etc
And obviously I'm not sure if I can collect then charge beforehand because this might trigger 3ds if not flagged as MOTO?
What aspects of validation?
Well everything that the payment element does out the box essentially, expired cvc, insufficent funds etc. I know I can get this all from the API I just was wondering if it was possible
incorrect card number, expiry date
expired cvc, insufficent funds etc. I know I can get this all from the API I just was wondering if it was possible
You won't get any of that with the MOTO flow until you try and charge it (i.e. after you've completed the form)
createPaymentMethod just tokenises the card details, there's no card network activity
Card Element will give you basic luhn check validation and date checks, etc.
Ah I see, so using the card element should be fine for collecting the payment method, then can do the MOTO call after
Correct. I have a MOTO example here with Card Element: https://stripe-tinydemos-moto-payments.glitch.me/
A tinydemo to show how to complete MOTO transactions with the Card Element.
thats perfect thank you pal