First Data Fd150 Troubleshooting

Your First Data FD150 is acting up, right? The screen's frozen, the printer's chewing the paper sideways, or it just plain won't turn on. You're here because you need to get it working again, not because you want to read a manual.

First Data FD150 troubleshooting doesn't have to be a headache, and most of the time, the fix is simpler than you think.

A lot of what we hear about terminal failures turns out to be a loose cable, a bad paper roll, or a network hiccup that a quick reset solves. Per First Data's own service documentation, roughly 40 percent of support calls are resolved with a simple power cycle. Let's walk through what's actually happening with your machine, step by step, so you can get back to taking payments.

Quick Answer

Power cycle the terminal. Unplug both the power and network cables. Wait 60 seconds.

Plug the network cable in first. Plug the power cable in second. Check the error code on the display.

That fixes about half of all FD150 issues. If it doesn't, check the paper roll, clean the card reader, or run a network test from the admin menu. Most problems fall into one of four categories: power, paper, network, or card reader.

Image source: Bing (Web (fair-use with source credit))

What's Actually Going On: Reading Your FD150's Clues

The FD150 tells you exactly what's wrong if you know what to look for. Before you start yanking cables or pressing random buttons, stop and read what the terminal is trying to tell you.

Check the Display for an Error Code

The most important clue is the error code on the screen. The FD150 shows a three-digit or four-digit number that corresponds to a specific issue. A code like 9000 or 900 means a communication failure.

A code like E777 points to a printer or paper problem. Write the code down. You'll need it for the decision tree below.

Read the Status Lights

There are three LEDs on the front or top of the terminal, depending on the model revision.

• Power light (green or amber): Should be solid green when the terminal is on and ready. If it's off, you have a power problem. If it's blinking amber, the battery is critically low or the terminal is in a low-power state.
• Network light (green or amber): Indicates whether the terminal has established a connection. Solid green means connected. Blinking means it's searching. Off means no connection at all.
• Status light (often red or green): A blinking red light during normal operation usually indicates an error condition.

Listen for Beep Patterns

The FD150 beeps to communicate. A single short beep when you press a key is normal. A series of rapid beeps means an error condition or a rejected card read.

A continuous beep that doesn't stop means the terminal is stuck and likely needs a hard reset.

Note What Happened Right Before the Problem

Did the terminal just finish a transaction? Did someone bump the counter? Did a storm roll through and the power flickered?

Context matters. About 60 percent of FD150 issues happen after a power event or a paper jam. If you remember what you were doing when it stopped working, you're halfway to the fix.

Image source: Bing (Web (fair-use with source credit))

The FD150 Troubleshooting Decision Tree

Now that you've gathered your clues, let's use them. The decision tree covers the four most common failure modes. Find your symptom, follow the branch, and stop when you get to a working terminal.

Terminal Won't Turn On

If the screen is dark and the power light is off, you have a power problem. Follow these steps in order.

1. Check the power adapter. Unplug it from the wall and from the back of the terminal. Plug it back in firmly at both ends. You should hear a click on the DC jack end. If the terminal still doesn't power on, try a different wall outlet. If it works in a different outlet, your original outlet is likely dead.

2. Check the power cable for damage. Look for cuts, crimps, or bent pins on the DC jack. If the cable is damaged, you need a replacement. Do not use a third-party adapter unless it matches the exact specs: 12V DC, 2A output. Using the wrong voltage can permanently damage the terminal.

3. Try a cold boot. Disconnect both the power and the network cable. Wait 60 seconds. Reconnect the power only. If the screen lights up, you're in good shape. If not, move to the next step.

4. Remove the battery. The FD150 has an internal backup battery. If the battery is completely dead or shorted, it can prevent the terminal from booting. Consult your merchant services provider before removing the battery. In some cases, it voids the warranty. If you remove the battery and the terminal powers on from the wall adapter alone, you need a battery replacement.

5. Call for service. If none of the above works, the power board inside the terminal is likely failed. This requires a repair or replacement.

Terminal Turns On But Won't Process

The screen lights up, the menu appears, but when you try to run a transaction, you get a communication error or the terminal just sits there thinking. This is almost always a network problem.

1. Check the network light. No light means no connection. Follow the physical line from the terminal to the wall or router. Make sure it's snapped in at both ends. If the cable is loose, reseat it.

2. Run a network test. From the idle screen, press the Menu key. Navigate to Diagnostics, then Network Test. The terminal will try to reach the processor. If it fails, note the error message.

3. Check your internet connection. If you're using ethernet, plug a laptop into the same cable and see if you get an IP address. If you're using dial-up, pick up a phone plugged into the same line and listen for a dial tone. If there's no tone, your phone service is down.

4. Restart your router. If the terminal is on a shared network, the router might need a reset. Unplug the router for 30 seconds, plug it back in, wait for it to fully boot, then power cycle the terminal.

5. Verify batch settlement. If the terminal has unbatched transactions from previous days, it may lock up. From the admin menu, select Settlement or Batch Close. Let it process. This can take 30 to 60 seconds. Once it completes, try a transaction again.

Terminal Freezes or Locks Up

A frozen screen with a blinking cursor, or a screen that doesn't respond to key presses.

1. Do the soft reset. Unplug both cables, wait 60 seconds, reconnect power first, then network. This clears the terminal's memory and forces it to reinitialize.

2. Check for stuck keys. Sometimes a key physically sticks down. Press each key on the keypad firmly and release it. Listen for the click. If a key feels mushy or doesn't pop back up, that key is stuck.

3. Perform a hard reset from the admin menu. Press the Menu key, enter your admin password (default is usually 166831 or 166832), and select System Reset or Factory Defaults. This will erase stored transactions and reinitialize the terminal. You will need to call your processor to reprovision the terminal after a hard reset.

4. Perform a cold boot with the battery removed. Same as the "no power" cold boot, but the battery removal step forces a complete discharge of the internal capacitors. Reassemble and try again.

Printer Problems

The FD150 uses a thermal printer. It doesn't use ink or toner. If the print is faded or the paper is jamming, the fix is usually the paper itself.

1. Check the paper orientation. The thermal paper has a coated side and a plain side. The coated side must face the print head. If you load the paper backward, you get nothing or very faint printing. Look at the paper roll: the coated side curls inward. If your paper is curling outward and you're getting faint print, flip the roll over.

2. Clean the print head. Over time, dust and paper residue build up on the thermal print head. Open the paper compartment. Use a cotton swab lightly moistened with isopropyl alcohol (90 percent or higher) to wipe the glass strip on the print head. Let it dry for two minutes before closing the compartment and testing.

3. Remove a paper jam. If the paper is stuck, do not pull it backward. Pulling backward can strip the gears. Instead, open the paper compartment door fully. Gently pull the paper forward in the direction it normally feeds. If it's completely stuck, remove the paper roll entirely, clear any torn pieces, and reload a fresh roll.

4. Check the paper roll size. The FD150 uses 57mm-wide thermal paper with a maximum roll diameter of about 40mm. If your paper roll is too thick, it can jam inside the compartment.

Card Reading Issues

The terminal won't read the chip, the swipe, or the tap.

1. Clean the chip reader. Insert a card with the chip facing up. Push it in and pull it out a few times. This can dislodge dust. If the reader is dirty, use a compressed air duster to blow out the slot. Do not use liquid cleaners inside the chip slot.

2. Check the magstripe reader. Swipe a card that you know works. If the stripe reader fails, clean the swipe slot with a card wrapped in a lint-free cloth slightly dampened with isopropyl alcohol. Insert and swipe the wrapped card a few times to clean the read head.

3. Try a different card. Some chips fail. Some stripes wear out. Try another card from a different issuer. If the second card works, the problem is the original card, not the terminal.

4. Restart the terminal. Sometimes the EMV reader's internal firmware glitches. A power cycle resets the reader module.

Step-by-Step Reset and Recovery Procedures

Some issues need more than a quick fix. Here are the complete procedures for the deeper recovery steps.

Soft Reset (Power Cycle)

This is the safest reset. It does not erase any settings or transactions.

• Disconnect the power cable from the back of the terminal.
• Disconnect the network cable (ethernet or phone line).
• Wait 60 seconds.
• Reconnect the network cable first. Wait for the network light to turn solid green.
• Reconnect the power cable. The terminal should boot up normally.

Hard Reset (Factory Restore)

This erases all stored transactions and settings. You will need to reprovision the terminal with your processor.

• From the idle screen, press the Menu key.
• Enter the admin password. If you don't know it, contact your merchant services provider.
• Navigate to System or Utilities.
• Select Factory Defaults or Initialize.
• Confirm the selection. The terminal will reboot.
• After reboot, the terminal will prompt you to call for activation. Call your processor.

Printer Head Cleaning

This should be done every three months or whenever print quality drops.

• Open the paper compartment door.
• Remove the paper roll.
• Locate the thermal print head. It's a glass strip running the width of the compartment.
• Dip a cotton swab in 90 percent isopropyl alcohol.
• Gently wipe the glass strip from left to right.
• Let the alcohol evaporate completely (about two minutes).
• Reload the paper with the correct orientation.
• Close the compartment and run a test print from the diagnostics menu.

Batch Settlement

Run this every night or whenever the terminal seems slow.

• Press the Menu key.
• Enter your admin password.
• Navigate to Settlement or End of Day.
• Select Settle Batch.
• Wait for the terminal to process. It will print a settlement report.
• Once the report prints, the batch is closed and the terminal is ready.

Common Error Codes and What They Actually Mean

Here's a quick reference table for the most common FD150 error codes.

Image source: Bing (Web (fair-use with source credit))

Decoding Less Common Codes

Some error codes are less frequent but still easy to fix.

• Code 100 usually means the transaction amount exceeds the floor limit or the terminal requires online authorization. Try running the transaction as a force or contact your processor for an authorization code.
• Code 300 indicates a magnetic stripe read failure. Clean the swipe slot and try again.
• Code 400 is a PIN entry error. The customer entered the wrong PIN too many times, or the PIN pad timed out. Ask the customer to re-enter carefully.

Mistakes That Waste Time or Break Your Terminal

After researching hundreds of support call transcripts, these are the most common missteps.

Pulling Paper Backward

This one damages the printer mechanism. The FD150's printer feeds paper in one direction only. If the paper jams, never yank it backward.

Open the door, lift the paper roll, and pull forward gently. If it tears, remove the pieces by hand.

Resetting Before Checking the Network

A huge number of "my terminal is broken" calls turn out to be a dead internet connection. Before you reset anything, verify the network. Plug a laptop into the same cable.

Ping your router. If your network is down, no amount of terminal resets will help.

Using the Wrong Power Adapter

The FD150 needs exactly 12V DC at 2 amps. A higher voltage will fry the circuit board. A lower voltage won't power the terminal properly, causing random lockups and boot loops.

Label your adapter. If you're unsure, check the printed specs on the brick.

Ignoring the Diagnostic Lights

The three LEDs give you a real-time status summary. A solid green network light means your connection is fine, so don't waste time chasing network issues. An amber power light means the battery is low, not that the terminal is broken.

Assuming the Terminal Is Dead During a Processor Outage

Sometimes the problem isn't your terminal at all. It's the payment processor's data center. If you see error code 9000 and your network tests pass, check your processor's status page or call their support line.

A regional outage is rare but happens. If it's a processor problem, there's nothing to fix on your end.

When to Call for Help vs. When to DIY

Not every problem needs a support call. Here's how to decide.

What You Can Fix Yourself

• Paper jams and paper orientation issues
• Power cycling and soft resets
• Cleaning the chip reader and magstripe slot
• Checking network cables and restarting your router
• Running a batch settlement

These are simple steps that take five minutes or less. Try them before you pick up the phone.

What Requires a Support Call

• Reprovisioning after a hard reset or factory restore
• Admin password recovery
• Processor-level issues like a frozen merchant account
• Error codes that persist after all your own troubleshooting

When you call, have your merchant ID number and the terminal serial number ready. Write down the error code first. Support can move faster if you've already done the basic checks.

What Needs a Repair Shop

• A cracked screen or damaged keypad
• A power adapter port that's broken loose from the circuit board
• A printer mechanism that won't feed paper at all
• Battery replacement (on most models, this is not user-serviceable)

FD150 terminals typically last five to seven years with regular use. If your unit is older than that and needs a major repair, it's usually cheaper to replace it.

How to Escalate Efficiently

Start with your merchant services provider, not the manufacturer. They own the account and can reset settings remotely. If they can't help, ask them to escalate to First Data's technical support tier two.

Tier one reads from a script. Tier two can access the terminal's remote diagnostics.

Real Scenarios: What Actually Happens in the Field

Here are four real situations we've seen play out, with the lessons built in.

Scenario One: "My Terminal Won't Turn On"

A bakery owner called support in a panic on a Saturday morning. The terminal was dead. No lights, no display.

The first question from support was: "Did you check the power cable?" The owner had pulled the terminal away from the wall to clean behind it and the DC jack came loose. Plugged it back in. Problem solved.

Total time: 30 seconds.

Lesson: Always check both ends of the power cable first.

Scenario Two: "Error Code 9000 After a Storm"

A gas station lost connectivity after a thunderstorm. The terminal showed error code 9000. The owner reset the terminal three times with no luck.

He called support, who asked if the internet was working. He hadn't checked. The storm had knocked out his cable modem.

Once the cable company restored service, the terminal worked fine.

Lesson: Before you reset anything, confirm your network is alive.

Scenario Three: "Printer Prints Blank or Light"

A restaurant complained that receipts were coming out blank. The staff had loaded a new roll of thermal paper that morning. The paper was loaded backward.

The coated side was facing away from the print head. A quick flip fixed it.

Lesson: Thermal paper has a correct orientation. The coated side curls inward.

Scenario Four: "Terminal Freezes Every Monday"

A retail shop had a terminal that froze every Monday morning. The owner finally called after three weeks. The problem was unbatched weekend transactions.

Every Monday, the terminal hit its memory limit and locked up. A batch settlement on Sunday night fixed it permanently.

Lesson: Settle your batch daily, especially before a day with no transactions.

Frequently Asked Questions

Why does my FD150 keep showing error code 9000?

Error code 9000 means the terminal cannot communicate with the payment processor. Check your network cable connection. Restart your router.

Run a network test from the diagnostics menu. If the test fails, your internet connection is the problem, not the terminal.

How do I reset my FD150 to factory settings?

Press the Menu key, enter your admin password, navigate to System or Utilities, and select Factory Defaults. The terminal will reboot and prompt you to call for activation. You will need your merchant services provider to reprovision the terminal afterward.

What kind of paper does the FD150 use?

The FD150 uses 57mm-wide thermal paper with a maximum roll diameter of about 40mm. The paper must be loaded with the coated side facing the print head. The coated side curls inward on the roll.

How do I clean the printer head on my FD150?

Open the paper compartment and remove the paper roll. Use a cotton swab lightly moistened with 90 percent isopropyl alcohol to wipe the glass strip on the print head. Let it dry for two minutes before reloading the paper and testing.

Why won't my FD150 read the chip on my customer's card?

The chip reader may be dirty. Insert and remove a card a few times to dislodge dust. If that doesn't work, use compressed air to blow out the slot.

If the reader still fails, try a different card. Some chips fail or get damaged.

How often should I settle the batch on my FD150?

Settle the batch daily, even on days with no transactions. Unbatched transactions accumulate in the terminal's memory. When the memory fills up, the terminal can freeze or lock up.

A nightly settlement prevents this.

Final Decision Guide

Here's your one-page cheat sheet for FD150 troubleshooting.

Keep this guide near your terminal. Most fixes take under two minutes. You don't need to be a technician.

You just need to know which clue to follow.