TEST Mode transactions return as declined

[nmoerbeek]

Hi,

We are attempting to run full tests before deployment while setting our Merchant account to test mode. It appears that everything works, however we are still getting an error each time we process the EMV chip that the transaction was declined.

When examining the EMV_SDK_LOGS it appears at least that the transaction is successful:
5/27/2020 4:57:17 AM:WalkerCardListenerBase:doAuthOrAuthCaptureIfQuickChip

5/27/2020 4:57:17 AM:Posting request:1authOnlyTransaction

5/27/2020 4:57:17 AM:Terminal Number:00222273

5/27/2020 4:57:17 AM:Response received trans id0

5/27/2020 4:57:17 AM:Response received messagesThis transaction has been approved.1

5/27/2020 4:57:17 AM:Request failedObject reference not set to an instance of an object.authOnlyTransaction

5/27/2020 4:57:17 AM:Connection error occurred

5/27/2020 4:57:19 AM:WalkerCardListenerBase:getActiveListener

5/27/2020 4:57:19 AM:WalkerCardListenerBase:getActiveListener

5/27/2020 4:57:19 AM:WalkerCardListenerBase:doVoidTheTransaction

5/27/2020 4:57:19 AM:Posting request:0voidTransaction

5/27/2020 4:57:19 AM:Response received trans id0

5/27/2020 4:57:19 AM:Response receivedA valid referenced transaction ID is required.33

What is perplexing to us is that when we enable the magstrip reader and force a credit swipe, the event handlers return a transaction response indicating that the transaction is successful with an ID of 0. However, we also believe that the magstrip must be using different logic, as it does not make any records in the EMV_SDK_Logs

We would like to move forward with deployment, but I want to confirm if this is a known issue, that all EMV transactions in test mode will return that the transaction is declined. This issue does not occur in the VPOS portal when in test mode, only in the WIN SDK, when we have tested our merchant account

[nmoerbeek]

Edited comment above to add more information.

[leeleito]

Can I ask what reader you are using?