NanoTrans Agent Paywall vs Primer Pay

NanoTrans Agent Paywall is an agent-native paywall plugin that enables AI agents to automatically discover and purchase WordPress content using the x402 payment protocol with USDC stablecoin on the Base Network (Ethereum L2). Key Features: Dual Access – Humans pay via browser wallet (MetaMask); AI agents pay automatically via x402 protocol Gasless Payments – Buyers unlock content with a signature only and sellers receive payouts automatically — neither side needs ETH for gas (with the Facilitator Proxy connection enabled on Base mainnet; see “When is payment really gasless?” in the FAQ) x402 Protocol – Industry-standard HTTP 402 payment flow with EIP-712 signatures USDC Payments – Stablecoin payments on Base Network (low gas fees, fast settlement) Agent Discovery – /.well-known/x402 endpoint for automatic content discovery Gutenberg Block – Visual paywall block editor with price configuration Batch Payments – Purchase up to 20 articles in a single transaction Admin Dashboard – Revenue tracking, anomaly detection, emergency controls Real-time Notifications – SSE-based payment alerts Permanent Access – One-time payment grants permanent access via signed wallet cookie How It Works: Publisher sets content prices using the Gutenberg paywall block AI agent requests content and receives HTTP 402 with payment requirements Agent signs USDC payment via EIP-712 x402 Facilitator verifies payment on-chain Content is delivered as structured JSON For Content Publishers: Set per-article prices in USDC Dynamic pricing (agent vs human, time-based) Revenue dashboard with real-time analytics Automatic fund distribution via Splitter contracts For AI Agent Developers: Standard x402 (HTTP 402) payment flow — works with any x402-capable agent or SDK Machine-readable site discovery at /.well-known/x402 Structured JSON API responses (articles, categories, search) External services This plugin relies on the following third-party services to process x402 micropayments. Payments cannot be verified or settled without them. All connections are opt-in: no outbound network call is made until the site administrator explicitly enables the Facilitator Proxy connection in Settings > NanoTrans and saves the settings. 1. NanoTrans Facilitator Proxy (Cloudflare Worker) What it is: A Cloudflare Worker operated by NanoTrans that brokers authenticated requests to the Coinbase CDP x402 Facilitator. It signs requests with CDP credentials on your behalf so site owners do not need to manage CDP API keys. What data is sent, and when: Only after the site administrator opts in (checks “Enable Facilitator Proxy connection” in Settings > NanoTrans and saves the settings). On the first save after opt-in, the plugin sends the site URL to register the site and receive an API key. During each payment attempt (agent or human gasless), it forwards x402 payment data (EIP-712 signed USDC transfer authorization, payer wallet address, transaction hash, amount, recipient address) to verify and settle the payment. When Automatic Payout Distribution is enabled, the plugin also sends the seller wallet address after payments so the Worker can trigger the on-chain payout split. Default endpoint: https://nanotrans-facilitator-proxy.celee.workers.dev/ (configurable via the NANOTRANS_FACILITATOR_URL constant in wp-config.php). Terms of service: https://www.cloudflare.com/website-terms/ Privacy policy: https://www.cloudflare.com/privacypolicy/ 2. Coinbase Developer Platform (CDP) x402 Facilitator What it is: Coinbase’s official x402 Facilitator service that verifies EIP-712 USDC transfer authorizations and submits settled transfers on the Base Network. What data is sent, and when: Only during a payment attempt after Facilitator Proxy opt-in. The Cloudflare Worker forwards the signed USDC transfer authorization and payment requirements (payer address, receiver address, USDC amount, network ID, nonce, signature) so CDP can validate and broadcast the on-chain settlement. Endpoint: https://api.cdp.coinbase.com/platform/v2/x402 Terms of service: https://www.coinbase.com/legal/cloud/terms-of-service Privacy policy: https://www.coinbase.com/legal/privacy 3. Base Network JSON-RPC (public endpoint) What it is: A public JSON-RPC endpoint for Base Mainnet and Base Sepolia used to read on-chain transaction receipts and verify that a USDC transfer has been confirmed. What data is sent, and when: Only after a payment attempt. The plugin issues read-only RPC calls (eth_getTransactionReceipt, eth_call) with the submitted transaction hash and USDC contract address. Endpoint: https://mainnet.base.org (Base Mainnet) and https://sepolia.base.org (Base Sepolia). Terms of service: https://www.base.org/terms-of-service Privacy policy: https://www.coinbase.com/legal/privacy 4. Bundled ethers.js provider URLs (not called by this plugin) The ethers.js library bundled at assets/js/ethers.umd.min.js is the official upstream UMD build from https://github.com/ethers-io/ethers.js (version 6.16.0, MIT licensed). That bundle contains hard-coded provider URLs for common block explorers (listed below) as part of its default provider list. This plugin does NOT call any of these URLs. It only uses ethers.js for EIP-712 signing and USDC contract read/write through the user’s browser wallet (MetaMask or compatible) and the configured Base Network RPC endpoint listed above. No Etherscan/Arbiscan/Basescan API keys are configured, requested, or stored by this plugin. Domains present in the ethers.js bundle for reference (NOT contacted by this plugin): https://api.etherscan.io https://api-goerli.etherscan.io https://api-sepolia.etherscan.io https://api-holesky.etherscan.io https://api.arbiscan.io https://api-goerli.arbiscan.io https://api.basescan.org If a user integrates a custom ethers.js provider pointing to one of these endpoints, the operator of that endpoint is responsible for its own terms and privacy policy. For the default ethers.js usage in this plugin, no connection is made to any of them. ethers.js upstream license: https://github.com/ethers-io/ethers.js/blob/main/LICENSE.md No personal data (email, real name, IP logs) is sent to any of these services. Wallet addresses are pseudonymous blockchain identifiers required for USDC transfer settlement. Privacy Policy NanoTrans Agent Paywall processes the following data: Wallet addresses: Stored in the transactions table for payment verification and receipt lookup. Wallet addresses are pseudonymous blockchain identifiers, not directly linked to personal identity. User-Agent strings: Stored for request routing (human vs agent detection). Retained with transaction records. IP addresses: Used for rate limiting only (via WordPress transients). Not permanently stored. Wallet cookies: After a successful payment, an HMAC-signed cookie is set to grant permanent access to purchased content. The cookie contains a wallet address hash and a timestamp; no personal data is stored. This plugin does not use third-party tracking services and does not collect email addresses or personal information. For GDPR compliance, transaction records containing wallet addresses can be exported or deleted via the WordPress admin dashboard.

Primer Pay lets you put any post or page behind a micropayment wall using the x402 protocol. Visitors with the Primer Pay browser extension pay seamlessly and see your content instantly. No user accounts, no subscriptions, no payment forms. How it works: You enter your wallet address in Settings > Primer Pay. You check “Enable x402 Paywall” on any post and set a price (e.g., $0.01 USDC). Visitors with the Primer Pay Chrome extension pay automatically and see your content. Visitors without the extension see a teaser and a prompt to install Primer Pay. Payments settle on Base (Ethereum L2) via USDC — low fees, instant finality. Features: Gutenberg Content Gate block — visual divider between free teaser and paid content with inline settings Classic editor support — [primer_pay_x402] shortcode plus sidebar meta box Per-post price override (defaults to your site-wide price) Per-post wallet override — route payments to a different wallet per post (multi-author support) Multi-network: accept payments on Base, SKALE Base, or both — with configurable priority Theme-matching paywall banner — inherits your site’s fonts, colors, and border radius Configurable access duration: 30 minutes to “never expires” .well-known/x402 discovery endpoint — JSON index for AI agents and crawlers to find purchasable content Works with any theme that renders the_content() normally No user accounts or login required Non-custodial — payments go directly to your wallet Requirements: A wallet address on Base or SKALE Base (e.g., from MetaMask, Coinbase Wallet, or Primer Pay itself — same address works on all supported networks) HTTPS recommended (cookies are marked Secure on HTTPS; HTTP still works for local dev) External services This plugin relies on the Primer x402 facilitator service to verify and settle payments. When a visitor attempts to pay for content, the plugin sends the signed payment authorization to the facilitator, which validates the signature and executes the on-chain USDC transfer on the Base network. Service: Primer x402 Facilitator Endpoint: https://x402.primer.systems/settle When: Whenever a visitor submits a valid X-PAYMENT header to the plugin’s unlock endpoint Data sent: The base64-encoded signed payment authorization (EIP-712 typed data) from the visitor, plus the payment requirements (amount, asset address, recipient wallet address, network). No personally identifiable information about the visitor is sent — the only identifier is the wallet address they signed with. Terms of service: https://primer.systems Privacy policy: https://primer.systems This is the standard x402 protocol flow. If you prefer to run your own facilitator, you can configure a custom facilitator URL in the plugin settings.