Skip to main content
The WalletConnect Pay SDK allows wallet users to pay merchants using their crypto assets. The SDK handles payment option discovery, permit signing coordination, and payment confirmation while leveraging your wallet’s existing signing infrastructure.

Sample Wallet

For a complete working example, check out our sample wallet implementation:

Sample Wallet - React Native

A reference React Native wallet app demonstrating WalletConnect Pay integration.

Requirements

  • React Native 0.70+
  • @walletconnect/react-native-compat installed and linked

Installation

Install the WalletConnect Pay SDK using npm or yarn:
React Native Setup This SDK requires the WalletConnect React Native native module. Make sure you have @walletconnect/react-native-compat installed and linked in your React Native project:

Architecture

The SDK uses a provider abstraction that allows different implementations:
  • NativeProvider: Uses React Native uniffi module (current)
  • WasmProvider: Uses WebAssembly module (coming soon for web browsers)
The SDK auto-detects the best available provider for your environment.

Initialization

Initialize the WalletConnect Pay client with your credentials:
Configuration Parameters
Either appId or apiKey must be provided for authentication.
Don’t have a project ID? Create one at the WalletConnect Dashboard by signing up and creating a new project.

Supported Networks & Tokens

WalletConnect Pay currently supports the following tokens and networks:
Include accounts for all supported networks to maximize payment options for your users.

Payment Flow

The payment flow consists of five main steps: Get Options -> Collect Data (if required) -> Get Actions -> Sign Actions -> Confirm Payment
1

Get Payment Options

When a user scans a payment QR code or opens a payment link, fetch available payment options:
2

Collect User Data (If Required)

After the user selects an option, check for collectData on it. If present, collect the data before fetching the required actions.

Embedded Data Collection Form

When a payment requires user information (e.g., for Travel Rule compliance), the SDK returns a collectData field on individual payment options. Each option may independently require data collection — some options may require it while others don’t.The form is loaded from selectedOption.collectData.url and embedded in your wallet (a WebView on mobile, an iframe on web). It handles field rendering, validation, Terms & Conditions and Privacy Policy acceptance, and submits data directly to the backend.Collect this data before fetching the required actions. For an option that requires Information Capture, getRequiredPaymentActions fails with 400 IC data required until the data has been submitted.The recommended approach is to display all payment options upfront, then handle data collection only when the user selects an option that requires it:
  1. Call getPaymentOptions and display all available options to the user
  2. Show a visual indicator (e.g., “Info required” badge) on options where option.collectData is present
  3. When the user selects an option, check selectedOption.collectData
  4. If present, load selectedOption.collectData.url in the embedded form
  5. Optionally append query parameters to the form URL — prefill (known user data), theme, and themeVariables (appearance). See Form URL parameters below. Use proper URL building so existing query parameters are preserved.
  6. Listen for completion messages: IC_COMPLETE (success) or IC_ERROR (failure)
  7. On IC_COMPLETE, continue the flow — fetch the required actions, sign, and confirm the payment. Don’t pass collectedData to confirmPayment(); the form submits data directly to the backend

Decision Matrix

Form URL parameters

The form URL accepts the following optional query parameters. Append them to selectedOption.collectData.url before loading it, preserving any existing query parameters.
collectData.schema is a JSON schema string — parse it and read its required array to discover the field keys for prefill. For example, a required array of ["fullName", "dob", "pobAddress"] maps to a prefill object of {"fullName": "...", "dob": "...", "pobAddress": "..."}.

Customizing the form appearance

theme and themeVariables are optional and independent — pass either, both, or neither:
  • theme switches the form between light and dark base color modes. Match it to your wallet’s active mode for a seamless transition.
  • themeVariables applies brand-level overrides (font, font size, select colors, button border radius, and input border radius). Generate the theme in the WalletConnect Pay Dashboard, export it as a base64url string, and append it to the form URL verbatim — you don’t need to encode it at runtime.
The top-level collectData on the payment options response is still available for backward compatibility. However, the per-option collectData is the recommended approach as it provides more granular control over the flow.
Do not pass collectedData to confirmPayment() when using the embedded form. The form handles data submission directly.

WebView Message Types

The WebView communicates with your wallet through JavaScript bridge messages. The message payload is a JSON string with the following structure:Platform-Specific Bridge Names
3

Get Required Actions

After the user selects a payment option, get the wallet RPC actions required to complete the payment:
4

Sign Actions

Sign each action with your wallet’s signing implementation:
Payment options may include multiple actions with different RPC methods. For example, a Permit2 payment where the user lacks sufficient allowance returns two actions: an eth_sendTransaction to approve the token allowance, followed by an eth_signTypedData_v4 to sign the Permit2 transfer. Your wallet must check action.walletRpc.method and dispatch to the appropriate handler. For full implementation guidance, see USDT support.
Signatures must be in the same order as the actions array.
5

Confirm Payment

Submit the signatures and collected data to complete the payment:

Data Collection Implementation

When selectedOption.collectData.url is present, display the URL in a WebView using react-native-webview. Install the dependency:
Data Collection Best Practices
  • Display prominently: Show the form full-screen or as a prominent modal so users can interact with it easily
  • Loading indicator: Show a loading indicator while the form loads
  • Handle errors: Listen for IC_ERROR messages and display a user-facing error message with an option to retry
  • External links: Open Terms & Conditions and Privacy Policy links in the system browser rather than navigating within the form
  • Domain restriction: Only allow navigation to WalletConnect pay domains and HTTPS URLs
  • Back navigation: Handle back/dismiss gracefully — confirm cancellation with the user before closing the form mid-flow
  • Keyboard behavior: Test that the soft keyboard appears and behaves correctly when users tap on form inputs
  • Theme to match your brand: Pass theme=light or theme=dark to match your wallet’s active color mode, and apply brand tokens with themeVariables exported from the WalletConnect Pay Dashboard. See Form URL parameters.

Complete Example

Here’s a complete implementation example:

Provider Utilities

The SDK provides utilities for checking provider availability:

API Reference

WalletConnectPay Main client for payment operations. Constructor
Methods Data Types PaymentStatus
PayProviderType
CollectDataFieldType
Method Parameters
Response Types
PaymentOption
Action
Amount Types
Payment Info Types
Collect Data Types

Error Handling

The SDK throws typed errors for different failure scenarios:
Error Types Error Codes The PayError class includes a code property with one of the following values:

Best Practices

  1. Check Provider Availability: Always check if a provider is available before using the SDK
  2. Account Format: Always use CAIP-10 format for accounts: eip155:{chainId}:{address}
  3. Multiple Chains: Provide accounts for all supported chains to maximize payment options
  4. Signature Order: Maintain the same order of signatures as the actions array
  5. Error Handling: Always handle errors gracefully and show appropriate user feedback
  6. Loading States: Show loading indicators during API calls and signing operations
  7. Expiration: Check paymentInfo.expiresAt and warn users if time is running low
  8. User Data: Only collect data when collectData is present on the selected payment option and you don’t already have the required user data. If you already have the required data, you can submit this without collecting from the user. You must make sure the user accepts WalletConnect Terms and Conditions and Privacy Policy before submitting user information to WalletConnect.
  9. WebView Data Collection: When selectedOption.collectData?.url is present, display the URL in a WebView using react-native-webview rather than building native forms. The WebView handles form rendering, validation, and T&C acceptance.
  10. Per-Option Data Collection: When displaying payment options, check each option’s collectData field. Show a visual indicator (e.g., “Info required” badge) on options that require data collection. Only open the WebView when the user selects an option with collectData present — use the option’s collectData.url which is already scoped to that option’s account.