topic Re: Triggering Specific Transaction Responses Using Test Account in Integration and Testing

Triggering Specific Transaction Responses

Michelle — Tue, 03 Dec 2013 22:39:59 GMT

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-Responses/td-p/34842

Richard

Re: Triggering Specific Transaction Responses Using Test Account

oakleaf — Mon, 09 Aug 2010 15:34:23 GMT

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 response. Please note the dual decimal points. Can anyone else reproduce this or have a suggestion? If further information is needed, please let me know. Thanks.

Re: Triggering Specific Transaction Responses Using Test Account

Michelle — Wed, 11 Aug 2010 21:13:00 GMT

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

Re: Triggering Specific Transaction Responses Using Test Account

cptest1080 — Fri, 03 Sep 2010 14:00:29 GMT

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.

Re: Triggering Specific Transaction Responses Using Test Account

Trevor — Tue, 07 Sep 2010 22:15:52 GMT

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.

Re: Triggering Specific Transaction Responses Using Test Account

cptest1080 — Tue, 21 Sep 2010 20:38:01 GMT

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.

Re: Triggering Specific Transaction Responses Using Test Account

nexus — Wed, 22 Sep 2010 18:14:05 GMT

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....

Re: Triggering Specific Transaction Responses Using Test Account

nexus — Wed, 22 Sep 2010 18:37:44 GMT

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.

Re: Triggering Specific Transaction Responses Using Test Account

tracent — Fri, 24 Sep 2010 20:26:46 GMT

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?

Re: Triggering Specific Transaction Responses Using Test Account

Michelle — Tue, 28 Sep 2010 22:24:03 GMT

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

Re: Triggering Specific Transaction Responses Using Test Account

tracent — Tue, 28 Sep 2010 22:45:18 GMT

Thanks! I must have missed the 13 digit requirement. It's working great now.

Re: Triggering Specific Transaction Responses Using Test Account

Michelle — Tue, 28 Sep 2010 22:53:44 GMT

Sweet. :smileyhappy:

Re: Triggering Specific Transaction Responses Using Test Account

joatmon — Wed, 15 Dec 2010 23:19:30 GMT

What is the current status of this? I cannot get any of the zip codes to produce a transaction response. They all generate an error message on the payment form.

Re: Triggering Specific Transaction Responses Using Test Account

joatmon — Thu, 16 Dec 2010 19:13:01 GMT

No need to reply to previous post. I have resolved the problem.

Re: Triggering Specific Transaction Responses Using Test Account

rmiron — Fri, 04 Feb 2011 15:01:16 GMT

Hi,

Could you please provide a description for field [split_tender_status] returned in AIM response?
It will be of a great help to know its possible values and its position in the AIM response.

This field is mentioned in AIM official documentation (http://developer.authorize.net/guides/AIM/)

in section [Home > Section Two - Submitting Transactions > Partial Authorization Transactions],
but doens't shows up in section [Home > Section Four - Transaction Response > Fields in the Payment Gateway Response] I can't tell if it is present or not in my response.

Basically we need to establish when an order (containing multiple partial payments) is complete.

Here is an example:
HTTP POST Url:
https://test.authorize.net/gateway/transact.dll?&x_login=8vLAwF38qF&x_tran_key=6sYgn3u3Nx98r5Tb&x_allow_partial_Auth=TRUE&x_version=3.1&x_type=AUTH_CAPTURE&x_method=CC&x_amount=1&x_card_num=4222222222222&x_exp_date=0213&x_card_code=378&x_split_tender_id= 02401&x_zip=46225&x_invoice_num=180870253&x_cust_id=43044&x_test_request=False&x_delim_data=TRUE&x_delim_char=,
HTTP POST Response
4,1,295,The amount of this request was only partially approved on the given prepaid card. An additional payment is required to fulfill the balance of this transaction.,BKY0YN,Y,2157344524,180870253,,1.23,CC,auth_capture,43044,,,,,,,46225,,,,,,,,,,,,,,,,,,B817C974DBB30368ABF5619EC3ADE699,P,2,,,,,,,,,,,XXXX2222,Visa,102401,1.00,,,,,,,,,,,,,,

Rares

Re: Triggering Specific Transaction Responses Using Test Account

Trevor — Wed, 09 Feb 2011 23:28:02 GMT

First off, that field actually should be removed from the documentation. It is something that actually isn't returned with AIM or SIM using partial authorization.

As for the specific example that you provided, it is actually an invalid transaction. The way that these triggers are designed, they will always attempt to provide the specified result, even if it is logically impossible. You submitted an amount of $1 for your transaction, the 46225 zip code trigger that you used is designed return a partial authorization for $1.23. The result is an impossible situation where you were partially authorized for more that you initially requested. You'll want to run the transaction for more than $1.23 to see a reasonable transaction response.

You can determine whether or not the split tender transactions have been captured based upon the basic transaction result. If you have run the transactions as AUTH_CAPTURE, then they will all be captured whenever a transaction is sucessfully processed (authorized in full) under that split tender ID. If you have run the transactions as AUTH_ONLY, then they will never capture until you explicitly send the capture request.

Re: Triggering Specific Transaction Responses Using Test Account

jaredanderton — Fri, 18 Feb 2011 22:38:05 GMT

Hello,

I am having a hard time triggering the specific responses. I am a vendor doing this work for a client, and so I don't have access to the merchant interface, but I am sending x_allow_partial_auth=TRUE with my parameters. It is my understanding that parameter will enable the partial authorization for the current transaction. Is that accurate?

I am also sending these parameters:

x_card_num=4222222222222

x_amount=295.00

x_zip=46225

I am getting part of the response I am expecting, including the response code, response reason code, However the amount being returned is the amount I sent over, (not the expected 1.23). I am also not getting the new response fields, including the split tender id. An example response is:

4|1|295|(TESTMODE) The amount of this request was only partially approved on the given prepaid card. An additional payment is required to fulfill the balance of this transaction.|000000|P|0|||295.00|CC|auth_only|12|Jared|Anderton||606 West 9320 South|Sandy|UT|46225||||||||||||||||||E6ED01487EB921A0DC69F326E36A3B41|||||||||||||XXXX2222||||||||||||||||||FALSE

Is there something that I am missing?

Re: Triggering Specific Transaction Responses Using Test Account

Trevor — Tue, 22 Feb 2011 23:32:05 GMT

You are actually combining two separate ways of generating errors. The 4222222222222 card number can be used to generate any specific response code in test mode, the zip code triggers are designed to cause specific responses on the the test server but in live mode. In order for the zip code to cause a partial authorization response, you'll want to run the transaction in live mode with any other card number.

Re: Triggering Specific Transaction Responses Using Test Account

treii28 — Tue, 19 Apr 2011 21:21:14 GMT

re:

@Trevor wrote:
You are actually combining two separate ways of generating errors. The 4222222222222 card number can be used to generate any specific response code in test mode, the zip code triggers are designed to cause specific responses on the the test server but in live mode. In order for the zip code to cause a partial authorization response, you'll want to run the transaction in live mode with any other card number.

UM, ok - then someone clarify to me please. Can you 'test' in 'live' mode without generating a 'real' transaction? And if you have to do it in 'live' mode than what is the purpose of test mode?

Re: Triggering Specific Transaction Responses Using Test Account

Trevor — Thu, 21 Apr 2011 23:37:44 GMT

Test mode is primarily for use on a real Authorize.Net account. The developer test accounts that we provide should be run in live mode to simulate a much wider range of behaviors. Transactions processed through a developer test account will never result in an actual charge to a credit card.