Project Agorá: When the Transaction Becomes Programmable

Project Agorá is a useful test of the difference between programmable payments and programmable money because it puts conditional logic inside a wholesale cross-border payment platform without presenting every digital claim as the same object. This chapter examines how the BIS Innovation Hub project combines tokenized central bank reserves, tokenized commercial bank deposits, a shared multi-currency platform, and smart-contract workflow. The aim is to identify where the transaction becomes programmable—and where the available evidence stops short of calling the money itself programmable.

Cross-border payments are difficult partly because several institutions and systems must coordinate a single economic exchange. Sequential processes can delay settlement, increase cost, reduce visibility, and leave liquidity divided across networks. These frictions affect treasury management and the ability of businesses and financial institutions to move value across currencies. Project Agorá addresses that problem at the level of wholesale payment infrastructure rather than by offering a new retail currency to the public.

A shared platform for two kinds of tokenized money

The BIS describes Project Agorá as a public–private collaboration testing the desirability, feasibility, and viability of a multi-currency shared programmable platform for wholesale cross-border payments. Its central design records two forms of monetary value on a common platform: tokenized central bank reserves and tokenized commercial bank deposits. The project’s stated ambition is to combine the safety and trust associated with central bank money with the reach and practical role of commercial-bank payment relationships.

That combination is important. A central bank reserve and a commercial bank deposit are not interchangeable merely because both are represented digitally. They have different issuers and different relationships with the institutions that hold them. The platform’s purpose is to let them participate in one settlement environment while preserving the distinction between the claims.

In the reported real-value testing arrangement, central banks used their Project Agorá suites to issue and redeem tokenized reserves and monitor settlement on jurisdictional ledgers. Financial institutions used their suites to issue and redeem tokenized deposits, manage tokenized reserve holdings, submit payments, and monitor balances and activity. Some institutions handled both tokenized deposits and reserves; others managed tokenized deposits only. This division of responsibility is not a minor implementation detail. It tells us where monetary authority, commercial-bank intermediation, and transaction use meet.

The platform therefore has several interfaces rather than one undifferentiated “coin.” Central banks connect the tokenized reserve representation to their jurisdictional monetary systems. Financial institutions connect commercial-bank deposits and customer or institutional payment activity to the shared environment. The platform coordinates the transaction across currencies. External systems, including real-time gross settlement and core banking systems in the testing environment, remain part of the surrounding monetary infrastructure.

The testing arrangement makes those interfaces more concrete. Central banks used their suites to issue and redeem tokenized reserves and to monitor settlement on jurisdictional ledgers. Financial institutions used theirs to issue and redeem tokenized deposits, manage reserve holdings, submit payments, and monitor balances and transaction activity. A central bank’s reserve-side role was therefore not the same as a commercial bank’s deposit-side role, even when both interacted with the same platform.