New Member
Posts: 1
Registered: ‎04-19-2017

TRANSACTION_DECLINED even tho network transaction reports success



we are using a chip reader from your device loaner program and android in-person SDK.

During development we have noticed a strange SDK behavior, which we would prefer to clear up before going to production.


As mentioned here we only use Visa cards for sandbox requests.


What we have observed is that with the vast majority of Visa cards the first web request the in-person sdk attempts is reported as TRANSACTION_DECLINED in our EMVTransactionListener. onEMVReadError callback, although when we inspect the app network traffic, we can see that the authOnlyTransaction was a success, we get the email receipt, and the transaction is visible in the sandbox website unsettled transactions


We have found some Visa cards that work with no problem, but have no idea what makes them special.


Transaction with transactionId: 60021414341 on sandbox API is an example of the transaction which was a success, but the in-person SDK reported it as a failure.


What may cause the difference in status reported from API and in-person sdk?


Appreciate your help!

Posts: 2,165
Topics: 50
Kudos: 140
Blog Posts: 64
Registered: ‎12-05-2011

Re: TRANSACTION_DECLINED even tho network transaction reports success

Hello @Mindaugas

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.




Webhooks are now available for Authorize.Net

Using SOAP, see our deprecation notice.
Check out Accept.js, our Javascript replacement for DPM.
Pro Tip: Never use test mode in the sandbox, instead use the Testing Guide.