By Eric Kuvykin. Substantially revised October 17, 2026. The original publication date and URL are retained.
Define what would trigger a change
A delayed response can mean several things: a connection problem, a provider incident or a transaction still being processed. A business should not treat every timeout as proof that the first attempt failed. Define the status checks and escalation that occur before another route is used.
Ask each provider to document its supported behavior during an interruption. Identify who can authorize a change and which transaction types are eligible. The plan should reflect the actual integration and agreement rather than a generic promise that a backup processor solves every outage.
Test uncertainty rather than only failure
Use approved test cases in which a request is submitted but the application does not receive a clear response. Determine how staff or software checks whether a charge succeeded. Record how duplicate prevention works when two systems could act on the same order.
Test the customer communication as well. Staff should be able to explain that a status is being checked without promising that no charge occurred. Preserve the reference used for the investigation so the next employee can continue it.
Follow the second provider’s records
If an approved route change occurs, verify where the order stores the new transaction reference. Test how a later refund finds the correct provider and how the payout appears in reconciliation. A backup route that leaves reporting fragmented can create work long after checkout resumes.
For a Florida business preparing for a closure or communications disruption, include the approved alternative working arrangement in the exercise. Confirm how managers reach provider support and access essential reports if the usual premises are unavailable. Do not infer that a route change guarantees business continuity.
Practice restoration as well as failover
Identify who decides that normal routing can resume and how unresolved transactions are reviewed. Keep an incident log covering the time window, affected orders, provider communications and corrective actions. Do not delete uncertain attempts simply to make the dashboard look clean.
Review current network and provider requirements for the proposed configuration. Visa’s merchant rules resource is one starting point, while the acquiring providers must confirm the actual implementation and contractual constraints.
After the exercise, inspect duplicate attempts, unresolved payment statuses and manual reconciliation effort. Update the plan where staff had to guess. A sound handoff makes both the interruption and the return to normal operations traceable.
References and related reading
Primary resource checked for this review: Visa’s current merchant rates, fees and rules resources. Confirm the current requirements and implementation with the responsible provider or appropriate adviser.
Continue with Payment Routing: Evaluate Success, Cost and Duplicate Prevention and Card-Not-Present Fraud: Review the Order Before Repeating the Charge.
For state and local business resources alongside this operating checklist, use the Florida business operations guide on All State Merchants.
