Connecting tokenized deposits across private ledgers, public Layer 2 solutions, and real-time gross settlement (RTGS) systems isn’t just some far-off fantasy anymore; it’s actually happening! Regulators are looking forward to this shift, especially with the ISO 20022 transitions and the disclosure deadlines coming up in 2026. It's becoming a reality, and we can expect to see some exciting developments on the horizon! Alright, here’s the scoop on how to keep everything running smoothly--making sure it’s interoperable, easy to audit, and still brings in the profits, all while keeping your procurement plans on the right track and protecting those settlements.

Bridging the Gap: Interoperability Solutions for Tokenized Deposits

In the finance world, especially with all the buzz around digital assets, one big challenge we’re running into is making sure that different systems can actually communicate with each other smoothly. And that's where interoperability really steps in. When we dive into the topic of interoperability solutions for tokenized deposits, we're really focused on finding ways to help different platforms connect and do business with each other more smoothly. It's all about making communication and transactions as seamless as possible!

Why Interoperability Matters

With more people and institutions diving into tokenized assets, it's becoming really important to have a solid system in place. Here are a few reasons why interoperability is so important:

• Efficiency: When systems can seamlessly share data and make transactions, it really speeds things up! Say goodbye to the days of waiting for those transfers to go through!
• Accessibility: Thanks to interoperability, users can tap into a wider variety of services without getting stuck dealing with annoying compatibility problems.
• Innovation: When various platforms team up, it really sparks new ideas and services that can make the user experience so much better.

Current Solutions

There are a bunch of different ways to boost interoperability when it comes to tokenized deposits. Here are a few highlights worth mentioning:

1. Cross-Chain Protocols: These cool systems let various blockchain networks chat with each other, making it super easy to transfer assets without needing any middlemen.

2. Atomic Swaps: So, this cool tech lets you swap cryptocurrencies directly with someone else, even if they’re on different blockchains. The best part? You don’t have to depend on a centralized exchange to make it happen!

3. Interoperability Standards: Having common standards in place makes it a lot easier for different systems to work together. It kind of lays the groundwork for what they can all do.

4. Middleware Solutions: Think of these as the connectors that help different systems communicate. They offer APIs and various interfaces that simplify the way these systems interact with one another.

Challenges Ahead

We’re definitely making progress, but there are still a few bumps in the road.

• Security: When you have several systems chatting with each other, making sure that all transactions are secure is super important.
• Scalability: With more and more people diving into the tokenized world, it's super important for systems to manage those growing numbers without any hiccups.
• Regulatory Compliance: Dealing with the different regulations in each area can make it tricky to achieve smooth interoperability.

Final Thoughts

When we talk about interoperability for tokenized deposits, it’s not only a tech issue. It’s really about making finance easier to access and more inclusive for everyone. As we dive into these solutions and face the challenges right on, we're getting closer to creating a financial ecosystem that's more connected than ever. Let’s keep exploring and see what amazing places this adventure leads us to!

You've definitely made some great strides with tokenized deposits in the sandbox! However, there are still three major challenges that are keeping the execs from giving the green light.

• Bridging legacy and ledger gaps: It's super important to make sure that ISO 20022 flows can kick off actions on the blockchain, and the other way around too. So, we all know that the whole cross-border MT thing wrapped up back in November 2025, right? And now, with more Fedwire ISO 20022 updates on the way by November 16, 2026, it's super important for you to get that camt/pacs mapping just right. If you want to stay on top of your game, you'll definitely need to hit those operating windows! For more details, take a look at swift.com. You'll find some great info there!
• Cross-chain fragmentation: Imagine this--your deposit token is super effective on one network, but all your partners are vibing with a completely different one. It’s like being in a group chat where everyone’s speaking a different language! You may be working with something like Canton, which is more on the permissioned side, while they’re all about Base and EVM L2. It's definitely a tricky situation! On the bright side, Swift has figured out how to move tokenized value between different public and private chains. However, it seems like your current internal tools just aren't quite up to the task. If you're interested, you can check out their findings over at swift.com. It’s pretty fascinating stuff about blockchain experiments and how they’re opening up new possibilities for tokenization!
• Compliance is outpacing code: So, back in 2025, regulators decided to ease up on the whole "pre-approval" thing for banks working with crypto, which was a big deal. But just to keep things interesting, Basel's new crypto disclosure framework is gearing up to launch on January 1, 2026.
  Governance is on the lookout for telemetry that's easy for machines to read and ready for pillar-3 across all chain hops. They're really focused on making sure that any personal identifiable information (PII) stays safe and secure. If you’re looking for more info, check out fdic.gov. They’ve got all the details you need!
• Missed program milestones: So, it looks like we’ve hit the end of the CBPR+/ISO 20022 coexistence period. What this means for all of us is that we can finally say goodbye to those manual MT/ISO mapping workarounds when dealing with cross-border transactions. No more juggling those old methods! Once the cutover happens, it's really important to have your post-fallbacks all neatly organized and planned out. If you slip up here, be ready for a mountain of reconciliation backlogs and exception queues piling up by Monday morning. If you want to dive deeper, head over to swift.com for all the juicy details! Hey there! So, with Fedwire's 2026 release coming up soon, it's time to start wrapping your mind around some new ways to structure those address and investigation messages. If your tokenized cash leg isn't consistently managing these fields, you’re going to have a tough time getting your “always-on” claims through UAT. Check out more info on this over at frbservices.org. There’s a lot to explore!
• Regulatory whiplash:
• U.S. Banking agencies just made an important announcement: banks are now free to jump into tokenized assets without having to get any approvals beforehand. It sounds like your board is hoping to see those pilot programs transition into full production by 2026, and they definitely want to make sure there are solid risk controls in place when that happens. If you want to dive deeper into this topic, just head over to fdic.gov for more information. Basel is really making waves with their new disclosure plans and updated prudential standards for 2026. They're tightening the rules, especially when it comes to stablecoins. So, your treasury, finance, and risk teams need to hit the ground running with machine-readable controls and a good stockpile of digital money objects (DMOs) right from Day 1. For more info, you can check out bis.org.
• You can’t hold off on market proof: Citi is already handling billions in transactions through their Citi Token Services in places like the US, UK, Hong Kong, and Singapore. That's pretty impressive! They’ve got around-the-clock USD clearing set up and are now working on adding euro integration, too. This is the real deal: cross-border tokenized cash happening right now! If you're not keeping pace with others who are diving into this, don't be shocked if your partners start bypassing you. Learn more at citigroup.com.
• J.P. Morgan just rolled out a new USD deposit token called JPMD on a public Layer 2 (Base). They’re also joining forces with Mastercard and some market-makers to get things moving right from the start. This is really shaking things up for how we think about “bank money on public chains.” Just a heads up, your network isolation strategy comes with its own set of trade-offs. For all the latest info, check out jpmorgan.com.

To keep production deployments as safe as possible, we’ve set up a five-layer architecture. This setup connects ISO 20022 messaging, permissioned networks, and public L2s. It's all about reducing risks while we work! This setup is built on reliable interoperability standards and top-notch security measures that you'd expect from a bank.

1) Money Object Layer (Solidity + policy controls)

• Objective: We're on a mission to create deposit tokens that work as governed “digital money objects” (DMOs). You'll see top-notch security measures for transfers, keep an eye on sanctions, and make sure that redeeming is a breeze across various blockchain networks.
• Design:
• Standards: We’re going to go with ERC-20 compatibility because it makes integrating with the tools we already use a breeze. On top of that, we're going to throw in some transfer-restriction modules that follow the ERC-3643 standard (we’re calling it T-REX). This means we'll be able to set up allowlists, manage split balances, and do compliance checks in real time. Sounds pretty cool, right? Oh, and just so you know, DTCC jumped on board with the ERC‑3643 Association back in 2025. It's a pretty solid move that shows they're all in when it comes to adopting token standards that prioritize compliance. (dtcc.com).
• Identifiers: We're planning to add ISO 24165 DTI and Functionally Fungible Group DTI metadata. This will make it easier for supervision tasks and help us whip up some machine-readable reports that are a lot like those under MiCA. (iso.org).
• Upgrades and controls: We'll be using the EIP-1967 proxy for any upgrades, and just to be safe, we're putting some solid upgrade guardianship measures in place. We’re also going to throw in some emergency pauses and circuit-breakers that will be linked to specific incident runbooks.
• How we deliver:
• Our awesome team is all set to take care of the smart contract engineering for you. If you're curious about what we have in store, take a moment to explore our smart contract development services and our security audit offerings. There’s a lot we can do to help you out!

2) Messaging & Interop Layer (provable cross‑chain)

• Objective: We want to make sure that we can move value and share instructions securely between different networks, like Canton (private) and EVM L2 (public), without getting tangled up in the sketchy business of trying to “build your own bridge.” ”.
• Design options (choose what fits your risk tolerance and partnerships best):
• Public-public and public-permissioned: We're diving into Chainlink CCIP, which comes with a risk management network and some nifty ISO 20022 workflow triggers. Check this out: there have been some really cool pilots with Swift and UBS where they've successfully transferred tokenized value across different chains. It's pretty impressive! Take a look at this: (prnewswire.com). It's worth checking out!
• Permissioned-permissioned: So, for this choice, we’re looking at the Canton Network. This one really shines when it comes to keeping things private during multi-app settlements. We've seen some exciting progress lately with collaborations between DTCC and Euroclear, along with a bunch of multi-institution pilots. It’s clear that there's genuine momentum building around collateral and the movement of tokenized securities. If you want to dive deeper into the details, check this out: (blog.digitalasset.com). You'll find some good info there!
• Different cross-chain options to explore: We're looking into alternatives like Axelar, LayerZero, and IBC. We’re keeping a close eye on them all, weighing the risks in a similar way. We’ve really nailed down our selection process by using cross-chain datasets from 2025 and diving deep into research on failure containment. We're all about substance here, not just flashy marketing talk. Want to explore our findings in more detail? Check it out here: (arxiv.org).
• How we get it done: We’re all about making things run smoothly across different networks. We work our magic with cross-network orchestration and offer adapters through our cross-chain solutions and blockchain bridge development. It's all about connecting the dots for you!

3) Off‑chain Payment Workflow Layer (ISO 20022 ⇄ on‑chain)

• Objective: We’re aiming to ensure that pacs and camt can be easily mapped to processes such as token minting and burning, escrow, payment-versus-payment (PvP), as well as corporate actions. We want this to be a smooth experience for everyone involved!
• Design:
• “Message-first” orchestration: We really focus on handling Swift CBPR+ ISO 20022 messages (after the coexistence period) as well as the Fedwire ISO 20022 variations. This lets us jumpstart on-chain actions using a platform like CRE. By using this method, we can keep up with Swift's cool experiments in making tokenized assets work well together. Check it out here.
• RTGS sync: We’re getting everything ready for some cool experiments that sync RTGS with DLT, like what Meridian FX and Rialto are doing. Our goal is to ensure that payment-versus-payment transactions have that solid guarantee of settlement finality. If you want to dive deeper into the details, just check it out here.
• How we deliver:
• We're here to help you connect your systems with your Swift gateway/core through our awesome blockchain integration services.

4) Privacy, AML/CFT & Audit Layer (ZK + Travel Rule telemetry)

• Goal: Prove that we're following the rules while keeping our clients' identities a secret.
• Design:
• ZK-KYC attestations: We're looking to weave zero-knowledge credentials directly into our transfer hooks. So, basically, we’re only going to share the info related to FATF R. It all depends on the transaction size and the specific corridor. We just need to be a bit picky about what we disclose. Hey, just a heads-up - the FATF has made some updates to R. In 2025, we’re rolling out some updates to make it easier and safer for senders and beneficiaries by simplifying the way their information is handled. This should help prevent fraud and make the whole verification process a lot more secure. (fatf-gafi.org).
• Travel Rule ops: We’re working on linking up with VASP discovery and making it easier to exchange payloads. In 2025, we saw a huge jump in industry compliance, which really helped reduce those frustrating false starts with our counterparties. (coindesk.com).
• Machine-readable disclosures: We’re working on some data exhaust that matches up with the Basel crypto disclosures set for 2026, as well as the ongoing Basel discussions about machine-readable Pillar 3. This way, the Risk team can smoothly pipeline metrics without the hassle of fiddling with PDFs. (bis.org).
• How we deliver: We've got some pretty cool stuff going on with our security audit services, like policy-aware token logic and audit trails. Plus, we throw in compliance automation as a part of our web3 development services. You can check it all out here and here!

5) Operations & Resilience Layer (runbooks > whitepapers)

• Goal: Make sure our tokenized cash is up and running around the clock, providing top-notch service that meets banking-quality standards.
• Design: We're really into crypto-agility and key rotation, especially since we're following NIST's 2025 guidelines for staying flexible in our crypto strategies. So, when we're talking about interoperability paths, it's really crucial to nail down the Recovery Time Objective (RTO) and Recovery Point Objective (RPO). This way, if we hit any bumps along the way, we can manage things smoothly. If something goes off track, we'll hit pause on those cross-chain transactions, but don’t worry, same-chain redemptions will still keep rolling. It's all about keeping everything running as smoothly as possible! If you want to dive deeper into the details, feel free to check it out here. It’s got some great info for you!
• Monitoring: We'll be watching the chain state closely and keeping tabs on the ISO 20022 queue to make sure everything's running smoothly. Every night, we'll check to make sure that the DTI-tagged on-chain events match up with their off-chain postings. It's all about keeping things in sync and making sure everything fits together just right!

What “Good” Looks Like in 2026: Patterns We Implement

• Multi‑rail deposit tokenization Imagine it this way: we’ve got this public Layer 2 train line (kind of like Base) that runs 24/7, allowing for quick settlements and bustling with liquidity from the ecosystem. Then, on the other hand, we have a more private rail system (similar to Canton) designed for those close-knit, data-light transactions, whether it’s between two parties or a whole group. These two rails are totally connected thanks to a trustworthy cross-chain protocol. J.P. Morgan's JPMD on Base and DTCC's plan for tokenization by 2026 show us that this dual-rail world isn't just some far-off fantasy--it's actually unfolding right before our eyes! (jpmorgan.com).
• ISO‑native triggers Picture this: what if all those corporate actions, like subscriptions, redemptions, and cash sweeps, could just start rolling out automatically from ISO 20022 messages? How cool would that be? These messages can trigger smart contract functions, similar to what we've observed in the Swift/UBS pilot programs. The great thing is, your operations team doesn’t even have to get into the nitty-gritty of “web3.” They can stick to their usual messaging, and everything runs like a charm on the chain! (coindesk.com).
• Player vs. Player action and synchronized settlement. Hey team! Just a quick note: when we're handling FX and collateral transactions, let’s definitely incorporate Payment versus Payment (PvP). We’ve learned some important lessons from BIS Meridian/Rialto that we shouldn’t overlook. Say goodbye to those “one-leg settles alone” deals! This really starts to matter when we get into using tokenized deposits along with tokenized treasuries and collateral. (bis.org).
• Identifiers and reporting So, we're looking at a way to weave DTI/LEI straight into the token metadata and event logs for those supervisory filings. It's all about making things smoother and more efficient! So, this basically means we’re all set to have that MiCA-style machine-readable data and the ESMA interim register practices up and running. Even if you're mainly focused on the U.S. Getting these identifiers synced up now will really save you a bunch of headaches later on. Trust me, it’s worth it! (eur-lex.europa.eu).

24/7 Cross-Border Liquidity Hub (USD/EUR) for Intraday Netting

Setup

• Tokens: We're utilizing USD and EUR deposit tokens on a permissioned ledger to make those bilateral sweeps super smooth. Oh, and by the way, there’s a USD mirror on Base that you can use for settling within the ecosystem. Cool, right?
• Triggers: That's where the real magic happens, thanks to pacs. 009/camt. You’ve got 056 ISO 20022 messages that start the whole minting and burning process, plus the player-versus-player action happening across different platforms.
• Interop: Imagine CCIP but for messages that are public and permissioned, combined with Canton sync for those private networks.

Why Now

Citi is really making a splash with live volumes in the US, UK, Hong Kong, and Singapore. They've got this awesome 24/7 USD clearing system in place, plus a strong presence in the EU, and it’s all paying off! If you want your liquidity operations to really stand out, they’ve got to be ready to work with other systems. Check it out here!.

Procurement-Ready Scope Items

Alright, here’s what we need for the UAT exit criteria: we want to see the Player vs. Player (PvP) for EUR to USD, and it's important that the ISO-triggered on-chain settlement goes down in under 2 seconds at the 95th percentile during our network partition tests. Let's nail this! ”.

2) UK Mortgage Remortgaging + Tokenized Deposits for Fraud-Reduced Disbursements

• Setup: We're planning to take the UK Finance tokenized sterling pilot and use it to send out remortgage proceeds as programmable deposits. What this means is that the title release and the transfer of funds occur simultaneously. If you're curious to learn more about it, feel free to click here for all the details!
• This plan really fits with what the Bank of England has in mind for RTGS "synchronization." We’re gearing up to follow the BoE’s Synchronisation Lab approach, and we should have some updates ready by 2026. If you're curious, you can check it out here. It’s got some really interesting insights!
• Compliance Knobs:
• We're going to include the FATF R. There are 16 payloads that go along with the payment messages. On top of that, we're rolling out zero-knowledge proofs for KYC status. This way, we can keep your personal data away from the blockchain. Super handy, right? If you want to dive deeper into this topic, take a look at this link: FATF Recommendations. It’s got all the nitty-gritty details you might be interested in!

3) Collateral Mobility: Tokenized Treasuries vs. Tokenized Deposits as Cash Leg

• Setup:
• Get excited to connect with a DTCC-approved tokenized U.S. The Treasuries scene is really gearing up to take off in the second half of 2026, and it’ll be powered by your deposit token. What this means is that you can easily switch out collateral and manage margin calls right away. If you want to dive deeper into the topic, you can find all the details here. Hey! So, if you're thinking about settlement on Canton, it might be a good idea to go with permissioned options. Also, you might want to look into adding CCIP or maybe even a reliable gateway. That way, you can let public L2 liquidity move freely where it's permitted. Just a thought! If you’re looking for more details, check out this blog post. It's packed with insights that you won’t want to miss!
• Outcome: If you go ahead and make this change, you’ll notice a big drop in failures because of cut-offs. Plus, you’ll be in a much better spot to make those “same-minute” collateral moves when things happen in the U.S. and EU markets overlap.

4) Public-Chain Market Connectivity, Safely

• Setup: How about we go ahead and mirror those deposit tokens to Base? It’ll really help ramp up liquidity for the ecosystem. Of course, we’ll make sure to implement some smart policy contracts to keep everything in check. We're really diving into JPMD's strategy to see if public L2 is a good fit for banking funds. If you want to dive deeper into the details, just click here. It’s a great resource!
• Guardrails:
• When it's time to pick a bridge, we'll dive into the cross-chain datasets from 2025. We're also planning to roll out some really effective failure-containment methods and circuit-breaker patterns, all based on the newest research out there. If you’re curious and want to explore this topic a bit more, check out the findings right here. It's got some interesting details!

Emerging best practices we recommend adopting in 2026 SOWs

• Get on the same page with identifiers and metadata: Just a heads up--make sure to include ISO 24165 DTI and LEI in your token metadata, as well as in your event logs for actions like transfers, minting, and burning. It’s a good practice that can save you some hassle down the line! It totally fits in with the EU’s machine-readable requirements and on top of that, it really simplifies those Basel Pillar 3 data pipelines. (eur-lex.europa.eu).
• Give ISO messages top priority: Make sure to set aside some time to jot down how your pacs/camt fields map to the contracts. It's definitely worth it! Oh, and make sure you keep in mind the SR2025 CBPR+ cutover behaviors when you’re designing things. Plus, don’t overlook the changes coming to Fedwire in 2026, like the removal of unstructured addresses and the improvements to investigations. It’s really important to incorporate these updates! Don’t forget to include these details in your UAT playbooks! (swift.com).
• Separate interop concerns: Think of the idea of “value and message moving together” as something you just can't overlook. It's super important! Don't just go for bridges that only move tokens around without any clear instructions you can trust. The Swift/Chainlink pilots really demonstrate how ISO triggers can set off on-chain actions in a pretty controlled manner. It's cool to see this in action! (coindesk.com).
• Engineer for crypto-agility: Make sure to keep NIST’s 2025 crypto-agility guidance top of mind when you’re considering key rotation, algorithm flexibility, and running deprecation drills. It’s really important to stay on track with these! It’s a good idea to frame these as SLA metrics instead of just a simple checklist of tasks. ” (csrc.nist.gov).
• Model PvP early: Hey, just a quick reminder! Make sure to add those BIS Meridian/Rialto PvP designs into your integration tests. This way, we can ensure that the FX legs don't end up settling in just one direction. This is definitely going to catch the attention of regulators and auditors alike. (bis.org).
• Prefer production-proven rails:
• Focus on networks and patterns that have already gained some solid backing from institutions. For example, check out CCIP for cross-chain solutions, Canton when it comes to permissioned privacy, and Base if you're into public liquidity. These are spots where your counterparts are probably already spending their time. (swift.com).
• Who this is for:
• This is specifically for Heads of Payments Architecture, CTOs in Transaction Banking, leaders in Treasury & Liquidity Ops, program directors handling RTGS/ISO 20022, and Procurement leads at top-tier banks and Financial Market Infrastructures.
• What they’re looking for in your RFP/SOW: Make sure to toss in phrases like “CBPR+ mapping” and “pacs.” 009/camt. Sure thing! Here’s a more casual take on that:

Alright, so let’s break down some of these terms you might come across:

• 056 orchestration involves coordinating various processes to make things run smoothly.
• Then there’s DTI/LEI tagging, which is all about labeling data so it’s easily identifiable.
• PvP settlement and settlement finality? That’s just a fancy way of saying ensuring that transactions are completed securely and can’t be reversed.
• Intraday liquidity buffers are basically safeguards we set up to manage cash flow throughout the trading day.
• On to Extended RTGS hours -- that's just extending the time for real-time gross settlement so people have more flexibility.
• Consider the synchronisation interface a vital connection point that keeps everything in sync.
• When we talk about machine-readable Pillar 3, we’re discussing regulatory disclosures that can be easily processed by machines.
• BAFO-ready TCO means gearing up for the best and final offers in terms of total cost of ownership, just to keep things competitive.
• And then there’s RTO/RPO for cross-chain incidents, which refers to recovery time objectives and recovery point objectives when dealing with issues across different blockchains.
• As for three lines of defense controls, that’s a nice way of outlining risk management strategies to keep everything secure.
• Finally, KRI/KPI for exception queues refers to key risk indicators and key performance indicators that help track and manage any exceptions that pop up.

Hope that gives you a clearer picture of what these terms are all about! ”.

How 7Block Labs Executes (And Why Enterprises Choose Us)

Plan

• 2-Week Interop Readiness: We start by diving into all the ISO 20022 connections, figuring out which corridors are the most important, and putting together a shortlist of interop options with a risk score for each. It’s all about getting a clear picture of where we stand and what needs our attention!

Build

• 8-12 Week MVP: Here’s where the fun begins! We’ll help you set up those governed deposit token contracts, complete with DTI/LEI metadata. We’ll also wire in ISO triggers, set up your PvP workflows, and make sure everything's rock solid with some attack-path tests and crypto-agility drills. Exciting stuff, right?
• Ready to explore more? Take a look at our custom blockchain development services, our awesome web3 development services, and check out our blockchain integration options. You won’t want to miss these!

Secure and Scale

We're all about keeping things secure! You can look forward to some thorough security audits, tests for the Travel Rule payload, and even pilots for RTGS sync. On top of that, we offer ongoing runbooks and SLAs as part of our security audit services and cross-chain solutions. We've got your back covered there!

Extend

• As your needs change, we've got your back when it comes to growth! You can totally add bridges or rails based on what your partners need, and you can also work in some tokenized collateral or securities flows using those DTCC or Canton-style setups. Hey, just a quick reminder to swing by and check out our asset tokenization services and our dApp development options! You won’t want to miss them!

Proof it works: GTM metrics you can take to ExCo

• Time to Pilot: We’re aiming to wrap things up in about 12 weeks, getting us from the Discovery phase to our MVP. We'll have everything in place for ISO 20022 triggers and PvP tests, all housed in a secure setup. Exciting times ahead! And on top of that, our Statement of Work (SOW) is really straightforward for procurement. It has clear User Acceptance Testing (UAT) milestones that are easy to track and measure!
• Compliance-by-design: We’ve integrated machine-readable metrics that meet Basel's 2026 crypto disclosure guidelines, and we’ve also nailed down the Travel Rule payload validation. Say goodbye to the hassle of “spreadsheet glue!” If you want to dive deeper into this, you can find more info here.
• Counterparty reach: We're simplifying the process for connecting with banks that have active tokenized cash systems. Citi’s rolled out 24/7 USD clearing, which is pretty awesome, and they're also branching out into euros. Plus, we’re linked up with public L2s like Base, where JPMD is already up and running. Check out all the juicy details here. You'll find some interesting insights about Citi's latest moves in integrating their token services with around-the-clock USD clearing and real-time cross-border payment solutions. It’s all about enhancing liquidity management, and trust me, it’s worth a look!
• Ops resilience: We’ve put together our Recovery Time Objective (RTO) and Recovery Point Objective (RPO), and we've also been running some crypto-agility drills to stay in line with NIST's guidance for 2025. We've built our systems to smoothly tackle any cross-chain issues that might pop up. If you want to dive deeper into this topic, check it out here. It’s got some great info!

Brief In-Depth Details: Technical Stack Snapshot

• Contracts
  We're working with Solidity and using an EIP-1967 proxy, plus a role-gated policy engine. This setup has got some checks for solvent transfers and includes a list of approved jurisdictions. Plus, there are a few rules inspired by ERC-3643 that add an extra layer of restrictions. Every cash-leg event brings along some event logs that give you the lowdown on DTI and LEI. If you're interested, you can dive deeper into the topic here. It's a great read!
• Interop
  For both public and private messaging, we’ve got CCIP set up, and it also includes independent risk monitoring. Also, Canton synchronization helps keep your app's privacy in check while making sure that settlements are predictable. If you want to learn more, check this out here.
• Off-Chain Adapters
  We're using ISO 20022 parsers (like pacs and camt) to translate on-chain function calls at runtime, similar to what they tried out in the Swift and UBS pilots. It’s pretty exciting to see how this all comes together! Hey, just a quick reminder about the Fedwire-specific address handling that's set to roll out in 2026! If you're curious and want to dive deeper, you can check out all the details here. Don't miss it!
• PvP
  We use a two-phase commit process that includes hashed time-locks or state-proof gating. Settlement only happens when both sides of the transaction check off all the finality requirements, just like how Meridian/Rialto has it set up. If you're interested, you can check out more details here. It’s definitely worth a look!
• Privacy & AML
  We're really into zero-knowledge (ZK) credentials for selective disclosure, and we’re also working on implementing a Travel Rule payload exchange. We've got policy templates that are designed to align with the latest updates from FATF R. 16 guidance. Get the scoop here.
• Ops
  We keep a close eye on ISO message queues and track events throughout the chain. Our Key Management System (KMS) is super flexible when it comes to crypto, and we make sure everything runs seamlessly with our key ceremonies. At the same time, we’re busy checking out the latest security research for cross-chain setups, so we can validate our graceful degradation patterns for 2025-2026. Want to dive deeper? Check it out here!

What’s Changed Since January 2026--and Why It’s Key for Your Roadmap

• Regulatory timelines are a big deal: Hey there! Just a heads up: Basel's new framework for disclosing cryptoassets is set to kick in for the 2026 reporting period. Exciting times ahead in the world of finance! Also, there's a consultation happening on machine-readable formats that goes all the way until March 2026. So, if you haven't already, now's the perfect time to get your data in order! (bis.org).
• Messaging cutovers happened:
  So, Swift’s CBPR+ coexistence is finishing up in November 2025, and right after that, Fedwire is set to roll out its next batch of ISO enhancements in November 2026. Just a heads-up: make sure your deposit tokens are ISO-native! (swift.com).
• Production proof exists:
  Citi's tokenized cash services and JPMD on Base are proof that your colleagues are already working across various platforms. Oh, and just a heads-up--DTCC’s tokenization service launching in 2026 is going to really streamline those “cash vs collateral” workflows. Basically, your deposit token will act like cash, making everything flow a lot smoother! (citigroup.com).
• Public and private spaces naturally mix: The Swift/Chainlink pilots and Canton’s trials with institutions are really showing us that interoperability is where it’s at. It’s all about connecting different chains instead of betting everything on just one. Just keep this in mind when you’re designing your systems! (swift.com).

Where Our Services Fit Into Your 2026 Plan

• Crafting Strategies and Solutions. If you need assistance with creating architecture blueprints or picking the right corridors, we've got you covered with our blockchain development services. Just reach out, and we'll help you figure it all out!
• Build and Integrate Alright, let’s dive into creating those policy-aware tokens, ISO adapters, and PvP flows together with our web3 development services and blockchain integration. It’s going to be an exciting journey! You can check out what we offer here for web3 development and here for blockchain integration. Can't wait to see what we create!
• Interop and Bridges We're really passionate about making cross-chain orchestration and audits work smoothly! If you want to dive deeper into what we offer, check out our cross-chain solutions development and blockchain bridge development. There's a lot to explore!
• Security, Audits, and Runbooks: Okay, so let’s talk about some important stuff here. Security is key--we want to keep everything safe and sound. Audits help us check our systems regularly, making sure everything’s running smoothly and nothing dodgy is going on. And runbooks? They’re basically our go-to guides for handling different situations. Think of them as our trusty playbook when things get a little crazy. Make sure your operations stay secure with our range of services--everything from threat modeling and ZK attestations to crypto-agility drills and ongoing compliance checks. Check out our security audit services to see how we can help keep things safe and sound!

Personalized, High-Conviction CTA

Hey! If you’re the Head of Payments Architecture or the RTGS/ISO 20022 Program Director at a Tier-1 or Tier-2 bank, and you're involved with the Fedwire release coming up on November 16, 2026, as well as the Basel disclosure deadlines, we’ve got some really cool stuff in store for you!

We're excited to kick off a 10-week Interoperability Accelerator! This program will explore some really interesting topics, like deposit tokens driven by ISO 20022, PvP FX using two different rails (think Base and Canton), ZK-KYC integrations, and DTI-tagged audit logs. It’s going to be a deep dive into some cutting-edge stuff that we can’t wait to share with you! On top of that, we’ll make sure everything fits perfectly with your Swift gateway and your favorite AML vendor.

If you can get that focused RFP approved this month, we’ll whip up an MVP for you that includes the pass/fail UAT criteria. Your procurement team can wrap it up in just one meeting!

Internal Service Links (for your convenience)

Hey there! If you’re interested in web3, take a look at our awesome web3 development services. We’ve got some cool stuff going on!

• Check out our awesome custom blockchain development services!
• Looking for a security check? Check out our security audit services to see how we can help! Are you curious about blockchain integration? Well, you’re in luck--we’ve got everything you need!
• Check out our blockchain bridge development services! We've got some great options for you to explore.
• Take a look at our services for developing cross-chain solutions here. You might find just what you need!
• Let's jump into dApp development together!
• If you want to dive deeper into asset tokenization, check it out here!

References (selection)

Hey, just a heads up--Swift's gearing up for a major shift with the ISO 20022 end of coexistence happening in November 2025. Big changes are on the horizon! (swift.com). Hey, just a heads-up! Fedwire is all set to roll out its ISO 20022 update on November 16, 2026. Pretty exciting stuff! (frbservices.org). So, in 2025, the FDIC, OCC, and the Fed are planning to shake things up a bit. They’re going to let banks jump into tokenized activities without having to get prior approvals. It's a pretty big move! (fdic.gov). Hey, have you heard about the Basel crypto disclosure framework? It's all set to launch in 2026, and it sounds pretty interesting! (bis.org). Citi Token Services is really making strides! They've got live deployments happening and they've set up a 24/7 USD clearing integration. And guess what? They're also branching out into euros. Exciting times ahead! (citigroup.com). JPMD has decided to go with Base, which is the public Layer 2 solution, for handling their settlement needs for institutions. (jpmorgan.com). So, Swift and DLT are teaming up to do some really interesting stuff with tokenization and interoperability. UBS is at the helm of a pilot project that connects ISO messages to actions on the blockchain. Exciting times ahead! (swift.com). So, it looks like DTCC is stepping up with a SEC no-action letter and is gearing up to launch a tokenization service by 2026. They’re also teaming up with Canton on this project, which sounds pretty exciting! (dtcc.com). BIS is sharing some insights about how Meridian FX and Rialto are handling PvP and synchronization for wholesale settlements. (bis.org). There's a lot of excitement about ERC-3643 lately, and it looks like there are some encouraging signs that institutions are starting to warm up to it. (dtcc.com). NIST has put out some guidance about crypto-agility that will roll out in 2025, and it really hones in on how to improve our operational posture. (csrc.nist.gov).

If you're aiming for a great return on investment and a foolproof plan for procurement, we’ve got you covered! We’ll bring in the architects, Solidity engineers, and integration leads straight to your design room. It's all about getting the right team together to make things happen! Once you're done, you'll have a solid interop stack that's good to go and ready to meet any regulatory requirements.