Assetera Docs
Issuers and suppliers

List your asset on Assetera

A worked B2B example. An issuer brings one instrument and reaches every partner tenant entitled to carry it, without a separate integration for each distributor.

You bring one instrument. It reaches every partner tenant entitled to carry it. You do not integrate with each distributor, and you do not build a customer journey, a compliance operation, or a settlement path.

This is the other direction of the same network described in Embed the marketplace in your app. There, a partner brings customers. Here, an institution brings an asset, and the two meet in one catalog.

At a glance

Who does it
The instrument, its documents and its termsyou
The price and the per-purchase limitsyou, as contract state you control
How the instrument settlesyou, agreed with Assetera at onboarding. Distributors consume it
Deciding who may buyAssetera, on every purchase
The distribution reachAssetera's partner tenants, per the entitlements you agree
Taking the money and delivering the tokensthe settlement rail, on chain or by bank transfer
The audit trail and the reportingAssetera

The journey

Your firmAsseteraChain12345678
  1. 1You supply the onboarding pack · Your firmIssuer, instrument, documents, token and network details.
  2. 2Assetera configures and reviews the listing · AsseteraIt activates only after the required approvals.
  3. 3Entitlement decides who may carry it · AsseteraPer partner tenant, so two distributors can see different catalogs.
  4. 4You set the price and the caps · Your firmOn the own-issuance rail these are contract state you hold the role for.
  5. 5Partner apps show it to their customers · Your firmOne listing, many front ends, no per-distributor build.
  6. 6Each buyer is screened and checked · AsseteraEligibility, appropriateness, limits, trading window.
  7. 7The purchase settles and is measured · ChainAmounts come from balance deltas, not from a reported figure.
  8. 8You reconcile · Your firmIn the issuer portal for the bank-transfer rail.
Steps 2, 3, 6 and 7 are the ones you would otherwise have to build or buy.

The three ways a sale settles, and you choose which

This is your decision, not a distributor's. You agree the settlement method with Assetera when the instrument is onboarded, and it becomes a property of that instrument. Every partner distributing it consumes that choice: they read the catalog and implement the flow it names. A buyer cannot pick a rail at request time, and neither can a distributor.

Choosing well is therefore a distribution decision as much as an operational one. A rail that few partners have implemented reaches fewer of their customers, so it is worth asking your Assetera contact which rails the partners you care about already support.

RailThe buyer pays withWhat happensRead
Bank transfera bank transfer against a referenceAssetera reconciles the payment, then the tokens are deliveredOff-chain sale
Your own issuancea settlement currency on chainyour issuance venue mints against the price you set, in one transactionPrimary issuance
A third-party venuea settlement currency on chainthe router buys from an external venue and delivers atomicallyPrimary settlement

On the on-chain rails a purchase is one transaction. An ERC-2612 permit and the settlement travel together, so a buyer does not send a separate approval first and does not need to hold gas.

What the price and the caps really are

On the own-issuance rail, one contract is deployed per offering. It holds the unit price and the minting right, so the terms of your offering are on chain and are not an instruction someone sends with a purchase.

Where it lives
Unit pricecontract state, changed only by the role holder, inside deploy-time bounds
Per-purchase capcontract state. A cap of zero means closed, not unlimited
Minting rightgranted by you to the venue. Ungranted, the first purchase fails
Delivery amountmeasured from the balance change, never from a reported number

See Issuance venue for the contract itself and Contracts and addresses for the deployed routers. If your token issues through a call of its own, such as one that requires the investor to be whitelisted first, your developers extend that contract rather than replace it: Extend the issuance venue.

A primary purchase moves no chart

Market data comes from secondary fills. A primary purchase has no maker, no taker and no side, so inventing one would corrupt the market data. An instrument can sell steadily and show a flat chart, which is correct rather than a gap. Do not build a "sold so far" figure out of chart data.

Onboarding the listing

You send the onboarding pack, Assetera configures the listing, reviews it and activates it. The rail, the currency, the window and the channels are part of the pack.

Entitlement is explicit

A listing does not appear in every partner catalog by default. Instruments are assigned to tenants, which is what lets two distributors be offered different subsets of the same assets. Agree the entitlements you want as part of the distribution terms.

After it is live

Issuer-facing reporting beyond reconciliation

The issuer portal covers receiving accounts and bank-transfer reconciliation today. Reporting for the on-chain rails is coordinated with Assetera rather than self-service, and the self-service surface for it is not documented here yet.

For an integration that needs the purchase data programmatically, the on-chain event is the record: every amount on it is a measured balance delta. See Contract events.

Next

On this page