Wallets & payments
Control wallet authority, connect payment workflows, and evaluate funding routes.
HYBRID DEVNET · PUBLIC EVIDENCE LIVEVerifiable infrastructure for value, markets, identity, and operational dataInspect the network ↗
Own. Operate. Prove.
Infrastructure for digital assets, payments, and trusted data.
Connect wallets, payments, digital assets, and protected data through shared identity, policy, and verifiable records. Start with one workflow. Expand as you need.
For business and developer teamsAvailability is specific to each product and network
Your product. Connected infrastructure.One platform.
A practical place to start.
A practical place to start.
Identity · policy · verifiable recordsShared foundations, with distinct controls for each operation.
Start with your outcome
See how the pieces fit.
Choose a workflow to see the relevant products and their responsibilities. You don’t need the entire platform to begin.
From checkout to a reconciled outcome.
Connect the payment request, enabled provider, delivery decision, and back-office acknowledgement. Native funding routes have separate activation requirements.
- 01Payments & Commerce ↗
Create the payment request
- 02Transfer Compliance ↗
Apply relevant counterparty rules
- 03Automation ↗
Notify and reconcile
Shared foundationsIdentity & permissionsPolicy & authorizationVerifiable records
A payment record your operations team can follow.
Explore this workflow ↗Keep ownership connected to its history.
Define an asset, establish its supply and ownership rules, and connect a listing to the supported payment and delivery workflow.
- 01Digital Assets ↗
Define the asset and collection
- 02Payments & Commerce ↗
Connect payment to delivery
- 03Trust Center ↗
Attach relevant credentials
Shared foundationsIdentity & permissionsPolicy & authorizationVerifiable records
An asset with traceable issuance and ownership records.
Explore this workflow ↗Keep the record private. Make integrity checkable.
Protect sensitive files, govern who may access them, and connect operational events to retained evidence without publishing the underlying content.
- 01Data Vault ↗
Protect the record
- 02Evidence Streams ↗
Connect events and commitments
- 03Automation ↗
Respond to policy-bound events
Shared foundationsIdentity & permissionsPolicy & authorizationVerifiable records
Protected records with an inspectable integrity and access history.
Explore this workflow ↗Let the agent propose. Keep authority explicit.
Start with a decision-only pilot: inspect a policy and evaluate a proposed intent. The current public milestone does not approve, sign, or broadcast payments.
- 01AI Wallet Control ↗
Evaluate the proposed intent
- 02Trust Center ↗
Understand identity and claims
- 03Native MPC Wallets ↗
Review the execution boundary
Shared foundationsIdentity & permissionsPolicy & authorizationVerifiable records
A policy decision, not an automatic transfer of funds.
Explore this workflow ↗Illustrative product relationships. Required controls and available operations depend on the workflow, network, and deployment.
The product families
Find the capability you need.
Explore a focused product, understand its operating boundaries, and connect adjacent capabilities when your workflow needs them.
Markets & digital assets
Connect market observations, product lifecycles, and digital ownership.
Identity & trust
Portable identity, governed transfers, and public-safe proof.
Data & automation
Verifiable ingestion, protected storage, and event-driven operations.
From components to a working flow
Build around the whole operation.
Go beyond a feature list. Understand what enters a workflow, which controls apply, and what your team can inspect at the end.
Payments & commerce
A payment is more than a checkout.
Keep the request, provider response, delivery decision, and reconciliation together. Start with an enabled payment route.
See the workflow ↗
Digital assets
Ownership should come with a history.
Connect collection, issuance, listing, and delivery so an asset stays attached to its provenance.
See the workflow ↗
Data Vault
Private records. Checkable integrity.
Protect business files and connect them to access policies and integrity records without publishing their contents.
See the workflow ↗Trust has to be specificUnderstand the controls.
Understand the controls.
Know the boundaries.
Architecture, a successful API read, and a completed transaction are different things. Evaluate the exact operation you intend to use.
Review product availability ↗- Authority stays explicit
Review who can request, approve, and perform an action. A connected application does not automatically receive signing authority.
- Private information stays behind its boundary
Separate protected records from the commitments and receipts that can be independently inspected.
- Availability comes before commitment
Confirm the environment, enabled operations, and access requirements. Preview and gated workflows are identified on their product pages.
Start with one useful pilot.
Define the outcome, the people involved, and the evidence you need. Match those requirements to a bounded set of products.
Discuss your use case ↗A clearer path to integration.
Choose your domain, check access and scopes, then follow current API contracts and implementation guidance.
Open the developer portal ↗One workflow is a good beginning