Skip to content
Start a projecttafseel@walqalum.com

Work · Case study

Send an invoice. Let them pay it from any wallet they own.

Client
Nefentus, global
Year
Live
Scope
Multi-tenant architecture, Web3 wallets, invoicing
Stack
React · Ant Design · Spring Boot · Web3.js · Solidity · MySQL

01 / Challenge

Crypto commerce breaks at the point where a business has to invoice. Payments could not move cleanly across wallet ecosystems, there was no professional platform for crypto invoicing or product payment links, and existing tools supported a fixed short list of wallets — which meant a merchant's choice of platform quietly dictated their customer's choice of wallet.

02 / Approach

Roles were made structural. Admin, vendor and broker are separate tenants with segregated data rather than three permission levels over one dataset, which is what allowed the client to market specific tools to vendors and to brokers as distinct products rather than as tiers of one.

Every user can generate and manage a native wallet inside the platform, so onboarding does not require someone to already hold crypto elsewhere before they can be paid.

Wallet connectivity was the genuinely hard part, because each protocol presents itself differently. Thirdweb and Web3 hooks were used to build one unified interface over them, so the platform is not maintaining an integration per wallet and a customer pays from whatever they already use.

03 / Outcome

3

isolated tenant roles

1

unified interface for any wallet

The platform is live and handling real crypto commerce: professional invoicing, product payment links and a sales analytics dashboard. The multi-tenant structure let the client go to market immediately with separate vendor and broker propositions, and unlimited wallet support removed the checkout friction that came from telling a customer which wallet to use.

Next project

POS Promotions, Loyalty and Age Verification
Start a project