What if a subsidy could only be spent on food? What if a supplier got paid the exact second a shipment was verified, with no invoice chasing? What if a travel allowance simply refused to work at a jewellery store?
None of this requires new laws of economics. It requires programmable money, digital currency that carries rules about how, when and where it can move. It is one of the most talked-about ideas in finance, and in India it has already moved from whiteboards into real pilots.
What programmable money actually is
At its core, programmable money is money combined with logic. The logic can live in different places:
- In the payment instruction, where a system checks conditions before executing a transfer. This is sometimes called "programmable payments."
- In the money token itself, where the digital currency carries rules that travel with it wherever it goes. This is closer to "programmable money" in the strict sense.
Both approaches use the same building blocks: conditions (if this happens), actions (then do that), and constraints (only here, only until then, only for this purpose).
A few everyday examples make it concrete:
- Purpose-bound: these funds can be spent only at pharmacies.
- Time-bound: this voucher expires in 90 days and unspent value returns to the issuer.
- Conditional release: pay the contractor when the inspection certificate is uploaded.
- Split automatically: route 18% of every sale to a tax wallet at the moment of payment.
- Escrow: lock funds until both buyer and seller confirm delivery.
India's head start: e-RUPI
India has been experimenting with purpose-specific digital money for longer than many realise.
e-RUPI, launched on 2 August 2021, is a person-specific and purpose-specific prepaid voucher built on NPCI's UPI platform. It is delivered to beneficiaries as a QR code or SMS string, can be redeemed without a card, app or internet banking, and only at defined merchant categories.
It was first used for COVID-19 vaccination benefits, with further uses envisaged across welfare schemes and by private organisations for employee benefits and CSR programmes.
e-RUPI proved something important: people and merchants can use purpose-restricted digital money comfortably when the experience is simple.
The next step: programmable CBDC
The RBI's programmable CBDC work extends that idea to central bank money itself.
When the offline Digital Rupee was unveiled at the Global Fintech Fest in October 2025, it was presented as part of the RBI's broader Programmable CBDC initiative. The programmability features were described as allowing government agencies to ensure payments are used for defined benefits, and allowing corporates to programme specified expenditures such as employee business travel.
Then came real-world deployment. According to the RBI's Annual Report 2025-26, public distribution system beneficiaries in Gujarat, Puducherry and Chandigarh received food subsidies through programmable CBDC, redeemable only for eligible goods at fair price shops and designated merchants.
That is programmable money doing exactly what it promises: making sure public funds reach the intended purpose, with a digital trail that can be audited.
Global experiments worth knowing
Singapore's Purpose Bound Money (PBM). The Monetary Authority of Singapore published a technical whitepaper describing PBM, a protocol that wraps an underlying digital money with a set of usage conditions. The idea is powerful because the rules and the money are separated: the underlying asset stays the same, while the "wrapper" defines how it can be used, across different ledger technologies.
Project Agorá. The BIS-led project, involving seven central banks and more than 40 financial institutions, reported in May 2026 that smart contracts on a shared platform allow institutions to integrate workflow logic, compliance requirements and conditional payment triggers directly into wholesale cross-border transactions.
Project Rosalind. The BIS and Bank of England explored an API layer for retail CBDC, including private sector programmability, developing 33 API functionalities across more than 30 use cases. The lesson: central banks provide the core; private innovators build the programmable experiences on top.
How it works under the hood
You do not need to be an engineer to understand the basic mechanics.
Account-based vs token-based designs
In an account-based system, balances sit in accounts and a central system checks rules before updating them. In a token-based system, value exists as discrete digital tokens, and rules can be attached to the tokens themselves.
The UTXO model
Many token-based designs use a UTXO (Unspent Transaction Output) model, familiar from Bitcoin. Each token is like a specific banknote with its own history and properties. Because each unit is distinct, it can carry its own conditions, such as a spend restriction, an expiry date or an escrow lock.
Smart contracts
A smart contract is code that runs on a ledger and executes automatically when its conditions are met. In programmable payments, the smart contract is the referee: it checks conditions, moves value and records the result.
Oracles
Real-world conditions, like "the shipment arrived," must be fed into the system. Oracles are trusted data sources, such as IoT sensors, logistics platforms or digital bills of lading, that confirm events so contracts can act on them.
Use cases that change how business works
Government and welfare
- Subsidies that can be spent only on intended categories.
- Unclaimed balances automatically returned or redirected.
- Real-time proof that funds reached beneficiaries.
Corporate expense management
- Virtual cards limited to travel, fuel or specific vendors.
- Tax components automatically routed at point of sale.
- Per-diem allowances that expire after a trip.
Supply chain and procurement
- Milestone payments released on verified delivery.
- Multi-party escrow that pays suppliers, logistics providers and insurers in one coordinated flow.
- Early-payment discounts applied automatically.
Subscriptions and digital services
- Renewals that extend access rights instantly.
- Failed payments that trigger smart retries and, eventually, automatic revocation.
Payroll
- Salaries disbursed on schedule, with compliance checks embedded.
- Contractor payments released on approved timesheets.
Loyalty and rewards
- Cashback and points issued as tokens that can be redeemed across a network of merchants.
The concerns, taken seriously
Programmable money raises legitimate questions, and any serious design must address them.
Will programmability limit freedom? This is the most important concern. The consensus across central bank research is that general-purpose money should remain general-purpose. Programmability should be applied to specific, consented use cases, such as a subsidy, a corporate allowance or an escrow agreement, not to ordinary money in a citizen's wallet.
What about privacy? Programmable payments generate data. Designs should minimise what is recorded, keep sensitive personal data off shared ledgers, and comply with frameworks like India's Digital Personal Data Protection Act.
What happens when code is wrong? Smart contracts can have bugs. That is why auditing, testing, controlled rollouts and administrative safeguards like pause functions are essential.
Does it fragment money? If every programmed token behaves differently, money could lose its uniformity. Approaches like Singapore's PBM, which separate the underlying money from the rules wrapper, are designed to avoid that.
Is it interoperable? Programmable rules must work across banks, wallets and ledgers. Otherwise, a condition set in one system breaks in another.
Designing programmable money well
Based on what pilots and research have shown, a few principles stand out:
- Keep the base money neutral. Attach rules to specific uses, not to the currency as a whole.
- Make rules transparent. Users should know exactly what conditions apply before they accept funds.
- Keep personal data off-chain. Use the ledger for proofs and events, not for identity documents.
- Build in human override. Freezes, clawbacks and dispute paths must exist, with proper governance.
- Design for interoperability. Rules should work across ledgers and institutions.
- Start with high-value, low-controversy use cases like subsidies, escrow and corporate expenses.
Frequently asked questions
Is programmable money the same as a smart contract?
Not exactly. A smart contract is the code that enforces rules. Programmable money is the broader idea of money that can be governed by such rules, whether the logic sits in the token or in the payment system.
Can programmable restrictions be removed?
That depends on the design. Purpose-bound funds, like a subsidy, typically keep their restrictions until spent or expired. Once the restricted value is redeemed by an eligible merchant, the merchant usually receives ordinary, unrestricted money.
Will ordinary people need to understand code?
No. Good design hides the complexity. A beneficiary should simply see that a benefit can be used at certain shops, just as e-RUPI users see where their voucher is valid.
Does programmable money work offline?
Offline payments and programmability are both part of the RBI's programmable CBDC work, though the rules that can be enforced offline may be simpler than those enforced online.
Who writes the rules?
The party that issues or funds the money, such as a government department, an employer or two parties to an escrow agreement, within the limits set by regulation.
How E1 is building for programmable money
Programmable money sits at the heart of E1's vision. We believe the future of finance is not just faster payments but smarter money: money that can enforce agreements, protect users and automate the busywork that slows businesses down.
E1's approach includes:
- Programmable rules at the currency level for central banks and public programmes, designed to support conditional spending, targeted stimulus, wallet caps and expiry dates on specific funds.
- Conditional money at scale for fintechs and developers, using UTXO-based tokens designed to carry native rules, spend restrictions, expiry dates and escrow conditions.
- Chainpay, E1's payment orchestration interface, designed so that a payment on familiar rails can trigger smart-contract logic, such as releasing funds only when milestones are met.
- Embedded supply chain finance, designed around conditional milestone payments that release funds to suppliers on verified logistics or inventory handoffs.
- Programmable corporate expense controls, such as cards restricted to travel spend or automatic tax routing at the point of sale.
- Responsible design, with sensitive fiat and KYC data kept strictly off-chain, and AI-enabled safeguards that are auditable and explainable.
The RBI's pilots have shown that programmable money works in the real world. E1's vision is to make it practical for every bank, business and public programme, so that money does not just move, but moves with purpose.
Sources
