Domain-driven design and the future of payments

3
August
,
2023
By:

Yoav Ash, Senior Product Manager

Over time, banks’ payment orchestration platforms have evolved as a collection of isolated systems to serve the specific requirements of different payment rails. 

As a result, aggregating front-end channel access, integrating with the bank stack, billing, and performing analytics across these systems can be difficult. It is time and resource-consuming when changes are needed to comply with new regulatory requirements or to add new features to enhance customer experience. Supporting new payment rails or use cases often entails significant investment and business disruption. The need to operate multiple systems also comes with cost considerations, including licensing and operations support.

Why do banks need a new payment engine?

Banks face the challenge of handling multiple and diverse payment methods, including traditional methods such as cash, cheques and wire transfers, and newer methods such as digital payments, mobile payments, and e-commerce payments. Each payment method has its unique characteristics and requires different systems and processes to support it, and consequently, a common payments stack consists of multiple payment platforms.

It stands to reason that banks want to consolidate payment processes into a single platform. By doing so, banks gain operational and cost efficiency, have less exposure to cybersecurity and regulatory compliance risk, and can offer a frictionless customer experience.

However, consolidating multiple and disparate payment methods, schemes, and types into a single platform presents challenges.

Different payment methods may have varying business requirements, compliance standards and procedures — leading to additional technical considerations. For example, a credit card processor must be able to respond to authorisation requests within a matter of a few hundred milliseconds. A credit card processor must also be aware of the card scheme’s guarantees.

In contrast, the processing of direct debit batches is not time sensitive, but the processor must be able to schedule sending payments and settle them over multiple days. Modern instant payment systems such as RT1 and FedNow use single ISO 20022 messages, while older systems such as BACS and ACH use files with proprietary formats.

Banks won’t find a payment system with connectivity to all payment methods because they cannot anticipate enough of the new payment methods that may arise in today’s fast-evolving and complex financial world. A simple look at the payment methods that came onto the scene over the last two years makes the case.

And so here is the key point of this paper: Banks need a single payment orchestration system to simplify their stack and lower the cost of ownership and change, while gaining full control over the behaviour of their payments and the flexibility to future proof the solution, add new payment methods, and innovate.

To read this piece in full, visit here.

<< Previous blog
Next blog >>
Empowering our clients to accelerate their modernisation
Read this blog
Money20/20 Banking Infrastructure Summit: Building a modern technology stack
Read this blog
To be ISO 20022 ‘ready’ is not good enough
Read this blog
Building a winning team with a strong culture
Read this blog
Domain-driven design and the future of payments
Read this blog
How does Vault Core compare to closed-box systems, and what does this mean for product development?
Read this blog
Cloud Native - what does it mean? An interview with CNCF's Cheryl Hung
Read this blog
Why are cloud systems so much more reliable?
Read this blog
Strengthening our commitment to cloud native design
Read this blog
Life may have slowed down but innovation doesn’t!
Read this blog
A demand for COBOL expertise underlines the fragility of critical infrastructure
Read this blog
Q&A with Nick Wilde, MD of Thought Machine Asia-Pacific
Read this blog
Thought Machine redefining banking with Standard Chartered
Read this blog
Building a core banking system in a distributed environment
Read this blog
How Thought Machine can unlock the cloud for banks with Red Hat OpenShift
Read this blog
Round table: Meeting the challenge of a digital future
Read this blog
Let business justify your investments into digital-native core banking systems
Read this blog
The Integration Library: a growing collection of solutions with best-in-class technology vendors
Read this blog
Introducing our Enablement Portal – a complete resource for support, knowledge and training on the Vault platform
Read this blog
Building a bank on top of kubernetes
Read this blog
GFT and Thought Machine forge strategic partnership to accelerate global banking transformation programmes
Read this blog
Shaping the future of banking IT: We’ve joined the Banking Industry Architecture Network (BIAN)
Read this blog
Why microservices are the future of banking
Read this blog
Meet our chair Andy Maguire
Read this blog
From speech technology to banking
Read this blog
Core banking transformed: accelerating migrations with cloud-native cores
Read this blog
How to go full cloud native with CockroachDB
Read this blog
How Thought Machine exceeds global industry standards in compliance and security
Read this blog
Cloud computing will save banks billions. Here's how
Read this blog
Strategic partnership with Lloyds Banking Group
Read this blog
Melden Sie sich für unseren Newsletter an
Thank you! You will now receive some incredible content in your inbox!
Oops! Something went wrong while submitting the form.
Informationen darüber, wie wir Ihre Daten verwenden, finden Sie in unserer Datenschutzrichtlinie.