Request
A person, script, or agent asks for the resource.
APIs, articles, actions, downloads, creative assets, and current data can each have a direct machine-readable payment path—without turning the whole business into a subscription.
Start with the thing a buyer can understand, request, and receive as one useful unit.
APIs01
Workflows02
Live data03
Files04
Content05
Media06Access402 sits between the protected resource and the payment infrastructure. Your application decides what is valuable; Access402 helps enforce the payment rule and records the result.
A person, script, or agent asks for the resource.
The server returns exact machine-readable payment terms.
The client authorizes payment and retries the request.
The verified request receives the original response.
Protect exact methods, routes, pages, or files.
Keep facilitator credentials and policy checks server-side.
Test on Base Sepolia, then enable supported Live payments.
See payment outcomes and enforce managed usage controls.
Any bounded digital resource that can be delivered through a protected HTTP request may be a candidate: API results, content, workflow actions, files, media, and current data.
No. The website or API owner uses Access402. Buyers use a compatible x402 client and wallet to respond to the payment challenge.
Yes. You choose the exact routes, posts, pages, or files to protect. Public marketing, previews, documentation, and free product surfaces can remain open.
Access402 manages the hosted payment path, authoritative policy checks, facilitator communication, idempotency controls, usage enforcement, and activity records around supported integrations.