Access402 is a managed x402 payment and access platform for websites and APIs. It provides the payment challenge, hosted verification and settlement, project receiving wallet, usage enforcement, activity records, and adapter configuration.

What Access402 manages

x402 version 2 payment challenges.
USDC verification and settlement through the hosted facilitator.
A Coinbase project wallet used as the authoritative payTo destination.
Installation-scoped credentials, server-side rules, idempotency, and transaction limits.
Sandbox payments on Base Sepolia and live payments on Base.
Optional publication of eligible resources to CDP Bazaar discovery.

Access402 does not replace your application, authentication system, content platform, or hosting provider. It connects to them through an adapter.

Choose an adapter

Choose the adapter that matches where your resources already live. Your adapter identifies available resources, enforces the payment challenge at request time, and communicates with Access402 using an installation-scoped key.

An adapter may be installed into an existing application, configured through code, or managed through a platform integration. Regardless of implementation, it uses the same Access402 project, policy, settlement, usage, and discovery model.

If you use Codex, Claude Code, or Cursor, start with the Coding agents documentation. The public Access402 skill gives each agent the same integration and security workflow, while the CLI handles browser authorization, installation reuse, diagnostics, and tests. WordPress and FastAPI remain native adapters; other HTTP applications can use the Universal HTTP Gateway on Node or Cloudflare Workers.

Shared payment model

Your adapter authenticates one installation to one Access402 project. A request either proceeds under an explicit bypass or valid grant, or receives an HTTP 402 challenge. After a valid paid retry, Access402 settles the payment, records usage, and tells your adapter to return the original resource.