Known Issues

This section lists the pre-identified issues with Commerce SDK and the corresponding workarounds.

iSC250 application confirmation screen defectThe application confirmation screen for a debit payment on iSC250 device contains an unmarked, non-functional button between 2 valid options “yes”/“no”. It’s a cosmetic defect that doesn’t have any impact on the page functionality.
IP Connectivity / Device StatusWhen using IP connectivity and connected to the card reader; unplugging the card reader (the power to card reader itself, or ethernet cable) outside of a transaction, device status will not detect the disconnect.
IP ConnectivityFor iOS, when using IP connectivity the card reader can get into an unusable state when the ethernet cable is unplugged from the device when in the middle of processing a transaction. If this occurs, reboot the card reader to get the device into a usable state.
IP ConnectivityFor iOS/Android, toggling WiFi may cause Commerce SDK to lose its connection to the card reader if the card reader uses secure IP connectivity. If this situation occurs, reboot the card reader and restart the app that uses Commerce SDK.
Card Read FreezeAfter running approximately 25 - 35 consecutive transactions over WiFi, Link/2500 freezes during a card read.

As a workaround, press and hold the # and Yellow buttons at the same to reboot the card reader. After the card reader reboots, Commerce SDK will reconnect and run the next transaction without interruption or freezing.

Interrupted UPP upgradeKeep application integrated with CSDK running in the foreground and keep mobile device from going to sleep during the update. Otherwise, the card reader might get disconnected and UPP update will not be completed. If this happens, UPP update will restart when a card reader connection is restored. If you encounter any issues due to the interrupted update, reboot your device and restart the application.
PIN not entered on the deviceWhen running an EMV contactless transaction on RBA devices (iCMP, iSC250 or iPP320) for a service fee enabled account, If cancel button is pressed when PIN entry is prompted on device, transaction proceeds to Service Fee and Zip code prompting instead of cancelling. The transaction will be cancelled after card holder accepts service fee and enters zip code on device.
Data not supported in TXNQUERYOAR/PS2000 Data is not returned in transaction search results so OAR/PS2000 data will not be presented in xml authorization requests to Converge for the secondary transactions like void and preauth complete.
Transaction is stuck when starting it too quickly after device is rebooted due to pinless debit configuration change.After merchant makes changes to Pinless debit support switch in Converge and calls CSDK to get TMS settings from Converge. CSDK will deploy the updated configuration to card reader and reboot it.
If merchant starts a transaction too quickly after device displays “Welcome” screen, the transaction will be stuck.
CSDK crashes when starting a transaction with10-digit (invalid) zip code on Android device with Android OS of 5.1.CSDK crashes when starting a transaction with invalid zip code, for example 10 digits.