// the evidence
Claims, and where each one stands.
Every claim on this page carries its evidence tier. Nothing is smoothed over, and nothing a project told me is presented as something I checked.
HandlPay's documentation lists Canton Network as a supported network, with CC, CBTC, USDCx and HANDL among the assets available there, and states that on Canton only the user and the sender can see each transaction.
docs.handlpay.com supported networksThe Canton ecosystem directory lists HandlPay under Payments and Wallets, with the roles Apps (Featured) and Validator.
Canton ecosystem directory, HandlPayThe docs describe the mechanism: a sender picks a platform and types a username, HandlPay looks up the wallet address linked to that handle and routes the payment there. The social account is used for authentication only.
docs.handlpay.com how it worksThe terms of service name Verso Network AG, Switzerland, as the operator, and state that HandlPay does not provide payments or financial services but connects users to third-party service providers.
handlpay.com terms of serviceThe token docs state a fixed supply of 1,000,000,000 HANDL with a published allocation and release table, including a 12-month cliff followed by 12 months of vesting on the team and advisory allocation.
docs.handlpay.com token overviewThe token page lists trading venues on MEXC, Aerodrome on Base, QuickSwap on Polygon, and OneSwap, Cantex and Tradecraft on Canton, and lists total HANDL burned as coming soon.
handlpay.com/tokenThe product FAQ states Canton wallets created in the app are self-custodial with keys protected by passkeys, that HandlPay does not store the private key, and that Loop, Send, Bron, Console, Cantor8 and Zoro wallets can also be connected.
docs.handlpay.com product FAQThe loyalty program pays each participant a share of a weekly Canton Coin reward pool, earned through holding HANDL in a linked Canton wallet, posting about the product, and bridging assets onto Canton.
docs.handlpay.com loyalty programThe docs introduction reports 360,000 social media accounts onboarded as of January 2026 and more than 2 million transactions processed during 2025.
docs.handlpay.com introductionThe homepage reports over 30,000 active users able to receive money through HandlPay.
handlpay.com homepageThe token page reports more than 300,000 users onboarded and about 8.4 million dollars average monthly payment volume.
handlpay.com/tokenThe July 2026 recap reports 200 million HANDL bridged from EVM chains to Canton in July, and a first release of HandlPay v2, a full rebuild with payments private by default through Canton, targeted for the end of Q3.
HandlPay July 2026 recapIn the August community Q&A the team said burns will be tied to a planned public metrics dashboard, buybacks may or may not be announced, v2 will ship first as a web app and Telegram mini app, and unclaimed payments to handles that have not signed up will be held in escrow and returned.
HandlPay community Q&A #15// what would move the score
Catalysts.
Each one names what I am watching and what would prove me wrong.
The team targeted a first release of the rebuilt app, private by default through Canton, by the end of Q3 2026.
Falsified if: no public release or dated delay notice from HandlPay by 31 October 2026.
The team tied burns to a planned public metrics dashboard.
Falsified if: the token page still lists total burned as coming soon at the next reverify.
// what I could not verify
Gaps.
These are findings, not omissions. I looked and state what I found.
Active against onboarded. The docs report 360,000 accounts onboarded and the homepage over 30,000 active users. The two counts are not reconciled on HandlPay's surfaces, and neither states a definition of active.
Source of the Canton Coin reward pool. The loyalty program pays a share of a weekly Canton Coin pool. HandlPay is listed as a featured app, and featured apps earn Canton Coin rewards, but the docs do not state that the pool is funded from them.
Hosting of in-app Canton wallets. Which validator node hosts the Canton parties created inside the app is not stated on the pages cited here.
Burn record. The token docs describe a burn on payments received through handles, but no burn has been published and the token page lists total burned as coming soon.
Independent audit. No third-party audit of the bridge or the token contracts was located on HandlPay's surfaces.
Named leadership. The pages cited here do not name the founding team or leadership titles.
// open to the project
Sections HandlPay can fill.
These stay empty until the project supplies them. Anything supplied is labeled as supplied, dated, and never rendered as something I verified. Declining changes nothing else on this page.
Architecture
How the product is built, in the team's own words.
Audit
Any audit, review or internal security practice not published today.
Roadmap
What ships next and when, so the catalysts above can carry real dates.
Usage figures
Published usage with a methodology, so a count can move off announced tier.
// conflicts
Position.
Position disclosure. I hold $CC, $CNTN and $HANDL. This page covers a product integrated with Canton Network, which triggers disclosure under my map, and HandlPay's own $HANDL token is a holding of mine. The full conflicts register is on the disclosure page. HandlPay has no commercial relationship with Canton Catalyst, and nothing here was requested, reviewed or paid for.
// corrections
Correction log.
No corrections recorded. First published 27 September 2026.