NanoTrans Agent Paywall

Gasless is the default path, but it depends on three things:

• Buyers sign a USDC payment authorization (EIP-3009) and the Facilitator submits it on-chain and pays the gas — this requires the Facilitator Proxy connection to be enabled (Settings > NanoTrans). Without it, or if the wallet cannot sign typed data, buyers are offered the classic wallet transfer, which needs a little ETH for gas — the plugin never switches to that path silently; the buyer must explicitly choose it.
• Sellers receive their share without holding ETH when Automatic Payout Distribution is enabled (Settings > NanoTrans; off by default) on Base mainnet with the Facilitator Proxy connection — the Facilitator service pays the gas to distribute Splitter funds. On Base Sepolia, or with a custom NANOTRANS_RELEASE_KEY, the site's own key signs the payout and needs ETH. If no Splitter is configured, payments go straight to the seller wallet and no payout step is needed at all.
• Agents (x402 API) always pay by signature; the Facilitator pays the gas.

x402 is an open protocol that enables machine-to-machine payments over HTTP. When content requires payment, the server responds with HTTP 402 (Payment Required) along with payment details. The client automatically signs and submits payment, then receives the content.

NanoTrans uses the Base Network (Ethereum L2) for USDC stablecoin payments. Base offers low gas fees (~$0.01) and fast confirmation times (~2 seconds).

NanoTrans operates independently of WooCommerce. It uses its own payment flow (x402 protocol) and does not conflict with WooCommerce product pricing.

• EIP-712 typed data signatures for payment authorization
• x402 Facilitator verifies signatures on-chain before settlement
• Replay attack prevention via unique transaction hashes
• Rate limiting and anomaly detection
• All payment attempts logged for audit

Any AI agent that supports the x402 payment protocol. The plugin exposes a standard HTTP 402 flow plus a machine-readable discovery endpoint (/.well-known/x402), so any x402-capable agent or SDK can discover and purchase content.

Use the Base Sepolia testnet. Set the network to "base-sepolia" in plugin settings and use testnet USDC from a faucet.

No. The plugin automatically registers with the Facilitator Proxy on activation and receives an API key. No wp-config.php editing or CDP keys required. The Cloudflare Worker proxy handles all CDP JWT signing on your behalf.

No. The plugin does not require or store any private keys. Payment verification is handled by the Facilitator proxy (Cloudflare Worker). Only your public wallet address is needed.

No. NanoTrans Agent Paywall currently supports single-site WordPress installations only. On multisite, settings and transaction records would be shared across all sites, which is not suitable for separate content publishers. Multisite support is planned for a future release.

Yes. NanoTrans sends Cache-Control: no-store and X-NanoTrans: payment-gateway headers on all payment-required (HTTP 402) responses, so caching plugins like WP Super Cache and W3 Total Cache should automatically exclude them. If you experience issues, add a cache exclusion rule for URLs containing /nanotrans/v1/.

NanoTrans includes a circuit breaker that detects Facilitator outages. After 3 consecutive failures, payments are temporarily paused for 5 minutes to prevent cascading timeouts. An admin notice will appear on the NanoTrans dashboard. The system automatically retries when the cooldown expires. If a settlement response is lost after the transfer may already have been broadcast, the payment is marked "uncertain" and reconciled from chain state (USDC authorization state + transfer receipt) — buyers are never asked to sign again while that is unresolved, and "Already paid? Restore access" re-checks it on demand.

By default the plugin only trusts REMOTE_ADDR (forwarded headers are spoofable). Behind a proxy or CDN every visitor then shares one per-IP bucket. Register your proxy addresses in wp-config.php — define( 'NANOTRANS_TRUSTED_PROXIES', '10.0.0.0/8, 173.245.48.0/20' ); (comma-separated IPs/CIDRs; the nanotrans_trusted_proxies filter also works) — and the plugin will read the real client IP from X-Forwarded-For (right-most hop that is not a trusted proxy) only when the request actually arrives from one of those proxies. Make sure the proxy appends the client address to X-Forwarded-For (nginx: proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;); Cloudflare does so by default.