Release Notes

Release Notes

4.4.0

Feature Description
New device Added support for Lane/3000 & Lane/5000 for US and Canada
Surcharge in-App The Credit Surcharge feature (see CSDK 4.3.0 release notes) is now available for RP457 & Moby/5500 card readers.
To support surcharge when connected to those devices, Commerce SDK will send surcharge confirmation to Integrator's POS system through API callbacks instead of sending surcharge confirmation to card reader.
Optional Signature Capture Added option for merchants to configure whether to prompt for a signature or not.

4.3.0

Feature Description
New device Added support for Moby/5500
Credit Card Cost Control (Credit Surcharge) The Credit Surcharge feature automatically detects credit card transactions by searching for a BIN (bank identification number). If the BIN is valid, a credit surcharge is applied as an additional charge equal to the credit card provider's transaction processing fee. The cardholder receives an alert when a surcharge is added, and has the option to accept the surcharge or change the payment type to debit to avoid paying a fee.
Customer Support enables this feature during the new terminal set up process. If an existing customer would like this feature, they can contact Customer Support at 1-800-377-3962 to request a new terminal or have their current terminal altered.

4.2.0

Feature Description
New device for Canada Added Link/2500 support for Canada
UPP Update A new version of UPP (UPP 5.08.08) will be pushed to all Link/2500 devices not running UPP 5.08.08. Merchants will need to be prepared for a 15-30 minute update of their device as a result. Please keep application integrated with CSDK running in the foreground and keep mobile device from going to sleep during the update, otherwise 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, please reboot your device and restart the application. Once the update is complete, the device will reboot itself.
Link/2500 Standby Timeout is off Standby timeout for Link/2500 is disabled. Please check the battery run-time table for Link/2500 and make sure to charge your device when required.
Link/2500 Menu changes Admin Menu has changed for Link/2500. Please check the device updated connection guide.
Find devices Before attempting to connect to devices such as card readers and printers, you have an option to set the specific connection criteria to use during the device search, which will result in a faster connection to the device.
Contactless CVM limit update Cardholder Verification Method (CVM) limits are updated for contactless payments to reflect changes made by payment card association brands:
card brandcountryold CVM limitnew CVM limit
AMEXUS$50$200
AMEXCAN$100$250
MCCAN$100$250
VISACAN$100$250

Battery run-time for WiFi Connection:

Transaction Type Total Transactions Total Time
EMV transaction after every 5 minutes 72 EMV Contact transactions 9 hours 11 minutes
Contactless transaction after every 5 minutes 124 EMV C'less transactions** 9 hours 44 minutes
Contactless transaction after every 10 minutes 56 EMV C'less transaction 8 hours and 2 minutes

Battery run-time for Bluetooth Connection:

Transaction Type Total Transactions Total Time
EMV transaction after every 5 minutes 86 EMV contact transactions 7 hours 19 minutes
Contactless transaction after every 5 minutes 104 EMV C'less transactions 8 hours 52 minutes
Contactless transaction after every 10 minutes 74 EMV C'less transactions 8 hours 15 minutes

4.1.0

Feature Description
64 Bit Support (Android) The Commerce SDK build system, sample app, and 3rd party libraries now support 64-bit Android devices.
Android Gradle Plugin Upgrade The development environment to build Android applications with Commerce SDK now requires Android Gradle Plugin 3.0.1.

4.0.0

Feature Description
Windows Bluetooth Support Commerce SDK now supports Bluetooth connections between a Windows host and an iCMP card reader.
US Common Debit Commerce SDK now supports US Common Debit Application IDs (AIDs). As the name suggests, this feature is enabled only for US terminals.

If a card with a mix for US Common Debit and non-US Common Debit AIDs is used, you have a choice to specify the preference for the routing network - either in the Converge terminal or through the POS application, using Commerce SDK APIs. The choices are: US Common Debit preferred, credit preferred or no preference - in which case the user would have to choose their preferred option in the event there are multiple choices.

PIN Bypass Commerce SDK now allows the user to bypass PIN entry for the US terminals.

PIN entry bypass is a systematic way for a customer to bypass entering the PIN on a terminal. In such a scenario, neither PIN data nor CVM results of online PIN may be sent in the authorization request message and the system will move on to the next available CVM (signature, no CVM etc.)

Supported brands: Visa, Mastercard, American Express, Discover, Visa US Common Debit, Mastercard US Common Debit, Discover US Common Debit, Union Pay and JCB

EMV Refund Commerce SDK now supports chip based refunds for all the card brands.
New Devices Added support for Link/2500, iPP320 V4 and iSC250 V4.
24-Hour Reboot Commerce SDK now supports setting the daily reboot time of PCI V4 terminals.

As a PCI requirement, all PCI V4 terminals must reboot after 24 hours of continous running time.

RBA Update A new version of RBA (RBA 23) will be pushed to all devices not running RBA 23. Merchants will need to be prepared for an 8-10 minute update of their device as a result. Once the update is complete, the device will reboot itself.
Enforced SSL Commerce SDK now enforces SSL on all operations via IP except for the initial card reader connection and update operations. Commerce SDK will also enforce SSL on all terminals.
Visa Online PIN Commerce SDK now includes online PIN as a cardholder verification method (CVM) for Visa transactions.
CUP Online PIN Commerce SDK now includes online PIN as a cardholder verification method (CVM) for China Union Pay transactions.
3rd Party Software License Updated list of 3rd party software licenses.

3.3.0

Feature Description
Interac Chip-Based (EMV) Refunds Available for Canada only.

Supported devices: iCMP and iPP320

Supported platforms: Windows, iOS, and Android

Supported card entry types: Contact and Contactless

Supported refund types: Linked refund and Standalone refund

RP457c Device Support Available for US only.

Supported platforms: iOS and Android

Includes EMV Contact, MSR Contactless, and MSR card entry type capabilities

Supported connection types: Bluetooth and 3.5mm audio jack connections

USB On-the-Go (OTG) for M70 Available for US only.

Supported platform: Android

The RP457c device can be used within the M70 enclosure.

Device Stability Improvements Stability improvements around device connectivity and device freezing problems.

3.1.0

Feature Description
Communication Over IP Support for communication over IP is now available on Android.
EMV Contactless EMV Contactless is now supported on all certified devices. This is supported as part of the update. No action is needed.
Expanded Geography Support Commerce SDK now supports the Canadian market with the iPP320 and iCMP. Support is now available for Android and Windows. This includes support for Interac, French language on supported pinpads and EMV Contactless.

error_outline
note

US and Canadian devices are unique. A US device cannot be used to test Canada and vise versa.

Merchant Transaction Reference Number Integrators now have the ability to pass in a unique identifier for each initiated transaction.
Merchant Transaction Reference Number Search Integrators can now perform a search using the Merchant Transaction Reference Number. The only supported search is exact match on reference number.
Pinpad Upgrade Detection Integrators can now determine if a supported pinpad will need to be updated prior to initiating a transaction.
RBA Update A new version of RBA (RBA 20) will be pushed to all devices not running RBA 20. Merchants will need to be prepared for an 8-10 minute update of their device as a result. Once the update has completed the device will reboot itself.

2.5.0

Feature Description
IP Connectivity Commerce SDK now supports the ability to communicate to an iPP320 or iSC250 pinpad over IP.

This requires an Ingenico Magic Box in order to assist with this communication.

Support for IP connectivity is only available for iOS, Windows Java, C# and Commerce Web Service.

Address Verification Service (AVS) Support Integrators can now pass in AVS fields as part of a manual entry sale.
Encrypted Card Read Commerce SDK now allows an integrator to perform an encrypted card read so an integrator can support gift card or loyalty card through Converge.
Connection and Battery Status Integrators now have the ability to obtain information on if the pinpad is connected to the point of sale, as well as, information on the battery status if utilizing a battery powered pinpad.
Reset Card Reader Integrators now have the ability to reset the card reader prior to authorization through Commerce SDK.
EMV Support for Auth Only Commerce SDK now supports EMV for Auth Only transactions.
EMV Partial Approval Support Commerce SDK now supports EMV for partial approval transactions.
Token Request (Auth Only) An integrator can now request a token as part of an Auth Only transaction.
New Integrator Fields To better understand who is integrating Commerce SDK, integrators will now be required to provide information about their point-of-sale application.

The following information must be supplied by the integrator when initializing Commerce SDK:

  • merchantId
  • PIN
  • userId
  • serverType
  • vendorId - This is a unique identifier representing a specific integrator. Contact your Elavon Solutions Engineer to obtain one.
  • vendorAppName - This is the name of your application that is using Commerce SDK. For example, "MyCoolPaymentApp".
  • vendorAppVersion - This is the version of your application. For example, "1.0.0.0".