FD150: Batch Error "Call Center"

FD150: Batch Error "Call Support"

Last Updated: July 25, 2023

Symptoms

  • (Optional Symptom) Attempting to run transaction and terminal says to settle the batch first
  • Attempting to settle a batch on an FD150 and receives error Call Support or Call Center

Causes

  • Issue with settling batch
    • Possible network connection Issue
    • Possible Parameter issue
    • Possible the batch closed with the processor, but is stuck on the terminal

Resolution

Try each step in order and check after each step

  1. Make sure your date and time is correct. If it is not, please correct this:
  2. If you needed to update your date or time, please re-attempt to settle the batch
  3. If no correction was needed or the batch still gives the error, Verify the network connection with a Ping Test:
    FD150: Verify Network Connection
    Public | Dec 02, 2024
    1. Enter a known IP Address to ping

      Tip: www.yahoo.com is typically entered in by default. Use that if it is already there.
      Tip:  A good IP to test on is 8.8.8.8 This is Google's DNS IP.

    2. Press green Enter button
    3. you will get the results of the Ping test on the screen.
    4. Press red Cancel button three times to return to the home screen 


  4. If the Ping test failed, please attempt to connect to a network and re-run the Ping Test 
    If Ping was successful, continue below
  5. Update the Param Init on the terminal
    FD150: Pram Init
    Public | Nov 25, 2024
    1. dcee78f890e7f68d4286e0a04a8c2bcd.pngSelect the Toolbox icon
    2. Select Settings
    3. Select Credit
    4. Select Params
    5. Select Param init
    6. Select your connection type:
      • If you use a phoneline, select Dial
      • If you use the internet, select IP based on connection type
    7. Press Enter (A number or site might show. pressing enter will populate the field.)
    8. Terminal will Download the Param init and reboot
  6. After the terminal reboots verify the date and time are still correct and that the Param Init did not change this
  7. Re-Attempt to close the batch
  8. If issue persists call Fortis Support

I found this article helpful
I did not find this article helpful