Founders, operators, and developers who need a precise statement of commercial readiness.
Current payment rail status: what is live now vs planned
The service already models multiple rails, but modeled is not the same as live. The current public paid path is Solana USDC via MPP over ACP jobs.
Key facts
- Current live public rail: Solana mainnet USDC via MPP over ACP jobs.
- Supported or modeled rails are not automatically public, buyer-safe rails.
- A truthful storefront should separate live-now, quote-only, and future rails.
Modeled rails versus public rails
A service can contain route handlers, pricing logic, and readiness structures for multiple rails without those rails being public, hardened, or commercially safe to market. That distinction is central to honest launch language.
The storefront should therefore distinguish between live-now purchase paths, broader quote paths, and future rails that are still planned.
What is live right now
The current public paid path is the Solana USDC Micropayment Protocol flow exposed through ACP jobs. That is the route a truthful buyer-facing UI should elevate.
What should still be labeled as planned or manual
Other combinations, including x402 and additional chain targets, should remain clearly labeled as planned until production proof and public readiness are both present.
Likewise, larger catalog or whole-channel scopes may still end in quote-only or manual-review states even if the buyer can browse the storefront publicly.
FAQ
Does supported mean shipped?
No. Supported can mean code paths and readiness structures exist. Shipped means public, verified, buyer-safe, and backed by production proof.
Why is this distinction important for SEO and product copy?
Because the public content should match the real product state. Accurate copy improves trust, reduces bounce from misleading claims, and avoids teaching search engines or LLMs the wrong contract.
Can the storefront still be useful if only one rail is live?
Yes. A truthful storefront can still convert by clearly elevating the live path, exposing quote-first workflows, and documenting which rails are planned.
Next steps
Related guides
Developer integration guide for transcript packs and paid delivery
A concise guide to the public service routes, ACP job flow, manifests, exports, and readiness checks.
How to buy transcript packs from the channel knowledge service
A factual guide to instant-buy offers, quote-only scopes, manual review, checkout, and transcript pack delivery.
Whole-channel pricing, queueing, and manual review
What whole-channel requests mean, when queue pressure matters, and why large channels can move into manual review.