I am using a test account to test transactions. I am using the Direct Post Method. It seems to be going well. I did a few transactions and got the expected responses. Now, whenever I send a transaction, I get:
|Response Reason Code||97|
|Response Reason Text||(TESTMODE) This transaction cannot be accepted.|
Use the error 97 tool http://developer.authorize.net/tools/responsecode97/
are you using 4222222222222 as the credit card #?use 4111111111111111
also, if you using a test account, no need to turn testmode on.
>Use the error 97 tool http://developer.authorize.net/tools/responsecode97/
I have verified my timestamps and they are within several seconds of Authorize.net's.
>are you using 4222222222222 as the credit card #?use 4111111111111111
I have used several credit card numbers, including real ones.
>also, if you using a test account, no need to turn testmode on.
Perhaps not, but it's good to have that documented in the values I'm sending. Also, that shouldn't cause the code 97 error. That's what I'm trying to get an explanation for.
>What API are you using, or are you trying to send raw XML requests?
As I said above, I'm using Direct Post.
>Post your code, preferably in a code box
I'm not using code, I'm just sending the values from a web page.
>Test accounts are not the same as test mode. Always use Authorize.net accounts in live mode
I'll try that and see if it helps. Thanks.
> The other thing that I could think of you may be sending something unexpected in you DPM form.
The weird thing is that it worked the first few times. I got an approved response. I'm sending the same data again, except for the timestamp and its related hash. I've tried sending it a new invoice number, but that doesn't seem to help.
>Can you copy the form post from the web browser page source on that DPM page, and blank out the loginID so we can see it here?
I went to copy that information from the page and it winds up my software wasn't loading one of the values after the first test. Thanks for all the help.