How do I get started with integrating the OpenPAYGO Token?

As the first step, we recommend you to visit the GitHub Repository and familiarize yourself with the General Documentation (implementation details) and the Example Implementation (technical examples for C and C+).

 

Once you are ready to integrate the OpenPAYGO Token into your own device, the software code is openly available for downloading on GitHub and the OpenPAYGO Token integration demoshows step-by-step how to integrate the code into solar-based devices. On the EnAccess Open Source Community Forum you can ask questions that come up during the integration process and have them answered by Community members. 

 

If you are having difficulties integrating and cannot find the information you need within the documentation or the community, you can reach out to us for assistance.

How much of the adoption process is free?

It’s absolutely free and will stay that way forever. The EnAccess Foundation covered the development costs as part of our mission and the technology is provided for free to maximise the number of companies that adopt it into their products/projects.

I do not have an in-house Software Developer – Is it still possible for my company to integrate the OpenPAYGO Token?

In order to help your company incorporate the OpenPAYGO Token into your devices, we are able to offer you support. To understand if and how we can provide this support free of charge, we need to understand more about your company and your specific needs. Please write up the scope of the help you require & the specifics of your (Solar) Devices to info@enaccess.org.

What devices can the OpenPAYGO Token be integrated into?

Into any device that is electrically run (TV, fridge, Solar Home Systems, tablet, mobile phone, etc.) and meets specific minimum hardware requirements:

 

1. Microcontroller with enough memory storage to switch the power lines on/off;

 

2. Input method to enter the token (keypad/Bluetooth/GSM/WiFi).

How is the token generation controlled?

The tokens are generated on the servers of the software provider of your choice (or even your own servers or the one of your manufacturer depending on your preferences).

Is it possible to expand on the code and add new features?

Yes. OpenPAYGO Token was designed to be expandable through the examples of extended tokens. For example, using the token to transmit something other than activation time.

 

You are encouraged to expand and open a merge request to share the expansion with the rest of the Open Source Community.

Can I use this token with my own or any other PAYGO platform?

Yes, any PAYGO platform (including your own) can integrate the OpenPAYGO Token as it is platform-agnostic.

Can tokens be generated offline in an app?

Thanks to the Open Source nature it is possible to directly integrate the OpenPAYGO Token into an app without an internet connection to access an API.

How secure is the OpenPAYGO Token?

The security relies on cryptographic principles and is linked to secrecy of the keys you generate and add to your products.

 

The token is encrypted in the device using a 32-digit key in accessible format, making the token secure to be used. The encryption mechanism has been audited by an external security consultant with extensive experience in cryptography and communication protocol.

 

For the security to operate as intended, the developer should always keep the key secure and not open-source that element. Additionally, the device or the server should be set up in a way that the key letter can be updated. Therefore, in the unlikely event of someone getting access to the keys, the developer should be able to invalidate the old token and use the immune token.