Why get certified
Certified wallets benefit from:- Trust and visibility — a WalletConnect Certified badge, shown when users open the connection modal to access an app, a listing on WalletGuide, and co-marketing opportunities with the WalletConnect brand.
- Higher rank in the wallet list — certified wallets appear before non-certified wallets in the wallet list shown when users connect via WalletConnect.
- Improved analytics — data on how a wallet’s users are connecting via the WalletConnect Network, in a dedicated dashboard for certified wallets.
- New revenue streams — access to rewards and incentives, including $WCT token rewards, interchange fees, and revenue-generating programs exclusive to certified wallets.
How the program works
The program runs in seasons, each with its own theme and progressively higher requirements. Each season builds on the last: certification requires meeting the criteria for every season up to the current one.
Requirements are set by WalletConnect in collaboration with the WalletConnect Council, which represents leading projects across the ecosystem. The Season 2 requirements, for example, came out of a workshop with wallets at WalletCon II in Bangkok.
Eligibility
Certification is high-touch and collaborative, so only a limited number of wallets are certified per season. To be eligible, a wallet must meet at least one of the following:- Top 40 wallet by number of WalletConnect connections.
- Demonstrated growth potential — a credible path to becoming top 40.
- High transaction volume — for example, institutional-grade wallets.
Not sure a wallet qualifies? Reach out to evaluate eligibility.
Criteria by season
Each season below follows the same shape: what the season is about, then the requirements a wallet must meet.Season 1 — “It just works”
The foundational season, focused on reliable connections across dapps. Requirements- Integrate the WalletKit SDK.
- Pass every test case in the “It Just Works” QA sheet.
Season 2 — UX excellence
Focused on fewer clicks and a cleaner connection experience. Requirements- Upgrade to the latest SDK version.
- Implement a simple “Connect” screen:
- Abstract the network — hide it entirely, or keep it out of the user’s way.
- Let users change the account during connection, and expose multiple accounts.
- Let users reject the connection.
- Show proper error messages (chain names, not identifiers like
eip155:1).
- Transaction approval screen improvements.
- Ecosystem-specific RPC support, where applicable to the wallet:
- Solana: all methods in the Solana RPC reference, plus
signAndSendAllTransactions. - Ethereum:
wallet_sendCallsper the Ethereum RPC reference. - Bitcoin: all methods in the Bitcoin RPC reference.
- Solana: all methods in the Solana RPC reference, plus
Season 3 — Payments
Focused on stablecoin and crypto payments through WalletConnect Pay: in-store QR payments and 1-click checkout online, with interchange-like revenue on every transaction. Season 3 also requires meeting the WCT staking requirements for the Wallet Rewards program — Certified wallets need a minimumstakeWeight of 12,500 (e.g. 50,000 WCT staked for 52 weeks).
Requirements
- Native WalletConnect Pay integration (primary criterion). The native integration delivers the best user experience and unlocks interchange-like revenue. It’s an SDK upgrade plus enablement, roughly two weeks of effort. Get started with the WalletConnect Pay integration docs.
- Fallback flow. This already works for any wallet that supports WalletConnect sessions — no SDK changes needed. The user lands on the payment gateway, connects their wallet via WalletConnect, and completes the payment. Certification confirms this path functions correctly and covers users during staged rollouts of native Pay.
- Before native Pay integration: fallback is tested via both the wallet QR scanner and the device camera.
- After native Pay integration: the wallet QR scanner triggers native Pay, so fallback is only tested via the device camera (lower priority).
How to apply
1
Check eligibility
Confirm the wallet meets one of the eligibility criteria above.
2
Meet the requirements
Complete the SDK integration and the QA checklist for the active season. Run QA independently first by making a copy of the self-serve QA checklist to validate the integration before submitting.
3
Submit for review
Apply via the form, or reach out on existing channels, email wallets@walletconnect.com, or book an intro call.
4
Get listed and rewarded
Once approved, the wallet appears on WalletGuide and becomes eligible for all Certified benefits.
How we review
Certification is a guided process, not a one-shot submission:- The WalletConnect team walks the wallet team through testing and validation once submitted.
- Each criterion is tested across the relevant flows — for Season 3, that means both QR scanning methods (the wallet’s built-in scanner and the device’s default camera), on both in-store and online checkout where applicable.
- Wallet teams share QA builds of their app with WalletConnect for verification against the season’s test cases.
- Flows across certified wallets are tested on an ongoing basis, and any issues found are flagged — certification is maintained, not just awarded.