Reply
Member
iblood
Posts: 3
Registered: ‎05-13-2010

AN ERROR OCCURRED DURING PROCESSING. PLEASE TRY AGAIN.

What causes this error:

AN ERROR OCCURRED DURING PROCESSING. PLEASE TRY AGAIN.

And how can it be resolved. 

I been trying to lots of test order on our site and it keeps sending me this error, but it's working on test mode..

Just dont know why it's throwing me this error when I turn off the testmode.

 

Hope somebody can help and enlighten me :robothappy:

 

thanks

stymiee
Posts: 1,462
Topics: 17
Kudos: 70
Solutions: 126
Registered: ‎09-14-2009

Re: AN ERROR OCCURRED DURING PROCESSING. PLEASE TRY AGAIN.

We'll probably need to see your code. If it's PHP I can check it out for you.


-------------------------------------------------------------------------------------------------------------------------------------------
John Conde :: Certified Authorize.Net Developer (Brainyminds) :: Official Authorize.Net Blogger

NEW! Integrate Every Authorize.Net XML API with One PHP Class (Sample code included)

Tutorials for integrating Authorize.Net with PHP: AIM, ARB, CIM, Silent Post
All About Authorize.Net's Silent Post

The Handling Online Payments With Authorize.Net and PHP Series
Part 1 | Part 2 | Part 3 | Part 4 | Part 5 | Part 6 | Part 7 | Part 8 | Part 9 | Part 10 | Part 11

My Blog posts for Authorize.Net - The Validating Credit Card Series
Credit Card Numbers | Expiration Dates | CVV Numbers

My Blog posts for Authorize.Net - Other Topics
Notifying Users Their Credit Card Is About to Expire Without PCI Compliance Issues
Precision Math with PHP
HTTP Headers to Help Secure Your Website

Please don't ask me questions via private message or email. They will be ignored.
Use the forums. That's what they are here for.
Moderator
Trevor
Posts: 545
Registered: ‎08-21-2009

Re: AN ERROR OCCURRED DURING PROCESSING. PLEASE TRY AGAIN.

If the transactions are working in test mode, this is most likely an error from the account setup.  If you are receiving it for every transaction, than your Authorize.Net account probably isn't properly linked to your merchant account.  This can usually be resolved by retrieving your processing parameters (commonly called var sheet ) from your merchant account provider and providing them to Authorize.Net support.  For security reasons, that update has to be done over the phone.

Member
iblood
Posts: 3
Registered: ‎05-13-2010

Re: AN ERROR OCCURRED DURING PROCESSING. PLEASE TRY AGAIN.

[ Edited ]

$post_values = array(

"x_login" => X_LOGIN,

"x_tran_key" => X_TRAN_KEY,

"x_version" => "3.1",
"x_delim_data" => "TRUE",
"x_delim_char" => "|",
"x_relay_response" => "FALSE",
"x_type" => "AUTH_CAPTURE",
"x_method" => "CC",
"x_card_num" => $values['cardnumber'],
"x_exp_date" => $values['expire_date'],
"x_card_code"       => $values['security_code'],
"x_amount" => $values['order_total'],
"x_description" => X_DESCRIPTION,
"x_first_name" => $values['firstname'],
"x_last_name" => $values['lastname'],
"x_address" => $values['address1'],
"x_state" => $values['state'],
"x_phone" => $values['phone'],
"x_email" => $values['email'],
"x_city" => $values['city'],
"x_zip" => $values['zipcode']
);

 

 

$post_url = "https://secure.authorize.net/gateway/transact.dll";

 

 

$post_string = "";

foreach( $post_values as $key => $value )

{ $post_string .= "$key=" . urlencode( $value ) . "&"; }

$post_string = rtrim( $post_string, "& " );

 

 

 

$request = curl_init($post_url);

curl_setopt($request, CURLOPT_HEADER, 0); 

curl_setopt($request, CURLOPT_RETURNTRANSFER, 1); 

curl_setopt($request, CURLOPT_POSTFIELDS, $post_string); 

curl_setopt($request, CURLOPT_SSL_VERIFYPEER, FALSE); 

$post_response = curl_exec($request); 

curl_close ($request);

 

 

that's my code...

This has been used on other sites i have, and this is working fine on those sites.

 

hope anyone can help.


Member
iblood
Posts: 3
Registered: ‎05-13-2010

Re: AN ERROR OCCURRED DURING PROCESSING. PLEASE TRY AGAIN.

@trevor, can you please give further details? 

Moderator
Trevor
Posts: 545
Registered: ‎08-21-2009

Re: AN ERROR OCCURRED DURING PROCESSING. PLEASE TRY AGAIN.

What I described would mean that it is not a development issue at all.  It is something that the merchant needs to work out with Authorize.Net support and their merchant account provider.  The merchant would need to provide Authorize.Net support the correct processing parameters to address the issue.  If you are listed as a user on the account, one of our support representatives should be able to confirm if this is actually the issue or not.