#Kamon
final furnace
latent jolt
Hi this is up to you really
Do you want a hosted solution?
Or are you fine with building your own checkout page
uncut lantern
We already have our own checkout page/process. It's pretty straight forward, only checkout elements from Stripe that we're using are for managing cards/payment methods.
But, we're using the Orders API to facilitate everything from the Stripe side
latent jolt
Got it. So if you want to keep customers on that page, using Payment Element would be the way to go
But if you're fine with redirecting them to a stripe hosted page, checkout is simpler to integrate. You just forgo some customizability since it's a hosted page
uncut lantern
Hmm, that's not quite what I'm asking.
We're currently using the Orders V2 API to create, authorize and capture charges. Same thing with refunds/cancellations.
I'm looking at either using the Checkout Session or PaymentIntents API to refactor to since the Orders V2 API is being deprecated, but I'm unsure of the route to go.
latent jolt
Well Checkout Sessions just use PaymentIntents under the hood
So it's a question of whether or not you want a hosted flow
uncut lantern
Is Checkout Sessions only for the flow being hosted?
latent jolt
Yes, but there's some differences. Like you can define a price/product instead of just the raw amount. And you have access to Stripe Tax and the ability to generate an Invoice
So in some ways Checkout takes away some features (with customizability) but in other ways it adds features
Up to you really
uncut lantern
Gotcha. Can you implement Stripe tax w/o using Checkout Sessions?
latent jolt
You can if you use Invoices
latent jolt
No problem! Same to you!