From e5291b4aed9e7fb0a83e025edc71cfd4b34f292d Mon Sep 17 00:00:00 2001 From: "walletconnect-agent[bot]" <287978535+walletconnect-agent[bot]@users.noreply.github.com> Date: Wed, 23 Sep 2026 10:12:35 +0000 Subject: [PATCH 1/8] docs: add WalletConnect Certified page under WalletGuide --- docs.jsonwallets/walletguide/certified.mdx | 0 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 docs.jsonwallets/walletguide/certified.mdx diff --git a/docs.jsonwallets/walletguide/certified.mdx b/docs.jsonwallets/walletguide/certified.mdx new file mode 100644 index 0000000..e69de29 From 707947fa8be8db4909e15e5ce4fd1b723a81176e Mon Sep 17 00:00:00 2001 From: "walletconnect-agent[bot]" <287978535+walletconnect-agent[bot]@users.noreply.github.com> Date: Wed, 23 Sep 2026 10:12:58 +0000 Subject: [PATCH 2/8] docs: add WalletConnect Certified page From ce4a0169b17862236cb26090688e22578c8658d9 Mon Sep 17 00:00:00 2001 From: "walletconnect-agent[bot]" <287978535+walletconnect-agent[bot]@users.noreply.github.com> Date: Wed, 23 Sep 2026 10:13:10 +0000 Subject: [PATCH 3/8] docs: add WalletConnect Certified page under WalletGuide --- wallets/walletguide/certified.mdx | 119 ++++++++++++++++++++++++++++++ 1 file changed, 119 insertions(+) create mode 100644 wallets/walletguide/certified.mdx diff --git a/wallets/walletguide/certified.mdx b/wallets/walletguide/certified.mdx new file mode 100644 index 0000000..f881c76 --- /dev/null +++ b/wallets/walletguide/certified.mdx @@ -0,0 +1,119 @@ +--- +title: WalletConnect Certified +sidebarTitle: WalletConnect Certified +description: The WalletConnect Certified program, its requirements by season, and how to apply. +--- + +WalletConnect Certified is a program to improve onchain connectivity together with the wallet ecosystem. It recognizes wallets that meet the highest standards for reliability, usability, security, and interoperability on the WalletConnect Network. + +To date, 32 wallets have been certified. Find them all on [WalletGuide](https://walletguide.walletconnect.network/). + +## 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. + +| Season | Theme | Status | +| --- | --- | --- | +| Season 1 (2024) | "It just works" — foundational reliability | Complete | +| Season 2 (2025) | UX excellence | Complete | +| Season 3 (2026) | Payments | Open (Jan 21, 2026 – end of 2026) | + +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_sendCalls` per the Ethereum RPC reference. + - Bitcoin: all methods in the Bitcoin RPC reference. + +### 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 minimum `stakeWeight` 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](/payments/wallets/overview). +- **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). + +WalletConnect Pay supports mobile wallets, hardware wallets, browser extensions, and wallet-as-a-service providers. Both in-store (POS) and e-commerce flows are part of certification; testing is adapted to each wallet's capabilities. + +## How to apply + + + + + Confirm the wallet meets one of the eligibility criteria above. + + + + 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. + + + + Apply via the form, or reach out on existing channels, email [wallets@walletconnect.com](mailto:wallets@walletconnect.com), or book an intro call. + + + + 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. From e9842190e29755aab7f5300811fa92bb4d1d6ff3 Mon Sep 17 00:00:00 2001 From: "walletconnect-agent[bot]" <287978535+walletconnect-agent[bot]@users.noreply.github.com> Date: Wed, 23 Sep 2026 10:14:45 +0000 Subject: [PATCH 4/8] docs: wire WalletConnect Certified page into WalletGuide nav From 879e7cd446c1a78b0bacd666654a86a7651889b9 Mon Sep 17 00:00:00 2001 From: "walletconnect-agent[bot]" <287978535+walletconnect-agent[bot]@users.noreply.github.com> Date: Wed, 23 Sep 2026 10:15:07 +0000 Subject: [PATCH 5/8] docs: wire WalletConnect Certified page into WalletGuide nav --- docs.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs.json b/docs.json index 8f43cdd..b5f8899 100644 --- a/docs.json +++ b/docs.json @@ -209,7 +209,8 @@ "wallets/walletguide/wallet-list", "wallets/walletguide/submit-chain", "wallets/walletguide/chain-list", - "wallets/walletguide/explorer-api" + "wallets/walletguide/explorer-api", + "wallets/walletguide/certified" ] }, { From 8b554058817267b1fcc12068e4cf65ee7f208bd0 Mon Sep 17 00:00:00 2001 From: "walletconnect-agent[bot]" <287978535+walletconnect-agent[bot]@users.noreply.github.com> Date: Wed, 23 Sep 2026 10:16:19 +0000 Subject: [PATCH 6/8] docs: remove stray artifact file from prior commit --- docs.jsonwallets/walletguide/certified.mdx | 0 1 file changed, 0 insertions(+), 0 deletions(-) delete mode 100644 docs.jsonwallets/walletguide/certified.mdx diff --git a/docs.jsonwallets/walletguide/certified.mdx b/docs.jsonwallets/walletguide/certified.mdx deleted file mode 100644 index e69de29..0000000 From 897857eee036d0d7455a7e4c22fafdfebb999a94 Mon Sep 17 00:00:00 2001 From: "walletconnect-agent[bot]" <287978535+walletconnect-agent[bot]@users.noreply.github.com> Date: Wed, 23 Sep 2026 20:16:28 +0000 Subject: [PATCH 7/8] docs: update WalletConnect Certified page content --- wallets/walletguide/certified.mdx | 52 +++++++------------------------ 1 file changed, 12 insertions(+), 40 deletions(-) diff --git a/wallets/walletguide/certified.mdx b/wallets/walletguide/certified.mdx index f881c76..b62573b 100644 --- a/wallets/walletguide/certified.mdx +++ b/wallets/walletguide/certified.mdx @@ -6,7 +6,7 @@ description: The WalletConnect Certified program, its requirements by season, an WalletConnect Certified is a program to improve onchain connectivity together with the wallet ecosystem. It recognizes wallets that meet the highest standards for reliability, usability, security, and interoperability on the WalletConnect Network. -To date, 32 wallets have been certified. Find them all on [WalletGuide](https://walletguide.walletconnect.network/). +To date, 32 wallets have been certified. Find them all on [WalletGuide](https://walletguide.walletconnect.network/?badge_type=certified). ## Why get certified @@ -27,15 +27,15 @@ The program runs in seasons, each with its own theme and progressively higher re | Season 2 (2025) | UX excellence | Complete | | Season 3 (2026) | Payments | Open (Jan 21, 2026 – end of 2026) | -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. +Requirements are set by WalletConnect in collaboration with the [WalletConnect Council](https://walletconnect.com/blog/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. +1. **Top 40 wallet** by number of WalletConnect connections. +2. **Demonstrated growth potential** — a credible path to becoming top 40. +3. **High transaction volume** — for example, institutional-grade wallets. @@ -45,47 +45,19 @@ 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. +The foundation: connecting a wallet to apps through WalletConnect works reliably, every time. Wallets integrate the WalletKit SDK and prove that connecting, switching chains and accounts, disconnecting, and handling errors all work smoothly and fast — even on poor networks. ### 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_sendCalls` per the Ethereum RPC reference. - - Bitcoin: all methods in the Bitcoin RPC reference. +Fewer clicks, better experience. Wallets make connecting and approving as simple as possible — Link Mode, One-Click Auth, a clean connect screen — and support the key RPC methods of every chain they offer (EVM, Solana, Bitcoin), so users can do everything an app asks of them. ### 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 minimum `stakeWeight` 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](/payments/wallets/overview). -- **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). +Wallets become a way to pay. Through WalletConnect Pay, users scan a merchant QR code in-store or check out online and approve the payment in one click, and the wallet earns interchange-like revenue on every transaction. Wallets integrate native WalletConnect Pay and confirm the fallback payment flow works for users who haven't updated yet. -WalletConnect Pay supports mobile wallets, hardware wallets, browser extensions, and wallet-as-a-service providers. Both in-store (POS) and e-commerce flows are part of certification; testing is adapted to each wallet's capabilities. +Certification requires meeting the criteria of all seasons. Every test case, with steps and expected results, is in the detailed QA sheet: [WalletConnect Certified QA Template](https://docs.google.com/spreadsheets/d/1sGZnBilocXfSQKSFlDSkB_G3OUMNr0x_41JD-Qc-UuY/copy). ## How to apply @@ -96,15 +68,15 @@ WalletConnect Pay supports mobile wallets, hardware wallets, browser extensions, - 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. + Complete the SDK integration and work through the [WalletConnect Certified QA Template](https://docs.google.com/spreadsheets/d/1sGZnBilocXfSQKSFlDSkB_G3OUMNr0x_41JD-Qc-UuY/copy) to validate the integration before submitting. - Apply via the form, or reach out on existing channels, email [wallets@walletconnect.com](mailto:wallets@walletconnect.com), or book an intro call. + [Apply via the form](https://share.hsforms.com/1Q12irNdNRo2HJe3Jl1OJiAnxw6s), reach out on existing channels, or email [wallets@walletconnect.com](mailto:wallets@walletconnect.com). - Once approved, the wallet appears on WalletGuide and becomes eligible for all Certified benefits. + Once approved, the wallet appears on [WalletGuide](https://walletguide.walletconnect.network/) and becomes eligible for all Certified benefits. From a6aff8759a51b28e0d9d8f668133c2081c8c64dd Mon Sep 17 00:00:00 2001 From: "walletconnect-agent[bot]" <287978535+walletconnect-agent[bot]@users.noreply.github.com> Date: Wed, 23 Sep 2026 20:47:19 +0000 Subject: [PATCH 8/8] docs: link eligibility CTA on WalletConnect Certified page --- wallets/walletguide/certified.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wallets/walletguide/certified.mdx b/wallets/walletguide/certified.mdx index b62573b..4e906f6 100644 --- a/wallets/walletguide/certified.mdx +++ b/wallets/walletguide/certified.mdx @@ -39,7 +39,7 @@ Certification is high-touch and collaborative, so only a limited number of walle -Not sure a wallet qualifies? Reach out to evaluate eligibility. +Not sure a wallet qualifies? [Reach out](https://share.hsforms.com/1Q12irNdNRo2HJe3Jl1OJiAnxw6s) to evaluate eligibility.