Error 99: This transaction cannot be accepted.
Response Reason Code: 99
Response Reason Text: This transaction cannot be accepted.
Notes: Applicable only to the SIM API. The server-generated fingerprint does not match the merchant-specified fingerprint in the x_fp_hash field.
For security reasons, SIM requires the generation of a fingerprint hash, based on five values: amount, API Login ID, Transaction Key, timestamp and sequence number. (The sequence number can be set to the invoice number you generate for each order, or it may be randomly generated as long as it is a unique number that changes from one order to another.)
Issues with these values or with the generation process can cause Error 99. The three most likely causes of Error 99 are:
1) The Transaction Key that you have embedded in your script is not correct. Just to be sure, generate a new transaction key, disable the old transaction key, enter the new value in your script and test the connection.
To obtain the Transaction Key:
1. Log into your Merchant Interface at
https://account.authorize.net.
2. Click
Account from the main toolbar.
3. Click
Settings in the main left side menu.
4. Click
API Login ID and Transaction Key.
5. Enter your Secret Answer (the answer to your Secret Question configured at account setup).
6. To disable the old transaction key, click the check box labeled
Disable Old Transaction Key.
(Note: If the Disable Old Transaction Key check box is not selected, the old transaction key will automatically expire in 24 hours.)
7. Click
Submit to continue. Your new Transaction Key is displayed.
Please be sure to have your API Login ID and Transaction Key set in your scripts. When using PHP and ASP sample scripts, these fields must be filled out in your simdata.php or simdata.asp file, respectively. In the PERL sample script, it must be entered into the sim.pl script.
2) The amount has to be set in your scripting prior to the generation of the fingerprint hash. This usually means that the amount should be set in a previous form and posted to the script that generates the fingerprint hash.
3) You may not be properly posting all the required fields for SIM.
The following fields must be present in your payment form request in order for the transaction to be accepted:
1. API Login ID (x_Login)
2. The sequence number of the transaction (x_FP_Sequence)
3. The time when the sequence number was generated (x_FP_Timestamp)
4. The Fingerprint Hash (x_FP_Hash)
5. The amount of the transaction (x_Amount)
4) If you are attempting to pass the field x_currency_code with your payment form request, you must include this field in your fingerprint hash generation. Since Authorize.Net currently handles transaction amounts in the merchant's local currency by default, you may alternately stop passing x_currency_code.
For more information, see our Error 99 resolution tool at
https://developer.authorize.net/resp...p?page_id=7199
Bookmarks