CCYFX 2026 Roadmap: Where We're Going and Why It Matters for Our Clients

I don't usually publish roadmap details. There are good reasons for that — product timelines are uncertain, priorities shift, and announcing things before they're delivered sets expectations you can't always meet. But I'm going to make an exception here, because the investments we're making in 2026 are significant enough that our clients and prospective clients deserve to understand where we're heading. This isn't a marketing document. It's my honest account of what we're building, why, and what it will mean for the businesses that depend on us.

The three things I'll cover are jurisdictional expansion, treasury infrastructure deepening, and our approach to stablecoin capability. Each of these connects directly to problems that clients have raised with us, and each reflects a deliberate strategic choice about where CCYFX needs to go to be genuinely useful to the businesses we serve.

Jurisdictional Expansion: Beyond the Current Twelve

CCYFX currently offers named IBANs in twelve jurisdictions. That coverage serves the majority of our current clients well — European payment routing, UK GBP accounts, USD access, major Asian currencies. But the gaps in our coverage are meaningful for specific client types, and filling them is a priority for 2026.

The two gaps I hear about most consistently are Southeast Asian payment corridors and Latin American fiat infrastructure. Our iGaming clients with material player bases in the Philippines, Indonesia, and Malaysia are managing FX and payment flows that require local currency settlement capability we don't currently provide in those markets at the quality level I'd accept. Our crypto exchange clients with Latin American operations need BRL, COP, and MXN infrastructure that the correspondent banking market has made increasingly difficult to access.

We are actively working on correspondent relationships in both regions. I won't name jurisdictions we haven't confirmed, but by Q4 2026 I expect our IBAN coverage to extend meaningfully into both areas. The approach in each case is the same: build the compliance capability for the specific local regulatory environment before offering the product, not the reverse. We've seen too many firms launch into a jurisdiction and then struggle with the compliance complexity. We won't make that mistake.

Treasury Infrastructure: The API Layer

The most substantive product investment we're making in 2026 is in the API layer and the treasury data architecture that sits beneath it. What we have today is functional but not yet at the standard I want for clients who are building genuine treasury integrations — TMS connections, automated payment workflows, real-time reconciliation. The data model is coherent, but the webhook reliability, the ISO 20022-compatible data structures, and the SDK coverage are not yet where they need to be for enterprise integration.

By end of 2026, I want CCYFX's API to be genuinely enterprise-grade: webhook delivery with guaranteed ordering and replay capability, full ISO 20022 transaction data including all enrichment fields, real-time balance APIs with sub-second latency, and rate streaming infrastructure for FX that integrates cleanly with TMS rate feeds. We're also investing in the SDK coverage — Python, JavaScript, and Java by mid-year, with Go and PHP to follow. And critically, we're investing in the documentation. I wrote at length about why API documentation matters, and I mean it: we're hiring a dedicated technical writer whose sole focus is making our developer documentation good enough that an engineer at a sophisticated client can implement a full integration without needing to call our support team.

This matters for clients because treasury automation is where the real efficiency gains sit. A client who has automated their reconciliation against our balance APIs, who receives ISO 20022 transaction data that maps directly into their TMS, who has configured webhooks for payment confirmation and failed payment notification — that client is running a materially better treasury operation than one who is logging into a portal to download CSV files. We're committed to making that automation possible, and 2026 is the year we deliver it properly.

Stablecoin Infrastructure: The Honest Position

We get asked about stablecoins constantly. The question is usually some variant of: when will CCYFX support USDC settlements? The honest answer is: we're building toward it, but we're not going to launch it before we can do it well.

The challenge isn't technical. Our Hong Kong entity — CCYFX Limited — operates in a jurisdiction with mature stablecoin regulation, and the technical integration with major stablecoin infrastructure is not difficult. The challenge is compliance architecture: building the Travel Rule compliance for stablecoin transfers, establishing the blockchain analytics integration that meets our AML standards for on-chain transaction screening, and designing the fiat/stablecoin interface in a way that doesn't create compliance vulnerabilities at the conversion point.

Gabriel Pincus and I have been through this carefully. Our position is that we will launch stablecoin settlement capability when we can do it to the same compliance standard as our fiat infrastructure — not before. That means we're not going to be first to market. It also means that when we do launch, it will be robust, our correspondent relationships will be comfortable with the capability, and our clients won't be exposed to compliance risk at the stablecoin interface.

My current expectation is H2 2026 for a limited launch with specific client types — primarily crypto exchange clients where the use case is clearest and the compliance framework is best established. Broader availability will follow as we build confidence in the operational model.

What This Means in Practice

The 2026 roadmap is about depth, not breadth. We're not trying to be everything to everyone. We're trying to be the best possible banking infrastructure for the specific client types we serve — deeper API capability, wider jurisdictional coverage in the markets our clients actually operate in, and stablecoin infrastructure that is genuinely safe and compliant when we launch it. That's a narrower ambition than some of our competitors, but it's the right one. Complex businesses don't need a generic payment provider. They need one that actually understands their business and has built the infrastructure their specific operations require. That's what we're building.