Layer 3 — Issuance and distribution
Turn the platform into products you can issue
The layer that takes an asset from idea to issued, distributed, and settled — with the compliance rules traveling inside the token.
Every issued asset needs four things: an issuer, a register, custody, and a venue. Layer 3 provides the technology for all four, for any asset class, on the ledger and operating system beneath it. You bring the issuer authorization; the platform brings the workflow.
3.1 — Tokenization-as-a-service
Compliance compiled into the token itself
Standard templates (ERC-3643 and ERC-1400 for securities, ERC-20 for payment and utility tokens) carry the regulatory rules inside the smart contract. A token checks its own transfer restrictions and investor requirements at the moment of transfer. A classification framework sorts each token by the rules of the jurisdictions where it will be offered and defaults to the stricter treatment where those rules are unclear; the legal classification itself remains the issuer's decision. Reusable compliance modules and API-driven issuance shorten the path from decision to issued token.
What it gives you:
- Any asset class: deposits, funds, bonds, private markets, real estate, commodities
- Distribution across jurisdictions, with local transfer rules checked by the token
- Built-in connectivity to secondary-market venues
3.2 — Stablecoin issuing platform
Issue your own coin, on your own authorization
An issuing platform for institutions that hold, or partner with a holder of, the required issuer authorization. You choose the chains your coin supports, the functions of its contract, and the composition of its reserve. The platform automates the workflow from deposit and safeguarding to minting, circulation, and redemption. It is designed with the requirements of MiCAR and the U.S. GENIUS Act in mind.
What it gives you:
- A coin under your brand, issued by you
- Your choice of conversion partners, liquidity providers, and terms
- Compliance checks, reserve reporting, and attestation workflows in one platform
3.3 — Reserve management
The reserve stays under your mandate
Reserve operations as a platform service, under the issuer's own mandate. You define the composition — for example, cash and short-dated government securities — and the platform supports segregated reserve structures, reserve reporting, and attestation workflows for the issuer. Investment decisions for the reserve stay with the issuer or with an authorized manager the issuer appoints.
What it gives you:
- A reserve composition you define and can change
- Reporting prepared for your auditors and supervisors
- Audit-ready records for compliance, finance, and governance
3.4 — Settlement infrastructure
The right settlement route for every transaction
Three routes sit behind one engine: tokenized settlement in near real time, depending on the rail used; SWIFT messaging where the counterparty requires it; and direct bank connections for local-currency legs. The routing engine selects a path by cost, speed, counterparty, and jurisdiction, or shows you the options. Multilateral netting offsets flows before settlement. Atomic payment-versus-payment (PvP) and delivery-versus-payment (DvP) are designed to remove principal risk between the two legs.
What it gives you:
- Netted flows, designed to reduce settlement cost and pre-funding
- One operating window around the clock, without cut-off times on the on-chain leg
- No forced move away from SWIFT
3.5 — Institutional marketplace
A repeatable path from issuance to secondary market
An institutional marketplace for tokenized structured products — a protected marketplace for institutional participants. Issuers, venues, and custodians work from a shared evidence set and a common assessment logic. The aim: a secondary listing becomes a repeatable, configuration-driven process instead of a new integration project each time.
What it gives you:
- Issuers: more venues and investors within reach of one product
- Venues: a standardized path from product to listing
- Investors: products that can be held and moved across venues
3.6 — Agentic banking layer
AI agents that act only under a signed mandate
A client tells an agent what it may do and signs that mandate. The mandate is stored on the ledger. When the agent finds a counterparty, the mandate is verified on-chain and the transaction completes — or it is stopped. Identity, policy enforcement, and settlement work across both digital asset and traditional payment routes.
What it gives you:
- Proof of client intent for every agent-driven transaction
- Spending limits and real-time risk monitoring you configure
- A treasury policy that executes itself, inside limits your client sets
Bring one product to market first
You can start with a single issuance or a single settlement corridor and extend from there.