Key Takeaways

• Utila lets banks issue and manage tokenized real world assets and stablecoins on the same platform they use for custody, treasury, and payments.

• Every mint, burn, and holder action goes through the Utila Policy Engine, with approvals, segregation of duties, and a full audit history.

• No single party, including Utila, can move assets on its own.

• Tokenization is available in the console and API on EVM chains and Solana, and through the API on Stellar, the XRP Ledger, Sui, and Aptos.

• New supply can be minted directly to investors, internal wallets, or counterparties on Utila Link.

A growing number of banks are issuing tokenized funds and bonds, and some are preparing to launch their own stablecoins. Before any of these programs go live, risk, compliance, and operations teams get involved. Those teams want to know who controls the supply, how restrictions on holders are enforced, and whether every action can be traced afterwards.

This article explains how RWA tokenization for banks works on Utila, and how it answers those questions. To show how this works in practice, we'll follow a bank as it launches a tokenized money market fund, from setup to its first redemption.

What Does RWA Tokenization Mean for a Bank?

Tokenization for banks means representing a financial asset, such as a fund, a bond, or cash, as a token on a blockchain, and then operating that token for as long as it exists. As the issuer, the bank is responsible for how much supply exists, who is allowed to hold it, and the record of every change.

For a tokenized fund, the lifecycle maps directly to onchain actions. When an investor puts money into a tokenized fund, the fund issues new tokens to represent their share. When the investor exits, those tokens are removed from circulation. Onchain, these two actions are called minting and burning.

Regulated assets also come with rules on who is allowed to hold them, such as completed KYC or residence in an approved country. Those rules have to be enforced onchain, every time the token moves.

Stablecoins use the same mechanics for a different purpose. They are payment and settlement instruments, and their supply changes as clients exchange cash for tokens and redeem them.

Who Controls the Token Supply?

Say your bank has decided to launch a tokenized money market fund. Before anything goes live, your risk committee will want to know who can create new tokens.

On Utila, minting and burning are transactions, so each one goes through the Utila Policy Engine before it is signed. The same controls apply to every token operation in this article: minting, burning, distribution, and holder actions. You define:

• who can initiate a mint or burn

• how many approvals each one requires, and from whom

• which admin wallet it runs from

• the amount limits it must stay within, including hourly and daily velocity limits

On EVM chains, policies apply at the level of individual contract functions and parameters, so minting, burning, and other token functions can each carry their own approval rules. Solana mint and burn operations have dedicated policy rules as well.

Tiered roles and wallet level access controls separate the people who request new supply from the people who approve it, and admin quorum protects sensitive vault actions. Before anyone approves, the transaction can be simulated with decoded payloads, so approvers see exactly what a mint will do before they sign it.

How Does a Bank Set Up Its Token on Utila?

If your bank is launching a new token, your team can deploy the token contract from a dedicated wallet in Utila. If the contract already exists, your team adds the token in the Utila console, selecting its network and the admin wallet that controls it. The console then shows the token's address, admin wallet, and current total supply.

Next, the team assigns wallet roles and configures the policies for each token operation. Admin wallets that control the token contract can be kept separate from the operational wallets that handle daily activity, which reduces onchain risk. Utila works with the token contract you choose and has no fixed issuance flow: you can call mint, burn, redeem, or any other function your contract supports.

How Do Tokens Reach Investors?

Your first investor puts money into the fund, so new tokens need to be issued to represent their share. How the mint is triggered depends on how the investor pays.

If the investor pays in digital assets such as stablecoins, the funds can arrive in a Utila wallet and the mint can be triggered once they are received, so the full flow runs inside Utila.

If the investor pays in cash or traditional assets, those assets stay wherever your bank holds them. Your own systems confirm the payment, and the mint or distribution in Utila is triggered only after that approval.

Banks can also combine both flows. In every case, the real world asset never sits with Utila, and the mint goes through approvals before it is signed.

New supply can go to:

• an address book entry

• a Utila wallet

• an external address

• a counterparty on Utila Link

Utila Link connects you to 80+ verified counterparties, including institutional investors, liquidity providers, asset managers, and exchanges. Both sides approve before funds move.

As the fund grows, distributions to many holders can run as batch payouts, with gas management covering network fees, inside the same platform.

How Are Holder Restrictions Enforced?

Six months after launch, one of your fund's holders no longer meets the fund's requirements, for example because their KYC review has lapsed. Your compliance team freezes that address, so the holder can't send or receive the token. If a legal situation requires it, the tokens can be clawed back. New holders can also be required to receive authorization before they can hold the token at all. On EVM chains, Utila supports ERC-3643, a token standard built for permissioned assets, where transfers only go through to holders who meet the issuer’s eligibility requirements.

On EVM chains and Solana, these controls can be defined in your token contract or token program, and Utila lets you trigger them securely under policy, including whitelist and blacklist assignments from the console or API. On Stellar and the XRP Ledger, issuer controls are part of the protocol, and your team applies them from your issuing wallet, under the same policies. from your issuing wallet.

What Happens When an Investor Redeems?

When an investor exits the fund, your team burns their tokens. Burns run under their own policy, so the people who approve redemptions can be different from the people who approve new supply. The token's total supply in the console updates once the burn confirms.

How Do You Show Auditors What Happened?

Every mint, burn, and holder action is recorded in the Transactions page with its full approval history: who initiated it, who approved it, and when. The total supply shown for each token gives your operations and finance teams a reference point to reconcile against the fund's records.

Automating Mint and Burn for Stablecoins

Bank issued stablecoins work the same way as the fund, at much higher frequency. Supply changes whenever clients exchange cash for tokens or redeem them, often many times a day.

For that volume, Utila's API lets you trigger mint and burn from your own systems, under the same policies that govern manual operations. Your team keeps the console for oversight and exceptions.

tGBP runs its stablecoin mint and burn through the Utila API, with policy rules set at the contract function level. Routine operations below defined thresholds proceed automatically, while larger amounts or transfers to non-whitelisted addresses need additional admin approvals. Since onboarding with Utila, tGBP has grown its TVL 15x while keeping its team under 20 people. Read the case study

Which Blockchains Does Utila Support for Tokenization?

Banks choose networks based on where their counterparties, distribution partners, and settlement flows already are. Utila supports tokenization across EVM chains, Solana, Stellar, the XRP Ledger, Sui, Aptos and soon Canton.

Utila also supports Canton, where banks can hold and transfer CIP-56 tokens through the Utila API, under the same policies as every other operation on Utila. Banks can bring their own validator, so their holdings stay on infrastructure they control.

Any EVM compatible network can be added, often within the same week. Stellar and the XRP Ledger both include native asset issuance and issuer controls at the protocol level, which is why both are widely considered for payment and settlement use cases.

What You Bring and What Utila Handles

What Your Bank Brings:

• the asset and its legal structure

• the token contract or token design

• investor onboarding and KYC

• reserve management for stablecoins

What Utila Handles:

• key management and signing

• policy enforcement and approvals

• execution of mint, burn, and holder controls

• distribution to wallets and counterparties

• the audit record for every token operation

Why Banks Choose Utila for Tokenization

Control over the full token lifecycle. Deploy your contract from a dedicated wallet or bring an existing one, then mint, burn, and apply holder controls under your own policies, from issuance to redemption.

Security you choose. Run Utila with MPC in the cloud, an online HSM, or an airgapped HSM. Admin wallets stay separate from operational wallets, and no single party, including Utila, can move assets on its own.

Policy that scales with volume. Approval rules apply at the contract function level, so routine operations can run automatically while larger ones need more approvals. This is how tGBP grew its TVL 15x with a team of under 20 people.

Distribution built in. Mint directly to investors, internal wallets, or 80+ counterparties on Utila Link, across EVM chains, Solana, Stellar, the XRP Ledger, Sui, and Aptos. Bank issued tokenized deposits such as N3XT’s NDD are also available to Utila clients.

If your bank is evaluating tokenization for real world assets or stablecoins, contact our team to discuss your use case.

About Utila

Utila is the leading stablecoin and digital asset infrastructure platform for fintechs and enterprises. Utila enables organizations of all sizes to securely build, manage, and scale digital asset operations across stablecoin payments, treasury, trading, tokenization, and beyond. The platform combines institutional-grade MPC wallets, granular policy controls, robust APIs, multi-chain support, payment and tokenization engine, and deep integrations with banking, compliance, exchanges, DeFi, and more. Trusted by 400+ companies, Utila processes more than $30B in monthly volume and has secured over $500B in transactions to date.

Frequently Asked Questions

Can Banks Issue Stablecoins on Utila?

Yes, banks can issue stablecoins on Utila. They can mint and burn stablecoins through the console or API, with every operation governed by the Utila Policy Engine. tokenised GBP runs automated stablecoin mint and burn through the Utila API.

Which Blockchains Does Utila Support for Tokenization?

Utila supports tokenization on EVM chains and Solana through the console and API, and on Stellar, the XRP Ledger, Sui, and Aptos through the API.

Can Utila Mint or Move Tokens Without the Bank's Approval?

No, Utila cannot mint or move tokens without the bank's approval. Every token operation goes through the bank's own policies and approvals. With MPC, no single party, including Utila, can move assets on its own.

Can Banks Restrict Who Holds Their Tokens?

Yes, banks can restrict who holds their tokens. They can authorize holders, freeze addresses, and claw back tokens using the controls built into their token or, on Stellar and the XRP Ledger, the protocol's issuer controls. Each action goes through the bank's approval policies.

Does Utila Support Canton?

Yes, Utila supports Canton. Banks can hold and transfer CIP-56 tokens through the Utila API, under the same policies as every other operation on Utila, and can bring their own validator so their holdings stay on infrastructure they control.