ONPAY
Make Web3 feel like Web2
The problem ONPAY solves
The Problem OnPay Solves
Many people, especially in emerging markets, struggle to use Web3 due to gas fees, complex wallet addresses, and poor user experience. Sending money across borders is still costly and complicated, and most Web3 apps require users to hold native tokens and understand technical concepts like gas and addresses.
How OnPay Makes It Easier
OnPay removes these barriers by offering gasless transactions, so users don’t need LSK to send funds. It supports human-readable names like “alice.lisk.eth” instead of long wallet addresses, and provides a simple, Web2-style interface. OnPay enables fast, borderless payments with a user experience anyone can understand—no crypto knowledge required.
Challenges we ran into
We faced several challenges while integrating the core technologies behind OnPay.
First, since Lisk doesn’t yet support native account abstraction, we built our own meta-transaction system using a relayer (EOA) to simulate account abstraction. This allowed us to cover gas fees on behalf of users, enabling a truly gasless experience where users only need to hold IDRX.
Another major challenge was implementing ENS support. Because Lisk doesn’t natively support ENS, we had to dive deep into the documentation and explore how platforms like Coinbase and Uniswap built their naming systems. We studied their approaches and adapted them to our environment. Reaching out to ENS developers for guidance was also incredibly helpful during this process.
Lastly, we encountered confusion when integrating Xellar—specifically distinguishing between the Xellar SDK and Xellar Kit. With support from the Xellar team through the Lisk Hackathon Discord, we were able to clarify the differences and proceed with a working integration.
Technologies used