#irene_92049
1 messages · Page 1 of 1 (latest)
Hi 👋
If you are just getting started then I would recommend not using the createToken functionality and instead make use of our Payment Element for collecting card details.
I'm using Stripe elements for data collection. On the frontend, I am only collecting the token so that, once the internal information is validated in the backend, I can make the charge using the card token.
Okay but Tokens are not the recommended flow. We do have a current workflow that will allow you to first create a Payment Method object and later use that in a payment. What internal information are you validating?
the item he tries to buy is still available.
Ah okay that sounds like exactly why we built the "finalize on server" workflow: https://stripe.com/docs/payments/finalize-payments-on-the-server
It is designed to collect the payment method information but only finalize the payment after your server performs additional validation
Thank you!, I'll check it.
what is wrong with our implementation using "create token"? Is it Old?, or what could happen if we are using that way?
Correct, it's old and doesn't support newer security features.
Using the createToken method https://stripe.com/docs/js/tokens/create_token?type=cardElement means that, at best, you are using our Card element. This works but it isn't a fully functional as our Payment Element
You can see a comparison of the two products here: https://stripe.com/docs/payments/payment-card-element-comparison
Thank you @toxic flint!