Georgia’s bank treasury upgrade shows why payments infrastructure is moving up the stack

Georgia’s five largest banks are modernising treasury operations with Nasdaq Calypso, a sign that financial institutions are still investing in the systems behind settlement, liquidity, and market operations.

Radom Editorial

Georgia’s bank treasury upgrade shows why payments infrastructure is moving up the stack

Georgia’s five largest banks are set to modernise treasury operations with Nasdaq Calypso, according to Finextra, in a move that points to a broader priority across financial services: tightening the infrastructure that sits behind settlement, liquidity management, and market operations.

The reported deal between Nasdaq and the National Bank of Georgia is aimed at modernising the country’s treasury and financial markets infrastructure across the banking sector. That matters because treasury systems are not front-end products. They are the operational layer that helps institutions monitor balances, manage exposures, and keep money moving through the rails they rely on.

As Finextra put it, Nasdaq has struck a deal to modernise the country’s treasury and financial markets infrastructure. Source

For banks, that kind of upgrade is usually about control and consistency. Treasury teams need cleaner data, clearer workflows, and systems that reduce manual reconciliation. As payment volumes become more fragmented across fiat, stablecoins, and cross-border flows, the pressure to improve the back office only increases. The market is not just asking how money is collected. It is asking how it is tracked, converted, settled, and reported.

That is also why infrastructure conversations now reach beyond traditional banking. PSPs, fintechs, platforms, and payment processors increasingly want programmable systems that can handle acceptance, settlement, conversion, and payouts without stitching together separate tools for each step. In that context, Radom’s focus is similar in shape if not in market segment: give operators one place to manage crypto payments, billing, invoices, payment links, payouts, and conversion workflows. Radom describes its platform as a way to accept crypto payments from one account and keep control of settlement and reconciliation.

The practical lesson from the Georgia announcement is that infrastructure is becoming a competitive layer, not a background utility. Teams that can modernise treasury and payment operations can move faster on new rails, support more currencies, and reduce the operational drag that comes from fragmented systems. That applies to banks, but it also applies to internet businesses handling stablecoin settlement, global payouts, and crypto-to-fiat movement.

There is a second point here for operators building on top of financial infrastructure. The value is often not in the label on the rail, but in how reliably the system handles the workflow end to end. Whether the task is treasury modernisation, merchant settlement, or mass payouts, the buyer is usually looking for fewer manual steps, better visibility, and fewer surprises in reconciliation.

That is where white-label and API-based infrastructure matters. PSPs and platforms want to offer payments experiences that fit their own product without rebuilding the underlying rails every time they expand into a new market or currency. Treasury modernisation at the bank level and payment infrastructure at the platform level are solving related problems: how to move value with more control, more clarity, and less operational friction.

For readers evaluating their own stack, the useful question is not whether a system is branded as treasury software, payments infrastructure, or crypto rails. It is whether it helps finance and operations teams manage balances, settlement, and reporting without adding unnecessary complexity. That is especially true for businesses that now need to support both fiat and digital asset workflows.

Radom’s product set is built around that operator problem. For teams exploring crypto payments infrastructure, the next step is usually to compare acceptance, payout, and conversion workflows side by side, then decide whether the platform can support the payment model they actually run. A good starting point is the product page for crypto payments, which covers hosted checkout, payment links, invoices, subscriptions, and APIs.

Georgia’s treasury modernisation is a reminder that financial infrastructure spending is still very much alive. The winners are likely to be the institutions and platforms that treat settlement, conversion, and reporting as core product capabilities rather than afterthoughts.

Sources

Exploring how this affects your operating model?

Sign up to Radom to get started