NOTE: A Status Error does not mean the device needs to have the DataWire reset.  If the device hasn’t registered with DataWire, there is nothing to reset.  Check the description given after the “Status Error” and troubleshoot accordingly.

 

Datawire: This is used for all FIRST DATA transactions over LAN (Datawire is not used for terminals processing over dial).  It uses your merchant credentials to connect to First Data and download an IP Config file that First Data uses to confirm you are the correct merchant.

 

Datawire checks for a valid:

FDRCNV Verifies:

1. Merchant ID
2. Terminal ID (Datawire uses a leading "0" in front of the TID for North builds that have less than 8 digits)
3. Group ID

OMAHA Verifies:

1. Merchant ID
2. Device ID

Datawire Reset: The Datawire can be reset on the Host end. If the application uses a DID they may need to change the DID if it will not connect.  If the device was previously registered but is currently unable to connect, then the DataWire should be reset.

Self Registration: Terminal automatically registers the Datawire with the first transactions. This is typically done with the FDRC applications.

Host Register: Connects the Datawire to the terminal. Follow the steps below to do registration on the terminals. Once completed the terminal will say SUCCESSFUL.

1. Menu
2. Host Settings
3. Host Register
4. Provision (Self-Register if it's a FDRCNV app)

Status Error/ Connect Error:  Datawire issues can sometimes read as a "connect error" when trying to process a payment. Do a Host Register/Provision to isolate if the connect error is related to the Datawire (Status Error) or the Network.

A “Status Error” message us usually followed by a description of what the error is.  The error may be truncated, for example “Authentication Error” might show as “AU” on the terminal.

Authentication Error: This error means the information sent doesn't match what is on the Datawire side. Check the parameters and make sure the MID, TID, and GID are correct. Then do a Host Register/ Provision. If you are still getting an error, have the customer conference in Datawire Support. 

Access Denied: The TID is already registered, the DataWire was previously connected.  If the terminal cannot run a transaction, the DataWire must be reset.

No Ticket:

A “No Ticket” error means that there is no ticket to register the device with DataWire.  This could mean that the device hasn’t been created yet.  It could also meant there is an error in the file build that is causing DataWire to fail to recognize the device.

1. Check if the TID is using the leading "0" in your file build.
2. Confirm with Datawire the MID number they used to activate the Datawire and attempt another Host Register on the terminal.
3. Confirm the Group ID is correct

Note for Multi-Merchant Applications: If the merchant is running a Multi-Merchant Application one Merchant may be able to process and not the other(s). Verify the error and troubleshoot accordingly for the merchant.  If the sub-merchant was previously registered and now cannot connect, a referral to DataWire for a reset for the affected Merchant(s) would still be needed. 

Note for DigiRoot Certification/DataWire Hardware Refesh:  If the application is out of date, the connection will eventually be closed by FirstData, even if the device was previously registered and worked perfectly.  If a device has been working previously and is now not connecting, check the application version and update if not current.