The shopper has tapped. A few seconds later the register returns to the basket, but the terminal screen showed a spinner long enough to make everyone unsure. That is an unknown result, not proof of a decline. The reply and the payment are two separate things: one can go missing while the other is recorded.

Keep the original sale in view

Say what you can verify: “The register hasn’t shown me the result yet. I’m checking the first attempt so we don’t run it a second time.” Follow the lane’s status or transaction-search flow, or call the lead responsible for that system. Use the original sale reference, approximate time, amount and lane where the store permits. A notification in the customer’s app can help explain why they’re worried; it is not the merchant’s transaction record.

  • Approved and tied to this sale: follow the merchant’s workflow to finish or recover the sale once. Where there are two screens, the lead may need to reconcile them first.
  • Confirmed unsuccessful: retry only when the store’s documented procedure allows it and the shopper agrees to the new attempt.
  • Still unknown: leave the case open in the approved system. Don’t substitute a receipt from a similar sale, or guess that a silent terminal cleared the original.

A lane handoff worth reading

Training example: “4:12 p.m., Lane 2, $18.54, sale REF-TRAIN-118. POS says response missing; terminal result not verified. No second attempt. Lead checking original.” Give the next person a clear state and a clear owner. No customer identifiers or card digits are needed in the practice note. For a properly scoped paper record, see Find the receipt without collecting card data.

The Adyen terminal status guide documents an integration that checks the original transaction after a missing or timed-out response. Its integration-specific timings and fields are not universal thresholds for cashiers. The distinction is what transfers: verify before you repeat.