The free and secure Open-Source Token System to make any product PAYGO compatible
How does OpenPAYGO™ Token work?
OpenPAYGO™ Token technology consists of a token generation protocol, each token stipulating a certain number of activation days or any other relevant metric equating to product usage for a particular unit. This open-source technology is interoperable, so the token generation aspect of the system can then be integrated with any management software platform (such as PaygOps or any other), and it can be integrated into any device.
Why OpenPAYGO™ Token?
Paygo business models allow manufacturers to supply partnering distributors with a much higher volume of product and create potential for a consistent stream of revenue. This is particularly true in developing regions where consumers may not have the financial means to purchase such products outright and distributors have access to a more vast market.
Adopting the OpenPAYGO™ Token as part of a transition into the Paygo market contributes to decreased time and less cost allocated by manufacturers otherwise necessary for integrating different devices with each CRM platform. Furthermore, implementing OpenPAYGO™ Token allows manufacturers to maintain sovereignty and remain independent from any one software solution.
We also provide a certification service specifically for devices which have had OpenPAYGO™ Token implemented independently.
How to implement OpenPAYGO™ Token:
In order to ensure the Paygo compatibility and implement OpenPAYGO™ Token, it is essential for manufacturers to integrate a control switch and an intuitively designed user interface (UI) which includes an input method as well as a display. This will allow manufacturers to access a device activation status and the end user to accurately interact with the device itself.
In addition to the inclusion of UI elements to display Paygo status, manufacturers will need to assure their devices meet the following minimum system requirements for OpenPAYGO™ Token to be implemented:
An MCU with at least 8KB of available flash (after the rest of the firmware functions are implemented).
A hardware real time clock (RTC) that is accurate enough to drift by a non-noticeable time over 12 months, used to keep track of the elapsed time. For this reason, as the clock source we recommend a low-speed external crystal.
An EEPROM, or other memory, on which permanent data can be stored across power loss and reset events
A UART serial communication port that allows the factory setup of the device (uploading the secret key, the starting code and the serial number)
A backup battery in case the system becomes disconnected from the battery.
Looking for more information? Contact us.
Our technology is designed to be intuitive to integrate, but our engineers provide assistance when needed.
Thank you for contacting us, we'll get back to you as soon as possible!
Frequently Asked Questions
Do I have to pay you anything to add this into my products?No! It’s absolutely free and will stay that way forever. The EnAccess Foundation covered the development costs as part of their mission and provided the technology for free to maximise the number of companies that use it in their products/projects.
Can I use this with any PAYGO platform?Yes, anybody can integrate this for free to allow you to use any OpenPAYGO device in it.
Can it be secure even if everybody knows how it works?Yes absolutely, the security here relies on cryptographic principles and is linked to the secrecy of the keys you generate and put in your products. For more details you can find an independent security audit of this system with the package.
Can I use the token to transmit something other than activation time (e.g. settings)?Yes, this was designed to be expandable and allow you to do just this quite easily following the examples for the extended tokens.
What if I need help integrating?If you are having difficulties integrating and cannot find the information you need within the documentation or the community, SolarisLab team offers integration help on a consulting basis.