Pay4MeProxy

An HTTP proxy for x402-enabled services. It handles payment-required responses, signs supported payments from configured wallets, retries requests, and records proxy activity.

Demo / Admin UI Open the Pay4MeProxy dashboard. GitHub Repository View the source code and setup docs.

How the proxy flow works

  1. Your client sends a request through the proxy endpoint.
  2. If the upstream service returns an x402 payment-required response, Pay4MeProxy reads the payment challenge.
  3. The proxy signs the supported payment using the wallet configured in the admin dashboard.
  4. The original request is retried with the payment signature attached.
  5. The dashboard records the payment attempt and final transaction status.

Try it with demo.pay402me.com

Configure your HTTP client to use the proxy, then request an x402-protected resource on demo.pay402me.com. Login to the demo dashboard to review users, wallets, and transactions.

Preconfigured test users

The demo environment includes two proxy users for testing. Each user is mapped to its own configured wallet, so you can test transaction tracking per user and per wallet.

  1. Algorand => user test has access to algorand wallet testnet.
  2. Solana => user test1 has access to a solona wallet mainnet.
# Algorand testnet wallet for user test curl https://x402.goplausible.xyz/examples/weather -x http://test:1234@proxy.pay402me.com:8089 -v -k # Solana mainnet wallet for user test1 curl https://pro-api.coingecko.com/api/v3/x402/onchain/simple/networks/eth/token_price/0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 -x http://test1:1234@proxy.pay402me.com:8089 -v -k

Check transactions

  1. Open the dashboard at https://demo.pay402me.com.
  2. Go to Wallets and make sure an Algorand wallet is configured.
  3. Go to Transactions after making a proxied request.
  4. Use the filters to check transactions by user, wallet, or resource base URL.