Over six weeks we've traced cross-border payments from two separate rulebooks, through four G20 goals, to the layer that actually delivers them. Here's the whole argument, in one place.
We opened this series with a distinction: “A standard is something you implement. A scheme is something you commit to, and commitments come with expectations attached.” That was Swift, turning a connectivity network into a rulebook of price, speed, and transparency commitments.
A week later, Nexus arrived from the opposite direction. Not a network extending its reach, but a purpose-built scheme interlinking domestic instant-payment systems directly, incorporated by central banks across Southeast Asia with implementation targeted for 2027. We called it “different starting points, same destination,” and that's held up: both are converging on the same G20 roadmap. Costs under 1%, three-quarters of payments settled within an hour, and senders told upfront what a payment will cost and when it will arrive.
Neither one is “the” answer. Together, they're the backdrop against which the next four weeks made sense.
Speed. Instant rails, Swift's Scheme, and Nexus are all converging on that 75%-within-an-hour target, but instant payments are hard to unwind, and €4.2 billion in EU/EEA fraud in 2024 shows what happens when speed arrives without pre-payment verification. The better question isn't how fast a payment arrives. It's whether a bank can make it arrive that fast and still be confident it was the right payment to send in the first place.
Transparency. Swift's gpi already solved the back-end problem of knowing where a payment is. What it hasn't solved, for most banks, is the front-end gap: a customer seeing that answer inside their own banking app instead of calling to ask for it. A €10 parcel gets a live map. A €10,000 wire still too often gets silence.
Cost. The visible cost of a failed payment (the €20–60 to unwind a misdirected transfer, the roughly €100 in knock-on cost for corporates) is the small part. The larger cost is the ops team manually chasing a correspondent bank, and the fact that building payee verification in-house isn't a one-time project but a permanently moving target across EU VoP, UK CoP, Swift pre-validation, and Kinexys/Liink. The real question was never whether a bank can afford to fix it. It's whether it can afford to keep maintaining the fix itself.
Accessibility. Driving this goal forward means moving as an industry: end users deserve the same trust in a cross-border payment whether they bank with a traditional bank, a fintech, or a telco. That gap shows up even in the Nordics, where most banks still don't offer cross-border payments inside their app and only a limited version in online banking. Combining Swift's Scheme with other rails like SEPA Instant, with fraud prevention and payee verification built into the flow, lets a bank ease up on a purely risk-based approach and actually offer the service, which is what puts cross-border payments within reach of more consumers and corporates in the first place.
Regulation sets the floor. EU VoP under the Instant Payments Regulation, FATF's Recommendation 16, the direction of PSR/PSD3: these tell a bank what it must do. None of them, on their own, tell a bank what a customer actually experiences when a payment moves. That gap between “compliant” and “trusted” is the one this whole series has been circling. A bank can meet every regulatory requirement on the books and still leave a customer staring at a debit confirmation with no idea where their money is. Speed, transparency, cost, and accessibility are what closes that gap, not as four separate initiatives, but as one connected experience.
That's also why we've built one layer instead of four separate answers. Global Payee Verification and anomaly detection sit ahead of a payment, checking the payee and watching for risk patterns across every scheme a bank connects to, through one API, before money moves. Payment Tracking and Exceptions & Investigations sit after it, turning “where is my payment?” into a self-service answer instead of a phone call. Both halves drop into a bank's existing channels, white-label, without touching the core, which is also what makes them reachable for a regional bank through an existing partner channel, not only for a tier-one bank with its own integration team.
Four G20 goals, two moments in a payment's life: before it moves and after. That's the shape of the layer, and it's the same shape whether the rail underneath is Swift's Scheme or Nexus.
Modernization isn't a project with an end date. It's a standing capability to meet whatever scheme, rail, or regulation shows up next, without rebuilding something every time one does. The question worth asking isn't whether your bank has closed the gap between compliant and trusted. It's whether you built the capability to close it once, or you're planning to rebuild it every time the ground shifts again.
That's the series. Six weeks, two networks, four goals, and one answer to the question we kept circling back to: what does modern actually require? If any part of this maps to a conversation you're already having internally, we'd like to be part of it.
Movitz helps banks meet the G20's cross-border payment goals (speed, transparency, cost, and accessibility) through one pre- and post-payment layer that drops into existing systems without a core rebuild.