If your credit card processing is down, switch to backup connectivity first, then follow this checklist before losing another sale.

Immediate steps (first 5–10 minutes):

  • Power-cycle your terminal. Unplug it, wait 30 seconds, restart. Many “down” incidents are a frozen connection, not a network failure.
  • Check your internet connection. Switch from Wi-Fi to a wired connection or a cellular hotspot immediately.
  • Try a different card brand. If Visa declines but Mastercard goes through, the issue is network-specific, not your terminal.
  • Check your processor’s status page and Downdetector’s Visa monitor for real-time user reports. Spikes in reports confirm a wider outage.
  • Post signage for customers explaining the temporary disruption and your alternative payment options.
  • Enable offline mode only if your terminal and processor support it — and only after reading the risk warnings in the offline section below.

Cards remain the dominant payment method for U.S. consumers, according to 2021 findings from the Diary of Consumer Payment Choice, which means every minute of payment processing downtime costs you real revenue. Move fast, but move carefully.

Pro Tip: Bookmark your processor’s status page and the Visa Downdetector page right now, before the next outage. You will not have time to search for them mid-incident.

Key Takeaways

When credit card processing goes down, the merchants who recover fastest are the ones who diagnose the failure layer quickly, have a tested offline workflow, and escalate with the right information already in hand.

Point Details
Diagnose before acting Check terminal error codes, processor status, and Downdetector before assuming the cause.
Connectivity swap first Switch to cellular or a hotspot before enabling offline mode — most outages are local network failures.
Offline mode carries real risk Per Visa’s guidance, offline batches must be submitted promptly; unsubmitted transactions expire and declined batches mean lost revenue.
PCI rules still apply offline Manual and offline capture workflows increase PCI scope; limit data recorded and destroy paper records after batch submission.
Davincipay provides redundancy Multiple acquiring relationships and 24/7 incident support reduce the impact of processor-side and network-level outages.

Table of Contents

Is your credit card processing down locally or network-wide?

Knowing where the failure lives determines your next move. A frozen terminal needs a reboot. A processor outage needs a workaround. A card-network failure needs patience and alternatives.

Run this diagnostic checklist in order:

  • Read the error code on your terminal screen. “No route” and “timeout” errors point to a connectivity problem on your end. “Decline” with a response code (51, 05, 14) means the transaction reached the network and was rejected for a card-specific reason. “Host unavailable” or “connection failed” suggests your processor is unreachable.
  • Run the terminal’s built-in self-test. Most terminals have a diagnostic menu that confirms whether the device itself is functioning.
  • Check your merchant account status. Log into your payment dashboard. A suspended or flagged account produces declines that look identical to network errors.
  • Look for bank or acquirer notifications. Check your email and SMS alerts for any incident messages from your processor.
  • Test a second terminal or mobile reader on the same network. If both fail, the problem is upstream. If only one fails, the terminal itself is the issue.
  • Check Downdetector for Visa and your processor. A spike in user reports from across the country confirms a card-network or processor-side incident.

Real-world incidents are more common than merchants expect. Third-party incident trackers document events like Visa processing latency affecting point-of-sale systems, where the failure looked local but was actually a network authentication issue affecting thousands of merchants simultaneously.

Pro Tip: Test chip, magstripe, and contactless on the same card. If chip fails but tap works, the terminal’s chip reader may be faulty. If all three fail on multiple cards from multiple brands, you are almost certainly looking at a connectivity or processor-side credit card system issue.

How to keep selling while card processing is down

Speed matters here. The goal is to capture revenue safely while you diagnose the root cause.

Switch your connectivity first

Move to a different internet path before anything else. If your terminal runs on Wi-Fi, plug in an ethernet cable or switch to a cellular hotspot on your phone. Different connection types carry different reliability profiles: wired broadband is fastest but single-point-of-failure; cellular LTE/5G is slower but independent of your local network infrastructure. SIM-enabled terminals can switch automatically, which is why they are worth the upgrade for high-volume merchants.

Offer alternative payment methods

  • Digital wallets (Apple Pay, Google Pay): These route through NFC and may use different network paths than a standard card swipe. Worth trying before assuming all card acceptance is blocked.
  • QR codes and pay-by-link: Send a payment link via text or display a QR code that routes through your payment gateway’s hosted page. This works even when your physical terminal is offline.
  • ACH transfers: For B2B or high-ticket transactions, an ACH payment is a legitimate alternative that bypasses card networks entirely.
  • Cash: Post clear signage and have your staff communicate the situation honestly. Most customers understand a temporary disruption.

Offline mode: use it carefully

If both conditions are met, offline mode stores transactions locally on the terminal. Per Visa’s acceptance documentation, these stored transactions must be submitted as a batch for authorization once connectivity returns. Transactions that cannot be authorized at that point will decline, and you will not be paid.

Staff script for offline payments: “We’re experiencing a temporary system issue. We can still process your payment, but it will be authorized once our connection is restored. We’ll need your signature and a photo ID for transactions over $[your cap]. You’ll receive a receipt now and a confirmation once it’s processed.”

Hands capturing offline payment signature at register

Pro Tip: Set a per-transaction cap for offline acceptance — many processors recommend $50–$100 for retail. High-ticket offline transactions can carry increased fraud risk.

How offline transactions work and what to do after connectivity returns

Offline mode is not a free pass to keep selling indefinitely. It is a controlled fallback with strict rules.

How offline mode actually works

When your terminal enters offline mode, it stores each transaction’s card data, amount, timestamp, and terminal ID locally. Per Visa’s offline transaction guidance, the terminal must reconnect and submit the stored batch for authorization within the time window your processor specifies. Transactions not submitted within that window may expire and cannot be collected.

Step-by-step checklist for offline sales

  1. Confirm offline mode is enabled in your terminal’s local mode settings before accepting the first transaction.
  2. Set a per-transaction cap consistent with your processor’s guidelines (ask your acquirer for the approved limit).
  3. Require a signature for every offline transaction, regardless of amount.
  4. Request a photo ID for transactions above your cap or for any customer you cannot verify.
  5. Record manually for each transaction: terminal ID, timestamp, card BIN (first six digits), last four digits of the card number, transaction amount, and the staff member’s name.
  6. Give the customer a printed or written receipt noting the transaction is pending authorization.
  7. Flag all offline transactions in your records as “pending batch submission” so they are easy to identify later.

Storing cardholder data during offline workflows increases your PCI scope. The PCI Security Standards Council requires that any manual or offline capture process follow strict data-handling rules. Limit what you record, never store full card numbers, and destroy paper records securely once the batch is submitted.

Reconciliation after connectivity returns

Once your connection is restored, submit the offline batch immediately. Do not wait. Review each transaction in the batch against your manual records. Flag any transaction where the card BIN, amount, or timestamp does not match your written log. If a transaction declines during batch submission, contact the customer directly and offer an alternative payment method before assuming the sale is lost.

Pro Tip: Tag offline transactions with a custom label in your reporting system (e.g., “OFFLINE-[date]”) so your team can pull them instantly during a chargeback dispute. A timestamped log with terminal ID and staff name is your strongest defense.

For nutraceutical and supplement merchants, who already carry elevated chargeback risk, offline acceptance should be a last resort. The combination of high ticket sizes and a customer base that disputes charges at higher-than-average rates makes every unverified offline transaction a liability.

Where to check whether the outage is wider than your store

Do not spend 20 minutes troubleshooting your terminal if the problem is a nationwide card-network incident. Check these sources in order.

Primary sources:

  • Your processor’s official status page. This is your first stop. Most processors publish real-time incident status with affected components, start time, and estimated resolution. Subscribe to email or SMS alerts so you receive notifications automatically.
  • Visa’s Downdetector page. Downdetector aggregates user reports and flags incidents when report volumes spike significantly above normal thresholds for that time of day. A spike here confirms the problem is not isolated to your location.
  • Mastercard’s status page. Mastercard publishes discovered incidents and recommends that merchants subscribe to status feeds for real-time updates. If Mastercard transactions are also failing, the issue is likely at the network level or with your acquirer, not a single card brand.
  • Your processor’s social channels. Many processors post incident updates on their official accounts before their status page is updated. Check their most recent posts for any service disruption announcements.

What an incident page tells you:

A well-maintained status page shows the scope of the outage (which products or regions are affected), the start time, the current mitigation status, and an estimated recovery window. Use the start time to confirm whether your terminal failures align with the reported incident, which matters for your reconciliation records later.

Pro Tip: Subscribe to your processor’s status page alerts and Mastercard’s incident feed before you need them. Real-time alerts arrive faster than any support call.

How to reduce downtime before the next outage hits

Prevention is cheaper than recovery. These measures are prioritized by impact for most U.S. merchants.

Redundancy checklist:

  • UPS (uninterruptible power supply): Power grid disruptions can cascade into payment failures. A UPS on your terminal, router, and switch keeps your hardware running through brief outages. Energy infrastructure analysis consistently shows that weather events and grid stress increase local outage frequency, making physical power backup a practical investment.
  • Backup terminal or mobile reader: A second terminal on a different connectivity path (cellular vs. wired) means a single device failure never stops all sales.
  • Secondary payment gateway or acquirer relationship: For ecommerce merchants, a secondary gateway configured and tested in advance lets you reroute traffic within minutes. This is especially relevant for high-risk merchants whose primary processor may have narrower SLAs.

Operational policies to put in writing:

  1. Designate an outage response lead for each shift. This person owns the checklist, contacts the processor, and communicates with customers.
  2. Pre-approve offline transaction caps with your processor and document the approved limit in your staff manual.
  3. Create an escalation matrix with your processor’s support number, your acquirer’s emergency line, and your merchant account ID written down and posted near every terminal.
  4. Run a quarterly drill. Simulate a connectivity failure, walk staff through the offline workflow, and verify that your batch submission process works. Managed IT partners can help automate failover and networking best practices for merchants who want a hands-off approach.

How to contact your processor and what information to have ready

Calling support without the right information wastes time. Processors triage tickets faster when you arrive with specifics.

Before you call or open a ticket, collect:

  • Merchant ID (MID) and terminal ID
  • Device serial number and firmware/software version
  • Recent transaction IDs and their timestamps
  • Exact error codes displayed on the terminal
  • A brief description of when the issue started and which card brands are affected
  • Network routes you have already tested (Wi-Fi, ethernet, cellular)

Step-by-step escalation process:

  1. Call your processor’s merchant support line and reference your MID in the first sentence. This routes you to the correct team faster.
  2. Request an incident ID for your case. This number lets you track the ticket and reference it in follow-up calls without re-explaining the issue.
  3. Ask whether the issue is on your processor’s side or the card network’s side. The answer determines whether waiting is the right move or whether you need to activate a workaround.
  4. If the processor confirms a network-level outage, ask for an estimated resolution time and request that they notify you when service is restored.
  5. Document every call: timestamp, representative name, incident ID, and what was communicated. This log is valuable for reconciliation and for any dispute defense later.

Timing guidance: Escalate to your acquirer (not just your processor’s front-line support) if the outage affects your ability to process for more than 30 minutes and your processor cannot confirm a resolution timeline. For telehealth merchants and other high-volume verticals, a 30-minute window is a meaningful revenue threshold that justifies senior escalation.

A merchant services provider’s perspective on outages

Most outages merchants experience fall into three categories: local connectivity failures (the most common and the most fixable), processor-side incidents (less frequent but often resolved within an hour), and card-network events (rare, but wide-reaching when they occur). The honest reality is that no payment provider controls all three layers simultaneously.

What a good merchant services partner does control is how quickly they communicate during an incident, how clearly they document the scope, and how much they help you recover afterward. Merchants who treat their payment provider as a commodity relationship often discover during an outage that they have no direct escalation path, no incident ID system, and no reconciliation support. That gap costs more than the outage itself.

The other thing most merchants underestimate is their own preparation gap. Offline mode exists in most modern terminals, but the majority of merchants have never tested it. Batch submission after an outage is a documented process, but most staff have never run one. The merchants who recover fastest are the ones who have drilled the workflow at least once before they needed it.

Davincipay keeps you processing when systems fail

Davincipay

Davincipay gives high-risk and complex ecommerce merchants something most standard processors do not: multiple domestic and international acquiring relationships, so a single processor incident does not take your entire operation offline. When your primary gateway goes down, Davincipay’s infrastructure is built to reroute, not wait.

Beyond uptime, Davincipay provides dedicated chargeback mitigation and reconciliation support, which matters most in the hours after an outage when offline batches are submitting and disputed transactions start appearing. You get real-time reporting, 24/7 incident support, and a team that understands the compliance and fraud exposure that comes with offline capture workflows.

Ready to build a more resilient payment setup? Apply for a Davincipay merchant account or review our full payment processing services to see how we support merchants through outages, not just around them.

Sources

This article is general information, not a substitute for advice from a qualified financial advisor. Consult a qualified financial professional about your own circumstances before acting on anything here.