- Why SWIFT still matters to fintech products
- ISO 20022 changes the product conversation
- The future of cross-border products is more data-driven, not less
- Richer data helps only if the product layer is designed properly
- Cross-border payment speed is no longer the whole story
- Product teams should care about CBPR+ even if customers never hear the term
- The next frontier is not only payment movement. It is payment intelligence.
- Why many fintech stacks are not ready for this shift
- Why this matters for wallet, treasury, and embedded-finance products
- Finamp approach in this shift
- What founders should take from this now
Cross-border fintech products are changing quickly, but one assumption still causes confusion in founder discussions: the idea that new rails, wallets, local payment methods, and tokenized-value experiments have somehow made SWIFT less relevant. That is not how the market is developing. SWIFT remains deeply important to cross-border financial movement, and ISO 20022 has made that importance more visible rather than less. In November 2025, the global financial community completed the transition to ISO 20022 as the standard language for cross-border payment instructions on SWIFT, ending the coexistence period with MT for those instructions. SWIFT described the shift as a major milestone and said the new standard’s rich, structured data would support better compliance, faster innovation, and the next generation of payments. (swift.com)
For fintech founders, that matters for a simple reason: cross-border products are increasingly shaped by data quality, transaction visibility, and interoperability, not only by who moves money from point A to point B. SWIFT and ISO 20022 sit directly inside that shift. They influence how payment data is structured, how delays are explained, how compliance checks are supported, how richer remittance information travels, and how product teams should think about building the layer above underlying rails. This is why the topic is no longer only for banks, treasury teams, or infrastructure specialists. It is directly relevant to fintech product design.
Why SWIFT still matters to fintech products
Many fintech teams first encounter SWIFT as a bank-side concept, something associated with legacy cross-border payments, correspondent banking, or enterprise financial operations. That mental model is now too narrow.
SWIFT is still one of the core coordination layers for international financial messaging, and it continues to evolve its cross-border payment offering. SWIFT’s GPI service promotes real-time end-to-end tracking, visibility on deducts and processing times, and confirmed delivery, while the network says that nearly 60% of GPI payments reach end beneficiaries within 30 minutes and almost 100% within 24 hours. More importantly for product teams, SWIFT frames these capabilities in customer-experience terms: transparency, certainty, and faster problem resolution. (swift.com)
That point is easy to miss if the discussion stays too infrastructure-focused. A fintech product may never expose “SWIFT” directly in the interface, but the product still depends on the quality of the underlying data and the speed and predictability of the cross-border journey. Customers do not buy a message standard. They buy clarity, reliability, and confidence. SWIFT continues to matter because it shapes those outcomes in a large part of the international payments ecosystem.
ISO 20022 changes the product conversation
The move to ISO 20022 matters because it is more than a format upgrade. SWIFT describes ISO 20022 as enabling richer, better structured, and more granular data in payment messages, and links that directly to better transparency, more remittance information, improved analytics, more accurate compliance processes, higher resilience, and improved fraud prevention. It also highlights support for end-to-end automation and the use of modern technology. (swift.com)
For fintech product teams, that creates a practical shift. Cross-border products no longer need to treat payment messaging as a black box that disappears behind the provider layer. Richer structured data can affect:
- how transaction states are defined
- how payment purpose and remittance data are displayed
- how compliance and screening workflows are supported
- how support teams investigate delays and returns
- how reconciliation and exception handling work
- how businesses design payment visibility for end users
This is where ISO 20022 becomes a product topic rather than an industry-standard topic. Better data can support a better product, but only if the product layer is built to use it.
The future of cross-border products is more data-driven, not less
One of the most important consequences of ISO 20022 is that cross-border fintech products can no longer rely on vague or overly compressed transaction models if they want to compete seriously.
SWIFT’s own positioning makes this clear. It says quality data leads to quality payments and better customer experience. The organization also notes that the community’s focus after the 2025 migration milestone has shifted from format readiness to realising the value of structured data. That is a significant change in emphasis. The question is no longer “can the ecosystem carry ISO 20022 messages?” The question is “what can products actually do with the richer, structured information now available?” (swift.com)
For a fintech founder, that means the future of cross-border products depends less on surface-level international transfer functionality and more on whether the product can make better use of the information moving through the payment chain. Stronger tracking, clearer exception handling, richer remittance data, more explainable charges, and better operational visibility are all downstream effects of how the product interprets and surfaces that data.
Richer data helps only if the product layer is designed properly
This is where many teams will either gain an advantage or create new debt.
Structured data does not automatically improve the customer experience. A fintech still needs to decide how that information is modeled, mapped, displayed, and operationalized. If the provider layer handles ISO 20022 but the product layer still uses an overly simplified status model, customers will not experience most of the benefit. If remittance data exists but is not surfaced coherently, support teams will still struggle. If structured address requirements or richer party data are treated as “back-office details,” the product may end up carrying format risk and support friction into customer-facing operations.
That issue will become more visible over time. SWIFT has already made clear that further structured-data requirements are coming, including the removal of unstructured postal addresses in CBPR+ ISO 20022 traffic from November 2026. That is a concrete example of how the shift continues to affect product design, data quality, and operational readiness after the headline migration milestone. (swift.com)
This is why the future of cross-border fintech products depends on architecture as much as on connectivity. Teams need a product layer that can absorb better data without becoming harder to manage.
Cross-border payment speed is no longer the whole story
Speed still matters, but the next competitive layer is predictability.
SWIFT’s own 2026 communications around its retail payments framework emphasize this directly. The organization says 75% of transactions over SWIFT already reach the destination bank within 10 minutes, but also explains that much of the remaining friction sits in the “last mile” between payment arrival at the beneficiary institution and credit to the customer. Its new payments scheme is aimed at making cross-border payments more predictable, transparent, and consistent for retail users, with affordable and fixed fees from the start and better end-to-end experience. (swift.com)
That distinction matters for fintech. A cross-border product can be fast in infrastructure terms and still weak in product terms if the customer does not know what happens between send, arrival, and final credit. The future of cross-border products therefore depends on clear transaction narratives, especially around delays, fees, last-mile uncertainty, and confirmation of outcome.
This is one reason SWIFT remains relevant even in a world filled with local rails, A2A options, stablecoin experimentation, and alternative payout models. In many cases, those models still need to coexist with or connect to the wider cross-border financial system. The customer expectation, however, is increasingly shaped by product quality rather than by the underlying path the payment took.
Product teams should care about CBPR+ even if customers never hear the term
CBPR+ can sound like a bank implementation detail, but it has direct implications for fintech product quality. SWIFT describes CBPR+ as the workgroup and usage-guideline framework that defines how ISO 20022 messages should be used and validated for cross-border payments and reporting on the SWIFT network. In practice, that means the ecosystem is not only adopting richer data, but also trying to ensure that the richer data is used consistently. (swift.com)
Consistency matters because inconsistency creates support and reconciliation pain very quickly. When a fintech product depends on multiple providers, banks, market infrastructures, or corridors, structured-data quality and message-use discipline become part of the reliability story. A product that wants to be clear about payment purpose, remittance details, or expected outcomes benefits from a more consistent cross-border message environment. A product that ignores these shifts risks falling behind on the quality of its transaction handling even if the basic money movement still works.
The next frontier is not only payment movement. It is payment intelligence.
This is where ISO 20022 becomes more strategically important.
Once richer structured data is available, fintechs can use it to improve:
- customer-facing payment visibility
- automated exception handling
- payment routing logic
- reconciliation and ledger alignment
- compliance screening support
- B2B invoice and remittance workflows
- treasury and liquidity management features
These are not minor product refinements. They are some of the areas where fintechs can make cross-border products feel far more usable than traditional bank experiences have historically felt.
SWIFT itself frames ISO 20022 in this direction. It links the new standard to better analytics, more automation, more accurate compliance, and the foundations for future services and innovations. It also connects ISO 20022 to longer-term initiatives around payment schemes and tokenised-value movement. (swift.com)
For founders, that changes the competitive question. The opportunity is no longer only to offer “international transfers in-app.” The opportunity is to build a cross-border product that is significantly better at handling information, not just movement.
Why many fintech stacks are not ready for this shift
This is where the product-layer problem appears again.
A fintech can connect to a provider that supports SWIFT and ISO 20022-related capabilities without gaining most of the strategic value. That happens when the product stack remains too tightly coupled to provider-specific states, provider-specific terminology, or overly compressed transaction models. It also happens when internal tooling is too weak to support better investigations, clearer support flows, or richer reconciliation.
The risk is subtle. Teams may believe they have modernized the payments stack because the provider layer has modernized. In practice, the customer experience and the operating model may still behave like a thinner version of the older world.
The companies that benefit most from the shift will usually be the ones that treat structured-data improvement as a platform opportunity. They will define their own transaction model clearly, map provider data into that model, and build support and operations workflows that can take advantage of richer information instead of burying it.
Why this matters for wallet, treasury, and embedded-finance products
SWIFT and ISO 20022 are often discussed as if they matter mainly to banks. The product implications are wider than that.
Wallet products care about clearer funding and payout visibility. Treasury products care about better reconciliation, payment certainty, and liquidity insight. Embedded-finance products care about making cross-border movement and payout experience easier for the platform and its end users. B2B flows care about better remittance matching and less operational friction. These are all areas where richer data and better predictability improve the product, even if the company itself does not think of its offering as “SWIFT-based.”
This is another reason the topic belongs in fintech strategy. Cross-border product quality is now increasingly shaped by how well the company handles the information around the transaction, not only the transaction itself.
Finamp approach in this shift
Finamp operates at the product layer above underlying rails, providers, and infrastructure. In the context of SWIFT and ISO 20022, that means helping fintechs turn richer payment data and more complex cross-border capabilities into something coherent for the customer, the support team, and the business.
That includes:
- clearer transaction-state handling
- product-side control over customer-facing payment narratives
- structured support and operational workflows
- stronger abstraction above providers
- a platform that can evolve as cross-border capabilities, data standards, and product requirements continue to change
Now most fintechs do not need to become messaging-standard specialists. However, they still need a product architecture that can absorb the consequences of those standards and convert them into clearer, more trustworthy user experiences.
What founders should take from this now
SWIFT still matters because cross-border financial products still depend on trusted interoperability, broad reach, and growing data quality across the international payments ecosystem. ISO 20022 matters because it changes what a good product can do with payment information. Together, they shape the next stage of cross-border fintech design.
That should push founders toward a more mature view of product strategy. The future does not belong only to the company with the newest rail or the boldest payments narrative. It belongs to the company that can combine infrastructure reach, structured data, clear transaction design, and operational control into one coherent product.
That is why SWIFT, ISO 20022, and the future of cross-border fintech products belong in the same conversation. The new advantage is not simply moving money internationally. It is building a product that understands the payment deeply enough to make that movement clearer, faster to manage, and easier to trust.