Skip to main content

Start here: six questions about banking integration

The reading order for this series: which integration jobs you still own, which platforms have a date on them, and how to price a decision before a vendor does it for you.

Updated 4 min readMarkdown
Start here: six questions about banking integration

A vendor shortlist arrived before the inventory did. That order is why integration programmes fail politely: the decision is taken in a steering committee, and the evidence arrives six months later from operations. This series works the other way round. Six questions, in the order I ask them, each answered with a date and a source, and each ending in a trade-off rather than a pitch.

The six questions

1. Which integration jobs do I still own?

A bus and an API layer are not versions of each other; they encode opposite philosophies. A centralised bus puts routing, transformation, protocol mediation and orchestration in the middleware — smart pipes, dumb endpoints. API management keeps the logic in the service and the gateway thin — smart endpoints, dumb pipes. The jobs did not disappear when the products did. Mainframe and SAP adapters, long-running orchestration, B2B and EDI still need an owner, and usually a team.

2. Which of my platforms has a date on it?

The dates are public and close. Apache ServiceMix was retired in March 2026 and Apache Synapse sits in the Attic; Mule 3 Community Edition is end of life; Oracle Fusion Middleware 12c, the platform under Service Bus and SOA Suite, ends Premier Support in December 2026; SAP Process Orchestration 7.5 ends mainstream maintenance in 2027; BizTalk Server 2020 reaches end-of-sale on 31 March 2027; Red Hat 3scale ends maintenance on 30 June 2027. Ownership moves too: IBM completed its acquisition of Confluent in March 2026, on top of webMethods in 2024. Anything with a date inside three years belongs in this quarter's plan.

3. Is ISO 20022 a format change or a data change?

Format changes are projects; data changes are programmes. Cross-border coexistence ended in November 2025, and on 27 August 2026 Swift postponed the entire November 2026 Standards Release — the last date moved, not the work. What remains is address structure, reference integrity, charge bearer and reconciliation ownership, measured against a five-business-day examination window rather than a sprint calendar.

4. Do I need a payment hub, or do I already have three?

A payment hub is a layer that normalises and routes instructions across channels and banks. Many banks have that function spread across a core, a channel and a file-based integration, with no single routing table. The test is one question: can one place tell you which channel a payment will take, by currency and value, and what happens when it fails? Exception codes — invalid account, name mismatch, wrong BIC, insufficient funds — should be run by a written playbook, not by whoever is on shift.

5. What is a corporate banking platform made of?

Seven layers, from accounts and payments through trade finance, credit, FX and cash management. A mature bank runs four to six systems across them, and no single platform is best at all seven. That is why "replace the platform" is usually the wrong sentence. The question is which layer is missing, and whether it should be bought, rented or built.

6. How do I price this when every enterprise price is quote-only?

Price the metric, not the product. The category itself was estimated at USD 5.24 billion in 2025 and USD 6.92 billion in 2026, and per-call, per-unit, flat rate, credit consumption and per-core licensing behave completely differently as volume grows. Buyer-side estimates put large-enterprise discounts at 20–40% off list and first-year professional services at 20–40% of licence, and the hidden lines — environments, add-on analytics, connectors billed per environment, LLM tokens — are where budgets break. If the pricing metric does not grow roughly linearly with your volume, the business case is not finished.

Start with ESB isn't dead. It stopped being the default answer. — the life-cycle dates, the three options, and the 90-day plan for an incumbent integration layer. Then read ISO 20022 is a data project if payments are in scope this year, and Corporate banking platforms: build, buy or extend if the decision is at layer level rather than interface level.

Sources

Personal views. Client and employer details are anonymised. Figures are third-party estimates, not vendor quotes, and are dated November 2026.

No comments yet. Be the first to comment.