Skip to main content
Every Sumvin identity ships with a persistent x402-addressable acceptance surface. Rather than minting a one-shot link per request, the identity itself resolves to an x402 endpoint that any x402-capable client can settle against — discoverable by , authorised by , and anchored to the same verified identity claims any other point in the platform exposes. Global acceptance and payment request links are the two sides of the same primitive: one ad-hoc and scoped to a single request, the other persistent and tied to the identity for as long as it exists.

What it enables

  • Pay-to-identity as a first-class primitive. Any SRI is a valid payment target, resolvable by any x402 client, without provisioning a bespoke link per transaction.
  • Inline payments on the open web. A page, feed, or agent surface can embed an identity-keyed payment target and let x402 clients settle directly against it.
  • Agent-to-agent settlement. One agent can pay another by referencing its owner’s SRI — no prior handshake, no shared platform, no custom protocol.
  • Receipts tied to identity, not rails. Every settlement produces the same PINT-backed receipt the rest of the platform already understands.
Payment request linkGlobal x402 acceptance
ScopeOne request, fixed termsPersistent, identity-level
TriggerIssued per paymentAlways available
DiscoveryShared URLResolved from SRI
TermsBaked into the linkEvaluated per payment against the identity’s policy
Best forInvoice-like one-shotsOpen-ended, discoverable receive
The two surfaces share the underlying rail — PINT-challenged x402 — and the same identity guarantees. Most partners will expose both: request links for structured, bill-like collection, and global acceptance for open-ended, agent-driven receive.

Who it’s for

  • Partners building identity-first payment surfaces who want “pay this user” to be a resolvable primitive, not a form.
  • Agent platforms that need a stable, resolvable payment target per user without a per-transaction provisioning step.
  • Apps exposing Sumvin identities in feeds, profiles, or messaging surfaces where payment should be one resolve away.
Global x402 acceptance is in early access. Partners wiring in now help define how SRI-based resolution, policy evaluation, and identity-keyed receipts land in the final shape — contact your account manager to co-design your integration.

Where to start

Most partners start with payment request links — the ad-hoc counterpart to persistent acceptance — and layer global acceptance over the top once the one-shot shape is live. The payment links and x402 rail covers the mechanics both surfaces ride on, and the SRI reference explains how identities resolve to payable endpoints. Agentic commerce is where global acceptance earns its keep — agents pay agents by resolving each other’s SRIs, with no prior handshake.