E-commerce
July 1, 2026
A bank pre-authorization can worry a customer when they see an amount blocked even though their order is not confirmed or a payment has failed. They may think they have been charged twice, even if the money has not yet been debited.
The chatbot must explain the difference between a temporary authorization and a confirmed payment, check the order status, and direct the customer to their bank or support when the delay becomes abnormal.
This guide shows how to use an AI chatbot to answer questions about bank pre-authorizations calmly, accurately, and transparently.
Summary
Why does a bank pre-authorization cause concern?
On the banking application, an authorization can look like a debit. The customer sees an unavailable amount and does not know if the shop has actually collected it.
The chatbot must start by clarifying the words. A hold, an authorization, and a captured payment do not mean the same thing.
The customer does not need a banking lesson: they want to know if their money is withdrawn, blocked, or soon to be released.
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 status, amount, attempt date, payment method, capture status, any potential payment failure, and the usual release times.
It must never ask for the full card number, the CVV/cryptogram, or a bank code. Sensitive verifications must go through a secure area.
How to explain simply?
The chatbot can explain that a bank pre-authorization temporarily reserves an amount to verify that the card can pay. If the order is not finalized or if the payment fails, the authorization is generally released by the bank after a delay.
It must specify that the exact delay often depends on the bank, even if the shop has canceled or not captured the payment.
How to distinguish between a double charge and an authorization?
A true double charge means two payments have been captured. A temporary authorization means an amount is blocked but not captured. The chatbot must verify internal statuses before responding.
If two orders exist or if two captures appear, it must be escalated to payment support.
What should I do if the amount remains blocked?
The bot can indicate the usual timeframe, advise checking the bank statement description, and then offer a transfer if the authorization exceeds the normal duration or if the bank requests proof.
It can provide a useful summary: date, amount, order status, and known payment status.
Which flow to follow?
The flow must reduce panic before escalating.
Identify the order, date, amount, payment method, and concerned attempt.
Check if the payment is captured, failed, canceled, or only authorized.
Explain the difference between a bank authorization hold and an actual charge.
Provide the usual release timeframe based on the available information.
Escalate double captures, abnormal delays, disputed amounts, and bank statements.
Which messages should be used?
To reassure: "This amount may correspond to a temporary authorization, not necessarily a confirmed debit."
To explain: "The release often depends on your bank once the authorization is cancelled or expired."
For security: "Do not share your full card number or bank code in this conversation."
When to transfer?
The transfer is necessary if two payments are captured, if the amount remains blocked beyond the normal period, if the bank requests proof, if the order cannot be found, or if the customer formally disputes the payment.
The bot must transmit the order, amount, date, payment status, visible captures, bank message, and customer request.
Which KPIs should be monitored?
Track authorization hold requests, failed payments with authorization, confirmed double captures, release delays, payment transfers, and prevented disputes.
This data helps identify the payment journeys that generate the most confusion.
Which mistakes should be avoided?
Avoid saying "you have not been charged" without checking, promising an immediate release, asking for card data, or ignoring a genuinely duplicated capture.
The chatbot should explain with caution, as the customer's banking perception may differ from the merchant status.
How can Qstomy help?
Qstomy can connect the chatbot to the catalog, technical constraints, payments, T&Cs, help bases, test scenarios, and reassurance rules to answer clearly, then transfer sensitive cases with an actionable summary.
The chatbot helps the customer make a decision without inventing compatibility, bank validation, legal interpretation, test result, or commercial promise that has yet to be confirmed by a reliable source.
Explore AI support, the AI sales agent or request a demo.
Key takeaways
Key Takeaways
A bank print must be explained by distinguishing between temporary authorization, captured debit, and failed payment.
What the customer must understand
The customer must know whether the amount is debited, blocked, pending release, or to be verified.
The chatbot's correct limit
The chatbot can reassure and verify simple statuses, but it must transfer double captures, abnormal delays, and bank proofs.
Enzo
July 1, 2026
