Offer the catalog to your customers
Give your customers Assetera's tokenized securities inside your own product. Two ways to bring users, three ways to deliver it, and what to have ready for the first call.
Your customers, your brand, Assetera's licence. You choose how your users come in and how much you build. Behind every option Assetera runs onboarding, eligibility, settlement and reporting, and you never compute a price, a fee or a decision.
Two ways to bring your users
| Tied agent | Reliance partner | |
|---|---|---|
| Choose it when | you have customers and no investment-services licence | you are regulated and have already verified these customers |
| Your customer signs up | with Assetera, inside your journey | with you. Assetera relies on your record |
| Customer due diligence | Assetera runs it, embedded in your UI | you did it. You send the record and its provenance |
| Transaction reporting | Assetera, under a white-label arrangement | you, as executing broker, or Assetera under white-label |
| You keep | the relationship, the brand, the UI | the relationship, the brand, the UI and the identity |
Reliance is about who performed the due diligence. Customer identification, record keeping and eligibility apply in both models.
Three ways to deliver it
| You build | Choose it when | |
|---|---|---|
| Assetera-hosted journey | sign-in wiring only | you want to launch first and build later |
| Your own frontend | a backend that holds the tokens, a list, a detail page, a confirm step | your customers already live in your product |
| Backend only | machine-to-machine calls, no user browser | you run your own front end and your own sessions |
In every option the browser never holds an Assetera API token. Your backend does, and the browser gets an opaque session cookie. A tied-agent starter application that carries the purchase flows is in development. Today you build them from the walkthrough.
The journey
- 1Your customer opens your app · Your appAlready signed in to you. Nothing new to learn.
- 2A tenant-scoped session is issued · AsseteraStandard OpenID Connect. Your backend holds the tokens.
- 3Onboarding runs, or your record is relied on · AsseteraEmbedded in your frontend, or supplied under reliance.
- 4You render your catalog · Your appYour tenant sees only the instruments entitled to it.
- 5Assetera prices it and checks eligibility · AsseteraQuote, limits, appropriateness, trading window.
- 6Your customer confirms · Your appOne confirm in your UI, with your wording.
- 7It settles and the position is theirs · ChainOn chain, measured rather than reported.
What the catalog gives you
Your tenant is one of many on one Marketplace API, and Assetera's own marketplace is another. You see the instruments entitled to your tenant, and each one carries how it settles, because its issuer decided that when it was listed.
| The instrument settles by | You implement |
|---|---|
| bank transfer | a payment instruction, and delivery once Assetera reconciles the payment |
| an on-chain purchase, newly issued or from an external venue | one quote-and-sign flow. The two on-chain rails are the same shape |
| a secondary trade | the order and offer flows against the trading venue |
Start with the instruments whose flow you have built and widen the entitlement later. An instrument whose flow you have not built is simply not buyable in your app.
What you never acquire
| To offer this yourself you would need | With Assetera |
|---|---|
| An investment-services licence in the EEA | Assetera's, with you as tied agent or reliance partner |
| A KYC and AML operation, with ongoing monitoring | Assetera runs it in both models |
| Appropriateness and product-governance controls | enforced by the platform on every action |
| Custody, key management and chain operations | settlement is on chain and gas is relayed. Your customer never holds gas |
| Instrument sourcing and issuer relationships | the catalog, shared with every channel on the network |
Before the first call
Have an answer to these five. They shape the integration rather than being settings.
- Tied agent or reliance partner? Your licence position decides it.
- Do your customers already exist with a stable identifier you can federate?
- Hosted journey, your own frontend, or backend only?
- Which instruments do you want in your catalog?
- Who carries transaction reporting?
Then write to as@assetera.com, or pick the instruments on the Token Directory and send the request from there.
Reference
Embed the marketplace, worked
The B2B2C example end to end: what you build, what you consume, and the five questions.
Tied agent or reliance
The two models in detail, and what the customer experiences in each.
Tied-agent walkthrough
Your own frontend: a Next.js app and a backend that keeps the tokens server-side.
Reliance integration
Federated identity and the customer record you send under reliance.
Partner onboarding
The technical handover: credentials, what Assetera provisions, go-live checks.
Off-chain sale
The bank-transfer flow.
On-chain primary sale
The quote-and-sign flow, for both on-chain rails.
Tenancy
How one API serves every channel, and who is responsible for what.
The onboarding pack
The five items an instrument needs before Assetera configures its listing: identity, documents, token and network details, market terms, and the receiving account.
Tied agent or reliance partner
The two ways a partner brings its customers to Assetera, what each customer experiences under each, and where the choice is decided. Your licence position decides it.