The correspondent banking system is slow, opaque, and expensive. Your cross-border payments still route through multiple intermediaries, each adding latency and fees. Project Agora's recent trials show that tokenized commercial bank deposits and central bank reserves can operate on a shared interoperable platform. But what does that mean for your compliance program when this infrastructure moves from testing to production?
If your institution is involved in cross-border payment processing, you need a framework for evaluating tokenized deposit integration before regulatory requirements force rushed implementation. This guide walks through the operational and compliance steps.
The Problem: Why This Matters Now
The correspondent banking model creates compliance gaps you're already managing. Each intermediary bank in the chain maintains separate KYC records, applies different screening thresholds, and operates under distinct regulatory regimes. You can't see the full transaction path in real time, making sanctions screening reactive rather than preventive.
Project Agora has buy-in from over 40 private financial institutions, and the Bank of Canada recently joined central banks from the US Federal Reserve, Bank of England, South Korea, Mexico, and Japan. BIS Deputy General Manager Andrea Maechler emphasized that further testing is required before global scaling, but the direction is clear: tokenized money will integrate into regulated payment rails.
Unlike stablecoins issued by private entities like Circle or Tether, tokenized deposits operate within your existing regulatory framework. That means your AML/KYC obligations don't disappear, they evolve. You'll need to adapt transaction monitoring rules, update sanctions screening logic, and revise your customer due diligence procedures to handle real-time settlement on shared ledger infrastructure.
What You Need Before Starting
Before assessing tokenized deposit integration, establish your baseline:
Regulatory inventory: Document every jurisdiction where you process cross-border payments. List the AML/KYC requirements, sanctions screening obligations, and reporting thresholds for each. Include FATF Recommendations compliance status and any mutual evaluation findings that affect your correspondent relationships.
Current correspondent banking map: Chart every intermediary bank in your cross-border payment flows. Note where you rely on their KYC, where transaction visibility ends, and where you depend on their sanctions screening.
Transaction monitoring rules: Export your current cross-border payment monitoring scenarios. Identify rules that depend on correspondent bank data feeds, delayed settlement confirmations, or multi-day transaction windows.
Technology stack assessment: Inventory your core banking platform, payment switch (if you operate ISO 8583 infrastructure), sanctions screening engine, and transaction monitoring system. Determine API capabilities and whether your vendor roadmap includes tokenized asset support.
Legal and compliance sign-off: Secure written approval from your chief compliance officer and general counsel to proceed with an evaluation framework. Tokenized deposit integration will trigger Bank Secrecy Act (BSA) program updates and potentially new Suspicious Activity Report (SAR) filing scenarios.
Step-by-Step Implementation
Phase 1: Compliance Framework Adaptation
Start with your AML/KYC program. Tokenized deposits settle in real time, eliminating the multi-day float where you currently conduct post-transaction screening.
Update your risk assessment: Add a section covering tokenized deposit transactions. Address how real-time settlement changes your ability to freeze suspicious payments, how shared ledger visibility affects your independent verification obligations, and whether tokenization introduces new typologies for structuring or layering.
Revise sanctions screening logic: Your current screening likely runs at multiple points, initial payment instruction, correspondent bank handoff, and final settlement. With tokenized deposits on a shared platform, you'll screen once before committing the transaction to the ledger. Test whether your screening engine can handle sub-second latency requirements without introducing false positives that block legitimate payments.
Modify SAR procedures: Real-time settlement means you can't file a SAR and continue processing while you investigate. Document how you'll handle suspicious activity detection when the transaction completes instantly. Consider whether you'll need to implement pre-transaction risk scoring that blocks high-risk payments before ledger commitment.
Phase 2: Technical Integration Planning
Your payment infrastructure wasn't designed for shared ledger architecture. Plan the integration points:
API layer: If you participate in a tokenized deposit platform, you'll interact through APIs rather than SWIFT messaging. Map your current ISO 8583 transaction flows to the API calls required for tokenization, settlement, and confirmation. Document authentication requirements, expect Multi-Factor Authentication (MFA) and Role-Based Access Control (RBAC) at minimum.
Key management: Tokenized transactions require cryptographic signing. Establish key generation, storage, and rotation procedures that meet FIPS 140-3 standards. Implement Split Knowledge for any Key Encryption Keys (KEKs) used to protect transaction signing keys. Your data encryption keys (DEKs) should never exist in plaintext outside a hardware security module.
Transaction monitoring integration: Your monitoring system needs real-time access to tokenized transaction data. Build connectors that ingest ledger events, normalize them to your existing transaction schema, and trigger your monitoring rules without introducing latency that delays settlement.
Phase 3: Operational Procedures
Document the operational changes before you process your first tokenized transaction:
Customer onboarding: Update your KYC procedures to explain tokenized deposit functionality. Customers need to understand that their cross-border payments will settle in real time and that reversal procedures differ from traditional correspondent banking.
Staff training: Train your operations team on tokenized transaction monitoring, exception handling, and escalation procedures. They need to recognize when a transaction is pending on-chain versus settled, how to interpret ledger confirmations, and when to escalate to compliance.
Incident response: Revise your incident response plan to cover tokenized payment scenarios. Address how you'll handle failed transactions, disputed settlements, and potential smart contract vulnerabilities if the platform uses programmable logic.
Validation: How to Verify It Works
Before processing live customer payments, validate your integration:
Test sanctions screening: Submit test transactions involving sanctioned entities, Politically Exposed Persons (PEPs), and high-risk jurisdictions. Confirm your screening engine blocks these transactions before ledger commitment. Measure screening latency, if it exceeds your settlement window, you'll need to optimize or implement pre-screening.
Verify monitoring rules: Generate synthetic transactions that should trigger your monitoring scenarios, rapid movement between jurisdictions, unusual counterparties, structuring patterns. Confirm alerts fire correctly and that your team can investigate without access to traditional correspondent bank documentation.
Audit key management: Have your internal audit team verify that cryptographic keys are generated, stored, and rotated according to your procedures. Confirm that no single individual can access transaction signing keys without Split Knowledge controls.
Regulatory reporting test: Submit a test SAR covering a tokenized deposit transaction. Verify that your narrative includes all required elements and that FinCEN's BSA E-Filing System accepts the submission format.
Maintenance and Ongoing Tasks
Tokenized deposit infrastructure will evolve. Plan for continuous adaptation:
Quarterly rule review: Every quarter, analyze tokenized transaction patterns and adjust your monitoring rules. Look for new typologies that exploit real-time settlement, such as rapid cross-border movement designed to evade jurisdiction-specific controls.
Vendor roadmap tracking: Monitor your core banking and sanctions screening vendors' tokenization roadmaps. If they're not building native support, you'll need alternative integration strategies.
Regulatory monitoring: Track guidance from FinCEN, OFAC, and FATF on tokenized payment instruments. When new requirements emerge, update your procedures before enforcement actions begin.
Platform governance participation: If you join a shared tokenized deposit platform, participate in governance decisions. Protocol changes, screening standards, and settlement finality rules directly affect your compliance obligations.
BIS Deputy General Manager Andrea Maechler noted that further testing is needed before global scaling. That testing window is your opportunity to build the compliance and operational foundation before tokenized deposits become standard infrastructure. Start now.
