Using the inperson-ios-sdk and the QuickChip API, calls to
readQuickChipCardDataWithPredeterminedAmount just today stopped completing successfully when a chip-enabled card is swiped (not dipped). Non-chip enabled cards complete fine.
Is anyone else experiencing this?
This was the behavior in the sandbox environment for as long as I've been building our app. But our production environment behaved better (those are some scary words).... until just a few hours ago. I previously chalked up the difference to the fact that our payment processor (Chase) has not yet certified the Chipper2X and SDK for EMV payments... meaning swiping cards is all that was previously available to us. Now, nothing works because Chase rejects the chip transaction as well.
This happened after I was performing the firmware update for the Chipper2X. But we have two chippers, and I quickly switched to the one I hadn't updated yet once I found the issue. Sadly, both chippers behave the same way now.