AnsweredAssumed Answered

triPOS 5.17 isContactlessEmvEntryAllowed default issue

Question asked by chipschen on May 13, 2020
Latest reply on May 14, 2020 by jhess

I'm finding that triPOS 5.17 contactless EMV transactions only work when the lane is set to 
 <isContactlessEmvEntryAllowed>true </isContactlessEmvEntryAllowed> 

 

Despite the release note of sEmvSupported>true </isEmvSupported> will be true by default

 

I found that without the property in place when a transaction is sent to the device it immediately  responds with cancelled and the following entry in the triPOS error log.

 

2020-05-13 19:10:49,509 [9] triPOS ERROR - A PIN pad exception occurred. No processor request attempted.
TriPos.PinPads.Exceptions.PinPadException: IngenicoRBA 23. error s=R. PIN pad error

at TriPos.PinPads.Ingenico.IngenicoRbaPinPad.   .MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at TriPos.Pipeline.Common.PinPadHelper.<GetCardDataAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at ??. ?.??.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at ??. ?.??.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at ??.?.?.MoveNext()

Outcomes