A dated milestone for programmable payments

X Pay said on October 18 that it had crossed 50,000 transactions on x402. The company announced the milestone through its public channel, alongside a community giveaway. The figure provides a snapshot of activity reported by the project; it should not be read as 50,000 customers or as proof that every transaction was initiated by an autonomous AI agent.

Base and BNB support are now documented

X Pay's facilitator pages list payment verification and settlement on both Base and BNB Smart Chain. Base uses Circle USDC and EIP-3009 authorization, while the BNB implementation uses Binance-Peg USDC and Permit2. The assets have different contracts, decimal precision and authorization requirements. Supporting both networks broadens the integration options, but a merchant cannot safely treat their payment parameters as interchangeable.

Related reporting: X Pay Reports $1 Million Raise for AI Payment Infrastructure

What happens when software pays

Under x402, a service can respond to an unpaid request with HTTP 402 and machine-readable payment terms. A client authorizes the payment and retries. A facilitator helps verify that authorization and submit settlement, after which the service can return its paid resource. This can support per-request purchases by software. It does not establish who controlled a wallet, whether a request was useful, or whether the activity was recurring commercial demand.

The checks developers still need

X Pay says capability discovery is public, while verification and settlement require a facilitator API key. It also distinguishes an API being reachable from settlement being ready: the facilitator needs native network funds to submit transactions. Its documentation identifies the published network URLs as mainnet services and distinguishes them from dashboard test mode. An integration should inspect the correct network's requirements and confirm successful settlement before delivering a paid resource.

How to interpret the growth claim

The 50,000 figure is attributed to the company's announcement rather than an independent transaction-by-transaction audit by The Token Press. X Pay links public ecosystem explorers, but a headline count alone cannot show distinct paying users, repeat merchants, revenue or payment failures. Those measures would help establish the scale and quality of adoption as the service develops. The practical development for builders is the documented availability of a second network; the commercial significance of the milestone still depends on the activity behind it.

Sources

Prepared with AI assistance and source verification. Product descriptions and reported milestones are attributed to their sources.