Objective

To be able to determine specific errors retailers are experiencing when using a terminal/PIN Pad that uses the eConduit middleware. 

Setup

• eConduit application
• eConduit Portal

Steps

1. Navigate to the eConduit Portal
2. Enter the Serial Number of the terminal
3. Select the Transactions icon
4. Locate any Errors you can see in the transaction history option

There are a number of errors that can occur when programming a device, resulting in a variety of error prompts.

Please Settle Error

This means that the terminal hasn't batched out their previous sales and until they manually close the batch, they will not be able to run card transactions. 

Solution: Depending on the device, they will need to follow Manual Batch S300, Manual Batch D210 or Manual Batch A-series. We will then need to work with the contact who built the file, to make sure it is set to Auto-Batch.

Terminal Is Busy Error

This means that a previous transaction is 'stuck' hitting our servers. When a transaction is pushed to the Credit Card reader, it declines.

Solution: Resetting the router and Credit Card reader clears the traffic.

Terminal Is Offline

This means that the terminal is being blocked from sending outbound traffic to the eConduit service.

Solution: There is a customer facing article here that provides a checklist for the retailer to go through on their local network.

Receive Error 

The parameters that were entered into the file build are incorrect. 

Solution: The retailer will need to contact their partner or reseller who provided the terminal to update the BroadPOS file with the correct parameters under the processor tab to make sure it matches the information on the VAR sheet. They will then need to power cycle the terminal to update the changes made.

Dup Transaction error

The processor flags the second sale as a duplicate as it only recognizes the Credit Card number and sale amount, so it flags it for being a duplicate

Solution: Either change the sale amount so it's recognized as a new transaction or wait until the batch is closed on the terminal before attempting the duplicate transaction

Pax and Dejavoo duplicate check at the device level.  The processor who built the device  stage file can disable this feature to allow all sales to go through. This is not recommended unless a retailer processes a lot of  legitimate duplicate transactions (i.e. coffee shops).

1000003 Invalid Error

A retailer is unable to process transactions on their Pax terminal. When a sale is pushed over to the terminal, it either cancels straight away or is accepted on the terminal but declined in Retail POS

Solution: 

The current version of the BroadPOS application they are running on the Pax device isn't compatible with Retail POS. The partner needs to roll back the BroadPOS application in the Pax Store to an older version and then push a new download to the terminal.

1000007 Status Error

A retailer will successfully pair their Pax terminal to Retail POS, but when they attempt a transaction, the terminal isn't prompted and the sale cancels.

The data wire was requested but it was not activated. Normally this is done when the file download is pushed but it may also need to be manually done on the device and it needs to be activated on First Data’s end.

Solution

The Datawire ID  needs to be provisioned and this can be resolved 2 ways.

First, they need to attempt reactivate the Datawire request. To try and manually reactivate they will go to the First Data app on the device then select FUNC > Settings > Host Settings > Host Register and follow the prompts.

If that doesn't work,The partner will need to contact First Data to create a new one and then activate it. Once that has been done, the partner will need to push or manually download the file again to update it.