#unibit
1 messages · Page 1 of 1 (latest)
Hey there
Are you following a specific guide here?
Overall creating a Token client-side is our legacy integration
Can you tell me what you are trying to do exactly and maybe I can help guide you with our recommended path?
Okay so the recommended flow here would be to use Payment Element and confirm the PaymentIntent client-side as opposed to creating a Token. Basically following this flow: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements
yes, but this is .net MVC sample, as i said we are having simple asp.net web forms
we got samples from your git repository here
but these samples does not include server side implementation
Gotcha, overall those samples are pretty old but they do work
I'd recommend using createPaymentMethod client-side instead of createToken as that is our newer API
Then you create/confirm a PaymentIntent on your server and pass the PaymetnMethod ID to that to create the payment.
https://stripe.com/docs/api/payment_intents/create is the API you use server-side
really cant follow you, do you provide full samples client and server side
We have samples in our docs. But we don't have samples of creating a PaymentMethod via Stripe.JS as that isn't our recommended flow.
You can see a full sample with Payment Element for instance here: https://stripe.com/docs/payments/quickstart
Or with Card Element here: https://stripe.com/docs/payments/card-element
actually after very many tests we manage to have a working prototype of what we need but the problem is its impossible to style the card element