topic Re: In Sandbox - pre-auth using zip 46282 to force decline in Integration and Testing

In Sandbox - pre-auth using zip 46282 to force decline

SAHeath — Mon, 04 Apr 2016 17:56:23 GMT

While testing in the sandbox, I put through a sales transaction using a pre-auth code, but also using the 46282 zip to force a decline transaction. The transaction came back successful. Will an pre-auth code always override the use of the 46282 zip to force a declined transaction?

Re: In Sandbox - pre-auth using zip 46282 to force decline

RichardH — Mon, 04 Apr 2016 19:42:59 GMT

Hello @SAHeath

Which card brand did you use, and was a transaction id returned?

Richard

Re: In Sandbox - pre-auth using zip 46282 to force decline

SAHeath — Mon, 04 Apr 2016 20:09:51 GMT

Richard,

I used AMEX brand, and yes, a transaction ID was returned.

Thanks...

Scott

Re: In Sandbox - pre-auth using zip 46282 to force decline

RichardH — Mon, 04 Apr 2016 20:17:35 GMT

@SAHeath, do you get the same result using a Visa card?

Re: In Sandbox - pre-auth using zip 46282 to force decline

SAHeath — Mon, 04 Apr 2016 20:28:22 GMT

Richard,

I attempted another transaction using a VISA, and recieved the same result. An approval with a Trans ID returned.

Scott

Re: In Sandbox - pre-auth using zip 46282 to force decline

RichardH — Mon, 04 Apr 2016 21:44:19 GMT

@SAHeath, I've reported your issue to the product team for analysis.

I'd recommend subscribing to this topic so that you'll be alerted via email if there are updates. To subscribe, click Topic Options at the top of this thread and then select Subscribe. You'll then receive an email once anyone replies to your post.

Thanks,

Richard

Re: In Sandbox - pre-auth using zip 46282 to force decline

RichardH — Tue, 05 Apr 2016 15:56:23 GMT

@SAHeath Could you provide some sample transaction IDs for these transactions so we can look further?

Richard

Re: In Sandbox - pre-auth using zip 46282 to force decline

aabeach — Tue, 05 Apr 2016 17:55:50 GMT

@RichardH,

I work with @SAHeath. Here are the trans id's to the 2 cases mentioned above.

2254346086- Visa

2254329831 - AMEX

Thanks!

Re: In Sandbox - pre-auth using zip 46282 to force decline

SAHeath — Tue, 12 Apr 2016 12:46:15 GMT

@RichardH,

No further investigation needed. After looking into the history of our transactions, the case we were trying to test was determined to have never happened in the past. We have have dropped the test for that scenario from our testing script.

Thanks,

SAHeath

Re: In Sandbox - pre-auth using zip 46282 to force decline

nshah1221 — Fri, 06 Jan 2017 18:41:07 GMT

@SAHeath I am having the same issue too. we can't simulate declined transaction on sandbox environment.

Transaction Ids : for which i received Success on sandbox :

trn_321dc971-66ce-4e91-a70d-07aed418c8e3
trn_3528aaf4-41ff-4e89-b643-2da0eec8bda8

trn_b782586b-598c-473f-a804-439e90f23485

Credit Card used for above transactions :

master card, customer token for it : P6jTykm5TiO5jgUTDtGSPA

Zip used : 46282

Re: In Sandbox - pre-auth using zip 46282 to force decline

RichardH — Fri, 06 Jan 2017 19:06:16 GMT

@nshah1221

Can you provide a sample gateway response where the transaction was accepted but should have been declined? The transaction ids you reference are not from our system.

Re: In Sandbox - pre-auth using zip 46282 to force decline

dblaze — Thu, 06 Aug 2020 18:47:28 GMT

Hello, Richard,

We have had similar issues as we cannot consistently generate AVS failures or successes based on the documentation. It seems that there are other developers facing the similar issues with the sandbox:

I have found that using Discover card generates the most consistent result, but it is not perfect as demonstrated by attempting to validate the documentation using the provided zip codes.

Transactions That Didn’t Receive The Expected Result:
Transaction: 40053024998
Zip Code: 46217
AVS Response: Y
AVS Response Expected: Z

Transaction: 40053025104
Zip Code: 46201
AVS Response: N
AVS Response Expected: A

Transaction: 40053025089
Zip Code: 46201
AVS Response: N
AVS Response Expected: A

Transaction: 40053065880
Zip Code: 46211
AVS Response: Y
AVS Response Expected: W

Transaction: 40053066067
Zip Code: 46208
AVS Response: X
AVS Response Expected: S

Transactions That Did Receive The Expected Result:
Transaction: 40053024773
Zip Code: 46214
AVS Response: X
AVS Response Expected: X

Transaction: 40053024698
Zip Code: 46201
AVS Response: A
AVS Response Expected: A

Transaction: 40053024717
Zip Code: 46208
AVS Response: S
AVS Response Expected: S

Transaction: 40053024698
Zip Code: 46201
AVS Response: A
AVS Response Expected: A

Transaction: 40053024732
Zip Code: 46205
AVS Response: N
AVS Response Expected: N

I am not sure how to proceed at this point. I have been told by Authorize.net support that:

After reading over some other posts in our forum, it looks like that is the case. A transaction would need to be submitted with an amount greater than $0.00 to have the correct AVS response show in the Sandbox Account. Sorry for any frustration this may have caused.
I went through each Transaction ID you provided and everything looks good in regards to the testing as you mentioned. I think it would be safe to say you are good to continue your testing with the Discover Cards and it will give you the correct response for testing purposes.

The documentation does not mention to specifically use Discover or a value of over $0.00. I was under the impression: “Our sandbox functions like the live payment gateway. However, sandbox transactions do not process live payments. The response from the sandbox varies depending on the card type, ZIP code, and amount.”

Zip Codes that work more or less consistently with Discover:

46214 → X
46205 → N

Can this problem be escalated? It seems like this has been a problem for sometime. Thank you for your help!