Running a retail business means dealing with payment terminals every single day. When things go smoothly, you barely notice. But when errors pop up, lines stall, customers get frustrated, and sales slip away. One of the most common headaches is CALFORAUTH, but it’s far from the only issue merchants face.
After years following retail operations and talking with store owners and cashiers, I’ve seen the same errors repeat across locations. This guide covers the top 10 payment terminal errors—including CALFORAUTH—with clear explanations and practical fixes you can use today. Understanding these will help you reduce downtime and keep customers happy.
1. CALFORAUTH (Call for Authorization)
This error means the card issuer wants extra verification before approving the transaction. It often appears during chip reads, PIN entries, or tap payments.
Common Causes: Locked cards in banking apps, fraud flags, network hiccups, or method mismatches.
Quick Fixes:
- Retry with tap or credit mode.
- Ask the customer to check their banking app for a lock.
- Call the number on the card back for manual authorization (always verify through official channels).
- Wait 30 seconds and retry if you suspect connectivity.
Real Tip: Many cases resolve in under a minute. Train staff to communicate calmly: “This is a quick bank check—it usually clears fast.”
2. Declined – Do Not Honor (Code 05)
A generic hard decline where the bank refuses the transaction without much detail.
Common Causes: Insufficient funds, suspected fraud, or account restrictions.
Fixes:
- Ask the customer to try another card or payment method.
- Suggest contacting their bank directly.
- Avoid multiple retries on the same card to prevent further flags.
Merchants report this as one of the most frequent issues, especially with debit cards during tight paycheck cycles.
3. Insufficient Funds (Code 51)
Straightforward: The customer doesn’t have enough money available.
Fixes:
- Politely inform them and offer to split the purchase.
- Suggest cash or a different card.
- For loyal customers, some stores allow holding items briefly while they transfer funds.
Pro Insight: Track patterns—some customers hit this repeatedly near the end of the month.
4. Invalid Card or Card Number (Code 14)
The terminal can’t read the card properly or the number doesn’t match.
Common Causes: Damaged cards, expired cards, or entry errors.
Fixes:
- Clean the card reader.
- Try manual entry if allowed.
- Ask for another card or expiration date confirmation.
5. Transaction Not Permitted (Code 57 or 58)
The card or terminal isn’t set up for this type of transaction.
Common Causes: Merchant account restrictions, card type limits (e.g., prepaid cards), or terminal configuration issues.
Fixes:
- Check your merchant settings with your processor.
- Try running as credit instead of debit.
- Contact processor support for terminal configuration problems.
6. EMV/Chip Read Errors
The chip isn’t communicating properly with the terminal.
Common Causes: Dirty readers, damaged chips, or software glitches.
Fixes:
- Clean the reader with a dry cloth (no liquids).
- Try swipe or tap as backup.
- Restart the terminal if multiple cards fail.
Regular maintenance prevents many of these headaches.
7. Network or Connection Errors
The terminal can’t reach the payment processor.
Common Causes: Wi-Fi drops, Ethernet issues, or provider outages.
Fixes:
- Check internet connection and restart router/terminal.
- Have a backup method ready (some terminals support offline mode for limited time).
- Monitor during peak hours and consider signal boosters.
One chain reduced related errors significantly after upgrading routers.
8. Batch Settlement Failures
Problems closing out the day’s transactions.
Common Causes: Open batches, communication issues, or unsettled transactions.
Fixes:
- Settle batches daily at the recommended time.
- Restart the terminal and try again.
- Contact processor support if it persists.
Unsettled batches can delay your deposits.
9. PIN Verification Failures (Code 55)
Incorrect PIN or verification issues.
Common Causes: Customer error, forgotten PIN, or card lock after too many tries.
Fixes:
- Allow one polite retry.
- Suggest the customer contacts their bank.
- Offer alternative payment methods.
10. Terminal Offline or Frozen
The whole device stops responding.
Common Causes: Power issues, software glitches, or hardware problems.
Fixes:
- Power cycle the terminal (unplug and wait 30 seconds).
- Check cables and connections.
- Have backup payment options like cash, manual imprinters, or mobile card readers ready.
General Strategies to Reduce Payment Errors
Beyond individual fixes, build stronger habits:
- Train staff regularly with role-playing for common scenarios.
- Maintain equipment and keep software updated.
- Monitor error logs in your POS system for patterns.
- Build good relationships with your payment processor for faster support.
- Educate customers gently about common issues like app locks.
Stores that track errors and train teams see 30-50% fewer disruptions over time.
Why Getting These Right Matters for Your Business
Every unresolved error costs money in lost sales, longer lines, and unhappy customers. In competitive retail, smooth payments become a real advantage. Mastering these top 10 errors—including CALFORAUTH—helps protect your revenue and reputation.
Start by reviewing your most common errors this week. Share this guide with your team and discuss what’s happening in your store. Small improvements add up quickly.
Have you faced a particularly tricky terminal error? Drop your experience in the comments—I read them and often include real merchant stories in future guides. For more practical retail payment advice, check our other articles on CALFORAUTH troubleshooting and merchant tips.
