The terminal was unable to communicate with the server on the specified communication mode. This is usually due to the merchant account being closed due to risk concerns or a mismatch of the terminal ID in the application file.Īction: Contact our Merchant Services department at 47 to rectify any issues with the merchant account or being the process for applying for a new one. ![]() The terminal ID could not be verified on the merchant account. This usually occurs after major version updates on an application file.Īction: Contact our Technical Support at 47 to do a firmware update on the terminal. There is a mismatch between the firmware and application file versions. If the issue persists, contact our Technical Support at 47 or fill out our RMA form to request for a replacement. This could occur if the chip is not fully inserted into the card slot or if the EMV chip on the card is damaged.Īction: Retry the transaction and make sure to firmly insert the card all the way in or retry with a different card. Terminal was unable to correctly read the card information from the EMV chip. It may be necessary to re-provision the terminal if previously used with a different merchant ID. The device ID on the terminal associated with this merchant ID is not activated in Datawire or has been duplicated.Īction: Contact our Technical Support at 47 to activate the Datawire for the terminal or to register the Datawire for a new device ID. Note: If the batch needs to be force closed, any tips that were added on post-authorization will not be reflected and will need to be rekeyed. The terminal's database will need to be cleared afterwards. If the terminal still throws this error, then call our Technical Support at 47 to verify if the batch was already closed or to force close the batch. This can be caused by the batch number not properly incrementing on the previous batch operation, an overlap in the use of terminal/device ID numbers, etc.Īction: Increment the batch number and try to run the batch operation again. The batch number on the terminal does not match the expected batch number to be received or is not associated with a valid batch of transactions. This can cause an Added Tip fail, if the authorization was more than 25 min earlier. ![]() Note: This is a First Datawire Nashville process to prevent fraud, where they run a process called "Sweeps" that is used to clear off the data for authorizations. The Merchant must issue a refund.Īction: If possible and the card can be present, run a general refund for the amount or contact the processor for reversing the charges. If the POS has received a RW response (25 minutes after the original Authorization), the transaction cannot be reversed (voided). Reversal transaction was received, but the original matching authorization request was processed more than 25 minutes ago and is no longer eligible to be reversed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |