#formigueiro
agile daggerBOT
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.
- formigueiro, 49 minutes ago, 3 messages
slate oriole
What do you mean by " entire payment method was done on the backend side" ?
sick hollow
all the stripe manipulation, for example, stripe.checkout.sessions.... its doing by backend
In this case, on the front end I would send the stripe token
slate oriole
Checkout Sessions are stripe hosted pages that allow you to collect customer's payment method info.
So you don't need to use additional UI elements
sick hollow
But my page has a different form, I won't use your checkout page, don't I need to use UI elements to validate my form?
slate oriole
You said you're using stripe.checkout.sessions.... ??
sick hollow
it the backend..
i have a endpoit to create all checkout, so my question its about front, to validate forms and else
slate oriole
Sorry I don't really follow the flow you're describing.
Is there a guide or doc you're following for this? If so, can you share the link?
sick hollow
something about that
do i still need to use stripe elements on my form even if all the signing logic is in the back?
slate oriole
sorry what is signing logic?
You shared a link to the quickstart guide which outlines multiple payment flows
I'd recommend looking at these docs instead
https://stripe.com/docs/payments/accept-a-payment
They have step by step guide for the flow you want
sick hollow
In this example, the difference is that it does all the stripe manipulation directly at the front
