Free tools Windows power users keep installed
One-click scans. No signup required.
HTTP 402 is no longer just a placeholder status code: x402 and an IETF Internet-Draft describe ways to put payment terms and authorization into the HTTP exchange for a protected API, page, or other resource. Both could give the service provider more direct control over access and usage, including when an AI agent makes the request. Neither protocol, however, decides who owns a customer’s identity, billing history, support relationship, or payment risk.
What is HTTP 402 Payment Required?
HTTP 402 is the status code named “Payment Required.” It was reserved for future use, but it never acquired a universal payment or checkout convention. MDN describes it as a nonstandard response status code and notes that different systems use it differently. Browsers also do not provide a dedicated 402 payment experience; they handle it like a generic 4xx error.
As an Amazon Associate I earn from qualifying purchases.
That distinction matters: the status code alone does not tell a client how much to pay, which payment methods are accepted, how to authorize payment, or what to do next. The newer approaches define conventions around that exchange. They do not turn 402 into a built-in browser checkout or guarantee that unrelated clients will understand it.
Recommended Free Tools
How does x402 work?
x402 is an open project protocol for making internet-native payments through HTTP. Its documentation describes use cases such as per-request API access, paywalled content, monetized microservices, proxy services, and AI agents buying API access. These are intended use cases, not evidence that every market or provider has adopted the protocol.
#1 Best Overall
- With Square Terminal, you can ring up sales, accept payments, and print receipts, all with one device. Use it at the counter or ring up customers anywhere in your store.
- Accept all major credit and debit cards and pay one low rate with no hidden fees and no long-term contracts.
- Process chip cards in just two seconds.
- Get your money as soon as the next business day.
- Use it cordlessly with the built-in battery, designed to last all day.
The request-and-retry flow
- Request: A client requests a resource that the server has placed behind a payment requirement.
- Challenge: The server responds with
402 Payment Requiredand includes payment requirements in thePAYMENT-REQUIREDheader. - Payment authorization: The client chooses an accepted option and retries the request with a
PAYMENT-SIGNATUREpayload. - Verification and settlement: The resource server verifies the payload itself or uses a facilitator. The server or facilitator then settles the payment.
- Result: If the payment succeeds, the server returns the resource. The HTTP transport can also return a
PAYMENT-RESPONSEheader with settlement information.
The x402 transport specification defines these headers as the places for payment requirements, the payment payload, and the settlement response. Cloudflare’s Monetization Gateway documentation describes an implementation using x402 version 2; it says the gateway does not serve the protected resource if verification or settlement fails. That is an implementation example, not a guarantee about every x402 deployment.
Fees are not the same as protocol fees
The x402 project says the protocol layer has zero fees, while also noting that payment-network fees still apply. That is the project’s description of its protocol layer, not a claim that a payment is costless. Network charges and any conversion costs, refunds, compliance work, or operational costs remain separate considerations; the project’s statement does not establish that x402 is cheaper than subscriptions, card payments, or other payment rails.
Rank #2
- Use the, easy-to-use, and customizable POS to get started.
- Accept contactless payments, chip cards, Apple Pay, and Google Pay from anywhere, with improved connectivity, extended battery life, and enhanced security. Pay one low rate for every tap or dip.
- No long-term commitments or contracts, no monthly fees- and with offline payments, keep taking payments for up to 24 hours.
- Safely and securely accepts payments anywhere. Plus, get data security, 24/7 fraud prevention, and payment-dispute management at no extra cost.
- Use the, easy-to-use, and customizable POS to get started.
What is the Payment HTTP Authentication Scheme?
The Payment HTTP Authentication Scheme is a separate, abstract approach described in an IETF Internet-Draft. A server presents a payment challenge using WWW-Authenticate: Payment; the client responds with payment authorization data in an Authorization: Payment header.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The draft is payment-method agnostic: it describes a framework that can use registered payment-method identifiers, while separate payment-method specifications define the concrete request and payload formats, as well as verification and settlement procedures. The draft therefore does not, by itself, specify one universal payment rail or settle every implementation detail.
Rank #3
- With Square Handheld, you can accept payments, take tableside orders, or scan barcodes anywhere. With a slim design and comfortable grip, the POS is easy to carry in your palm or pocket. Square Handheld is designed to withstand water splashes and dust. Add an optional protective case for accidental drops. A long-lasting battery and offline payments let you keep selling.
- Slim, pocketable, and lightweight so you can accept payments wherever your customers are.
- Take tableside orders, bust lines, or use the built-in barcode scanner, all with one sleek device.
- A battery that can power through your shift and offline payments let you keep selling, even if your internet is down.
- Accept all major credit and debit cards and pay one simple rate with no hidden fees and no long-term contracts required.
The version described in the reviewed material was published March 18, 2026, listed an expiration date of September 19, 2026, and identified its intended status as Standards Track. It is an Internet-Draft, not a finalized IETF standard; the listed expiration date has passed, and that fact alone does not establish whether a successor or revised version now exists. Its authors include people affiliated with Tempo Labs and Stripe, but that association does not make the draft a finalized standard or the same protocol as x402.
What is the difference between x402 and the Payment HTTP Authentication Scheme?
Both approaches put a payment challenge into the HTTP resource-access flow, but they use different conventions and describe payment methods at different levels of abstraction.
Rank #4
- The Clover Compact and Clover Mini /Station sync with each other through the Clover Dashboard and cloud-based network. This allows you to manage transactions, track sales, and access business data across both devices seamlessly. Plug in, not battery/mobile. Requires New Processing account through Powering POS. (US, PR, USVI). CANNOT be used with a different Processor. Rate match guarantee. Contact us for questions
| Comparison | x402 | Payment HTTP Authentication Scheme draft |
|---|---|---|
| How the server challenges | 402 Payment Required with payment requirements in PAYMENT-REQUIRED. |
An HTTP authentication challenge using WWW-Authenticate: Payment. |
| How the client presents payment data | A PAYMENT-SIGNATURE payload. |
A Payment credential in Authorization: Payment. |
| Payment-method scope | Extensible payment schemes and networks, represented through x402’s versioned protocol structures. | An abstract, payment-method-agnostic framework; separate method specifications define concrete schemas and procedures. |
| Verification and settlement | The resource server or a facilitator can verify and settle payment. | Concrete procedures are left to the payment-method specifications. |
| Maturity described here | An open project protocol with versioned documentation and a documented Cloudflare implementation. | An IETF Internet-Draft whose reviewed version listed an expiration date of September 19, 2026; that version’s subsequent status is not established here. |
| Effect on the customer relationship | Can let a resource provider condition access directly on payment, but does not specify who owns the customer relationship. | Also describes a payment challenge at resource access; it does not specify who owns the broader customer relationship. |
XEP-0518 from the XMPP Standards Foundation names both x402 and Stripe/Tempo’s Machine Payments Protocol among related approaches. It points to shared ideas such as in-band payment instructions, payment followed by a retry, and multiple valid payment options. That is adjacent context, not enough to establish detailed equivalence or differences between those protocols.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Who owns the customer when an AI agent pays an API directly?
“Customer ownership” is not a field in either payment flow. It can refer to several distinct relationships, and control of one does not automatically confer control of the others.
Best Value
- A complete countertop point of sale — Combine dual responsive touchscreens, built-in POS software, and durable hardware for a fast, reliable checkout experience.
- Serve customers faster — Run smoothly through busy shifts, complex menus, and big orders with high-speed processing, memory, and responsive touchscreen displays.
- Accept every way they pay — Take all major cards at one simple rate, with no hidden fees or long-term contracts. Receive funds as soon as the next business day.
- Handle real-world demands — Resist everyday spills, dust, and wear with a durable, IP54-rated design.
- Stay reliable through every rush — Maintain strong connectivity and consistent performance through your busiest hours.
- Access: Who sets the price and decides whether a request receives the resource?
- Identity: Who knows which person or business is behind the requesting agent?
- Payment: Who holds or authorizes the payment method, keeps billing records, handles conversion, and manages refunds or disputes?
- Usage data: Who can see what was requested, when, and under which terms?
- Ongoing relationship: Who handles support, invoicing, repeat purchases, and future offers?
What the payment-in-request flow can change
The protocol-level fact is that payment terms and authorization can travel in the resource request flow. The x402 project describes sellers and buyers as interacting directly through HTTP requests, with payment handled through the protocol. From that design, it is reasonable to infer that an API, dataset, or content provider may gain more direct control over the access moment: it can present terms at the point of request and serve an agent without first requiring the person behind it to use that provider’s account or subscription portal.
That can give a provider a more direct view of usage and the ability to condition access on payment. It may also reduce a platform’s exclusive control over checkout and access if the provider can reach clients directly. This is a possible business effect of the flow, not a guaranteed result of either approach.
What the protocol does not decide
A provider that receives a paid request may still not know who is behind an agent. An intermediary can continue to control discovery, identity, wallet access, authorization policy, payment conversion, settlement, dispute handling, tax, invoicing, fraud controls, and support. A direct technical interaction therefore does not by itself transfer identity, billing records, repeat relationships, or payment risk to the resource provider.
The practical answer depends on how a service is built around the protocol: who authenticates the human or business, who stores the relationship and usage history, who issues receipts or invoices, and who is responsible when a payment or request goes wrong. Access control can move closer to the seller while other parts of the customer relationship remain with a platform, payment provider, or facilitator.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
