Requirements
- Min SDK: 23 (Android 6.0)
- WalletKit: 1.6.0+
Pre-Requisites
In order to use your WalletConnect Pay, you need to obtain an App ID for your project from the WalletConnect Dashboard.How to obtain an App ID
- Navigate to the WalletConnect Dashboard.
- Select the project that is associated with your wallet (as in, the projectId that is being used for your wallet’s WalletConnect integration).

- Click on the “Get Started” button to get an App ID associated with your project.
- The Dashboard will now show the App ID associated with your project.
- Click on the three dots on the right of the App ID and select “Copy App ID”. You will be using this for your wallet’s WalletConnect Pay integration.

Installation
First, add the required repositories to your project’ssettings.gradle.kts or root build.gradle.kts:
build.gradle.kts using the BOM (Bill of Materials):
Check the GitHub releases for the latest BOM version.
Initialization
WalletConnectPay is automatically initialized when you initialize WalletKit. No additional setup is required.appIdfrom your WalletConnect Project IDpackageNamefrom your application context
For more details on WalletKit initialization, see the WalletKit Usage documentation.
Payment Link Detection
UseWalletKit.Pay.isPaymentLink() to determine if a scanned URI is a payment link or a standard WalletConnect pairing URI:
Payment Flow
The payment flow consists of five main steps: Detect Payment Link -> Get Options -> Get Actions -> Sign Actions -> Confirm PaymentSign Actions
Collect User Data (If Required)
Some payments require additional user information:
WebView-Based Data Collection
When a payment requires user information (e.g., for Travel Rule compliance), the SDK returns acollectDataAction with a url field pointing to a WalletConnect-hosted form page.Instead of building native forms, wallets display this URL in a WebView. The hosted form handles rendering, validation, and Terms & Conditions acceptance. When the user completes the form, the WebView communicates back to the wallet via JavaScript bridge messages.How It Works
- Check if
collectDataAction.urlis present in the payment options response - Open the URL in a WebView within your wallet
- Optionally append a
prefill=<base64-json>query parameter with known user data (e.g., name, date of birth, address). Use proper URL building to handle existing query parameters. - Listen for JS bridge messages:
IC_COMPLETE(success) orIC_ERROR(failure) - On
IC_COMPLETE, proceed toconfirmPayment()without passingcollectedData— the WebView submits data directly to the backend
The
collectDataAction also includes a schema field — a JSON schema string describing the required fields. The required list in this schema tells you which fields the form expects. Wallets can use these field names as keys when building the prefill JSON object. For example, if the schema’s required array contains ["fullName", "dateOfBirth", "pobAddress"], you can prefill with {"fullName": "...", "dateOfBirth": "...", "pobAddress": "..."}.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 |
WebView Implementation
WhencollectDataAction.url is present, display the URL in a WebView. The WebView handles form rendering, validation, and T&C acceptance.
Complete Example
Here’s a complete implementation example:API Reference
WalletKit.Pay
The payment operations object within WalletKit.Methods
| Method | Description |
|---|---|
isPaymentLink(uri: String): Boolean | Check if URI is a payment link |
getPaymentOptions(paymentLink, accounts) | Get available payment options |
getRequiredPaymentActions(params) | Get actions requiring signatures |
confirmPayment(params) | Confirm and finalize payment |
Parameters
Wallet.Params.RequiredPaymentActions
Wallet.Params.ConfirmPayment
Data Models
Wallet.Model.PaymentOptionsResponse
Wallet.Model.PaymentInfo
Wallet.Model.PaymentOption
Wallet.Model.PaymentAmount
Wallet.Model.WalletRpcAction
Wallet.Model.CollectDataAction
Wallet.Model.ConfirmPaymentResponse
Wallet.Model.PaymentStatus
| Status | Description |
|---|---|
REQUIRES_ACTION | Additional action needed |
PROCESSING | Payment in progress |
SUCCEEDED | Payment completed |
FAILED | Payment failed |
EXPIRED | Payment expired |
Best Practices
- Use WalletKit Integration: If your wallet already uses WalletKit, prefer this approach for automatic configuration
-
Use
isPaymentLink()for Detection: Use the utility method instead of manual URL parsing for reliable payment link detection -
Account Format: Always use CAIP-10 format for accounts:
eip155:{chainId}:{address} - Multiple Chains: Provide accounts for all supported chains to maximize payment options
- Signature Order: Maintain the same order of signatures 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 in the response 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
collectDataAction.urlis present, display the URL in a WebView rather than building native forms. The WebView handles form rendering, validation, and T&C acceptance.