Card Terminal Down? Who to Call First

Why the answer is not obvious

Many businesses deal with one salesperson when they open a card account, so it feels like one company. Behind the scenes there are usually several. The agent or reseller who set up the account, the processor that moves the card payments, the bank that sponsors the account, the company that made the terminal and, if you use one, the company that runs your POS software can all be separate businesses with separate help desks. When something breaks on a busy Saturday, staff lose time calling the wrong one. The fix is simple: work out who supports what while things are calm, and write it down.

Match the problem to the right line

Start with what the screen or the customer is telling you. If cards are declined with a message from the network, deposits are missing, or a fee looks wrong, that is usually a question for your processor's merchant support line. If the terminal will not power on, freezes, shows a software error or a menu you cannot get past, that often goes to the terminal or POS provider, which may or may not be your processor. If every device in the shop has lost the internet, call whoever supplies your connection first, because no payment company can fix your router. If you are not sure, ask your processor's support line which part has failed; they can usually see whether your transactions are reaching them.

When the network is the problem: Card payment outage plan: keep taking cards

Build a one-page contact sheet

Put these on one page and keep a copy next to every register and one with the owner or manager. The merchant support phone number for your processing account, and the hours it is actually staffed, including weekends and holidays. Your merchant ID, which nearly every support line asks for first. The terminal ID and serial number for each device, so support knows exactly which one you mean. The support number for the terminal or POS software, if it is a different company. The name of your agent or account contact, if you have one, for billing and contract questions. Who on your team is allowed to call support and approve changes. Never write passwords or full card numbers on this sheet.

Device lists also help with security: Card terminal security settings to check

Questions to ask your provider now

Call or email your current provider on a quiet day and ask: which number do we call for terminal problems, and which for account and funding problems? What hours is each line staffed? How do you verify that a caller is from our business? If a terminal fails, how is a replacement sent, and how long does it usually take to arrive? Will you ever send a technician or a new device without us asking? Get the answers in writing where you can. The last question matters for security: the PCI Security Standards Council's skimming guidance for merchants says not to allow unannounced service visits or upgrades without checking with your service provider first.

Have the backup plan written down

Support can take time even when you reach the right line. Decide in advance what staff should do while a terminal is down: whether a second device or a phone-based reader can take over, whether to accept cash or another payment method for a while, and when to stop and wait instead of keying in card numbers by hand. Keyed payments are card-not-present transactions and usually cost more, so keep them for real emergencies. Write the plan on the same page as the contact list.

Related: Keyed-in card payments: what to check

What changes for small, mid-size and enterprise businesses

A small business with one terminal needs one sheet taped inside the counter and one saved on the owner's phone. A mid-size business with several registers or a POS system should name a person on each shift who makes support calls, and keep the terminal IDs labelled on the devices themselves so staff read out the right one. Multi-location and enterprise operations need a central support list per location, because different sites may have been set up at different times on different accounts. A single escalation path, one internal owner for payment incidents, and a log of each outage (time, device, cause, how long it took to fix) turn support from a guessing game into something you can measure and raise with your provider at contract time.

For groups with several sites: Multi-location card batches and reporting

We can help you map it

CELER Merchants is an independent agent, not a processor. Send us a recent statement and tell us which terminals you use, and we will help you work out who supports what on your account, along with a plain-English read of your fees. The review is free and there is no obligation.