Payments as infrastructure#
Payments are one of the most important yet least visible layers of the modern economy.
Most of us never think about them. We click “Pay” tap a card on a terminal or authorize a bank transfer in an app and expect everything to simply work.
That is precisely the greatest success of payment systems: they remain invisible.
Behind this seemingly simple experience, however, lies a distributed system of organizations, regulations, financial institutions and technology platforms responsible for transmitting information, managing risk and coordinating trust.
Payments are not merely a technology problem. They are an organizational problem.
Architectural consequences#
Payments are often seen as the domain of fintech companies—this is a mistake.
Every company building a digital product will sooner or later face questions such as:
- How should we accept payments?
- Should we use an off-the-shelf platform?
- What are the costs of entering new markets?
- Who is responsible for fraud?
- How do refunds and chargebacks work?
Payment architecture affects:
- margins,
- time to market,
- expansion opportunities,
- operational overhead,
- regulatory compliance,
- access to data.
In practice, companies do not simply buy a payment gateway; they choose a particular operating model.
The evolution of trust#
The history of payments is a history of solving problems of coordination and trust.
Each successive layer addressed a different limitation of the one before it.
| Model | Problem addressed |
|---|---|
| Barter | Local trust |
| Cash | Exchange of value |
| Bank transfers | Distance |
| Cards | Scale |
| Payment platforms | Convenience |
| Open Banking | Cost and interoperability |
| Bitcoin | Sovereignty and finality |
It is worth noting that modern payment systems do not replace their predecessors. They accumulate in layers.
We still use cash, bank transfers, cards, BLIK and cryptocurrencies side by side.
Each of these models represents a different trade-off between convenience, control and responsibility.
The four-party model#
Modern card payments are based on the four-party model.
Its core participants are:
- Cardholder
- Merchant
- Acquirer
- Issuer
- Card Scheme
The card scheme is not formally a party to the transaction, but it coordinates communication between the acquirer and the issuer.
At first glance, this model may seem unnecessarily complicated.
Why can the customer not simply send money to the merchant?
The answer is simple: scale.
Increasing the number of participants from three to four creates seven new relationships, not one. Technical and organizational complexity grows with it.
The four-party model separates responsibilities among independent entities.
- The merchant does not need to integrate with every bank in the world.
- The issuer does not need to know every store.
- The card scheme provides a shared language for communication.
- The acquirer manages the relationship with the merchant.
This complexity did not arise by accident.
It was introduced deliberately so the system could operate globally.
The card scheme standardizes communication between banks and acquirers, allowing the system to scale.
Where complexity returns#
Abstractions are useful. They do not eliminate problems; they merely move their boundaries.
In practice, organizations quickly discover that payments involve far more than transaction authorization alone.
They must deal with:
- fraud,
- chargebacks,
- settlement — which often takes around two days,
- reconciliation,
- vendor lock-in — which rarely results from the vendor contract itself and more often from deep technical and operational integration,
- risk management,
- regulatory compliance.
Interestingly, some chargebacks are not caused by fraud. They may arise from:
- operational problems,
- communication errors,
- poor data quality,
- unclear refund processes.
This is the point at which payments stop being a product feature and become a system in their own right.
Choosing a payment architecture means deciding who bears the cost of its complexity.
The next decade#
The payments market is not standing still. Several major trends are unfolding at once:
- Open Banking and account-to-account payments,
- ISO 20022,
- the growing role of AI,
- the increasing importance of data,
- vertical integration.
Open Banking and A2A promise lower costs and greater competition.
ISO 20022 increases the volume and quality of data flowing through the system.
Payment platforms are increasingly moving beyond competition based solely on price.
They compete on:
- data quality,
- fraud detection,
- payment orchestration,
- user experience.
Transaction authorization itself may eventually become an almost entirely commoditized service, while payment platforms compete on their ability to manage the complexity generated by those transactions.
Alternative models of trust#
Traditional payment systems rely on intermediaries. Alternative models make different trade-offs.
| Characteristic | Card Networks | Open Banking (A2A) | Bitcoin |
|---|---|---|---|
| Trust model | Financial institutions | Banks | Protocol |
| Intermediaries | Many | Few | None |
| Reversibility | Yes | Limited | No |
| Complexity | Hidden | Shared | Explicit |
| Responsibility | Distributed | Distributed | User |
| Primary trade-off | Convenience | Cost | Sovereignty |
None of these models is objectively better. Each answers a different question about trust, responsibility and how complexity should be managed.
Conclusion#
Modern payment platforms are not primarily designed to transfer money.
They are systems for coordinating trust among organizations operating at global scale.
Successive models shift complexity away from institutions and toward system participants. They do not eliminate it; they change where it becomes visible.
When a company decides how it will accept payments, it is also deciding:
- who takes responsibility,
- who manages risk,
- who maintains the infrastructure,
- who bears the cost of the resulting complexity.
Only when we look at payments through the lens of trust do we begin to understand why the modern ecosystem looks the way it does.