Reply
All Star
Posts: 1,072
Registered: ‎08-17-2009

Triggering Specific Transaction Responses

[ Edited ]

Using the Sandbox Account Error Generation Guide, developers can trigger specific transaction responses in the sandbox including approvals, declines, errors, as well as AVS and Card Code responses.

 

Use this thread for discussion: http://community.developer.authorize.net/t5/Integration-and-Testing/Triggering-Specific-Transaction-...

 

Richard

Member
Posts: 2
Registered: ‎06-07-2010

Re: Triggering Specific Transaction Responses Using Test Account

Hi,

I am using the methods in this thread to post a partial auth transaction.

AIM method
Amount: $295.00

Zip code: 46225

x_type = "AUTH_CAPTURE"

x_test_request = "false" (was not working previously when set to true)

Posting to: https://test.authorize.net/gateway/transact.dll

This was working perfectly on Friday (returning 1.23), but at the moment, I am getting an authorized amount of  "1..23" in the raw responsePlease note the dual decimal points. Can anyone else reproduce this or have a suggestion? If further information is needed, please let me know. Thanks.

All Star
Posts: 1,072
Registered: ‎08-17-2009

Re: Triggering Specific Transaction Responses Using Test Account

Hi there,

 

Are you still seeing this error? We haven't had any reports of similar errors and aren't able to reproduce it on our end.

 

Thanks,

 

Michelle

Developer Community Manager

Member
Posts: 3
Registered: ‎08-31-2010

Re: Triggering Specific Transaction Responses Using Test Account

I can get specific AVS testing responses by using the 'zip-code' but I can't get any card-code responses by using the 3-digit card-code for CVV testing???

The cvv response is always 'blank'.

I've made sure to not send an address or a zip-code thinking that may override but still no luck.

Any suggestions.

 

Moderator
Posts: 590
Registered: ‎08-21-2009

Re: Triggering Specific Transaction Responses Using Test Account

If you are using AIM, make sure that you are setting the version to 3.1 either in the Merchant Settings or by submitting x_version=3.1

 

Version 3.0 of AIM was limited to only 38 fields, 3.1 expanded this to an indefinite number of fields with the CVV response in field 39.  Card Code Validation cannot be performed using version 3.0.

Member
Posts: 3
Registered: ‎08-31-2010

Re: Triggering Specific Transaction Responses Using Test Account

I'm sending x_version=3.1 but still BLANK CVVresultcodes with card code as 901 to produce an error.

field 39 ???

I'm receiving in XML and there is no 'field 39'.

//response/CVVResultCode  is still always BLANK.

 

Contributor
Posts: 28
Registered: ‎09-13-2010

Re: Triggering Specific Transaction Responses Using Test Account

I'm having a similar issue.  My address, cvv and expiration are being passed (I can echo them upon a successful transaction) but when I look up the transaction in my authnet account, it says CVV: Not Applicable and AVS: Not Applicable

 

Right now, I can enter a legitimate credit card with fake CVV and expiration and it still goes through as successful....

Contributor
Posts: 28
Registered: ‎09-13-2010

Re: Triggering Specific Transaction Responses Using Test Account

Ok, the reason why AVS and CVV is not applicable is because x_recurring_billing was set to true.

 

Recurring billing disables AVS.

 

I have to credit BobbySmith007 for the solution.

Member
Posts: 2
Registered: ‎09-24-2010

Re: Triggering Specific Transaction Responses Using Test Account

I've tried to test for declined transaction responses from AIM using both the 4222222222222222 credit card and the 46282 zip code value (independently and together) in the production environment with x_version=3.1 and x_test_request=TRUE.

Any request with the 4222 card yields an invalid card error; requests with a valid LUN card and the zip of 46282 yields an approved transaction.

 

Any ideas what I might be doing wrong?

Highlighted
All Star
Posts: 1,072
Registered: ‎08-17-2009

Re: Triggering Specific Transaction Responses Using Test Account

Hey tracent,

 

The zip code triggers only work when you are using the test environment. If you are using a production account, they won't work. Also, you need to make sure the 4222 test card you are quoting is only 13 digits. Any longer and it won't work. That test card will work in the test environment as well as the live one--but only in test mode on the live site.

 

Give it a try again using the fixes above and see if that works.

 

Thanks,

 

Michelle

Developer Community Manager