WalletConnect Pay SDK - React Native
Integrate WalletConnect Pay into your React Native wallet to enable seamless crypto payments for your users.
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/pay1.1.0 or later@walletconnect/react-native-compat2.25.0 or later, installed and linked (ships the native Yttrium module: yttrium-wcpay 0.10.60 on Android, YttriumWrapper 0.10.59 on iOS)
Installation
Install the WalletConnect Pay SDK using npm or yarn:
npm install @walletconnect/payReact Native Setup
This SDK requires the WalletConnect React Native native module. Make sure you have @walletconnect/react-native-compat 2.25.0 or later installed and linked in your React Native project:
npm install @walletconnect/react-native-compatArchitecture
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:
import { WalletConnectPay } from "@walletconnect/pay";
const client = new WalletConnectPay({
appId: "your-wcp-id",
// OR use apiKey instead:
// apiKey: "your-api-key",
});Configuration Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
appId | string | No* | WCP ID for authentication |
apiKey | string | No* | API key for authentication |
clientId | string | No | Client ID for tracking |
baseUrl | string | No | Custom API base URL |
logger | Logger | No | Custom logger instance or level |
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:
| Token | Network | Chain ID | CAIP-10 Format |
|---|---|---|---|
| USDC | Arbitrum | 42161 | eip155:42161:{address} |
| USDC | Base | 8453 | eip155:8453:{address} |
| USDC | Polygon | 137 | eip155:137:{address} |
| USDC | Ethereum | 1 | eip155:1:{address} |
| USDC | Optimism | 10 | eip155:10:{address} |
| USDC | Monad | 143 | eip155:143:{address} |
| USDC | Celo | 42220 | eip155:42220:{address} |
| USDC | BSC | 56 | eip155:56:{address} |
| EURC | Ethereum | 1 | eip155:1:{address} |
| EURC | Base | 8453 | eip155:8453:{address} |
| USDT0 | Arbitrum | 42161 | eip155:42161:{address} |
| PYUSD | Ethereum | 1 | eip155:1:{address} |
| PYUSD | Arbitrum | 42161 | eip155:42161:{address} |
| USDG | Ethereum | 1 | eip155:1:{address} |
| USDT | Ethereum | 1 | eip155:1:{address} |
| USDT | Polygon | 137 | eip155:137:{address} |
| USDT | BSC | 56 | eip155:56:{address} |
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
Get Payment Options
When a user scans a payment QR code or opens a payment link, fetch available payment options:
const options = await client.getPaymentOptions({
paymentLink: "https://pay.walletconnect.com/pay_123",
accounts: [
`eip155:1:${walletAddress}`, // Ethereum Mainnet
`eip155:8453:${walletAddress}`, // Base
],
includePaymentInfo: true,
});
console.log("Payment ID:", options.paymentId);
console.log("Options:", options.options);
// Display merchant info
if (options.info) {
console.log("Merchant:", options.info.merchant.name);
console.log("Amount:", options.info.amount.display.assetSymbol, options.info.amount.value);
}
// Check which options require data collection
for (const option of options.options) {
if (option.collectData) {
console.log(`Option ${option.id} requires info capture`);
}
}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.
Recommended Flow
The recommended approach is to display all payment options upfront, then handle data collection only when the user selects an option that requires it:
- Call
getPaymentOptionsand display all available options to the user - Show a visual indicator (e.g., "Info required" badge) on options where
option.collectDatais present - When the user selects an option, check
selectedOption.collectData - If present, load
selectedOption.collectData.urlin the embedded form - Optionally append query parameters to the form URL —
prefill(known user data),theme, andthemeVariables(appearance). See Form URL parameters below. Use proper URL building so existing query parameters are preserved. - Listen for completion messages:
IC_COMPLETE(success) orIC_ERROR(failure) - On
IC_COMPLETE, continue the flow — fetch the required actions, sign, and confirm the payment. Don't passcollectedDatatoconfirmPayment(); the form submits data directly to the backend
Decision Matrix
Response collectData | option.collectData | Behavior |
|---|---|---|
| present | present | Option requires IC — use option.collectData.url |
| present | null | Option does NOT require IC (others might) — skip IC for this option |
null | null | No IC needed for any option |
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.
| Parameter | Format | Description |
|---|---|---|
prefill | base64url-encoded JSON | Pre-populates known user fields so the user doesn't re-enter them. Keys must match the required fields from collectData.schema (e.g. fullName, dob, pobAddress). |
theme | light or dark | Sets the form's base color mode. |
themeVariables | base64url-encoded JSON | Overrides design tokens to match your brand — font, font size, select colors, button border radius, and input border radius. Generate and export this value from the WalletConnect Pay Dashboard. |
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:
themeswitches the form betweenlightanddarkbase color modes. Match it to your wallet's active mode for a seamless transition.themeVariablesapplies 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.
// Check per-option data collection requirement after user selects an option
if (selectedOption.collectData?.url) {
// Use the "required" list from selectedOption.collectData.schema to determine which fields to prefill
const prefillData = {
fullName: "John Doe",
dob: "1990-01-15",
pobAddress: "123 Main St, New York, NY 10001",
};
// Encode prefill as base64url (URL-safe, no padding)
const prefill = btoa(JSON.stringify(prefillData))
.replace(/\+/g, "-").replace(/\//g, "_").replace(/=+$/, "");
// Optional appearance params (see "Form URL parameters"):
// theme=light|dark — base color mode
// themeVariables=<base64url> — exported from the WalletConnect Pay Dashboard
const themeVariables = "<base64url-exported-from-dashboard>";
const query = `prefill=${prefill}&theme=dark&themeVariables=${themeVariables}`;
const separator = selectedOption.collectData.url.includes("?") ? "&" : "?";
const webViewUrl = `${selectedOption.collectData.url}${separator}${query}`;
// Show WebView for this specific option — see Data Collection Implementation section below
showDataCollectionWebView(webViewUrl);
}WebView Message Types
The WebView communicates with your wallet through JavaScript bridge messages. The message payload is a JSON string with the following structure:
| Message Type | Payload | Description |
|---|---|---|
IC_COMPLETE | { "type": "IC_COMPLETE", "success": true } | User completed the form successfully. Proceed to payment confirmation. |
IC_ERROR | { "type": "IC_ERROR", "error": "..." } | An error occurred. Display the error message and allow the user to retry. |
Platform-Specific Bridge Names
| Platform | Bridge Name | Handler |
|---|---|---|
| Kotlin (Android) | AndroidWallet | @JavascriptInterface onDataCollectionComplete(json: String) |
| Swift (iOS) | payDataCollectionComplete | WKScriptMessageHandler.didReceive(message:) |
| Flutter | ReactNativeWebView (injected via JS bridge) | JavaScriptChannel.onMessageReceived |
| React Native | ReactNativeWebView (native) | WebView.onMessage prop |
Get Required Actions
After the user selects a payment option, get the wallet RPC actions required to complete the payment:
const actions = await client.getRequiredPaymentActions({
paymentId: options.paymentId,
optionId: options.options[0].id,
});
// Each action contains wallet RPC data to sign
for (const action of actions) {
console.log("Chain:", action.walletRpc.chainId);
console.log("Method:", action.walletRpc.method);
console.log("Params:", action.walletRpc.params);
}Sign Actions
Sign each action with your wallet's signing implementation:
// Sign each action based on its RPC method
const data = await Promise.all(
actions.map(async (action) => {
const { chainId, method, params } = action.walletRpc;
const parsedParams = JSON.parse(params);
switch (method) {
case "eth_signTypedData_v4":
return await wallet.signTypedData(chainId, parsedParams);
case "eth_sendTransaction":
return await wallet.sendTransaction(chainId, parsedParams[0]);
case "personal_sign":
return await wallet.personalSign(chainId, parsedParams);
default:
throw new Error(`Unsupported RPC method: ${method}`);
}
})
);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.
Keep data in the same order as the actions array.
Confirm Payment
Submit the wallet RPC results (data) and collected data to complete the payment. Each element of data is either a plain string (a signature or transaction hash) or, for chains like Tron, a JSON object; the SDK forwards each element verbatim. See Tron support for the Tron payload.
const result = await client.confirmPayment({
paymentId: options.paymentId,
optionId: options.options[0].id,
data,
collectedData, // Include if collectData was present
});
if (result.status === "succeeded") {
console.log("Payment successful!");
} else if (result.status === "processing") {
console.log("Payment is processing...");
} else if (result.status === "failed") {
console.log("Payment failed");
}The signatures parameter is deprecated in favor of data and will be removed in a future major version. Existing integrations that pass signatures keep working; the SDK uses it as a fallback when data is omitted.
Data Collection Implementation
When selectedOption.collectData.url is present, display the URL in a WebView using react-native-webview. Install the dependency:
npm install react-native-webview@13.16.0Data 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_ERRORmessages 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=lightortheme=darkto match your wallet's active color mode, and apply brand tokens withthemeVariablesexported from the WalletConnect Pay Dashboard. See Form URL parameters.
import React, { useCallback } from "react";
import { WebView, WebViewMessageEvent } from "react-native-webview";
import { Linking, View, ActivityIndicator } from "react-native";
interface PayDataCollectionWebViewProps {
url: string;
onComplete: () => void;
onError: (error: string) => void;
}
function PayDataCollectionWebView({
url,
onComplete,
onError,
}: PayDataCollectionWebViewProps) {
const handleMessage = useCallback(
(event: WebViewMessageEvent) => {
try {
const data = JSON.parse(event.nativeEvent.data);
switch (data.type) {
case "IC_COMPLETE":
onComplete();
break;
case "IC_ERROR":
onError(data.error || "Unknown error");
break;
}
} catch {
// Ignore non-JSON messages
}
},
[onComplete, onError]
);
const handleNavigationRequest = useCallback(
(request: { url: string }) => {
// Open external links (T&C, Privacy Policy) in system browser
if (!request.url.includes("pay.walletconnect.com")) {
Linking.openURL(request.url);
return false;
}
return true;
},
[]
);
return (
<WebView
source={{ uri: url }}
onMessage={handleMessage}
onShouldStartLoadWithRequest={handleNavigationRequest}
javaScriptEnabled
domStorageEnabled
startInLoadingState
renderLoading={() => (
<View style={{ flex: 1, justifyContent: "center", alignItems: "center" }}>
<ActivityIndicator size="large" />
</View>
)}
/>
);
}
function buildFormUrl(
baseUrl: string,
options: {
prefill?: Record<string, string>;
theme?: "light" | "dark";
themeVariables?: string; // base64url string exported from the Pay Dashboard
} = {}
): string {
const params: string[] = [];
if (options.prefill && Object.keys(options.prefill).length > 0) {
// base64url: URL-safe, no padding
const prefill = btoa(JSON.stringify(options.prefill))
.replace(/\+/g, "-").replace(/\//g, "_").replace(/=+$/, "");
params.push(`prefill=${prefill}`);
}
if (options.theme) params.push(`theme=${options.theme}`);
if (options.themeVariables) params.push(`themeVariables=${options.themeVariables}`);
if (params.length === 0) return baseUrl;
const separator = baseUrl.includes("?") ? "&" : "?";
return `${baseUrl}${separator}${params.join("&")}`;
}Complete Example
Here's a complete implementation example:
import { WalletConnectPay, CollectDataFieldResult } from "@walletconnect/pay";
class PaymentManager {
private client: WalletConnectPay;
constructor() {
this.client = new WalletConnectPay({
appId: "your-wcp-id",
});
}
async processPayment(paymentLink: string, walletAddress: string) {
try {
// Step 1: Get payment options
const options = await this.client.getPaymentOptions({
paymentLink,
accounts: [
`eip155:1:${walletAddress}`,
`eip155:137:${walletAddress}`,
`eip155:8453:${walletAddress}`,
],
includePaymentInfo: true,
});
if (options.options.length === 0) {
throw new Error("No payment options available");
}
// Step 2: Let user select an option (simplified - use first option)
const selectedOption = options.options[0];
// Step 3: Collect data via WebView if required for selected option —
// must happen BEFORE fetching the required actions, otherwise the
// backend rejects the request
if (selectedOption.collectData?.url) {
// Show WebView and wait for IC_COMPLETE
await this.showDataCollectionWebView(selectedOption.collectData.url);
}
// Step 4: Get required actions
const actions = await this.client.getRequiredPaymentActions({
paymentId: options.paymentId,
optionId: selectedOption.id,
});
// Step 5: Sign all actions
const data = await Promise.all(
actions.map((action) =>
this.signAction(action, walletAddress)
)
);
// Step 6: Confirm payment
const result = await this.client.confirmPayment({
paymentId: options.paymentId,
optionId: selectedOption.id,
data,
});
return result;
} catch (error) {
console.error("Payment failed:", error);
throw error;
}
}
private async signAction(action: Action, walletAddress: string): Promise<string> {
const { chainId, method, params } = action.walletRpc;
const parsedParams = JSON.parse(params);
switch (method) {
case "eth_signTypedData_v4":
return await wallet.signTypedData(chainId, parsedParams);
case "eth_sendTransaction":
return await wallet.sendTransaction(chainId, parsedParams[0]);
case "personal_sign":
return await wallet.personalSign(chainId, parsedParams);
default:
throw new Error(`Unsupported RPC method: ${method}`);
}
}
}Provider Utilities
The SDK provides utilities for checking provider availability:
import {
isProviderAvailable,
detectProviderType,
isNativeProviderAvailable,
setNativeModule,
} from "@walletconnect/pay";
// Check if any provider is available
if (isProviderAvailable()) {
// SDK can be used
}
// Detect which provider type is available
const providerType = detectProviderType(); // 'native' | 'wasm' | null
// Check specifically for native provider
if (isNativeProviderAvailable()) {
// React Native native module is available
}
// Manually inject native module (if auto-discovery fails)
import { NativeModules } from "react-native";
setNativeModule(NativeModules.RNWalletConnectPay);API Reference
WalletConnectPay
Main client for payment operations.
Constructor
new WalletConnectPay(options: WalletConnectPayOptions)Methods
| Method | Description |
|---|---|
getPaymentOptions(params) | Fetch available payment options |
getRequiredPaymentActions(params) | Get signing actions for a payment option |
confirmPayment(params) | Confirm and execute the payment |
static isAvailable() | Check if a provider is available |
Data Types
PaymentStatus
type PaymentStatus =
| "requires_action"
| "processing"
| "succeeded"
| "failed"
| "expired";PayProviderType
type PayProviderType = "native" | "wasm";CollectDataFieldType
type CollectDataFieldType = "text" | "date";Method Parameters
interface GetPaymentOptionsParams {
/** Payment link or ID */
paymentLink: string;
/** List of CAIP-10 accounts */
accounts: string[];
/** Whether to include payment info in response */
includePaymentInfo?: boolean;
}
interface GetRequiredPaymentActionsParams {
/** Payment ID */
paymentId: string;
/** Option ID */
optionId: string;
}
interface ConfirmPaymentParams {
/** Payment ID */
paymentId: string;
/** Option ID */
optionId: string;
/** Wallet RPC results in action order: plain strings or JSON objects (e.g. Tron) */
data: (string | object)[];
/** @deprecated Alias for `data`, still accepted */
signatures?: string[];
}The SDK types data as (string | Record<string, unknown> | unknown[])[]. A value typed with a TypeScript interface does not satisfy Record<string, unknown>; declare it as a type alias or spread it into an object literal.
Response Types
interface PaymentOptionsResponse {
/** Payment ID extracted from the payment link */
paymentId: string;
/** Payment information (if includePaymentInfo was true) */
info?: PaymentInfo;
/** Available payment options */
options: PaymentOption[];
/** Data collection requirements (if any) */
collectData?: CollectDataAction;
/** Transaction result details (present when payment already completed) */
resultInfo?: PaymentResultInfo;
}
interface PaymentResultInfo {
/** Transaction ID */
txId: string;
/** Token amount details */
optionAmount: PayAmount;
}
interface ConfirmPaymentResponse {
/** Payment status */
status: PaymentStatus;
/** True if the payment is in a final state */
isFinal: boolean;
/** Time to poll for payment status, in milliseconds */
pollInMs?: number;
}PaymentOption
interface PaymentOption {
/** ID of the option */
id: string;
/** The option's token and amount */
amount: PayAmount;
/** Estimated time to complete the option, in seconds */
etaS: number;
/** Actions required to complete the option */
actions: Action[];
/** Per-option data collection requirements */
collectData?: CollectDataAction;
}Action
interface Action {
walletRpc: WalletRpcAction;
}
interface WalletRpcAction {
/** Chain ID in CAIP-2 format (e.g., "eip155:8453") */
chainId: string;
/** RPC method name (e.g., "eth_signTypedData_v4", "eth_sendTransaction") */
method: string;
/** JSON-encoded params array */
params: string;
}Amount Types
interface PayAmount {
/** Currency unit, prefixed with either "iso4217/" or "caip19/" */
unit: string;
/** Amount value, in the currency unit's minor units */
value: string;
/** Display information for the amount */
display: AmountDisplay;
}
interface AmountDisplay {
/** Ticker/symbol of the asset */
assetSymbol: string;
/** Full name of the asset */
assetName: string;
/** Number of minor decimals of the asset */
decimals: number;
/** URL of the icon of the asset (if token) */
iconUrl?: string;
/** Name of the network of the asset (if token) */
networkName?: string;
}Payment Info Types
interface PaymentInfo {
/** Payment status */
status: PaymentStatus;
/** Amount to be paid */
amount: PayAmount;
/** Payment expiration timestamp, in seconds since epoch */
expiresAt: number;
/** Merchant information */
merchant: MerchantInfo;
/** Buyer information (present if payment has been submitted) */
buyer?: BuyerInfo;
}
interface MerchantInfo {
/** Merchant name */
name: string;
/** Merchant icon URL */
iconUrl?: string;
}
interface BuyerInfo {
/** Account CAIP-10 */
accountCaip10: string;
/** Account provider name */
accountProviderName: string;
/** Account provider icon URL */
accountProviderIcon?: string;
}Collect Data Types
interface CollectDataAction {
/** URL for data collection (displayed in WebView) */
url: string;
/** JSON schema describing required fields */
schema?: string;
}Error Handling
The SDK throws typed errors for different failure scenarios:
import {
PayError,
PaymentOptionsError,
PaymentActionsError,
ConfirmPaymentError,
NativeModuleNotFoundError
} from "@walletconnect/pay";
try {
const options = await client.getPaymentOptions({
paymentLink: link,
accounts,
});
} catch (error) {
if (error instanceof PaymentOptionsError) {
console.error("Failed to get options:", error.originalMessage);
} else if (error instanceof PayError) {
console.error("Pay error:", error.code, error.message);
}
}Error Types
| Error Class | Description |
|---|---|
PayError | Base error class for all Pay SDK errors |
PaymentOptionsError | Error when fetching payment options |
PaymentActionsError | Error when fetching required payment actions |
ConfirmPaymentError | Error when confirming payment |
NativeModuleNotFoundError | Error when native module is not available |
Error Codes
The PayError class includes a code property with one of the following values:
type PayErrorCode =
| "JSON_PARSE"
| "JSON_SERIALIZE"
| "PAYMENT_OPTIONS"
| "PAYMENT_REQUEST"
| "CONFIRM_PAYMENT"
| "NATIVE_MODULE_NOT_FOUND"
| "INITIALIZATION_ERROR"
| "UNKNOWN";Best Practices
-
Check Provider Availability: Always check if a provider is available before using the SDK
-
Account Format: Always use CAIP-10 format for accounts:
eip155:{chainId}:{address} -
Multiple Chains: Provide accounts for all supported chains to maximize payment options
-
Result Order: Keep
datain the same order as the actions array -
Error Handling: Always handle errors gracefully and show appropriate user feedback
-
Loading States: Show loading indicators during API calls and signing operations
-
Expiration: Check
paymentInfo.expiresAtand warn users if time is running low -
User Data: Only collect data when
collectDatais 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. -
WebView Data Collection: When
selectedOption.collectData?.urlis present, display the URL in a WebView usingreact-native-webviewrather than building native forms. The WebView handles form rendering, validation, and T&C acceptance. -
Per-Option Data Collection: When displaying payment options, check each option's
collectDatafield. 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 withcollectDatapresent — use the option'scollectData.urlwhich is already scoped to that option's account.