Verifone Mx915/Mx925 - issues before activation
FORM AGENT - CRITICAL ERROR : FAILED TO GET NETWORK PARAMETERS!
This error means No Internet connection. Potentially a Ethernet Cable plugged into wrong spot on the Verifone device itself, not firmly plugged in, or improperly placed into the router/internet connection. Be sure to use the Ethernet port that is closest to the power jack on your Verifone terminal device.
Once you fix the cable and get it correctly placed, fully reboot the device by removing the power and connecting the power back up.
FORMAGENT - TCPIP - SSL
The device has obtained an IP address from your local network but it can't communicate with the TriPOS Cloud Service. Most likely this issue is the communication blocked on Router Firewall or other Network Firewall over Port 9001 to allow TCP/IP traffic. Other checks, please check that your internet is working and reset the device by unplugging the power cord and plugging it back in. If possible try a different Ethernet port on your switch or router. It is possible that the device may need to be replaced, but please do research first.
- Please see https://fullsteam.zendesk.com/hc/en-us/articles/360030462632-triPOS-network-connectivity-information for network requirements.
(***If you are seeing large amounts of these devices with this issue*** - Contact Vendor, as the devices may be configured without the passphrase.)
SYNCHRONIZING WITH XPI APP. PLEASE WAIT ...
Trouble Activating the device in MerchantTrack:
If Activation Code Starts with 'C' instead of 'P' - Get a new device. 'C' is used for Test devices only.
In very rare cases, if activation code was originally provided and then get a red error in MerchantTrack but the device itself goes to the TriPOS screen, but then cannot view the device in MerchantTrack, Use triPOS Lane Management API: https://tripos.vantiv.com/cloudapi/swagger/ui/index#/ or may have to contact development team to have them look into the logs with the processor and have them remove device, provide the development team the serial number from the device and all the names the merchant goes by (Legal/DBA/Identifier), once development has confirmed removal from the processor, then have merchant try again or activate for them in MerchantTrack when they get prompted for an activation code.