The past few weeks were dominated by MiCA. This week, the story widened.
The news from 13 to 19 July was not only about crypto authorization or who survived the deadline. It was about the payment infrastructure underneath regulated financial products: Wero gaining merchant distribution, the ECB choosing payment providers for the digital euro pilot, JCB exploring stablecoins with Circle, Kraken pushing crypto balances into a Mastercard debit card, DTCC testing tokenized assets with the biggest names in capital markets, and Revolut adding another local regulatory approval in Dubai.
Put together, the pattern is clear enough. The next phase is not about one rail replacing another. It is about regulated operators learning to run several rails at once: account-to-account payments, cards, stablecoins, tokenized assets, digital euro pilots and local licensing regimes.
Here is what caught my attention this week, and what I think founders should take away from it.
Fintech This Week - week of 20 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.
Two Wero stories landed in the same week, and they belong together.
On 14 July, Adyen joined the European Payments Initiative as a principal member, a move aimed at expanding merchant acceptance of Wero across Europe (The Paypers). Three days later, Airwallex enabled Wero payments for merchants in Europe, adding direct support for the instant account-to-account payment scheme and allowing merchants to accept Wero without setting up a European entity (The Paypers).
This is where Wero starts to become interesting. For a long time, "European payment sovereignty" sounded like a policy ambition more than a merchant proposition. Now the distribution layer is arriving: large PSPs, merchant plugins, checkout integrations, settlement in EUR and a route into ecommerce.
The operating story is not anti-card rhetoric. Cards will not disappear because Wero exists. The real question is whether merchants start treating instant account-to-account payments as a serious checkout rail alongside cards, wallets and local payment methods. If they do, the implications are practical: lower processing costs, faster settlement, different fraud patterns, different refund flows, and more pressure on payment infrastructure and orchestration.
For fintechs and payment companies, this is the point to watch. A2A payments are not just another button at checkout. They change the economics and operations behind the payment.
On 14 July, the European Central Bank selected 36 payment service providers from across the euro area to participate in a digital euro pilot. The pilot is scheduled to run for 12 months from the second half of 2027 and will test technical functionality and operational processes for a possible digital euro (The Paypers).
The selected providers include both banks and non-bank PSPs, with roles split between distribution and acceptance. Some will help users access beta digital euro services; others will support selected merchants in accepting beta payments across ecommerce, mobile, offline and physical point-of-sale environments.
That detail matters. The digital euro is often discussed as a central bank project, but its practical future depends on the private-sector interface. If users ever touch it, they will do so through banks, PSPs, wallets, apps and merchant acceptance infrastructure. The central bank may issue the instrument, but the operating layer sits with the market.
For regulated fintechs, the digital euro is worth tracking for the same reason Wero is worth tracking. Not because it will replace existing payment products overnight, but because it may add another regulated rail that product teams, ledgers, reconciliation engines and customer-service teams need to support. The firms with flexible core banking software will adapt. The ones with brittle payment stacks will experience every new rail as a mini re-platforming project.
JCB and Circle announced a partnership on 17 July to explore stablecoin use cases, initially around JCB's internal treasury management and potential retail payments (The Paypers). The same week, Kraken launched a Mastercard debit card across the UK and EEA, allowing eligible customers to spend crypto and fiat balances held in Kraken accounts, with conversion at the point of purchase (The Paypers).
The two stories are different, but they sit on the same road. JCB is looking at stablecoins as treasury and payment infrastructure. Kraken is turning crypto and fiat balances into everyday card spending. Neither story is about crypto as a speculative asset. Both are about access, conversion and movement.
The hard part is not the front end. A card that spends crypto feels simple to the user. Behind it sit asset selection, conversion logic, tax events, fee disclosures, issuing arrangements, safeguarding, transaction monitoring, complaints, and jurisdiction-specific regulation. JCB's stablecoin work faces the same truth from the network side: stablecoins can improve treasury movement, but only if the legal wrapper, transaction limits and operating controls are ready.
For founders, this is the lesson. "Crypto payments" is too vague a category. Are you enabling wallet-funded checkout? Card spending from crypto balances? Stablecoin treasury movement? Merchant settlement? Each version has a different compliance file and a different operational burden. A crypto and fiat wallet stack only works commercially when it is connected to the right issuing, accounting, monitoring and reporting controls.
On 17 July, DTCC completed a day-long tokenization exercise with more than 25 participants spanning traditional finance and digital assets. JPMorgan, Goldman Sachs, BlackRock, Vanguard and the New York Stock Exchange were among the firms involved. The exercise included tokenized versions of assets such as ETFs, equities and Treasuries, with use cases across collateral management, repo transactions, margin and asset transfers (The Paypers).
This is not a consumer fintech story, but it matters for anyone building financial infrastructure. DTCC is not a crypto-native experimenter. It is one of the core post-trade institutions in the US financial system. When infrastructure at that level tests tokenization, the signal is not "blockchain goes mainstream" in the lazy sense. The signal is that tokenized assets are being tested inside existing market plumbing, not outside it.
That is the same pattern we keep seeing across payments. New rails are not simply replacing old ones. They are being inserted into regulated workflows: custody, settlement, collateral, margin, reporting and asset servicing.
The opportunity is efficiency. The risk is pretending that tokenization removes the need for control. If anything, tokenized assets make the control layer more important because the ledger, ownership record, settlement logic and audit trail become part of the same operating environment. That is exactly where flexible financial infrastructure and licensing strategy matter.
On 17 July, Revolut received in-principle approval from Dubai's Virtual Assets Regulatory Authority to offer broker-dealer, management and investment, and exchange services related to virtual assets in the UAE (The Paypers). The approval follows Revolut's earlier payments approval from the Central Bank of the UAE.
This is a good reminder after weeks of MiCA coverage: global expansion is not solved by one European license. MiCA may create a single EU market for authorized CASPs, but outside Europe the game is still local. Dubai, the UK, Switzerland, Canada, Singapore and other serious markets each have their own perimeter, their own licensing process and their own view of what counts as substance.
For fintechs, that means expansion planning has to be more than a country list. It is a permission map. What can you do under your existing license? What needs a local entity? Which activities are payment services, which are virtual asset services, and which require a partner? What operational controls need to be local, and what can be centralized?
The mature firms are treating licensing as part of market entry. The immature ones still treat it as paperwork after sales has chosen the next geography. For firms weighing routes such as a CASP authorization under MiCA or Swiss SRO membership, the lesson is the same: market access has to be designed, not discovered late.
The future of fintech is not one winning rail. It is regulated infrastructure that can operate across many of them.
Three moves for the week.
First, treat payment rails as a portfolio. Cards, A2A payments, stablecoins, digital euro pilots and tokenized assets are not mutually exclusive futures. They are rails your infrastructure may need to route, reconcile and report across.
Second, build for operational plurality. A fintech stack that only works when one provider, one rail and one jurisdiction behave perfectly is not a serious operating model anymore. New rails should be configuration work, not a re-platforming event.
Third, make licensing part of product and market design early. Revolut's Dubai approval, MiCA authorizations, Wero distribution and stablecoin card products all point to the same reality: the permission set determines what you can sell, where you can sell it, and how much control you keep when the product scales.
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 practical rather than dramatic. The future of fintech is not one winning rail. It is regulated infrastructure that can operate across many of them.
If you want to pressure-test your licensing and infrastructure model, talk to our team.
