Jairo

[gloomy flame]

Hi! Let me help you with this.

Basically you want to lock the customer from creating a new Invoice while they're completing the payment?

[pine dagger]

I don't know which is the correct way. Our flow is as follows:

1. Customer submits the purchase
2. Backend creates invoice and tries to pay it
3. If the payment requires SCA, the flow is interrupted and control is passed to the Frontend
4. Customer completes SCA validation
5. The backend processes the flow again, but this time the Stripe invoice should no longer be created because it is already paid, so it should only assign the purchased items to the account

To prevent a new invoice from being created we have used idempotency key for the call, but the answer to second request says that it still needs SCA (because it is what the first call returned)

This makes us think that it is not the correct way to manage the SCA flow.

[gloomy flame]

If you set up your Payment Method like this, you shouldn't have issues with the authentication for off-session payments: https://stripe.com/docs/payments/save-and-reuse?platform=web&ui=elements

And if it fails for some reason (because of the bank still enforced SCA, for example), you can send a notification to your customer to add a different Payment Method.