#surgical-charge-migration
1 messages · Page 1 of 1 (latest)
you absolutely should use webhooks, you'll regret it if you don't. Same for charges reall since 5xx and network issues can always happen
but if you confirm server-side then you get a success/failure
we'd love to use webhook for every incoming order, however some of our orders are free $0 payments, but i don't think we can create $0 paymentintents right?
correct you can't
is there a typical pattern for a confirmation page on something like event tickets, where we would do a stripe.charges.create on an order submission, and then redirect them immediately to a confirmation page with their list of tickets. with webhooks & payment intent, it seems like we'd have to poll or tell them to come back later to view their order details?
yeah that's a really common mis-conception overall
you don't need to wait and pool. You know if it succeeds synchronously. You just need to make sure you handle webhooks for the case where something fails. For example the customer loses connection, their bank doesn't redirect them back to you properly, etc.
but if all works well you know synchronously on PaymentIntent confirmation, usually client-side