top of page

Terminal Management System

Terminal Management System



While payment device configuration updates can be done manually, requiring someone to physically update each and every payment device on site is inconvenient, impractical and time consuming. Our ChipDNA product checks for updates with our Terminal Management System (TMS) and automatically installs them, which is particularly helpful for large quantities of disparate payment devices.



Why do you need a TMS?



When integrating payments, it's essential to address the ability your customers have to manage the data upgrade elements required by the EMV standard and the firmware on the payment devices. This is crucial because if the payment devices aren’t updated on a regular basis, you run the risk of your solution not being EMV compliant, leaving your customers vulnerable to security breaches and processing issues. If these updates are not made regularly, this can lead to compliance issues and ultimately card brand fines, which will be passed down to merchants by the acquiring banks and processors.

A payment device is essentially an embedded platform that runs its own complex software stack. As with any software stack, it requires updates to keep the stack (and your solution) compliant with current versions of the EMV standard. Security vulnerability patches or general bug fixes also need to find their way to the payment device. Therefore, all EMV enabled solutions will require frequent data updates to cover off new data elements such as CA Public Keys and Data Object Lists which can change periodically. Having the correct CA Public Key is critical to the correct cryptographic operation of EMV.


How the TMS works



Our TMS is seamlessly integrated with our ChipDNA product. Upon initial configuration, ChipDNA reaches out to the TMS platform to determine what payment related configuration is required. The TMS is controlled entirely by the Jollypayments Gateway Platform, including the management of all terminal updates. 



  • Efficient and timely deployment of configuration updates and where supported, payment device firmware

  • Remote management of large quantities of payment devices

  • Continued EMV compliance

bottom of page