A Sneak Peek at the PullPayment Solution in the Making
When the community asks, we deliver. A member of our Telegram group recently expressed his interest in how the PullPayment solution comes to be, and he is not the only one. Excitement and curiosity are the sentiments that dominate the PumaPay community. Because in such exciting times during project development nothing compares to a word from the developer, we pried Aristos Christofides away from coding, again, who gave us a sneak peek at the PullPayment in the making.
Our community members are curious to learn more about how the PullPayment Protocol is coming about. What can you tell us?
AC: We are now testing the recurring payment solution on the blockchain. We’ve finalized the faucet, which allows users to access test tokens to try the solution and get a feel of what it would be like to pay for a monthly subscription with PumaPay in real life. However, we will only publish the link on GitHub when we’ve completed the development and testing of the recurring payment solution. We’re now also developing the 2nd version of the PumaPay native wallet app, which will support fixed-amount recurring payments based on time and casual, single payments. Single payments can either take the form of Pull payments or regular Push transactions, typical to the Ethereum network.
AC: Version 2.0 of the PumaPay Cryptocurrency Wallet is not a simple upgrade of the previous release. However, users of Version 1.0 do not need to reinstall the app to access their wallet. This release will allow them to either restore their account with the pre-existing balance of PMA, ETH or other ERC20 tokens they may have had available, or simply log in to their wallet in the same way they used to. Both ways will give them access to their funds, if any. In case anyone chooses to ‘restore’ their account and if they also happen to hold any other ERC20 wallet, which has been previously linked to the PumaPay wallet, they will be able to access the balance available in that wallet in the new PumaPay app.
That’s great! What stage of development are you in with the wallet? What are the programming languages that you use to develop it?
AC: We’ve established the flow and we’re now moving forward with the blockchain integration. We believe in multi-language development architecture, meaning we believe in using the correct language for the task at hand. For our POC we chose to use Typescript, NodeJS and Angular 5, as we felt those best complemented our open-source community. Tomorrow we may develop versions in C# or Java.
Our POC is available on GitHub and perfectly illustrates the principle of purchasing credits and photos with PumaPay tokens. These purchases are triggered as single push transactions. For a technical deep dive and code samples, I recommend readers to visit our previous article. The team and I are now developing the different types of PullContracts to enable recurring transactions. The wallet will have a different look and feel, new features will be added to ensure better user experience.
We often get asked on Telegram and other channels how does the PumaPay development team manage to handle multiple projects simultaneously? What team management methodologies do you use, Agile or other?
AC: We believe in parallel development life cycles. This is handled by utilizing the scrum and agile project management methodologies, with a strong scrum master as the facilitator, who is responsible for process management, and who also acts as a coach for the whole team.
Thank you, Aristos and team, for the update.