Products
What Assetera offers: the Marketplace for investors, the B2B2C distribution API for partner institutions, the issuer portal, and the identity layer under all three.
Assetera is a small set of products built on one identity layer and one multi-tenant trading API.
| Product | For | Status |
|---|---|---|
| Marketplace | Investors | Available by environment |
| Distribution (B2B2C API) | Partner institutions | Available to onboarded partners |
| Issuers and suppliers | Token issuers, token holders, settlement venues | Listing available; the portal covers bank-transfer reconciliation |
| Assetera Identity | Everyone | Available |
Marketplace
The trading venue where investors browse tokenized instruments and place, take and negotiate trades. It is served by the multi-tenant Marketplace API, and Assetera itself is one tenant of that API. Trades settle on-chain, gated per action by an eligibility check (see Compliance gating).
Distribution (B2B2C API)
The same Marketplace API is the distribution product: other regulated institutions offer a tokenized-asset catalog to their own customers through it. Each partner is a separate tenant with its own catalog, resolved from a signed token claim, so tenants never see each other's data. A partner operates under either a reliance agreement or a tied-agent arrangement, and in both cases Assetera runs the compliance layer.
Partners can let Assetera onboard each customer, or use an agreed reliance model for customers they have already verified. Start at Offer the catalog to your customers.
Issuers and suppliers
An issuer lists an instrument once and it reaches every channel Assetera serves: a new instrument with a primary sale, an existing token for secondary trading, or an instrument settled on the supplier's own venue. Onboarded issuers reconcile bank-transfer sales in a role-gated portal. Start at Bring your asset to Assetera.
Assetera Identity
The platform's identity layer. Every user and partner authenticates against standards-based OpenID Connect (OIDC / OAuth 2.0) (nothing proprietary), and every API validates a signed token locally against public keys (no shared secret, no per-request callback). The token also carries the compliance context (KYC status, investor category, tenant) that eligibility decisions rely on.
Supported sign-in methods:
- Email + password
- One-time passcode / two-factor authentication (2FA)
- Passkeys
- Social / single sign-on (where enabled for a tenant)
See Authentication for the integrator view.