Payment terminal troubleshooting
Why Is a Terminal Declining Every Card?
When different cards fail at the same terminal, the shared payment path deserves attention. Confirm what is affected, preserve transaction evidence, and check the terminal, connection, account service, and provider status without guessing at approval reasons.
Start with scope
Determine whether the problem is one card or the whole payment path
Try a different legitimate customer card or another approved payment method only when appropriate. Compare another register or terminal if one is available. Record the exact on-screen message, time, amount, payment method, affected station, and whether the transaction appears in the provider portal.
Isolation checklist
Check the shared causes in a controlled order
Read the message
Capture the exact response without recording full card data. Distinguish a true issuer decline from a connection error, reader error, configuration message, or incomplete transaction.
Confirm connectivity
Check the terminal's network indicator and the approved Ethernet, Wi-Fi, or cellular connection. Compare other connected business systems before changing network settings.
Check service status
Use your processor or POS provider's official status page or support channel. If every terminal or location is affected, a provider or network interruption may be involved.
Inspect the terminal
Check power, cables, date and time, software notices, and visible reader damage. Follow the exact model's official guide before restarting, updating, or resetting it.
Compare symptoms
Use what still works to narrow the fault
One card declines
Ask for another payment method and let the cardholder contact the issuer. Merchants generally do not receive a detailed issuer explanation and should not infer why the card was declined.
One payment method fails
If insert fails but tap or swipe behaves differently, follow the terminal's supported prompts and official reader guidance. Do not force fallback or manually enter card data merely to bypass a malfunction.
One terminal declines every card
Compare its connection, configuration, software state, and account assignment with a working device. Record differences before making changes.
Every terminal declines every card
Check the site network, provider status, and account notifications. Escalate with timestamps and sanitized examples so support can identify a shared service or account issue.
Protect the transaction trail
Confirm payment status before trying again
Review the POS transaction list or provider dashboard for approved, declined, pending, canceled, and offline transactions. A customer may see a temporary authorization hold even when a sale did not complete. Confirm the recorded status before retrying to reduce duplicate-charge risk.
Support handoff
Prepare a useful, privacy-safe incident summary
Include
- Terminal make, model, and affected station
- Exact error text or response code
- Time range and whether other terminals work
- Connection type and provider status result
- Sanitized transaction references and steps already tried
Do not include
- Full card numbers or security codes
- PINs, passwords, or bank credentials
- Secret API keys or unredacted receipts
- Guesses about a customer's credit or account
- Factory resets before pending transactions are protected
Common questions
Terminal decline troubleshooting FAQ
Should I keep retrying the same card?
No. Read the response, confirm transaction status, and ask for another payment method when appropriate. Repeated attempts can confuse the record and customer experience.
Does every-card failure mean the terminal is broken?
Not necessarily. Connectivity, provider service, configuration, software, and account conditions can affect every transaction. Isolate the shared layer before replacing hardware.
Should I factory-reset the terminal?
Only when the official provider or device instructions call for it and pending or offline transactions are protected. A reset can erase settings or unsent payment data.
Who should receive the incident?
Use the support contact shown by your processor, payment provider, POS provider, or device program. Provide exact errors and sanitized transaction references.
Last editorial review: August 12, 2026. Sources reviewed: current official Square payment troubleshooting and device-support guidance, plus Verifone terminal installation documentation.
Next step
Identify the shared failure before changing the system
Document the scope, confirm transaction status, check connectivity and official service status, then contact the responsible provider with a sanitized incident summary.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US