Who Are the Parties in an RWA Product? Issuer, Manager, Custodian, and Platform

When you read an RWA product page, it is easy to treat the product as one thing made by one company. It is not. Behind a single tokenized fund or private bond there is usually a chain of separate parties: the company whose asset sits at the bottom, the manager who makes decisions, a legal structure that holds the asset, a custodian, a record-keeping layer, and the platform where you see the product. Each party has a different job, and each one can fail in a different way.

This matters for one practical reason: when something goes wrong, your outcome depends on which party failed. An issuer default is not the same as a manager underperforming, and a platform outage is not the same as losing your claim on the asset. If you cannot name the parties in a product, you cannot tell which risks you are actually carrying.

This article walks through the typical parties in an RWA product, what each is responsible for, what failure at each layer looks like, and where in the documents you can verify who does what.

Why the Party List Matters More Than the Product Name

Product names describe the asset. The party list describes who you are relying on.

Two products can both be called "tokenized private credit fund" and still have very different reliance chains. One might have an experienced manager, an independent administrator, and a regulated custodian. Another might have the same company acting as originator, manager, and administrator at the same time. The second setup concentrates risk in one party, even if the underlying asset is identical.

Institutional work on tokenization makes the same point from the other direction. The Bank for International Settlements describes tokenization as putting a claim on a real asset into a new record-keeping layer — but the claim itself still depends on the legal and operational chain behind it. The token is the front of the product. The parties are the structure.

So before you look at any return figure, it helps to answer one question: how many separate parties stand between me and the underlying asset, and what does each one do?

The Issuer and Originator: Where the Asset and the Obligation Come From

The originator or issuer is the party whose asset or obligation sits at the bottom of the product.

• In a bond-type product, the issuer is the borrower. It owes the coupon and the principal repayment. Any coupon exists only because the issuer generates cash flow and chooses, or is legally bound, to pay it — over a stated term, with repayment or exit depending on the issuer staying solvent, and with default as the core risk.
• In a pre-IPO or equity-type product, the originator is the company whose shares (or share exposure) the product holds. There is no promised payment at all; the outcome depends on how that company performs and whether an exit event, such as a listing or acquisition, ever happens.
• In a fund-type product, the "issuer" role is often the fund vehicle itself, and the underlying obligations sit one level further down, in the assets the fund buys.

What failure looks like here: issuer default or business failure. The borrower stops paying, or the company loses value. This is the deepest layer of risk, and no party above it — manager, custodian, or platform — can undo it. Structural features such as collateral or guarantees can soften a default, but only as well as the collateral is worth and enforceable.

Where to verify: the offering document or prospectus names the issuer and describes its business, its repayment source, and any security package. If a product does not clearly name who owes the money or whose equity you hold, that is a gap worth treating seriously.

The Manager and the Administrator: Who Decides and Who Keeps the Structure Honest

Fund-type products add a second layer: someone has to make decisions.

The manager selects assets, decides when to buy and sell, and runs the strategy. In a private credit fund, the manager underwrites the borrowers. In a pre-IPO fund, the manager sources the deals and negotiates the terms. Manager quality is a separate risk from asset quality: a good asset class run by a weak manager can still produce poor results.

What manager failure looks like: usually not a dramatic collapse. It looks like underperformance — bad asset selection, mispriced deals, slow reaction to problems, or style drift away from the stated strategy. It can also look like operational failure: weak reporting, missed deadlines, or in the worst cases misuse of fund assets.

Most structured RWA products also involve a special purpose vehicle (SPV) — a separate legal entity created to hold the underlying asset and isolate it from other businesses — plus an administrator who keeps the SPV's records, processes subscriptions and redemptions, and calculates valuations. The administrator's job is boring on purpose: it is the party that makes sure the numbers and the register are kept independently of the manager.

Where to verify: the fund documents name the manager and the administrator, describe the strategy and its limits, and state who calculates the net asset value. Check whether the manager and administrator are actually separate entities. When one company plays both roles, there is no independent check on the numbers. Assessing the manager itself — track record, process, and conflicts — is its own exercise.

The Custodian and the Token Layer: Who Holds the Asset and Who Keeps the Record

Two more parties sit between the structure and your screen.

The custodian physically or legally holds the underlying asset — the securities account, the collateral, the commodity in a vault, or the cash. Custody answers a simple question: if every other party disappeared tomorrow, where is the asset, and who can prove it belongs to the structure?

What custody failure looks like: assets that were supposed to be segregated turn out to be commingled with someone else's, or the custodian itself fails and the recovery process is slow and uncertain. Custody failure is rarer than issuer default, but it is more damaging, because it attacks the assumption that the asset exists and is reachable at all.

The token or record layer is what makes an RWA product "tokenized": a register, often on a blockchain, that records who holds which claim. It is worth being precise about what this layer does and does not do. The token layer is evidence of your claim. It is not the claim itself, and it is not the asset. A perfectly functioning token pointing at an empty SPV is still worth nothing — a point industry pilots such as Project Guardian make repeatedly when they stress the legal wrapper around the token.

What token-layer failure looks like: record errors, smart contract bugs, or a mismatch between what the on-chain register says and what the legal register says. The key question in the documents is which register is legally authoritative if the two ever disagree.

Where to verify: the offering document should name the custodian and describe segregation arrangements, and should state how the token maps to the legal claim and which record governs.

The Distribution Platform: A Window, Not Necessarily the Counterparty

The platform is where you see the product: the product page, the subscription flow, the documents, the risk disclosures.

In many RWA structures, the platform is a distributor. It presents the product, handles onboarding steps such as KYC and eligibility checks, and routes your subscription into the structure. In that setup, your legal claim runs to the issuing vehicle — not to the platform. The platform is a window onto the product, not the party that owes you the outcome.

This distinction changes what platform failure means:

• Platform outage or service failure: you may temporarily lose access to information or the ability to transact, which is disruptive — but if the structure holds your claim properly, the claim itself continues to exist independently of the platform's website being up.
• Loss of claim: this is a different and more serious event, and it happens at the structure, custody, or record layer — not at the display layer.

Whether that separation actually holds for a given product is not something to assume. It depends on the structure: read the documents to see whether the platform is only a distributor, or whether it also acts as issuer, counterparty, or custodian for that product. The more roles the platform stacks, the more a platform problem becomes a product problem. Bifu's RWA section is the entry point to each product's information and formal documents, which is where the roles for that specific product are set out.

Where to verify: the offering documents and the platform's own terms state who the issuer is, who your counterparty is, and what role the platform plays. If you cannot find this, ask before you subscribe, not after.

What Failure Looks Like at Each Layer: A Summary Table

The table below puts the chain in one place. Note that these failures are not equally likely, and a product can be exposed to several at once.

Reading the table top to bottom also orders the severity for most products: the lower the layer, the harder the failure is to recover from. A platform outage is an inconvenience. An issuer default is a loss.

How to Use This When You Read a Product

You do not need to be a structuring lawyer to apply this. Three habits cover most of it:

1. Name every party. For any product, write down who the issuer is, who manages it, who administers the structure, who holds custody, and what the platform's role is. If any box stays empty after reading the documents, treat that as your first finding.
2. Look for concentration. Separate parties checking each other is a feature. The same entity acting as originator, manager, and administrator is a concentration of trust, whatever the marketing says.
3. Match each return claim to a party. Any stated return only makes sense next to its source, term, exit path, and risk — and each of those traces back to a specific party in this chain. The coupon comes from the issuer. The exit depends on the structure's terms. The risk sits wherever the weakest party sits.

This checklist pairs naturally with the document-reading habits covered in the 6 things to check first in RWA product information — the parties tell you who to trust, and the documents tell you what they actually promised.

None of this removes risk. RWA products can lose value, exits can take longer than stated, and no layer of the chain guarantees an outcome. But knowing the parties turns a vague worry — "is this safe?" — into specific, answerable questions: who owes me what, who is checking them, and what happens if each one fails.

FAQ

Are RWA products protected by deposit insurance?

No. RWA products are not bank deposits, and holding a claim on an SPV or a token record is not the same as a protected deposit account. Any protection comes from the product's own structure — collateral, guarantees, or legal segregation — not from a deposit insurance scheme.

What happens to my claim if the platform shuts down completely?

It depends on whether the platform was only a distributor or also stacked other roles such as issuer or custodian. If your legal claim runs to the issuing vehicle and the SPV holds the asset properly, the claim can continue to exist even after the platform stops operating, but if the platform also acted as issuer or custodian, its shutdown becomes a structure-level problem, not just a display-layer one.

How can I check who administers a specific RWA product?

Look in the offering document or fund documents, which should name the administrator and state who calculates the net asset value and processes subscriptions and redemptions. If a product does not name an administrator or the manager and administrator appear to be the same entity, treat that as a gap worth asking about.

Does having more parties in the structure make a product riskier?

Not by itself. Separate parties checking each other's work is a feature, since it means no single party controls the whole chain unchecked. The real risk is concentration — the same entity acting as originator, manager, and administrator at once — not the number of parties involved.

Related Reading

• New to this? Start with the RWA basics.
• In the same area: how tokenization works.