Developing “Facilitator” Middleware: The New Crypto‑to‑Fiat Gateway

Core Keywords We’ll Be Diving Into for This Audience:

ISO 20022 MX (pacs.008/pacs.009) is set to wrap up its SWIFT end-of-coexistence on Nov 22, 2025, and don't forget about Case Management (camt.110/111).
Let’s dive into the nitty-gritty of RTP and FedNow transaction limits, plus how things are shaping up with adoption. And let's not overlook instant credit transfer under the EU IPR!
We’re looking at a transition to the MiCA CASP by July 1, 2026 (but keep in mind, this one is in the hands of the Member States), alongside timelines for ART/EMT enforcement.
What's the scoop on the current status and oversight of the FATF R.16 Travel Rule implementation?
Get ready for the FCA/BoE sterling stablecoin regime, which features a 40/60 reserves setup with those non-remunerated central bank deposits. Expect some exciting updates in their 2026 joint approach!
Here’s what’s new with EMV 3DS 2.3.1.1--think SPC, OOB, and device binding. And yes, it really is the end for 2.1.0.
Curious about Visa and Mastercard’s crypto programs? They’ve got some cool stuff in the works, including Crypto Credential and those stablecoin settlement/payout pilots.
Lastly, keep an eye out for the rollout of Circle CCTP v2 “fast transfer” and the timeline for saying goodbye to V1!

If you're looking to achieve any of those goals, you're in the right place!

The headache you already have (but probably misdiagnosed)

You’ve finally launched your USDC on-ramp and included that handy “withdraw to bank” button. But here’s the kicker: users still aren’t completely satisfied. Here’s the feedback we’ve been getting:

Those “instant” payouts aren’t so instant after all; they’re dragging their feet and taking T+2 to show up. Looks like your ledger is having a real hard time balancing those USDC burns with the RTP/FedNow credits.
EU transactions? Yeah, they’re stuck in limbo because your CASP passporting is still in the works, and the timelines for Member-State grandfathering? Total chaos.
After enabling SCA, you took a hit on card conversions since your 3DS stack is still lingering on versions 2.1/2.2 and doesn’t have SPC or device binding yet.
And just when you thought it couldn’t get any worse, compliance is blowing up your phone with issues related to gaps in the Travel Rule payloads, OFAC concerns popping up with screened addresses, and those pesky mixers making a cameo in your transaction graphs.

Every symptom feels kind of disconnected--like you've got an ACH config hiccup over here and an RPC endpoint glitch over there--but the bigger issue lies in the orchestration as a whole. What you really don't need is just another gateway; what you actually need is a Facilitator.

Why this matters in Q1-Q3 2026 (with dates you can’t miss)

The SWIFT coexistence phase is coming to a close on November 22, 2025. Once that happens, any key MT payment instructions will either get NAK’d or hit you with a conversion fee. Meanwhile, E&I is shifting to ISO case management, with camt.110/111 milestones planned for 2026-2027. If you don't map everything out, your bank files could be out of sync for on-chain redemptions. Check out more details on (swift.com).
Big news for stablecoins: MiCA is officially kicking off! CASP authorizations are set to begin on December 30, 2024, and there are some transitional "grandfathering" rules by Member State that run until July 1, 2026. Countries like Spain have decided to extend their timelines to July 2026, while a few NCAs are wrapping things up sooner. If your EU liquidity or off-ramp depends on just one jurisdiction's grace period, you might want to reconsider your strategy. More details are up on (esma.europa.eu).
Over in the U.K., sterling stablecoins are on the radar with new FCA/BoE rules expected by 2026. The BoE is suggesting a 40/60 split between gilts and non-remunerated BoE deposits for systemic issuers, with a temporary ramp-up to 95% in gilts. It’s a good time to make sure your policy toggles for treasury and reserves are ready to roll. Dive deeper at (bankofengland.co.uk).
The FATF is watching the Travel Rule situation closely as we move into 2024-2025 updates. The rules for Recommendation 16 are tightening up for June 2025. If you’re running a crypto-fiat gateway, you’ll need to ensure you're compliant with exchanging the correct originator and beneficiary metadata, as well as proof of enforcement. Get the latest scoop at (fatf-gafi.org).
Card processing is evolving: the schemes have deprecated 3DS 2.1.0 in 2024, while the new 2.3.1.1 version introduces SPC, OOB, and device binding to help issuers fight CNP fraud without sacrificing user experience. If your on-ramp authentication isn’t compatible with 2.3.1.1 yet, be prepared for some soft declines and possibly higher costs down the line. Get all the details over at (developer.plus.authorize.net).
RTP and FedNow are both upping their game: RTP increased its limits to $10M back in February 2025 and has been smashing daily records with 1.8M transactions. By late 2025 and early 2026, FedNow had already surpassed 1,500-1,600 institutions. This is definitely where you want your “instant to bank” solutions to shine. Check it out at (theclearinghouse.org).
The EU IPR is making progress: instant credit transfers are aiming for a speedy 10-second turnaround, with equal fees and payee verification. This rollout will continue through October 2025 and beyond, setting new expectations for users when it comes to settlement experiences. Learn more at (europarl.europa.eu).
Network partners are moving forward: Mastercard's Crypto Credential is now live in P2P pilots and is taking care of Travel Rule metadata. Visa is also ramping up stablecoin settlement pilots and has been backing USDC on Solana since 2023. Plus, stablecoin payout pilots for creators and gig workers are set to launch in late 2025. Think of these as crucial rails for your gateway rather than just marketing opportunities. Get the full story from (newsroom.mastercard.com).
Cross-chain treasury is stepping into the limelight: Circle CCTP v2 is adding “fast transfer” capabilities and will become the industry standard by 2025, with v1 starting to phase out on July 31, 2026. Make sure your treasury router is geared up for v2. More info at (circle.com).
Don't forget: PCI DSS 4.0 future requirements kicked in on March 31, 2025. This includes things like e-commerce tamper detection, authenticated scanning, and a greater focus on awareness. If you accept cards, on-ramp checkout is definitely part of the mix. Find out more at (bdo.com).

If you're lacking any of those, you're really setting yourself up for blown SLAs, risking your licenses, and possibly leaking costs due to fraud. Believe me, that’s not going to sit well with your CFO!

The 7Block Labs “Facilitator” middleware

Facilitator is a super flexible middleware solution that we take care of for you. Think of it as the link connecting your wallets, KMS, and front-ends to banks, card networks, compliance providers, and ERP systems. It’s not just “another processor” out there. It's really the orchestration layer that makes sure your crypto-to-fiat operations run smoothly, while keeping everything compliant, transparent, and budget-friendly.

Architecture Pillars:

When we think about architecture, a few key elements really tie everything together. Let’s take a closer look at the main pillars that create a strong architectural framework.

1. Scalability

Scalability is all about ensuring your system can grow smoothly. When your user base starts to increase, your architecture should effortlessly adapt to the added load. This way, you can support more users, transactions, or data without any drop in performance.

2. Reliability

You definitely want your architecture to be rock-solid, don’t you? Reliability is all about how well your system can perform consistently over time. It’s crucial to keep downtime to a minimum, making sure that users can access your services whenever they need to. Staying on top of regular maintenance and monitoring is essential for keeping everything running like a well-oiled machine.

3. Security

In today’s world, having a strong security foundation is absolutely essential. Your architecture should come packed with built-in security features to safeguard sensitive data and block unauthorized access. This means using encryption, implementing solid authentication processes, and conducting regular security audits to keep everything safe and sound.

4. Maintainability

Nobody likes dealing with a system that’s a hassle to manage! Maintainability is all about how simple it is to update, fix, or enhance your architecture as time goes by. When maintainability is on point, you’ll experience less downtime and a smoother workflow for making those essential upgrades or changes.

5. Performance

Performance really comes down to speed and efficiency. You want your architecture to serve up quick responses and manage requests effortlessly. This could mean fine-tuning your databases, cutting down on latency, or employing caching strategies to boost the overall user experience.

6. Flexibility

Flexibility is key when it comes to your architecture--it helps you roll with the punches as requirements change. Since tech is always moving forward, you want your system to easily integrate new tools, frameworks, or processes without needing a complete makeover. This kind of adaptability is super important for staying successful in the long run.

7. Usability

Finally, let’s talk about usability--this is all about making sure your architecture is easy to use. It doesn't matter how powerful your system is; if users struggle to figure things out or get lost in the interface, they're not going to stick around. So, it’s super important to prioritize a seamless user experience in your architecture!

Keeping these pillars in mind lets you create an architecture that doesn’t just meet today’s needs but also sets you up for success down the road.

1) Network and Funds Orchestration

Multi-rail payout router: This includes options like RTP, FedNow, SEPA Instant (IPR), SWIFT MX (pacs.008/009), and when it fits the bill, card push-to-card transactions.
Stablecoin rails: We’re rolling with USDC and CCTP v2, which comes with both “standard” and “fast transfer” options. We’ve also added chain-aware slippage and failure retries to keep everything running smoothly, plus we’re keeping things tidy with canonical contract addresses. And don’t worry, we’ve got our v1→v2 migration controls ready to go before July 31, 2026. Take a peek here: (circle.com).
Card/Fiat Bridges: We’ve rolled out some cool plugin adapters for Mastercard’s Crypto Credential aliasing and metadata exchange. Plus, if you’re in the right partner programs, you can enjoy Visa acquirer settlement in USDC and stablecoin payout options tailored for creators and gig workers. Want more info? Check out the details here.

2) Compliance-By-Design

Travel Rule bus: Think of this as a helpful protocol that makes it super easy to share info with other VASPs, no matter what framework they're using. We're talking about delivery receipts, retries, and really detailed evidence logs. Plus, it’s a breeze to set up blocking policies for those counterparties that aren't on board with TR capabilities. We're staying in the loop with the FATF’s upcoming insights for 2024-2025 and ensuring Notabene/TRISA is accessible. Check it out here: (fatf-gafi.org).
Sanctions and mixer risk: We’re staying ahead of the game with our chain analytics (KYT) and running wallet-level OFAC screenings, especially for those tricky high-risk areas. And let's not overlook the recent FinCEN NPRM discussions aiming to boost transparency around CVC mixing. All the evidence artifacts we gather are designed to fit perfectly with your SAR playbooks. If you want to dive deeper, check it out here: (fincen.gov).
ZK-KYC/KYB options: We're exploring the world of verifiable-credential-based proofs. This includes things like confirming your age, residency, and whether you're an accredited investor, all through Polygon ID/zk-stacks with our guiding principle of "prove, don’t reveal." It’s all about collaborating with regulated KYC to verify legal identity under MiCA/FCA, while keeping your privacy locked down on-chain. Want to learn more? Check it out here: (polygon.technology).

3) Acceptance and Fraud Controls for Card On-Ramps

We're diving into EMV 3DS 2.3.1.1, which brings along SPC and device binding. This update also rolls out scheme-driven message objects. The idea is to keep things smooth whenever the risk scores give us the green light, but no stress--we've got those handy out-of-band (OOB) fallbacks for when things get a little tricky. And to top it off, the sunset guards are in place to ensure that any leftover issues from the 2.1.0 or 2.2.0 versions don’t throw a wrench into approval rates. You can read more about it here.
When it comes to PCI DSS 4.0 controls, we’re all set with page-tamper detection for our hosted checkouts, authenticated scanning, and comprehensive incident runbooks ready to tackle any rogue PANs that may surface. Curious to learn more? Check out the details here.

4) Data, Ledgering, and Reconciliation

We’ve put together an event-sourced subledger that tracks all the action on-chain, like mints, burns, and transfers. It connects seamlessly with fiat postings thanks to MX messages and RTP/FedNow credit advice. And don’t worry, our policies on settlement windows and liquidity buffers are crystal clear--no more relying on guesswork!
With the ISO 20022 transformations, we can now easily generate and process pacs, camt, and remt payloads. Plus, we’ve got case management hooks ready for Stop & Recall starting in November 2025. (swift.com)
Plus, we’ve created ERP-ready connectors for both SAP S/4HANA and Oracle Fusion. Every night, we put together controllership packets that include realized FX, fee accruals, chargeback P&L, and the latest RTP/FedNow settlement deltas.

5) Treasury and Liquidity

We're getting into chain-aware liquidity routing, and we're setting some limits to manage our exposure by chain or bridge. The aim? To land in those ideal target utilization bands and automatically funnel any extra into our bank liquidity using RTP/FedNow (if you're in the U.S.) or instant SEPA (if you're in the EU). It all depends on cutoffs and keeping those fees in check. For more details, check it out here.
We're excited to introduce a programmatic reserves policy for anyone interested in U.K. sterling stablecoin activity. Picture it as a 40/60 framework that lets us adjust the mix of gilts and BoE deposits for some scenario testing while we hang tight for the final codes of practice to come out. If you want to dive deeper, you can find more insights here.

6) Developer and Ops Ergonomics

We've got one API that takes care of everything--from on-chain minting and burning to fiat pushes, Travel Rule exchanges, and case creation. And guess what? It makes idempotency and compensating actions feel like a walk in the park.
When it comes to observability, we’re focused on the golden signals: auth rate, false positives in sanctions, TR delivery, aged buckets for settlement, and any hiccups in the ledger. Just to be on the safe side, we’ve integrated our SLOs with PagerDuty and Slack.

Where We Plug In:

Check out our all-in-one delivery with our web3 development services and blockchain development services. We’ve got you covered from start to finish!
Have an existing stack? Let’s beef it up together with a detailed security audit. Your safety is our priority!
Looking to connect with banks, processors, or ERPs? Our blockchain integration team is ready to make those connections smoother than ever.
Working on a multi-chain or multi-rail project? Check out our cross-chain solutions development and blockchain bridge development services to tackle those challenges head-on.
Want to explore smart contracts and tokenization? We’ve got you covered with our smart contract development, asset tokenization, and token development services. Let’s bring your ideas to life!

U.S. Creator Payouts: “Minutes, Not Days”

Flow: It’s pretty straightforward: Card on-ramp → USDC treasury → RTP/FedNow push-to-bank or USDC wallet payout.
What changed: RTP just upped its game with a $10M cap per payment, and FedNow now has about 1,500-1,600 institutions up and running. On top of that, Visa and Mastercard are excitingly testing out stablecoin aliasing, along with settlement and payout trials. Stripe is also stepping up by making its on-ramp easier, simplifying KYC, and managing fraud liability when you choose to opt in. (theclearinghouse.org)
Facilitator impact: The liquidity router is quite clever; it sticks to the per-rail limits and checks if banks are available. If it can’t reach a beneficiary bank, it’ll smoothly switch to a USDC payout, all while including the Travel Rule metadata.

2) EU Merchant Settlement: IPR + MiCA Constraints

Flow: Alright, here’s the deal: you kick things off with the EU checkout, then it moves through 3DS 2.3.1.1 SPC, and wraps up in USDC (if that's cool) or through SEPA Instant. Just a heads-up, you’ll want to remember the IPR fee parity and make sure you double-check who you’re sending money to. Plus, don’t forget to pick a stablecoin that checks all the boxes for MiCA compliance (you know, like EMT/ART issuer compliance).
What changed: Exciting updates! The IPR is now mandating instant payments and guaranteeing fee equality, with a rollout schedule stretching until 2025. On top of that, ESMA has clarified how they'll handle compliance for ART/EMT that don't meet the standards, with transition periods lasting until July 2026. For all the nitty-gritty details, check it out here.
Facilitator impact: When choosing routes, facilitators really need to weigh the scheme fees against those bank instant fees. This can create a bit of extra work when it comes to verifying payees, plus they'll have to block any ART/EMT that doesn’t align with EU standards.

3) Cross‑chain treasury for global marketplaces

Flow: Picture this: You kick things off with USDC collected on L2 A, then you breeze through a transfer to L2 B using CCTP v2. After that, there’s a nightly sweep to the bank via RTP, and the ledger does its magic by automatically reconciling mints/burns with pacs.008 credits, wrapping up case management events once the coexistence period is over.
What changed: CCTP v2 has officially taken the crown as the new standard, while V1 is on track to retire by July 31, 2026. The transition to SWIFT ISO 20022 for instructions is all wrapped up, and we’re looking at case management milestones stretching from 2026 to 2027. (circle.com)
Facilitator impact: No more juggling manual spreadsheets! Finance teams can now kick back and enjoy same-day realized P&L and fee accruals, all without a hitch across different chains and rails.

4) Privacy-Preserving KYC for High-Value DeFi On-Ramps

Flow: Here’s the scoop: a user mints a zk credential (which basically verifies their age, where they live, and their accredited status) using Polygon ID/zk-KYC. After that, the card on-ramp kicks into gear with the SPC device binding and VC proofs to get everything started. In the end, fiat or USDC is delivered, all while keeping things above board with the Travel Rule and OFAC screenings.
What Changed: We’ve got some exciting updates with a solid refresh of production-grade VC and dynamic credentials. These privacy-focused zkKYC suites really let us “prove without reveal.” Just a heads up, though--FATF and OFAC are still looking for enforceable AML/KYT results. If you want to dive deeper into this, you can check it out here.
Facilitator Impact: We control access using proofs, but we also tie each transaction to verifiable evidence objects, ensuring we stay on regulators' good side.

Best emerging practices we implement by default

“Compliance as Evidence”: Whenever there's a Travel Rule exchange, a revision of sanction hits, or any action in case management, we create a signed, unalterable evidence object that comes with timestamps and a check on whether the counterparty is reachable. We keep an eye on benchmarks to guarantee TR deliverability and ensure we have excellent supervisory coverage. (fatf-gafi.org)
“Rails-first routing”: When choosing between RTP and FedNow, think about which banks are participating and the limits for each payment type. If you find that SEPA Instant or USDC offers a quicker or more affordable option, don’t hesitate to use them, but make sure to maintain IPR parity and confirm the payee. (digitaltransactions.net)
“MX-native from day 0”: Begin producing pacs/camt/remt as soon as you can; only fall back on MT if the networks are up and running and it makes sense financially. (swift.com)
“3DS 2.3.1.1 or bust”: It's time to get SPC and device binding sorted out. This will seriously help reduce risks from sunsets and issuer soft declines. Check out more details here.
“v2 or don’t ship”: It's all about CCTP v2! Just remember to schedule those migration windows and knock out those fast-transfer cutovers before July 31, 2026. Check it out on (circle.com).
“Reserve policy abstraction”: Organize the U.K. systemic stablecoin reserve distributions--maybe something like 40/60 or even a quick 95/5--so the treasury has the flexibility to make adjustments when the final codes are in place. (bankofengland.co.uk)

How we deliver (and where ROI shows up)

We’ve put together a great program that’s super friendly for procurement, and we’re focused on delivering results you can actually measure.

Week 0-2: Technical and Regulatory Discovery
- Let's dive deep into the current infrastructure, check out the contracts we have with processors and banks, assess our stance on MiCA/FCA licensing, take a look at the on-ramp authentication setup, and identify any areas where we might have PCI 4.0 gaps.
- Output: By the end of this phase, we'll have a clear target architecture, an MX mapping spec, risk controls (covering sanctions/KYT/Travel Rule), and a KPI tree that ties back to both our revenue and operational costs.
Weeks 3-8: Building the Facilitator + Integrations
- We’re diving into creating adapters for banks, which means we’ll be working on RTP/FedNow/SEPA Instant, SWIFT MX, card 3DS 2.3.1.1, CCTP v2, Travel Rule gateways, and chain analytics.
- On top of that, we’ll make sure to focus on smart-contract hardening and audits to keep the mint and burn control paths nice and secure. If you want to learn more, check out our security audit services and smart contract development!
Week 9-12: Parallel Runs and Cutover
- During this phase, we’ll be getting into shadow-mode reconciliation, monitoring the SLO burn-down, putting together incident playbooks, and finishing things off with the finance close sign-off.
Operate: Our Site Reliability Engineering (SRE) team and Change Advisory Board are on the clock 24/7, ready to jump into action whenever a new scheme or regulatory update pops up.

GTM Metrics We Keep an Eye On (with Target Deltas for Your CFO/COO)

Card On-Ramp Approval Rate: We're anticipating a boost of around +150-300 bps thanks to 3DS 2.3.1.1 SPC/device binding, issuer routing, and network tokenization. The actual increase will vary based on the variety of issuers in play, but don’t worry--we're on it with baselining and A/B tests. For more details, take a look here.
“Instant to Bank” SLA: We're aiming to achieve the 95th percentile in under 60 seconds when it comes to RTP/FedNow reachability. Plus, we’re keeping tabs on our fallbacks, watching how much institutional coverage expands (FedNow has got over 1.5-1.6k FIs in the mix; RTP boasts more than 1k). If you're curious, you can dive deeper here.
Settlement Cycle Time: Our goal is T+0 for 80% of payouts; the remaining T+1 happens only when counterparties lack instant payment options. Boosting IPR parity could really enhance the economics in the EU. You can find more details here.
Travel Rule Deliverability: We're cruising at over 98% success, all thanks to our flexible, protocol-agnostic exchange. If there are any exceptions, we keep clear documentation with counterparty evidence, so we’re well within FATF guidelines. Want to dive deeper? Check it out here.
Reconciliation Breaks: We manage to keep these below 5 bps of volume by leveraging automated MX↔on-chain matchers paired with case management hooks. Want to learn more? Check it out here.
Fraud/Chargeback Efficiency: We're aiming to reduce those annoying false-positive 3DS issues while keeping CNP fraud levels steady or even lower by using SPC and risk-based workflows. If you want to dive deeper, check it out here.

What you get beyond middleware

Productized Services:
- Platform Builds: Take a look at our awesome dApp development, our robust DeFi development services, and our specialized DEX development.
- Asset Platforms: We’ve got you covered with everything from asset management platform development and asset tokenization to cool NFT development services and NFT marketplace development.
- Chain-Specific: Interested in TON development? Or maybe you want to get into blockchain game development? We’re ready to help!
- Capital Stack: Looking for assistance with fundraising? We’ve got your back on that!
A one-stop shop: we handle everything from engineering and compliance architecture to treasury design, all within one accountable team.

Brief in‑depth: “Facilitator” data model and control plane

The unified payment intent schema has a few key components:
- It features the actor (that’s the legal entity), profiles for both originators and beneficiaries (including handy links to transaction evidence), the chain asset (like USDC.), the target fiat currency (and its corresponding rail), and a few compliance flags to keep everything in check.
Here’s a look at how the state machine operates:
- start → risk_precheck (think OFAC/KYT) → funding (which could involve minting, burning, or netting) → route_selection (options here include RTP, FedNow, SEPA, or USDC) → delivery (either through MX or instant rail) → evidence_attachment (this involves TR receipts and sanctions decisions) → reconciliation (which includes ledger postings and MX acknowledgments) → settlement (where we wrap things up with a treasury sweep).
When it comes to the policy engine:
- We’ve set up some solid guardrails in YAML that's customized for each jurisdiction. This includes specifics like the MiCA EMT/ART allowlist, U.K. sterling details, caps for each rail, friction per counterparty, and any exceptions to the schemes.
For observability:
- We monitor key Kardinal metrics such as auth_rate, tr_deliverability, sanctions_fp_rate, instant_coverage, mx_case_age, and ledger_breaks_bps. All of this data gets exported through OTEL to your SIEM, making it super easy for you to access.

Why 7Block Labs

We’re at a pivotal point where Solidity/ZK technology meets payments operations. This is super crucial as we dive into integrating Circle’s CCTP v2 for that speedy transfer. Plus, we’re getting those 3DS 2.3.1.1 SPC handshakes in place and making sure MX messages sync up with on-chain events--no need to pull an all-nighter in a war room to get it done! (circle.com)
We're really focused on navigating the regulatory landscape we’re up against:
- We've got SWIFT MX, IPR, PSD3/PSR routes, FCA/BoE stablecoin rules, and FATF R.16 oversight all integrated into our Facilitator knobs. We're not just pushing this to a “someday” list! (swift.com)
When we talk about measuring success, it all boils down to the bottom line. We're looking at fewer chargebacks, quicker settlements, and higher authorization rates. This way, our Procurement and Finance teams can give the green light with confidence.

Very Specific CTA (designed just for you):

Hey there! If you’re the Head of Payments at a U.S. marketplace and you’ve got your sights set on an EU launch by September 2026, we’ve got some important steps you’ll want to take. Here’s what you need to focus on:

ISO 20022 MX case management readiness - Make sure you're all set up for this.
Go live with 3DS 2.3.1.1 and SPC - This is crucial for card on-ramps.
Nail that sweet 95th-percentile “instant-to-bank” time - Aim to keep it under 60 seconds via RTP/FedNow.

And don’t forget, you’ll need to keep those MiCA stablecoin flows compliant throughout the process. You've got this!

Why not grab some time with us for a working session? We’ll come together to sketch out your Facilitator blueprint, link it up with your banks and networks, and create a solid 12-week plan to get everything moving with our blockchain integration team. By the time you leave, you’ll have a spec ready for your CFO and CISO to give their thumbs up, plus a clear path to turning compliance into speed and margin. Let’s kick this off!