# Scenario B: Manage Vaults for End Users

You're offering Tesseract DCVs to your own customer base — custodian, exchange, fintech, or wallet provider. Each of your end users becomes a Tesseract client in their own right, and you orchestrate onboarding and day-to-day vault operations on their behalf.

Scenario B is a proper partnership, not a plug-and-play API. The on-chain surface is the same as [Scenario A](/dedicated-client-vaults/integration-guide/scenario-a.md) — the difference is everything that sits in front of it.

### What's involved

**Partnership and legal.** You and Tesseract agree on the commercial model ([Introducer / Distribution Agreement](/dedicated-client-vaults/fees-and-commercial-model.md) or Technology Access Fee), complete DDQ, and sign the partnership agreement. Your organization completes a KYB as the partnering entity.

**Compliance alignment.** We decide up front who runs KYC for your users — Tesseract Investment Oy (full KYC under our MiCA CASP authorisation), you (reliance on your existing AML program), or a hybrid. The choice depends on your regulatory status, jurisdiction, and user base. Tesseract runs ongoing AML screening on any wallet it whitelists regardless of the model chosen.

**Programmatic user onboarding (M2M).** You're provisioned with credentials for Tesseract's Compliance API and onboard each of your users into our compliance system via REST. Once a user is cleared, Tesseract writes their wallet to the on-chain `Whitelisting` contract with a KYC-expiration timestamp.

**Custody flexibility.** On-chain operations don't care who signs — what matters is that the signing wallet is whitelisted and owns the vault. You can have each end user sign from their own wallet, operate vaults from your custodial wallets per user, or (with the relevant licenses) pool users under a smaller set of partner-controlled wallets. The right shape is agreed during compliance setup.

**Optional compliance app embedding.** If you want users to complete KYC without leaving your product, Tesseract can provide an embeddable version of the Compliance app. This is available on request — we share the integration spec after partnership setup.

**Vault operations per user.** Once wallets are whitelisted, per-user vault deployment, deposits, withdrawals, strategy assignment, and reporting follow the same on-chain flow as Scenario A — see the [Scenario A material](/dedicated-client-vaults/integration-guide/scenario-a.md) for code-level walkthroughs that carry over one-to-one.

### What you get after partnership setup

* M2M credentials for the Compliance API, scoped to your partner account.
* Full request / response documentation for the Compliance API.
* The Compliance app embedding spec (if applicable).
* A named commercial and technical contact at Tesseract.
* Access to the reporting surface for all vaults under your partnership.

### How to start

Scenario B always starts with a commercial conversation. The technical documentation above is intentionally a summary — detailed specs and credentials are shared directly with partners after the initial discussion.

[**Get in touch**](https://tesseract.fi/#contact-us) to open the conversation.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-b.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.