A credit card processor issue means your payment system has failed, and you need to know whether the problem is on your end, your processor's end, or your bank's end before you can fix it.
When customers can't complete purchases because your card reader, online payment form, or payment gateway has stopped accepting cards, you've lost revenue and customer trust in real time. The cause matters: a merchant account problem requires a call to your processor; a technical glitch on your server requires your IT person; a bank hold requires a conversation with your acquiring bank. Each has a different fix and a different timeline.
This guide walks you through identifying what broke, who to contact, and what information you'll need to have ready when you call.
Key Takeaways
- Check whether the issue affects all card types or just one, all payment methods or just in-person, because that tells you whether the problem is with your processor, your terminal, or your internet connection.
- Your processor's support line is the fastest first call; have your merchant ID and terminal serial number ready before you dial.
- If your processor says their system is fine, contact your acquiring bank next, because they can see holds or blocks that your processor cannot.
- Document the exact time the issue started, which cards failed, and what error message appeared, because support will ask for all three.
- Most processor outages last under two hours; if yours has lasted longer, the problem is usually account-specific rather than system-wide.
Identify where the problem actually is
Before you call anyone, run a quick test to narrow down the source. Try processing a card yourself using the same method your customers use — if you have a physical terminal, swipe or insert a card; if you have an online store, try checking out with a test card number. Note exactly what happens: Does the terminal freeze? Does the payment form reject the card? Does it time out? Does it say "declined" or "connection error" or something else?
Then try a different card type if you have one — use a Visa if you just tried Mastercard, or an American Express if you tried Visa. If one card type works and another doesn't, the issue is usually with your processor's connection to that specific card network, not with your equipment. If all cards fail the same way, the problem is usually your terminal, your internet, or your merchant account itself.
If you process payments online, check your internet connection by opening a web browser and visiting a website you know works. If the browser loads fine but your payment form still fails, the problem is with your payment gateway or your processor's servers, not your internet. If the browser won't load anything, your internet is down — restart your router and wait two minutes before testing again.
Contact your processor's support line first
Your processor is the company that owns your payment terminal or hosts your payment gateway — common names include Square, Toast, Stripe, PayPal, Clover, and Ingenico, though there are many others. Find their support number on your merchant agreement, your terminal's screen, or your online dashboard. Have ready: your merchant ID (usually on your receipt paper or in your account settings), your terminal serial number (usually on the back of the device), and the exact time the issue started.
Tell them what you observed in your test: which card types failed, what error message appeared, whether the problem affects in-person payments, online payments, or both. If they tell you their system is running normally and they see no blocks on your account, ask them to check whether your acquiring bank has placed a hold on your merchant account. Some processors can see this; others cannot. If they cannot, write down the name of the support agent and the time of the call, then move to the next step.
If your processor confirms a system-wide outage, ask for an estimated time to resolution and whether they're routing transactions to a backup system. Most outages last under two hours. If yours has lasted longer than that, the problem is usually specific to your account, not their entire system.
Contact your acquiring bank if the processor says they're fine
Your acquiring bank is the financial institution that holds your merchant account and deposits your revenue. It is often different from your processor — for example, you might use Square (processor) but have your account through Chase (acquiring bank). Your processor should have told you the name of your acquiring bank when you signed up, or you can find it on your merchant agreement or your bank statements.
Call your acquiring bank's merchant services line and give them your merchant ID. Ask whether there is a hold, block, or reserve on your account. Banks place holds for several reasons: suspicious activity patterns, a chargeback dispute, a failed verification step, or a compliance review. A hold means transactions are being declined at the bank level, not at your processor's level, which is why your processor's support team couldn't see it.
If your bank confirms a hold, ask what triggered it and what you need to do to remove it. Most holds require you to provide documentation (bank statements, business license, proof of address) or to wait out a review period. Ask for a timeline: some holds last 24 hours, others last several business days.
Check for common technical causes while you wait
While your processor or bank investigates, try these steps yourself. Restart your payment terminal by holding the power button for ten seconds, then turning it back on. If you process online, clear your browser's cache and cookies, then try the payment form again in a different browser (Chrome instead of Safari, for example). If you use a mobile card reader, make sure the app is up to date by checking your phone's app store.
If you have a physical terminal, check that all cables are plugged in firmly — the power cable, the internet cable (if it's wired), and any cables connecting the terminal to a receipt printer. A loose cable can cause intermittent failures that look like a processor issue. If your terminal connects to the internet via WiFi, restart your WiFi router by unplugging it for 30 seconds, then plugging it back in.
If you process payments through a computer or tablet, restart that device. Close any other apps that might be using your internet connection — streaming video, large file uploads, or automatic backups can slow your connection enough to cause payment timeouts. If the problem persists after these steps, the issue is almost certainly with your processor or bank, not with your equipment.
Document everything for your records and your processor
Write down the date and time the issue started, how long it lasted, which payment methods failed (in-person card swipe, chip insert, contactless, online form), which card types were affected (Visa, Mastercard, Amex, Discover), and the exact error message that appeared. If customers tried to pay and were declined, note how many transactions failed and the approximate dollar amount. Take a screenshot of any error message if you can.
This information matters for three reasons. First, it helps your processor or bank pinpoint the cause faster. Second, if the outage cost you revenue, you may be able to request a fee credit from your processor — most have policies allowing this for outages longer than a set time (often one hour). Third, it creates a record for your own business records and insurance purposes.
Keep the names and badge numbers of any support agents you speak with, along with the time of each call. If you have to follow up, reference these details so you don't have to repeat yourself.
Prevent future outages with redundancy
If this is your first processor outage, consider whether you want a backup payment method. Some businesses keep a second terminal from a different processor, or a mobile card reader as a backup to their primary system. Others keep a manual credit card imprint machine (old-fashioned but functional) for emergencies. The cost is usually low — a backup mobile reader costs $20 to $50 — and the peace of mind is real.
If you process online, some payment gateways offer failover to a backup processor automatically, though this usually costs extra. Ask your processor whether they offer this feature. If you process in person, keeping a second terminal from a different company means you can still take payments even if your primary processor goes down.
You should also review your processor's uptime may provide and support response time in your merchant agreement. Most processors may provide 99.5% uptime, which sounds high but allows for about 3.5 hours of downtime per month. If your business cannot tolerate that much downtime, you need a backup system.
Frequently Asked Questions
How long do processor outages usually last?
Most last under two hours. If your issue has lasted longer, it is usually account-specific rather than a system-wide outage. Contact your processor's support line to confirm whether they are experiencing a widespread outage or whether the problem is isolated to your merchant account.
Will I get refunded for transactions that failed during an outage?
No transaction goes through if it fails, so there is nothing to refund. However, if your processor's outage lasted longer than their may provide uptime window (usually one hour), you may be able to request a fee credit. Ask your processor about their outage credit policy when you contact them.
What if my processor says the problem is my internet, but my internet works fine?
Ask them to run a connectivity test from their end. Most processors can ping your terminal or gateway to see whether they can reach it. If they can reach you but transactions still fail, the problem is on their side, not yours. Get this in writing if possible.
Can I process cards manually if my system is down?
Yes, if you have a manual imprint machine or if your processor allows phone-based transactions. However, manual processing is slower and riskier — you lose the fraud protection that comes with a real-time authorization. Use it only as a temporary measure while your system is being fixed.
Should I tell my customers about the outage?
Yes. Post a notice on your website, social media, or storefront saying that you are experiencing a temporary payment issue and are working to fix it. Customers appreciate transparency, and it reduces the number of support calls you'll receive asking why their card was declined.