A customer orders a limited edition print. The shop first checks whether it has a copy in good condition. In the meantime, its payment provider places a hold on the customer’s card. An AI assistant sees that the card was authorised and replies, “You’ve paid and your print is on its way.” The shop has done neither of the things the reply promises. It has not collected the money, and it has not dispatched a print.
The reply may sound like a small wording mistake until the customer sees a pending entry at the bank or asks for a tracking number. Then the shop has to explain several states it could have kept separate from the start. If you use AI at checkout or in customer support, decide which system can confirm each state and what the assistant should say before that confirmation arrives.
Separate the card hold from the order
For an eligible card payment, authorisation can reserve an amount while the business waits to capture it. Capture is the step that collects the payment. Stripe’s documentation on placing a hold explains how separate authorisation and capture work in its system and why the capture window matters. That window varies with the payment method and transaction details. A shop should use the information for the particular payment rather than promising that every hold lasts a fixed number of days.
Authorisation also leaves a separate question unanswered: has the business accepted the order on its own terms? A shop might reserve a print internally before collecting payment, or it might need someone to check the condition of the last copy. A warehouse has yet another question: was the parcel handed over for delivery? One label in a dashboard cannot answer all three. An assistant should consult the payment record for the money, the order record for the seller’s decision and the fulfilment record for dispatch.
In the hypothetical print shop, a useful reply at the hold stage might be: “A temporary card hold is in place while we check stock. We haven’t collected payment or dispatched the print.” The message gives the customer two facts they can act on. It also leaves room for a later update if the shop finds no usable copy. Words like “approved” and “confirmed” need an object: a card authorisation, the order or the shipment.
Plan for the checkout that does not finish neatly
Suppose the shop has a copy, but checks it after the authorisation expires. Stripe’s October 2026 explainer on authorisation and capture describes why an expired hold may require another authorisation. The assistant should not assume the old hold still works or quietly tell the customer that a new payment happened. It should check the provider’s current state and use the shop’s approved process for contacting the customer if a fresh payment step is needed.
A similar distinction matters when the shop cancels. If it never captured the payment, describe the cancellation and the status of the hold once confirmed. If it collected payment and subsequently initiated a refund, describe the refund separately. Avoid giving a date for when the customer’s bank display will change unless the provider can support it in that case. An accurate first message makes later support easier: the next person can see whether they are investigating a hold, a payment or a refund.
Another awkward case is a stale screen. A customer may open the chat while the payment page is still updating. If the assistant cannot confirm the live state, it can say that it cannot yet verify collection and explain what the customer should do next. It should avoid telling the customer to pay again simply because its own view is unclear. Confirming the original transaction first is less confusing than untangling two entries later.
Make the wording part of your checkout test
- Write a message for each state. Cover a hold, a captured payment, a cancelled order and a refund after capture. State what has happened and what the customer should expect next.
- Test an expired or cancelled hold. Check that the assistant sees the current record and stops using wording from the earlier authorisation.
- Test the gap between payment and dispatch. Confirm that a captured payment can produce an acknowledgement without generating a shipping claim.
- Test the missing record. Make the current payment state unavailable in a test environment. Verify that the assistant explains the uncertainty and routes the case to someone who can check it.
MaryChuks.com’s guide to testing an AI agent’s refund and complaint boundary covers the next decision: who is allowed to act when the customer wants a change. Here the first job is simpler. Ask the assistant to describe the current state accurately. For the print shop, the key sign of a good checkout is that the customer knows whether money was collected and whether an order exists, at each stage of the transaction.
Check the handover to a person, too. Give the support colleague the order reference, the verified payment state and the time it was checked, together with a short account of what the customer has already been told. If the provider and the shop disagree, make that visible. The colleague should be able to investigate the discrepancy without having to infer whether the word “paid” came from the bank, the shop or the assistant’s own wording.
Sources
- Stripe documentation: Place a hold on a payment method.
- Stripe: Authorise and capture: How card payments actually move money (updated 16 October 2026).
