Applet Debug Steps
Error: Bridge Service Not Running
If you are receiving a message from the Virtual Terminal page or a failure to connect to the SignalR bridge service, the first step is to check that the BFCSignalR Bridge service is running in the Windows Services applet.
Click the Start Menu and type “View Local Services” (Windows 8), “Services” (Windows 10, Windows 11) and select the Desktop App that will start the Windows Services list.
If the BFCSignalRBridge service is not present on the computer, please install it. See https://bfc-usa.com/knowledge-base/bfc-applet-v5-1/ for instructions on how to install.
If the Status of the BFCSignalRBridge service is not “Running,” please click the green right arrow and start the service.
If the Status is already “Running,” try to Restart the service. If it fails to stop (or it takes longer than 10 seconds), use Task Manager (Ctrl-Shift-Esc) to End Task the BFCSignalRBridge.exe process.
Once the task is ended, you and start it through the services application again.
Security Warning about Expired Certificate
If you received a warning message about the site has an expired certificate, the initial installation of the applet created an SSL certificate that was valid 3-5 years and has expired. Follow the instructions at https://bfc-usa.com/knowledge-base/browser-does-not-trust-signalr-host/ to generate a new SSL Certificate and get the system working.
No Response From Terminal
If the BFCSignalR Bridge service is running but no communication with the terminal is occurring (ie, the screen shows “Waiting for Customer” but the terminal is stuck at “This Lane Closed” or “Please wait for Cashier”), we can stop the BFCSignalRBridge service and then restart the EMV terminal.
- Follow the above steps to Stop the service (this will remove the application that may lock access to the COM port for the device).
- Next, press and hold the Yellow “<” key and the “.,#*” key together for 3-4 seconds. The terminal will restart.
- Start the BFCSignalRBridge service once the device starts the reboot process.
Does this correct the problem? If not, we need to check the COM port settings of the terminal.
Checking COM port settings
If the BFCSignalRBridge service cannot detect the terminal but the Bridge service is running, we need to check the connectivity and COM port setting of the device.
Right Click on the Start menu (Windows 8, 10 and 11) and select “Device Manager.” On Windows 7, click the Start menu and right click on “Computer” and select Manage. Then expand to Device Manager.
Expand the Ports (COM & LPT) option and look for the Ingenico iPP3xx/iPP4xx, Ingenico Lane3xxx or other Ingenico XXXXX entry.
Does it have a “COM” value just after it? Make note of that value. If it does not have a value in parenthesis, double click on the item and click on the “Force Com Port” tab.
If the “Force COM Port Feature enabled” is not checked, please check this value. If you plug in the device into a different USB port, the COM port might move. By turning this feature on, it will keep the Ingenico device on the same COM port if nothing else is already assigned to that port.
Above, make sure the PID of 0060* and the value 9 is present for the COM Port. (9 is the BFC default port for EMV hardware). Next, set the “Order” on the bottom at “9.” The value 9 can be another number if you desire. Next, we need to check the BFC Virtual Terminal Config (https://admin.bfc-usa.com/VirtualTerminal/VirtualTerminalConfig.aspx) to make sure the merchant account matches this COM port.
* = The “PID” value is different, depending on the hardware terminal you have access to. The following PID value should be used for your hardware:
- 0060 = iPP3XX/iPP4xxx
- 0052 = Move 5000
- 0053 = Move 3xxx
- 0055 = Move 2xxx
- 0056 = Lane 7xxx
- 0081 = Lane 5000
- 0082 = Lane 8xxx
- 0083 = Link 2xxx
- 0084 = Lane 3xxx
Additional Debugging Options:
- Using the Browser to connect to the SignalR Bridge server (SSL certificate generation, service problems). See https://bfc-usa.com/knowledge-base/bridge-service-not-running-but-it-is/
- RBA Test App connectivity testing (defective device or problems with the hardware) See https://bfc-usa.com/knowledge-base/ingenico-drivers/
- Driver’s missing or outdated for the Ingenico hardware. See https://bfc-usa.com/knowledge-base/ingenico-drivers/ for more information
- COM port is just bad in the operating system – change the COM port.
- Old Hardware/Wrong version of RBA, bad communication or slow speeds (https://bfc-usa.com/knowledge-base/old-hardware-wrong-version-of-ingenico-software/)
- Browser no longer trusts the SignalR communication to https://localhost:3068 (see https://bfc-usa.com/knowledge-base/browser-does-not-trust-signalr-host/)