tobias-itzel_best-practices

[native totem]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1313722885042601994

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[tired meadow]

Hi! Looking into your question!

You cannot change the authorization period. But it will be easier to understand if you can explain your use case with an example?

[dusk fox]

Example:

US Customer is displayed orderform without tax as we do not yet know the zipcode of the address
Customer initiates express checkout payment flow with clicking on the button
Customer is presented the net sales price because we don't yet have a tax amount.
Customer clicks on PAY
address is acquired from stripe via StripeExpressCheckoutElementConfirmEvent
tax amount is calculated based on this address
total order value is updated due to the application of the tax amount
Customer must be presented and finally confirm the new total amount.

To be able to present the customer the updated total we need to exit the express checkout payment popup but this only closes automatically when confirming the intent which was created during checkout.

So the situation is:
We confirm the intent (The intent is in uncaptured state)
The dialog closes
We can display the updated total amount and confirm button

If the user finally confirms, the intent will be captured directly.
If the user closes the dialog without confirming, the intent will be canceled.

But we need to deal with users who just close the browser or navigate somewhere else.

[untold plume]

Sure I think that's reasonable. You can capture your confirmed PI until 7 days, but you can always capture early if you want

[dusk fox]

The problem is that once the intent is confirmed the amount is held on the customers account and the customer also sees it when looking into the transaction list.

And customers get fearful if the amount is still held although they canceled (or didn't finally place) the order.

Don't get me wrong: We are definitely able to implement an async job which cancels uncaptured intents after a specific period of time

We are looking for an alternative approach which will not require a periodic job for this

[untold plume]

So bank statement is equal to the Confirmation call. Once you call the Confirm Payment API, it will hold the customer amount