topic Re: TESTMODE - An error occurred during processing. Please try again. in Integration and Testing

TESTMODE - An error occurred during processing. Please try again.

lakario — Thu, 12 Aug 2010 21:53:26 GMT

I am receiving the following error from all requests made with my developer account. The code being executed has worked fine until I became aware of it failing today. If I switch to different login credentials (a non-developer account), I do not receive any errors.

(TESTMODE) An error occurred during processing. Please try again.

This is what I am receiving from the Data Valdiation URL with my request parameters:

x_type	AUTH_ONLY
x_card_num	4111111111111111
x_exp_date	1-2013
x_card_code	145
x_version	3.1
x_method	CC
x_delim_data	True
x_password	********
x_login	********
x_test_request	True
x_amount	12.24
x_tax	0.79
x_first_name	Nathan
x_last_name	Taylor
x_zip	12345
x_address	123 Fake St
x_city	Fake Town
x_country	US
x_phone	5555555555

Re: TESTMODE - An error occurred during processing. Please try again.

GooMooJeff — Thu, 12 Aug 2010 22:08:18 GMT

I'm experiencing the same problem. Hopefully it will be fixed soon so I can continue to work on the test site.

Re: TESTMODE - An error occurred during processing. Please try again.

galori — Thu, 12 Aug 2010 22:39:32 GMT

Same here. I saw some old threads with a similar error message, and the conclusion was that it was an error on the authorize.net end, and they had to fix it.

Re: TESTMODE - An error occurred during processing. Please try again.

Michelle — Thu, 12 Aug 2010 23:09:30 GMT

The testing server is down right now. We'll be posting more the message here once we have more information available.

Thanks,

Michelle

Developer Community Manager

Re: TESTMODE - An error occurred during processing. Please try again.

ckistler — Sun, 29 Aug 2010 23:16:17 GMT

I'm still receiving this error. Is the server still down? If so, any idea of when it may be fixed? Is there another work around for testing?

Thanks

Re: TESTMODE - An error occurred during processing. Please try again.

yoeauthorize — Fri, 11 Mar 2011 09:54:26 GMT

i m getting the same error ? does anyone know wat exactly is the issue? or how to solve this?

Re: TESTMODE - An error occurred during processing. Please try again.

vicky9sharma — Fri, 11 Mar 2011 11:17:47 GMT

We are facing same problem. Getting error while processing the transaction and also unable to create new account

the captcha is failing again and again.

TESTMODE - An error occurred during processing. Please try again.

bangme9 — Fri, 11 Mar 2011 12:44:29 GMT

Hi,

From the morning I'm trying to do sample transaction in the test mode.

Its giving the error, “An error occurred during processing. Please try again. “

Is my account expired?

When I’m trying to create new account from URL: https://developer.authorize.net/testaccount it showing ever fields in the Green color, and when I click on the submit button the page post back’s and remain in the same. Failing captcha again and again.

I created my account on 05/10/2010

How to solve this? Please help

Regards,

Ravi Teja . Koneru

Re: TESTMODE - An error occurred during processing. Please try again.

Michelle — Fri, 11 Mar 2011 16:30:24 GMT

Hey there,

The test server is currently down. Check the post here for status updates.

Thanks,

Michelle

TESTMODE - An error occurred during processing. Please try again.

shanker346 — Mon, 01 Aug 2011 14:16:05 GMT

I am getting this error message.

Please do help.

Thanks in advance

Re: TESTMODE - An error occurred during processing. Please try again.

mukeshrane — Mon, 01 Aug 2011 14:20:54 GMT

am getting the same error today while testing the trascation using (TESTMODE) please help me out

Re: TESTMODE - An error occurred during processing. Please try again.

jbubbison — Mon, 01 Aug 2011 14:49:19 GMT

I began receiving this message this morning, too. All code was functioning as expected on Friday, 7/29, and no code has been modified since.

Re: TESTMODE - An error occurred during processing. Please try again.

vhtest — Mon, 01 Aug 2011 14:54:28 GMT

I am getting the same error today (08/01).