For the past month, the question was simple: who would make it through MiCA in time?
That phase is over. The stories from 6 to 12 July are interesting because they show what comes after the deadline. Licenses are no longer just permission to stay in market. They are becoming building blocks for product strategy, distribution and payment infrastructure. Product teams are already adjusting what users can access. Stablecoins are moving into ordinary payment flows. And outside the EU, the UK is preparing its own crypto authorization regime.
The transition phase is ending. The operating phase has begun.
Here is what caught my attention this week, and what I think founders should take away from it.
Fintech This Week - week of 13 July 2026.
I am not summarizing the week. I look for news from the past seven days that changes a decision in the parts of the business we live in at Advapay: regulation and licensing, payments and banking access, core banking technology, digital banking, embedded finance, crypto and stablecoin rules, compliance, and cross-border payments.
If a story changes how you build, launch or operate a regulated financial business, it belongs here.
Last week produced two useful signals from the licensing side of the market.
Latvia's central bank granted Nodu Digital both a Payment Institution license and a MiCA authorization, allowing the company to combine traditional payment services with regulated crypto activities under one roof (The Paypers; Finextra). Ripple, meanwhile, secured full MiCA CASP authorization in Luxembourg, adding it to the EMI license it already held there (The Paypers).
The useful point is not that two more firms received approvals. It is that both stories point toward the same operating model: payments, wallets, custody, stablecoins and cross-border settlement are starting to sit inside the same product architecture.
For years, fintech founders asked a simple question: which license do we need? Increasingly, the better question is: which combination of permissions lets us build the product we actually want?
A firm that wants to move value between fiat accounts, stablecoins and crypto wallets may need more than one regulatory layer. It may need a CASP route, an EMI or PI route, and a platform that can keep the ledger, customer records, safeguarding logic and transaction monitoring aligned across all of them.
That is why license architecture matters. The firms that win this phase will not necessarily be the ones holding the longest list of permissions. They will be the ones that understand how those permissions fit together commercially.
MiCA is no longer something compliance teams discuss in boardrooms. Customers are beginning to see it directly.
Revolut announced it would delist USDT for European users to align with MiCA requirements (The Paypers). Around the same time, Flutterwave secured investment from Circle Ventures to expand USDC-powered cross-border payments across Africa (The Paypers).
Placed together, those two stories show how regulation is beginning to shape the product layer. In one case, a major fintech removes support for an asset because the regulatory position is no longer comfortable. In the other, a payment company expands around a stablecoin that fits its settlement strategy.
That is a meaningful shift. Product availability is no longer only a commercial decision. It is becoming a regulatory outcome. Which assets can a platform support? Which customer journeys need to change? Which payment flows can be built around a particular stablecoin, and which ones introduce more risk than they are worth?
For operators, this pushes compliance into the product roadmap. Asset support, wallet flows, disclosures, conversion logic and customer exit plans all need owners. If an asset does not fit the rulebook, the response cannot be improvised after the fact. It has to be part of the operating model.
Two more stories from the week carried the stablecoin theme into payment infrastructure.
Volt introduced stablecoin-powered checkout for cross-border transfers through Profee (The Paypers). Sony Bank received conditional approval to establish a US trust bank focused on stablecoin operations (PYMNTS).
What is interesting here is how unglamorous the use cases are becoming. Volt is not asking the customer to think about crypto rails. It is making USDC another way to fund a regulated payment flow. The customer can pay from a wallet, while the business still needs KYC, AML, treasury, reconciliation, fiat settlement and a clean ledger behind the scenes.
Sony points at the institutional version of the same trend. If a bank is building a supervised structure around dollar-denominated stablecoins, the market is no longer debating whether digital dollars belong in financial services. It is working out who gets to issue, manage and distribute them under a regulated framework.
That is where the conversation has moved. The question is not whether stablecoins have a future. The question is where they sit inside treasury, settlement, correspondent banking and payment operations.
The language is changing too. These are no longer just "crypto products." Increasingly, they are payment products using digital assets underneath. To make that work in production, the wallet layer, payment infrastructure and core banking platform have to tell the same operational story.
While Europe has entered its post-MiCA phase, the United Kingdom is starting its own authorization journey.
The Financial Conduct Authority has published the next stage of its cryptoasset regime, including application windows and implementation timelines that will shape the UK market over the coming years (FCA). The details differ from MiCA, but the direction is familiar: clearer governance, stronger safeguarding, better operational resilience and more accountability for firms offering digital asset services.
For firms planning international expansion, this is the part to take seriously. Compliance strategies can no longer be built country by country as if every market were a separate project. A business that wants to operate across Europe, the UK and other major markets needs an operating model that can support several regulatory frameworks at once.
That does not mean one universal compliance file will satisfy every regulator. It means the underlying machinery has to be reusable: governance, controls, reporting, safeguarding, customer-risk processes, audit trails and incident management that can be adapted without being rebuilt from scratch.
The regulatory file is becoming part of the infrastructure.
The firms that prepared for regulation are now beginning to compete on top of it.
Three moves for the week.
First, stop thinking about licenses individually. Start thinking about license architecture. The competitive advantage increasingly comes from combining regulatory permissions, not simply obtaining one.
Second, expect regulation to shape your product roadmap. Decisions about supported assets, customer journeys, wallet flows and payment methods are becoming regulatory decisions as much as engineering ones.
Third, continue treating stablecoins as infrastructure rather than investment products. The firms building treasury, settlement and payment capabilities around them are moving faster than those still debating whether digital assets belong in financial services at all.
None of this is legal advice, and Advapay is not a law firm. It is the perspective of a team that has helped launch and support more than one hundred regulated financial businesses.
This week's pattern is becoming difficult to ignore: the firms that prepared for regulation are now beginning to compete on top of it.
If you want to pressure-test your licensing and infrastructure model, talk to our team.
