Reviewed October 17, 2026. This practical guide replaces an earlier general overview. The original publication date and URL are retained.
When a payment request times out, the merchant may not know whether the provider processed it. Sending the same customer through another route without checking the result can create duplicate-payment risk.
Define the three outcomes
Use separate labels for approved, declined and unknown. A communication failure belongs in the unknown category until the integration’s supported status check resolves it. Ask the provider which transaction reference identifies the original attempt and how duplicate submission protection works. Do not make a new identifier merely to force a retry through.
Rehearse the interrupted checkout
In a permitted test environment, simulate a lost response after submission. Verify that the order remains pending while the system checks the original attempt. Then confirm that a late approval attaches to that order without causing another capture. Record the receipt the customer sees and the support instruction when the status remains unresolved.
Write a customer-facing exception path
Staff need an approved way to explain that a transaction is being checked, including when the customer will hear back. Keep the order reference and investigation owner visible. Do not ask the customer to repeatedly try another card while the original outcome is unknown. A second attempted payment should follow the provider’s documented procedure and the confirmed state of the first.
Evaluate routing with more than an approval ratio
Track unknown outcomes, duplicate captures, unresolved orders and reconciliation effort alongside approvals and fees. Visa’s rules and policies provide a primary acceptance reference, while specific integration behavior must be checked with the provider. Change one routing condition at a time and retain a rollback setting. A higher approval count is not useful if the underlying order ledger becomes unreliable.
Sources and next steps
Primary reference: Visa acceptance rules and policies. The worksheet and examples above are operational analysis, not reported customer results.
Continue through the AMS New Jersey merchant reading path. For the broader framework, explore Eric Kuvykin’s fintech, payments, alternative financing and AI topic guides.
