Programmable payments are bank payments that follow rules a client sets in advance: when an event occurs, the bank’s platform checks a condition and, if it holds, moves money. On tokenized deposit platforms such as J.P. Morgan’s Kinexys Digital Payments, those rules run inside the bank’s own ledger, so sweeps, just-in-time funding and foreign exchange can execute around the clock without a treasury analyst sending each transfer.

Trigger, condition, action

A 2024 report by Kinexys by J.P. Morgan and the MIT Digital Currency Initiative describes each programmable instruction in three parts: “when an event occurs, evaluate if conditions are met, and perform actions.” If the condition fails, nothing happens.

The report gives two worked examples. In the first, a clock triggers the rule at 6 PM local time, the platform checks whether Account A holds more than $1,000,000, and the excess moves to Account B. In the second, a payment that lacks funds triggers a transfer of the shortfall from another account. The payment pauses while the rule runs and resumes once the account is funded.

Use Trigger Condition Action
End-of-day sweep The time is 6 PM local Account A balance is above $1,000,000 Move the excess to Account B
Just-in-time funding A payment lacks funds Account B can cover the shortfall Transfer the shortfall, then resume the payment
Programmed FX (BMW, December 2025) Conditions pre-defined by treasury teams Automated balance checks Convert EUR to USD and move funds from Frankfurt to New York

The first two rows come from the Kinexys and MIT report. The third comes from J.P. Morgan’s December 9, 2025 announcement about BMW Group.

Client-side vs bank-side programmability

Corporates already automate payments. A treasury system can call a bank API at 6 PM and request a sweep. J.P. Morgan calls this client-side programmability: the code runs in the client’s environment and talks to the bank through channels such as APIs.

Bank-side programmability moves the logic into the bank. The client deploys its instructions next to the bank’s transaction processor, and the bank’s systems execute them without waiting for the client’s systems. J.P. Morgan lists the claimed benefits:

  • less lag between an event and the payment it should cause;
  • fewer failures, because one environment runs the trigger and the action;
  • one audit trail in one data format;
  • access to events a client never saw before, such as interim payment states;
  • payments that can run closer to, or after, normal cut-off times;
  • linked instructions that either all succeed or all fail, the property behind delivery versus payment and payment versus payment.

That last point connects programmable payments to tokenized asset settlement, where the asset and cash legs must complete together.

Why the deposit ledger matters

Kinexys Digital Payments is, in the report’s words, “a blockchain-based demand deposit product.” Client accounts are Blockchain Deposit Accounts recorded on a private, permissioned ledger. That ledger is the official record of J.P. Morgan’s deposit liability, and the bank books those balances the same way it books a conventional demand deposit account. The report put daily transaction values above $1 billion.

The ledger runs on Quorum, an EVM-compatible platform, with every node controlled by J.P. Morgan. The payment processor stays mostly off-chain and handles fraud checks, sanctions screening and other controls. Each change in a payment’s state is written on-chain, and those state changes can trigger client rules.

This is the design difference that makes just-in-time funding possible. A conventional workflow checks funds and fails the payment if the balance is short. In the state-based design the report describes, a client rule can run before the bank’s funds check, draw money from another account and let the payment continue. For background on the token itself, see tokenized deposits.

Live and piloted examples

BMW Group and J.P. Morgan (December 9, 2025). J.P. Morgan said BMW Group became the first corporate to execute a fully pre-programmed FX transaction with Programmable Payments on Kinexys Digital Payments. The first transaction combined automated balance checks, conditional auto-deposits, near real-time FX and transfers between BMW’s Blockchain Deposit Accounts in Frankfurt and New York, completed outside traditional settlement windows. J.P. Morgan notes that only select currencies are available to clients.

Citi Token Services (September 18, 2023). Citi announced a pilot with Maersk and a canal authority that served the same purpose as bank guarantees and letters of credit. Citi said it showed “programmable transfer of tokenized deposits that provided instant payments to service providers via smart contracts.” A parallel cash pilot moved liquidity between Citi branches 24/7.

Ant International (client-side, described in the 2024 report). Ant International runs its own blockchain platform tied to its treasury management system, which uses the company’s AI-based triggers to move funds ahead of forecast needs. Its smart contracts sit on a different blockchain and talk to Kinexys through APIs, so this is client-side programmability linked to a bank ledger.

Limits the banks themselves name

The Kinexys and MIT report lists trade-offs:

  • Blurred responsibility. Conventional API calls separate what the client asked from what the bank did. Client code running inside the bank needs audit records that keep that separation.
  • Compute limits. Smart contract operations are computationally limited and may not finish in well-defined timeframes, so high-frequency workloads fit conventional systems better.
  • External data. The ledger guarantees consistency on-chain only. Rules that rely on off-chain data depend on oracles, the data feeds that bring that information onto the ledger.
  • Code risk. Poorly written code can degrade service and malicious code can cause losses. Banks may restrict what clients can write, for example by disallowing loops and recursion.
  • Scale. Hosting many clients’ logic expands the bank’s responsibilities and raises performance questions on a shared ledger.

Scope is the other limit. Kinexys Digital Payments is a single-bank platform. The report notes the same technology is licensed to Partior, a multi-bank shared ledger. The BIS argued in June 2025 for a unified ledger holding tokenized central bank reserves, commercial bank deposits and government bonds on one programmable platform, and its Project Agorá is testing that idea for cross-border payments.

What to ask a bank before building on it

  • Which events can trigger a rule: time, balance, incoming payment, interim payment state?
  • What can a rule do: internal transfer, external payment, FX?
  • What language limits apply, and who reviews a rule before it goes live?
  • Which party is responsible if a rule fires wrongly, and how is that recorded?
  • Do sanctions screening and fraud checks still run on every automated payment?
  • Which currencies and hours are supported, and what happens outside them?
  • How do automated movements reach your own ledger for account reconciliation ledger vs bank balance checks?

More pieces on this layer are in the tokenization section.