Banking & Financial Accounts Last updated:

Banking for Tokenisation Platforms: Client Money, Custody and the Off-Chain Leg

The most consequential fact about banking a tokenisation platform is that its product usually sits outside the crypto regime entirely: MiCA does not apply to crypto-assets that qualify as financial instruments. The counterparty needed is therefore often not a crypto-friendly bank but one with securities-services capability. Through Jagelski & Partners’ partner network we start from the perimeter question, because it determines which institutions are relevant at all.

Tokenisation Is a Securities Product, Not a Crypto One

MiCA does not apply to crypto-assets that qualify as financial instruments. The exclusion is written into the Regulation rather than inferred from it, and what it excludes falls instead under MiFID II, the prospectus regime, and where relevant the DLT Pilot Regime.[1]

In short: A crypto-asset service provider licence does not authorise tokenised securities activity, and presenting one as though it does is the fastest way to lose an institutional conversation. Institutions that serve this sector know the perimeter better than most applicants do.

So the counterparty an issuer needs is often not a crypto-friendly bank but a bank with securities-services capability: client asset segregation under investment-firm rules, settlement against delivery, and a custody arrangement that recognises the token as a representation of a security rather than as a crypto-asset.

Four Tests, and the Off-Chain Leg Is the One Applicants Prepare For Least

Perimeter clarity. Which regime the instrument sits in, which authorisation covers the activity, and who the regulator is. An applicant that describes its product as “RWA tokenisation” without naming the instrument type has not answered the first question.

Client asset segregation. Where subscription money sits before issuance, where redemption proceeds sit before payment, and how both are separated from the platform’s own funds.

The off-chain leg. A tokenised asset is a claim on something that exists off-chain. Institutions ask who holds the underlying, how the register reconciles to the token supply, and what happens to holders if the platform fails. This is the question most applicants prepare for least.

Investor onboarding. Whether the platform serves professional or retail investors, and how eligibility is enforced. A retail-facing platform carries prospectus and disclosure obligations a professional-only venue does not, and banks price the difference.

Stack and Timelines

LayerInstitutionDifficultyTimeline
Client money / subscription accountCredit institution with securities-services capabilityHardest; a narrow set of counterparties3–6 months
Operating accountBank or EMIRoutine once authorised2–6 weeks
Multi-currency treasuryBank or EMIRoutine2–6 weeks
Stablecoin settlement (optional)Authorised EMT issuer or PIDepends on issuer authorisation status4–10 weeks

Because the profile is a securities business rather than a high-risk one, the binding constraint is counterparty availability rather than price: the narrow set of institutions willing to hold subscription money for a tokenisation platform sets the timeline, and pricing follows once one of them says yes. Timelines are indicative across the partner network as of .

How Jagelski & Partners Helps

Placement starts by settling which regime the instrument sits in, because that one answer decides which institution list the file goes to. A platform issuing tokenised securities needs a securities-capable counterparty; a platform issuing an e-money token needs the reserve arrangement covered on the stablecoin issuer banking page. Approaching the wrong list first spends applications on institutions that were never relevant, and declines leave a record.

Assessment covers the instrument classification and the authorisation that supports it, client asset segregation for subscription and redemption flows, the off-chain custody and register reconciliation, and investor-eligibility enforcement. Where the classification is genuinely unsettled we say so rather than presenting a view an institution will test.

Frequently Asked Questions

No. MiCA expressly does not apply to crypto-assets that qualify as financial instruments; those sit under MiFID II, the prospectus regime, and where relevant the DLT Pilot Regime. A crypto-asset service provider authorisation does not authorise tokenised securities activity.

Presenting it as though it does is the fastest way to lose an institutional conversation, because institutions serving this sector know the perimeter better than most applicants.

Usually a bank with securities-services capability rather than a crypto-friendly bank. The requirements are client asset segregation under investment-firm rules, settlement against delivery, and a custody arrangement that treats the token as a representation of a security.

Those are different institution lists, and applying to the crypto list first wastes the applications that leave a record.

The off-chain leg. A tokenised asset is a claim on something that exists off-chain, so institutions ask who holds the underlying, how the register reconciles to token supply, and what happens to holders if the platform fails.

Applicants generally arrive with the on-chain architecture documented in detail and the custody and reconciliation of the underlying described in a paragraph.

Yes. A retail-facing platform carries prospectus and disclosure obligations a professional-only venue does not, and institutions price the difference in diligence and ongoing monitoring.

Eligibility enforcement is tested specifically: not whether the policy exists but how it is applied at onboarding and re-checked over time.

Less than most crypto profiles, because the underlying product is a securities business with a recognisable regulatory perimeter. Costs sit in the regulated-fintech range rather than the high-risk range.

Counterparty availability is the constraint rather than price: the set of institutions with both securities-services capability and appetite for a DLT-based issuer is small.

The client money and subscription account is the long pole at three to six months, because the counterparty set is narrow and each institution runs its own securities-services diligence. Operating and treasury accounts run 2 to 6 weeks.

Starting the subscription-account conversation alongside the authorisation rather than after it is the main scheduling decision.

Yes, and increasingly they are for business-to-business flows, but the issuer’s authorisation status is now a supervisory question rather than a commercial preference. An authorised e-money token and a non-compliant issuer are treated very differently by an institution.

Where settlement in a token is planned, expect the bank to ask which issuer, under which authorisation, and what happens if that issuer is restricted.

Say so. Classification of hybrid instruments is unsettled in places, and an institution that discovers an applicant asserted certainty it did not have will withdraw. Presenting the analysis, the competing readings, and the regulator engagement is a stronger position than a confident wrong answer.

Where the classification is unsettled we say so at the assessment stage rather than letting an institution test it.

No. The crypto licensing pages carry an RWA note per jurisdiction naming the governing regime, and the fund licensing page covers the vehicle side. This page covers only the banking question: which accounts a tokenisation platform needs and who will open them.

No. Jagelski & Partners is paid by the institution that takes the business, through a referral or revenue-share arrangement, not by a fee billed to the client. The pricing is the institutional rate, with no markup and no onboarding fee.

Ready to Approach the Right Institution List?

Book an assessment. We establish the instrument classification and the authorisation supporting it, then place client money, custody, and treasury against institutions with securities-services capability rather than the crypto list. No markup on institutional pricing. No onboarding fee.

References

Show all references
  1. European Union, Directive 2014/65/EU (MiFID II) and Regulation (EU) 2022/858 on a pilot regime for market infrastructures based on distributed ledger technology; MiCA Article 2(4) excludes financial instruments from its scope, eur-lex.europa.eu, accessed .