Cowrie Research

walletconnect-pay-primary-sources-2026-05-03

3 min read

WalletConnect Pay primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone WalletConnect Pay whitepaper or litepaper surfaced in this pass.
  • The clearest current sources of truth were the WalletConnect Pay overview, wallet-integration docs, ecommerce docs, user flow docs, and the agent-sdk README.
  • The materials consistently frame WalletConnect Pay as a PSP-compatible crypto payments layer rather than as only a wallet UI feature.

Primary-source snapshots

1) WalletConnect Pay overview

  • URL: https://docs.walletconnect.com/payments/overview
  • Key excerpt:
    • The overview says WalletConnect Pay provides a “complete end-to-end crypto payment solution” that fits directly into an existing PSP stack.
    • It says the system can align with common compliance requirements, including information capture and screening steps.
    • It frames the main flow as merchant-presented QR intents, wallet-side asset/network choice, transaction execution, and merchant settlement via the PSP.

2) Wallet integration overview

  • URL: https://docs.walletconnect.com/payments/wallets/overview
  • Key excerpt:
    • The wallet docs say one integration connects a wallet to a global network of PSPs and merchants across online and in-store payment contexts.
    • They describe three implementation paths: WalletKit, standalone SDK, and direct API-first integration.
    • They also document the common payment flow of detecting a payment link, fetching payment options, retrieving required actions, signing, collecting compliance data when needed, and confirming the payment.

3) Ecommerce overview

  • URL: https://docs.walletconnect.com/payments/ecommerce/overview
  • Key excerpt:
    • The ecommerce docs say WalletConnect Pay enables online checkout with “any wallet, any asset, one checkout flow.”
    • They emphasize compatibility with existing checkout and operations workflows and explicitly mention alignment with PSP compliance requirements.
    • They also highlight flexible fiat-or-crypto payouts and incentives intended to encourage customer usage.

4) User payment flow docs

  • URL: https://docs.walletconnect.com/payments/for-users
  • Key excerpt:
    • The user docs show that customers can pay either by scanning a WalletConnect QR code from a compatible wallet or by scanning a QR code with a phone camera to open a mobile payment page.
    • They make clear that the wallet presents the payment intent and lets the customer choose token and network before approval.
    • This confirms the product is trying to abstract merchant acceptance across wallets while preserving wallet-side user choice.

5) agent-sdk README

  • URL: https://github.com/WalletConnect/agent-sdk/blob/main/README.md
  • Key excerpt:
    • The README exposes an experimental walletconnect-pay CLI that can check payment status, create new merchant payments, and complete a payment using a connected wallet.
    • It documents both proxy mode and direct API mode, plus optional information-capture fields such as name, date of birth, and place-of-birth details.
    • This is important because it extends WalletConnect Pay beyond wallet-app UX into terminal and agent workflows.

Working conclusion

WalletConnect Pay is best cataloged as crypto payment-acceptance and interoperability infrastructure. The decisive signals are PSP-stack fit, wallet SDK and API-first integration paths, structured compliance-information capture, customer asset/network choice inside supported wallets, and an emerging agent/CLI surface for payment creation and checkout.

Graph View