System Five Add-Ons & Integrations help simplify the way you do things.
Our catalog of services has topic-based, role-based, or technical plans that can help you maximize your software investment.
Copyright © 1984-present
Windward Software Systems Inc.
All Rights Reserved.
Privacy Policy
Parent Article: Troubleshooting Credit Card Results From Mercury Payments
This is an error message that shows on the slip reciept. There are scenarios where these transaction get processed and go through, and other scenarios where the do not go through.
Here is a text representation of a merchant copy receipt showing the “Timeout on Response” message:
Company Name Goes Here Credit Card Sale Invoice # goes here DATE 10/2/2010 TIME 3:32:10 PM TILL 3 CARD NUMBER xxxxXXXXxxxx9999 EXPIRE 9999 CARD TYPE Master Card NAME Carholder name here AMOUNT $99.99 Timeout on Response RESULT Error AUTHORIZATION REFERENCE ---------------------------------------- Signature of Card holder I agree to pay the above amount according to the card issuer aggreement.
The quick answer is that there were “communication issues” between Mercury Payments servers and Global Payments servers. There would be various possible causes, but they are beyond our control, and not situations that we have details about.
This could apply to anyone using Mercury Payments.
Basically System Five sends a request to Mercury Payments then they sent the request to Global Payments. The request back from Global to Mercury did not get returned and the request timed out. The transaction may or may not have processed at Global Payments.
In this situation you retry processing the transaction. You do this because we do not know if the transaction was processed by Global Payments. The same invoice number must be used, so “DO NOT” open a new invoice and try the transaction there. It may result in double processing of the sale. If the transaction did process at Global Payments and we try to process it again on the same invoice, we will get a duplicate response. This is a good thing because it recognizes that the transaction has processed correctly. (Note: What exact message and screen would we see? Find out)
This is not a question for Windward Software as it is not in our control, but the answer is yes. Mercury Payments and Global Payments are always taking measures to prevent these types of problems, and they are very diligent about ensuring proper operation and reliability.
We will have to leave this up to the capable hands of those Global Payments, and Mercury Payments.
This error code is referenced in the programmers reference / ClientX document from Global Payments.