Reply
Highlighted
Contributor
Posts: 16
Registered: ‎05-23-2018

Accept.js payment nonce created with zip not running AVS on PHP-SDK transactions

[ Edited ]

Hello,

Currently we are experiencing an issue with AVS. First let me outline our basic process.

 

1. Create payment nonce with Accept.js, supplying all required fields as well as zip.

2. Create transaction using PHP-SDK and payment nonce.

 

For some reason AVS is not running, and we've had Authorize.net support tell us that the zip code is never being received at all. It could be they are referring to the PHP-SDK transaction's explicitly added data, but as detailed in this very similar issue (use case 2 applies to us precisely), using the zip to create the nonce should be enough to trigger AVS.

We would love to get to the bottom of this, any help is appreciated.

 

Thanks

David Cooley
Fivable, LLC

Our current settings

https://s3.amazonaws.com/www.fivable.com/image+(11).png
https://s3.amazonaws.com/www.fivable.com/image+(6).png

 

Our code which includes the zip (we have verified the outgoing request includes this data, just in case)

https://s3.amazonaws.com/www.fivable.com/image+(9).png


Accept.js documentation confirming our method of attaching zip
https://s3.amazonaws.com/www.fivable.com/image+(10).png


What we see when creating a transaction with this workflow

https://s3.amazonaws.com/www.fivable.com/image+(7).png

What we see when creating a transaction with a separate IVR workflow that doesn't use Accept.js
https://s3.amazonaws.com/www.fivable.com/image+(8).png

Highlighted
Member
Posts: 1
Registered: ‎02-12-2020

Re: Accept.js payment nonce created with zip not running AVS on PHP-SDK transactions


@fivable wrote:

Hello,

Currently we are experiencing an issue with AVS. First let me outline our basic process.

 

1. Create payment nonce with Accept.js, supplying all required fields as well as zip.

2. Create transaction using PHP-SDK and payment nonce.

 

For some reason AVS is not running, and we've Popeyes Survey
 had Authorize.net support tell us that the zip code is never being received at all. It could be they are referring to the PHP-SDK transaction's explicitly added data, but as detailed in this very similar issue (use case 2 applies to us precisely), using the zip to create the nonce should be enough to trigger AVS.

We would love to get to the bottom of this, any help is appreciated.

 

Thanks

David Cooley
Fivable, LLC

Our current settings

https://s3.amazonaws.com/www.fivable.com/image+(11).png
https://s3.amazonaws.com/www.fivable.com/image+(6).png

 

Our code which includes the zip (we have verified the outgoing request includes this data, just in case)

https://s3.amazonaws.com/www.fivable.com/image+(9).png


Accept.js documentation confirming our method of attaching zip
https://s3.amazonaws.com/www.fivable.com/image+(10).png


What we see when creating a transaction with this workflow

https://s3.amazonaws.com/www.fivable.com/image+(7).png

What we see when creating a transaction with a separate IVR workflow that doesn't use Accept.js
https://s3.amazonaws.com/www.fivable.com/image+(8).png


wait what is happening with you sir