Best practice payment flow with edge cases per provider about django-payments

[mariofix]

Hi @havard024 Thanks for your question, we're in the process of updating the provider for Stripe (payments.stripe.StripeProviderV3),
One of the main change is the use of Checkout Sessions, it handles by default the Creation using the API, and Payment Confirmation, Expiration, and Refund of each payment using Webhooks.

By using Checkout Sessions in my projects I got rid of the problem you're describing, but I'll make some more tests to see if the idempotency key is needed regardless.

[havard024]

Hi @mariofix thanks for the quick response.

From my experience, the idempotency key helps for cases where client application are able to send two requests to server to create a session. eg a user clicks on a button twice, it can be fixed by disabled the button client side.

I've tried the StripeProviderV3 already and it works like a charm, I believe creating a session for each payment / checkout solves the majority of cases. Looking forward to see finished product!

[mariofix]

Hey @havard024 they are enabled by default 😃 Automatic Retries

[havard024]

Hey @havard024 they are enabled by default 😃 Automatic Retries

Well that makes the job at lot easier 😄 Thanks for looking into it!