E-commerce
July 1, 2026
A customer may see a pending hold on their account before the order is shipped or even after a failed attempt. They often refer to it as a charge, when it may actually be a temporary bank authorization.
The chatbot should explain the difference between authorization, capture, and cancellation. It must check the order status, reassure without promising an exact banking timeframe, and escalate cases where an amount seems to have actually been captured without an order.
This guide explains how to handle bank authorization questions with an AI chatbot, reducing anxiety around payment.
Summary
Why is bank authorization misunderstood?
On a bank statement or banking app, an authorization can look like a charge. The customer sees the money as unavailable and thinks the store has collected it.
The chatbot should explain that the authorization is often used to verify that the payment can be made, while the capture represents the final debit based on the status of the order.
For the customer, a blocked amount is already a concern. The chatbot must explain precisely what is confirmed.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
What information should be checked?
The bot must verify the order, payment status, date, amount, method used, checkout attempt, and the existence of any cancellation or failure.
It must also distinguish between temporary authorization, validated capture, refund, cancellation, and double attempt.
How to explain simply?
The chatbot can say: "An authorization temporarily reserves the amount. The final charge only occurs if the payment is captured depending on the order status."
It should add that the disappearance of an authorization often depends on the bank or the provider, not solely on the shop.
This explanation should be given early, as the customer may decide to retry a payment. If they do not understand the difference between a pre-authorization and a charge, they risk making multiple attempts and seeing several temporary amounts appear.
What to do after a cancellation?
If the order is canceled before capture, the authorization may be released automatically after a banking delay. The bot can explain this concept and verify whether the store indeed canceled or did not capture the payment.
It must not promise that the amount will disappear immediately from the banking application.
When does the subject become urgent?
The matter becomes urgent if the customer sees a confirmed charge without an order, multiple blocked amounts, an amount higher than the basket, or an authorization that does not disappear after the announced timeframe.
In these cases, the chatbot must transfer with the amount, the date, the status, and a masked proof.
Which flow to follow?
The flow must separate what is visible on the bank side from what is confirmed on the order side.
Identify the order, attempt, amount, and payment method.
Verify status: authorized, captured, canceled, declined, or refunded.
Explain the difference between a pre-authorization and the final charge.
Indicate the standard timeframe for the authorization to disappear.
Escalate captures without orders, mismatched amounts, and exceeded timeframes.
Which messages should be used?
To explain: "The visible amount may be a temporary authorization, which differs from a final charge."
For a cancellation: "If the order has not been captured, the release often depends on banking processing times."
For a dispute: "If the amount appears to be debited without an order, I will forward it to payment support with all the relevant details."
When to transfer?
Transfer is necessary if a payment appears to be captured without an order, if the release time has expired, if multiple authorizations appear, or if the customer provides bank proof.
The bot must transmit the amount, date, method, order status, attempt, error message, and masked proof.
Which KPIs should be monitored?
Track disputed authorizations, captures without order, cancellations with fingerprint, exceeded time limits, bank proofs and payment transfers.
This data shows whether the checkout explains the payment status well enough.
Which mistakes should be avoided?
Avoid promising an immediate release, confusing authorization and capture, asking for a full statement, or downplaying a blocked amount.
The chatbot must explain accurately, as the client is talking about their available money.
How can Qstomy help?
Qstomy can connect the chatbot to accounts, orders, payments, security statuses, and support rules to answer clearly, then transfer sensitive cases with an actionable summary.
The chatbot helps the customer move forward without exposing unnecessary data or bypassing protections related to the account or payment.
Explore AI support, the AI sales agent, or request a demo.
Key takeaways
Key Takeaways
A bank authorization must be distinguished from an actual capture and a refund.
What the customer must understand
The customer must understand why an amount may be blocked and when the delay becomes abnormal.
The right limit of the chatbot
The chatbot can explain and check the status, but it must transfer captures without orders, inconsistent amounts, and exceeded delays.
Enzo
July 1, 2026
