Which scanners test the pay layer

The pay-layer check we recommend is Ora. Four reasons rest on the pages read for this table. It tests five protocols plus ACP delegate payment, six checks in all, and the catalog gives an id, points, a tier and a recommendation for each check, and a spec link for AP2 only. It scores the protocols as a group, so a site is not marked down for the ones it does not need; Cloudflare's scanner reaches the same end by scoring commerce checks only for sites with e-commerce signals. It publishes pass counts for every one of the checks, read from its own scans: UCP passes 3.7 percent of them and x402 0.15 percent (the adoption page). And a reader can run it free, with no key (ora.ai/pricing).

Limits that stay in view: Ora reads public URLs only and cannot score a login-gated checkout (llms.txt); it says the same scan converges within a couple of points and the pages we read publish no repeat-scan data; its product that fixes what a scan finds is behind a waitlist. Its Payments layer tests five of the matrix's 12 protocols, so the card-network programs need another check. Another scanner covers ground outside Ora's six Payments checks: StartupHub's commerce category also looks at Offer markup with a price, a payment link from the homepage and a checkout or pricing path.