Trevo documentation

Documentation in progress. Some articles and step-by-step guides are still being prepared. These pages are marked clearly, and you can use the available material as it is added.

Learn what tokenization means, create and manage tokens with Trevo, and understand the work around them—from preparing an instrument to helping its holders.

Tokenization represents something as a token recorded on a blockchain. For a financial instrument, the important questions are what the token represents, which rights its holder has, and how those rights connect to the instrument’s documents and records. Creating a token is one part of that process.

Trevo provides token infrastructure, configurable checks, applications for administration and holding tokens, and interfaces for integration. Your team and appointed providers define the financial instrument, manage investor relationships, and handle its legal records, cash processes and servicing.

Choose the path that matches what you want to do:

• Understand tokenization
• Create and manage a token
• Receive or transfer tokens
• Work with issuer clients
• Build an integration
• Understand costs or get help

Understand tokenization

Start with the basics: tokens and their units, represented rights, blockchain accounts, signing keys and the people involved. Follow an illustrative token from its creation through distribution, transfers and ongoing administration.

You do not need to understand blockchain implementation to use these guides. New terms are explained where they first matter.

Start with What is tokenization?, then explore tokens and represented rights.

Create and manage a token

Use Studio on the web to create and administer tokens. Use Vault on your phone to review and sign supported Studio requests offline through QR codes.

Begin with a learning exercise: create an illustrative token, configure a check, distribute a holding and try a transfer in Wallet. Then use the project preparation guide to connect the token workflow to a real instrument and its operating responsibilities.

The administration guides cover your team’s permissions, token information, issuing and distributing units, reviewing holders and activity, and handling changes or interrupted operations.

See Studio and Vault setup and the first-token exercise. These guides are in preparation.

Receive or transfer tokens

Use Wallet on your phone to view your holdings, receive and transfer tokens, and complete supported verification.

Start with account setup and protecting your signing keys. Learn how to identify a token, check its requirements, review any fee before sending, and understand a pending, rejected or completed operation. Each token’s rules determine who can hold and transfer it. Verification alone does not qualify you for every token.

For questions about an instrument’s rights, payments or redemption, use the information and contacts supplied by its issuer.

See Get started with Wallet. The step-by-step Wallet guides are in preparation.

Work with issuer clients

Use the setup and administration guides to prepare a client’s token workflow. The project guides explain how to agree responsibilities, arrange authorized access, hand over the setup and define ongoing administration or integration work.

See Prepare a real issuance and client handover.

Build an integration

The integration guides cover reading token data, preparing and signing operations, submitting them and handling their outcomes. Separate guides address custom checks and verification-service integrations, including the responsibilities of running those services.

See Start an integration.

Understand costs or get help

The billing guides explain Free and Paid capacity, how holders and actions are counted, annual capacity, invoices and subscription changes. Token capacity and native network fees are separate topics.

If something does not work as expected, start with the troubleshooting guide for your task. The data and evidence guides explain what is public, what is held by a service, and how to request supporting documents. The capabilities guide distinguishes supported scope from planned features.

See subscriptions, help and capabilities.