#paul_code
1 messages ¡ Page 1 of 1 (latest)
đ 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/1220355862535602198
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- paul_api, 6 days ago, 8 messages
yep
all is working as expected when we have been testing and in production using cards where we have the CVV number, but it's come to light that we don't ask for CVV for mail order orders and if we don't fill in the CVV number the form isn't valid and prevents us adding the card
Yep you can't prevent Payment Element from asking for CVV
So really if you want to not collect CVV then you want to use CardNumber Element instead
ok, we had a look at that but couldn't figure out what we should do after mounting the cardnumber and expiry elements onto the form
is there any documentation around it, everything recent points towards the payment element side
You call createPaymentMethod(https://docs.stripe.com/js/payment_methods/create_payment_method) which tokenizes the details and returns you a PaymentMethod object which you then pass to your backend to create/confirm the PaymentIntent with the MOTO parameters
No docs any more unfortunately as indeed this is the legacy path
ok, so we're calling that after calling elements.submit which is where we're having issues. do we not need to call that down this route?
nice, thanks for that.
We'll give that all a try in a bit thanks. Do we need to be concerned that it's the legacy path?
No it is still supported with no plans of deprecation. We just recommend Payment Element
ok great, thank you for all your help