x402 Payment
Supported Wallets

Supported Wallets

Summary

The x402 payment system supports any cryptocurrency wallet that implements standard signing methods, particularly EIP-712 structured data signing. This includes the vast majority of EVM-compatible wallets, making x402 accessible to users across the Ethereum ecosystem and compatible networks.

General Requirements

Any wallet that supports the following standards is compatible with x402:

  • EIP-712 Structured Data Signing — Required for creating payment authorizations
  • EVM Compatibility — Must work with Ethereum and EVM-compatible networks
  • Standard JSON-RPC Methods — Support for eth_signTypedData_v4 or similar signing methods

This broad compatibility means that most modern cryptocurrency wallets work seamlessly with the x402 payment protocol without requiring special integrations or modifications.

Supported Wallet Categories

Wallet CategoryDescription
EVM-Compatible WalletsAny wallet supporting EIP-712 signing on Ethereum and EVM networks. Includes popular options like MetaMask, Trust Wallet, Coinbase Wallet, Rainbow, and many others. These wallets provide the standard signing interface required for x402 payments.
CDP WalletCoinbase Developer Platform wallet, specifically recommended in the documentation for its robust developer tooling and seamless integration with x402 payment flows. Offers excellent support for structured data signing and meta-transactions.
AgentKitDeveloper-focused wallet solution designed for AI agent integrations. Provides programmatic access to signing capabilities, making it ideal for automated systems and AI agents that need to execute x402 payments without manual user intervention.

Key Features

Universal Compatibility

The x402 standard leverages existing wallet infrastructure, meaning no special wallet modifications or plugins are required. If your wallet can sign EIP-712 messages, it can process x402 payments.

No Additional Setup

Users don't need to install special extensions or configure additional settings. The payment flow works through standard wallet signing interfaces that users are already familiar with.

Developer Integration

Web Applications

// Works with any EIP-712 compatible wallet
const signature = await window.ethereum.request({
  method: 'eth_signTypedData_v4',
  params: [userAddress, typedData]
});

Mobile Applications

Mobile wallets that support WalletConnect or similar protocols can integrate with x402-enabled applications through standard connection methods.

Programmatic Access

For AI agents and automated systems, wallets like AgentKit provide programmatic signing capabilities:

// Example with AgentKit or similar programmatic wallet
const wallet = new ProgrammaticWallet(privateKey);
const signature = await wallet.signTypedData(domain, types, message);

Testing and Development

Local Development

For testing x402 integrations, any wallet that can connect to local networks (like Hardhat's localhost:8545) will work. MetaMask is commonly used for local development due to its easy network configuration.

Testnet Support

All supported wallets can be configured to work with testnets, allowing developers to test x402 payment flows without using real funds.

Security Considerations

Private Key Management

  • Use dedicated wallets for x402 payments when possible
  • Implement spending limits through wallet settings
  • Regularly rotate keys for programmatic wallets
  • Monitor transaction history for unusual activity

Network Security

  • Verify you're connected to the correct network before signing
  • Double-check payment amounts and recipients
  • Use hardware wallets for high-value operations when supported

Getting Started

  1. Choose any EVM-compatible wallet from the categories above
  2. Configure for your target network (mainnet, testnet, or local)
  3. Ensure sufficient token balance for payments
  4. Connect to x402-enabled applications using standard wallet connection methods

The x402 protocol's wallet-agnostic design ensures that users can leverage their existing wallet preferences while accessing pay-per-query datasets and services.