Wallet review
Understand connections, scopes, facts, context, risk presentation, rejection, approval, and local signing.
Evaluate the control model before live availability.
This program introduces the wallet experience, public contracts, integration paths, and selected pilot workflows while production release evidence remains gated.
Program status
Preview and pilot.
This is not a general-availability or live-merchant launch.
Product and safety educationPublic information for people, businesses, and developers.
Published developer contractsOpenAPI, JSON Schema, Quickstart, protocol, and MCP guidance.
Selected evaluation and pilot accessStart with sandbox, test data, and explicit capability labels.
General live onboardingNot open. Production support remains subject to release, legal, security, and operational gates.
What to evaluate
Focus on behavior and boundaries.
The Preview is most useful when participants test how a request moves across systems and how the user remains in control.
Integration contracts
Validate pairing, Payment Request creation, exact amount handling, expiry, idempotency, status, and events.
Operational clarity
Identify failures, unsupported capabilities, user support needs, and evidence required before a live decision.
What not to assume
Preview access is deliberately narrow.
Examples demonstrate contracts and behavior. They do not expand the supported product surface.
No blanket network or asset support
Only use combinations explicitly enabled and labeled in the exact wallet build being evaluated.
No production compliance conclusion
A non-custodial design is a product boundary, not a substitute for jurisdiction-specific legal review.
No recovery by the server
Loss of recovery material can mean loss of access. Cloud recovery is outside the current v1 boundary.
No merchant or agent signing authority
Pairing and connection tokens do not grant access to private keys or permission to sign for the user.
Choose a Preview path
Different participants, one control model.
Learn the wallet experience.
Understand how requests are reviewed, approved, signed, and revoked before using any enabled test path.
Personal Preview →Propose a selected pilot.
Describe your use case and integration method without sending secrets or production user data.
Request a pilot →Inspect the contracts.
Review the Quickstart, Platform API, protocol schemas, and MCP connector on the developer subdomain.
Open developer docs →Preview carefully. Expand only with evidence.
Start with the smallest safe test that proves your intended request and approval flow.