[Suit Up]

HOME / PLAYBOOKS / Cross-jurisdictional rollout sequencing for tokenised products
Playbook · Decision support

Cross-jurisdictional rollout sequencing for tokenised products


This playbook is for the operator inside an asset manager, bank, or new entrant who has already shipped a tokenised product in one jurisdiction and now has to decide where to take it next. The right sequence is rarely "biggest market first". It is "where the regulatory wrapper for your asset class is most mature, expanding toward jurisdictions whose rules your home structure already maps to, deferring jurisdictions where the product would have to be re-engineered". Get the sequencing wrong and the second jurisdiction takes 12 months of structural rework. Get it right and the second jurisdiction lands inside two quarters on the back of the first.

TL;DR

Launch where the regulatory wrapper for your asset class is most mature, not where the addressable market is biggest. Expand toward jurisdictions whose perimeter your home-jurisdiction structure already maps to, so you are negotiating distribution rather than rebuilding the product. Defer the jurisdictions where you would need a wholly new product structure. For tokenised money market funds, that usually means US-first under 3(c)(7) followed by Asia via Reg S into Singapore and Hong Kong private banks. For tokenised bonds, Hong Kong or the UK first, with the EU following on EMTN-equivalent rails. For tokenised credit funds out of the EU, Luxembourg first under AIFMD, Singapore second as a Restricted Scheme. The losses in translation are real: Reg D distribution does not become Reg S distribution by relabelling, and a MiCA-passported instrument cannot ride MiFID II rails for tokenised securities.

Decision frame

The institution has a tokenised product (an MMF, a bond programme, a tokenised deposit, a single-currency stablecoin) that has cleared the new product committee in its home jurisdiction. The brief is which jurisdiction comes second, which comes third, what gets sequenced into year two, and what gets explicitly deferred.

Three framings consistently lead operators wrong. The first is "launch everywhere at once". This is operationally impossible. Each jurisdiction needs a local distributor onboarding, a regulatory filing or notification, a tax-and-substance review, and a custody and transfer-agent integration that is rarely identical to the home set-up. The institutions that try this end up with the product half-launched in five places, fully launched in none, and a compliance team that resents the programme.

The second is "launch in the biggest market first". The biggest market may have the slowest regulatory path. The US is the largest pool of tokenisation capital but Reg D for qualified purchasers is a narrow gate, the SEC's 3(c)(7) interpretation has been the friendliest of the live regimes but the structural lift is non-trivial, and any non-US issuer hits the foreign-issuer comparability problem on payment-stablecoin distribution. Singapore's accredited-investor offering under SFA Section 274/275 can be operationally faster for a non-US asset manager than retro-fitting a 3(c)(7) wrapper.

The third is "launch where competitors are". This is following, not differentiating. If BlackRock BUIDL and Franklin Templeton FOBXX are already in the same APAC private banks, the slot for a third tokenised USD MMF is narrow. The sequencing question worth asking is where the competitor field is thinnest in your asset class, not where it is most crowded.

The sequencing framework

Five criteria, listed in order of how binding they are. Stop at the first one that disqualifies a jurisdiction from the next slot in the sequence.

Regulatory-wrapper maturity for your asset class. This is the most binding filter. A jurisdiction can have a sophisticated overall tokenisation regime and still lack the specific wrapper your product needs. For tokenised MMFs, the US 3(c)(7) qualified-purchaser route is the most mature, with BUIDL as the reference architecture and FOBXX as the public-fund variant. Singapore's VCC plus MAS Section 274 (institutional investors) and Section 275 (accredited investors) of the Securities and Futures Act is a close second, with Project Guardian giving the workstreams cover for the operational pattern. Hong Kong's SFC-authorised funds regime is a third, with the April 2026 secondary-trading framework (press release 26PR59) materially upgrading what tokenised authorised funds can do beyond primary-only distribution. The EU's UCITS regime is workable but slower because UCITS-eligible custody and transfer-agent rules around digital-asset wrappers remain partly under interpretation. Japan's FIEA route adds a trust-route operational layer (the Progmat pattern), which is workable for a Japan-domiciled product and significantly more friction for a non-Japan-domiciled one.

For tokenised bonds, the maturity ranking inverts. Hong Kong is the most mature: HSBC Orion plus the HKSAR multi-currency green bond series demonstrates the operational shape (see HSBC Orion + DIGIT). The UK comes second on the back of the DIGIT pilot. Singapore comes third on the strength of the Project Guardian Fixed Income workstream and the November 2025 ICMA addendum on tokenised-bond DvP and custody. For tokenised deposits, the wrapper sits inside the bank's existing licence, which makes the maturity ranking a function of the bank's own footprint rather than the jurisdiction's perimeter.

Distribution channel readiness. Which jurisdictions have private banks or wealth platforms already distributing comparable tokenised products. Singapore (DBS, UOB, Bank of Singapore) and Hong Kong (HSBC Private Banking, Standard Chartered Wealth) lead in APAC because both have private-bank desks already running BUIDL or FOBXX positions for clients, which means the operational discipline of intake, custody, and reporting is already in place. The next move into either is a distribution conversation rather than a from-scratch onboarding. Tokyo and Seoul are slower because the wealth-distribution channel for tokenised funds is less established and the local regulatory perimeter (FIEA in Japan, the VAUPA regime in Korea) does not yet plug into the same patterns. Sydney sits in the middle, with RBA tokenisation work via Project Acacia maturing the wholesale plumbing but the wealth-channel intake still partly bespoke.

Investor base eligibility. The regime determines who can buy. Reg D for US qualified purchasers is narrow, with USD 5 million in investments as the floor for individuals and broader thresholds for institutions, which limits the addressable wallet count even when the dollar size is large. Reg S is broader for non-US offering and is the standard distribution mechanism for an APAC private-bank channel buying a US-issued tokenised MMF. Singapore SFA Section 274 (institutional) and Section 275 (accredited individuals at SGD 1 million net financial assets or SGD 300,000 income) is workable and the threshold definitions are well understood. The Hong Kong SFC professional investor regime (HKD 8 million in the case of individuals, HKD 40 million for corporations) operates similarly. The EU's professional client regime under MiFID II is workable but the cross-border passporting interaction with the AIFMD overlay matters for tokenised funds specifically. Japan's specified investor regime under FIEA is structurally workable but operationally narrower than the APAC peers.

Tax efficiency for the target investor. Tokenisation does not change the tax wrapper but it does affect substance. Where the issuer sits, where the chain entry is logged, where the custodian operates from, and where the fund administrator runs all feed into the substance test. A Cayman SPV with a Singapore custodian and a Tokyo fund administrator produces a substance question that an entirely Singapore-based stack does not. For an APAC private-bank investor base, the substance call on a Cayman or Luxembourg vehicle is familiar; for an EU institutional base, the Luxembourg substance is cleaner. Surface the substance question before naming the rollout sequence, not during the second jurisdiction's onboarding.

Operational readiness in each jurisdiction. Custody, transfer agent, fund administrator, on-chain accounting integration, and reconciliation cadence all have to be in place before the second jurisdiction launches. Securitize handles transfer agency for the BUIDL pattern; Anchorage and comparable counterparties handle custody. The platform and custody decisions (see Evaluating issuance platforms and Evaluating custody providers) compound across jurisdictions. A custody provider strong in the home jurisdiction may not have a Hong Kong or Singapore presence, and procuring a second custody counterparty is a nine-month project the rollout plan needs to absorb.

Sequencing patterns

Three named patterns recur across the live programmes. Each fits a particular institutional starting point.

US-first / Asia-second pattern. Used by BlackRock BUIDL and Franklin Templeton FOBXX. Launch under 3(c)(7) for US qualified purchasers using Securitize as the transfer agent, with the on-chain wrapper supporting both primary subscription and limited secondary transferability between qualified holders. Expand into Asia via Reg S distribution to APAC private banks, with the HSBC Private Banking and Standard Chartered Wealth desks (in Hong Kong and Singapore) as the channels that have already onboarded the operational pattern. The BUIDL reference architecture page tracks the pattern in detail, including the ONDO / OUSG layered distribution that other DeFi-native venues stack on top of the underlying fund.

Singapore-first / regional-second pattern. Used by some Project Guardian cohort participants. Launch under MAS supervision via a VCC structure and an accredited-investor offering under SFA Section 275, with DBS or UOB in the distribution chain. Expand to Hong Kong via SFC professional-investor offering, often with HSBC Private Banking as the local distributor. Expand to Thailand via the SEC Thailand private placement pathway, and to Japan via a local partnership with one of the megabank-trust route Progmat consortium members. The pattern is slower than the US-first one but it is operationally easier for a non-US asset manager because the regulatory negotiation begins with MAS, which has more codified workstreams for tokenisation than any other APAC regulator.

Multi-issuance pattern. Used by HSBC Orion: separate issuance vehicles per jurisdiction, with the UK gilts via DIGIT, the multi-currency green bond series via the HKSAR Hong Kong issuer, and Luxembourg-domiciled institutional bonds for European distribution (see HSBC Orion + DIGIT). The pattern carries higher operational overhead because each issuance vehicle is a complete legal and operational stack, but it produces a cleaner regulatory perimeter per issuance and avoids the cross-border-passport problem entirely. The trade-off is the bank's tolerance for running multiple parallel stacks; a single-issuer programme cannot reasonably absorb that overhead.

Worked example

An EU asset manager with EUR 80bn AUM and a credit franchise centred on Asian direct-lending mid-market wants to launch a tokenised credit fund. The product committee has approved the tokenisation thesis and asks for a sequenced rollout plan covering the first 18 months.

Step 1, regulatory-wrapper maturity. Tokenised credit funds for institutional investors have a working pathway in Luxembourg under AIFMD, with the on-chain wrapper running on a permissioned blockchain and the fund interests represented as tokenised units. The same fund structure has a workable path in Singapore as a Restricted Scheme to accredited investors, with the on-chain pattern matching what the Project Guardian credit-fund workstreams have demonstrated. The US would require a 3(c)(7) qualified-purchaser layer, which means a structural change to the fund (a US feeder, a separate US subscription rail) that the firm has not yet built. Japan would require offshore-fund offering rules under the MOF perimeter, which adds three to six months of lead time. The EU UCITS path is not in scope because the underlying credit positions are not UCITS-eligible.

Step 2, distribution channel readiness. The firm's existing Luxembourg distribution to European institutional LPs is the strongest channel. In Singapore, DBS and UOB private banking already distribute comparable tokenised credit products from US issuers, so a Restricted Scheme offering would land into a known channel. Hong Kong's professional-investor channel is similar. The US would require the firm to build or rent a US distributor, which is a separate project.

Step 3, investor base eligibility. AIFMD-eligible professional investors in the EU are the primary base. SFA Section 274/275 in Singapore is workable. Reg D would be narrow on the US side. Step 4, tax substance. A Luxembourg AIF with a Singapore distribution overlay produces a familiar substance pattern for the target investor base.

The sequenced 18-month rollout. Months 0-6: launch in Luxembourg under AIFMD with the permissioned-blockchain wrapper, using the existing Luxembourg fund administrator and a transfer-agent counterparty experienced with tokenised wrappers. Months 6-12: expand to Singapore as a Restricted Scheme to accredited investors via local distribution partnerships with DBS and UOB, with the same fund-of-funds or feeder structure that other EU asset managers have used. Months 12-18: assess Hong Kong professional-investor offering once the Singapore intake is settled. Defer the US because a Reg D layer requires structural changes to the fund and the firm does not have a US distributor. Defer Japan because offshore-fund offering rules add lead time that the 18-month window does not absorb.

Red flags

  • Launching in your most-aspirational market first. The US is often the wrong first launch for a non-US asset manager because the structural lift on the wrapper is non-trivial and the addressable wallet count under Reg D is narrower than the press release suggests.
  • Underestimating local-distributor lead time. Onboarding a private-bank distributor in Singapore or Hong Kong takes three to six months minimum, longer if the bank's product committee has not previously cleared a tokenised version of your asset class.
  • Assuming MiCA passport works for tokenised securities. It does not. MiCA covers asset-referenced and e-money tokens; tokenised securities sit under MiFID II and the corresponding national securities laws, with no equivalent passport for the tokenised wrapper.
  • Cross-listing your token across jurisdictions without legal-control coordination. If the chain entry is the operative record in jurisdiction A but only a derivative reference in jurisdiction B, the token's holders end up with structurally different legal claims depending on where they bought. Resolve the legal-control mapping (see Tokenisation, legal control by jurisdiction) before the cross-listing.
  • Ignoring transfer-agent obligations in jurisdictions that require them (see Transfer agent in the tokenisation context). The US, the EU, and Singapore each treat the transfer-agent function differently, and a transfer agent licensed for one is not automatically usable for another.

Related

Weekly briefing

Sunday evening Singapore time. Importance-3 items, one deep dive, what's worth watching next.