Simplifying payments integration through one shared banking language

Simplifying payments integration through one shared banking language

November 18, 2026

Two people in an office working together at a computer.

Modernising payments for Standard Bank 

For Standard Bank, a major South African bank undertaking a significant payments modernisation programme, BBD is helping create a more consistent way for legacy and modern banking systems to exchange information.

Over time, the bank’s technology environment had evolved across different systems, regions and technologies, resulting in the same banking information being represented in different formats and structures. As new services were introduced, this created repeated modelling, mapping and translation work between systems.

The programme’s objective is to move payment processing off a tightly coupled legacy trade-finance and correspondent-banking platform and onto modern, event-driven payment services aligned to BIAN service domains, while the legacy platform continues to run the business.

Several pressures drove the need for this modernisation at once: ISO 20022 becoming the common language of payment messaging; new real-time payment rails to connect to, including a regional cross-border instant payments rail and a domestic rapid payments rail; and customer and account data spread across several regional source systems.

Delivery began in June 2025, when the first payment-domain services and the Rosetta model library were established. Rosetta Babel, the translation service, followed in March 2026, and party reference data integration began in May 2026. The full stack, including the cross-border instant payment flow from the legacy platform to the rail and back, has since been delivered into production, and the programme is now extending the same foundation to new service domains.

Objectives

  • Create a consistent way for legacy and modern banking systems to exchange information
  • Reduce reliance on bespoke point-to-point mappings between systems
  • Establish a common banking data model aligned to ISO 20022 and BIAN
  • Isolate legacy-system complexity from the modern payments platform
  • Simplify the integration of new services into the wider banking environment
  • Support incremental modernisation without requiring wholesale replacement of existing systems
  • Reuse established models and translation patterns rather than rebuilding them for every integration

Benefits

  • Greater consistency across systems through one shared representation of common banking concepts
  • Reduced integration complexity by limiting the number of bespoke relationships required between systems
  • Faster foundations for new development by starting from established banking models rather than redefining familiar concepts from scratch
  • Improved separation from legacy technology through defined adapter boundaries
  • Reusable translation capability across ISO 20022 payment flows and internal banking services
  • Incremental adoption allowing the approach to be applied within individual projects and extended as modernisation progresses

The programme in numbers

  • 16,689 Protocol Buffer definitions generated directly from the official ISO 20022 eRepository, covering around 3,900 code sets, 3,100 message definitions and 13,000 message components. None of the model code is handwritten.
  • 12 BIAN service domains modelled on top of that ISO 20022 foundation, from Payment Initiation through to Party Reference Data Directory and Customer Product and Service Directory.
  • 24 services and libraries built on the shared model, with about 1,400 source files working with one canonical representation instead of system-specific formats.
  • 3,121 reusable mapping descriptors driving Rosetta Babel’s translation across the pain (001–014) and pacs (002, 003, 004, 007, 008, 009) message families, including 11 versions of pain.001 and 13 of pain.002.
  • 9 legacy-platform adapters built behind one common adapter interface, keeping legacy data structures out of the modern services.
  • Faster reuse: A second payment-rail adapter was built in about two months by two engineers. It reused the canonical model, the translation service and the adapter patterns from the first rail, so the new work was the rail itself.
  • Fix once, apply everywhere: One fix in the generator corrected collection cardinality across the whole model in a single regeneration, taking 5,830 inconsistent definitions to zero. The standard is maintained at its source rather than patched service by service.

Overview of the solution

As part of the bank’s payments modernisation programme, BBD introduced a canonical integration approach using Rosetta, BBD’s Banking Interoperability Accelerator.

Rosetta provides a shared banking data model generated from the official ISO 20022 eRepository, with BIAN-aligned service-domain models layered on top. Instead of requiring each system to understand the internal structures and formats used by every other system, participating services exchange information through a common model.

BBD implemented this within a hexagonal architecture designed to keep legacy-system complexity at the edges of the modern platform. An adapter layer acts as the boundary between Rosetta and existing systems, translating proprietary or legacy formats into the shared canonical model and back again.

Rosetta’s associated translation service, Rosetta Babel, supports bidirectional translation between the canonical model and ISO 20022 XML or JSON. Its reusable mapping approach reduces the need to repeatedly hand-build translation logic for individual message flows.

Why it holds up in production

  • Translation as data. Rosetta Babel is driven by generated mapping descriptors rather than hand-written code, so supporting another ISO 20022 message version is largely a data change rather than a development project.
  • Documentation that cannot drift. Field-level documentation is generated from the same descriptors that drive translation, so it always describes what the system actually does.
  • Standards upgrades become a regeneration. Because the ISO 20022 layer is generated rather than hand-written, moving to a new ISO 20022 release regenerates the model instead of remodelling it.
  • One model in every language. The model is published for Java, Go, JavaScript and Python, so the Java payment services and the Go translation service share one definition of every banking concept.
  • Data protection by design. Raw payment messages are parsed once at the edge and held in a separate claim-check store, while downstream services store and process only the canonical form. Personal information lives in fewer places, which supports the bank’s POPIA obligations.
  • Tolerant of non-standard partners. Rosetta Babel normalises a counterparty’s non-standard payment status report into the standard form, so downstream services never see the deviation.

Core technologies and standards

  • ISO 20022, BIAN
  • Kafka, MQ
  • Java SpringBoot, Python, Node.js
  • PostreSQL, MongoDB, Oracle
  • Kubernetes

Creating a consistent view of customer and party data across systems

One area where the approach is already being applied is party reference data.

Customer and party information is held across different underlying systems within the bank’s regional environment. Those source systems use different technologies, structures and interfaces, meaning the same information can be represented differently depending on where it originates.

Using Rosetta, BBD created a common representation for that information. Requests can retrieve party data from the relevant source systems, translate it into the canonical model and return it to downstream services in a consistent format.

This means consuming services no longer need to understand how each underlying source represents the customer or party. They work with one shared banking language, while the differences between legacy systems remain contained behind the integration boundary.

Extending the foundation to accounts and products

The programme is now extending the same approach to account and product information through a new Customer Product and Service Directory service. A payment service asks one question, which product agreement an account belongs to, and receives one answer in the shared model. Behind that boundary, the request is routed to whichever system holds the account: a cache kept current by account events from the party reference data service, the core banking platform for the bank’s home market, a different core platform for accounts in other countries, or the legacy platform as a final fallback.

The new service domain was added to Rosetta first, and the service was then built on the generated model. Because the party reference data service already publishes the account events it consumes, each delivery builds directly on the last.

Impact of BBD’s partnership

BBD’s work on the payments modernisation programme has created a reusable integration foundation that allows the bank to modernise around its existing technology landscape rather than requiring every underlying system to change at once.

By combining banking domain expertise, modern integration architecture and reusable standards-based IP, the team has been able to create a common language between systems while isolating the complexity of legacy platforms behind defined adapter boundaries.

Rosetta and Rosetta Babel are running in production as the foundation of the bank’s payments modernisation platform. Every service in the platform exchanges data through the shared model, including the cross-border instant payment flow from the legacy platform to the rail and back.

The architecture also creates a foundation that can be extended as further services are introduced. Instead of beginning each new integration from first principles, future work can build on models, mappings and patterns already established through the programme.

The hardest part of payments integration isn’t writing code. It’s agreeing what a payment, a party or an account actually is in each system. Rosetta settles that question once. The model is generated straight from the ISO 20022 eRepository, so nobody hand-maintains thousands of definitions. When a cardinality issue is found, it is fixed in the generator and every service picks it up in one regeneration.

“The legacy platform still does its job. Our adapters keep its tables and message formats at the edge, so the modern services never need to know about them. When we built the second rail adapter, the team wasn’t starting from a blank page. The model, the translator and the adapter pattern were already there.”

Johnathan Botha, Payments Expert, BBD

Let’s build what’s next

Chat to your BBD contact about how we can help simplify integration and accelerate banking modernisation, or get in touch with our team to find out more.

Related Content

Featured insights

Case Studies

Simplifying payments integration through one shared banking language

Two people in an office working together at a computer.
Whitepaper

The business case for looking south

SATSEA logo next to a smiling woman in a black blazer, set against a draped South African flag.
Article

Why custom software outperforms off-the-shelf solutions

Four colleagues talk informally over coffee and documents in a modern office with a green plant wall.