Tradable Remittance Contract

A tradable remittance contract is a proposed way of packaging a single cross-border money transfer as a standard, machine-readable instruction that licensed payment firms could compete to carry out. The term is a practitioner concept rather than established industry vocabulary. Payments consultant Faisal Khan put it forward in 2026 as the building block of a hypothetical exchange, on which an international money transfer operator (IMTO) would post a customer's transfer and let approved payout providers bid to execute it.

The idea builds on the ordinary remittance contract, the agreement between a sender and a transfer company to deliver a set amount abroad. Today that obligation is usually fulfilled through correspondent banking relationships or payout partners chosen well in advance. A tradable version would separate the customer's promise from the delivery route, so that the route could be chosen transaction by transaction. No exchange of this kind is known to be operating as of November 2026.

Think of a parcel shop. A customer hands over a box addressed to another country and pays for delivery within two days. Normally the shop gives every box to the one courier it signed up with years ago. A tradable contract is like the shop pinning the delivery job on a board where several vetted couriers say what they would charge and how fast they would be, and the shop picks the best offer for that particular box.

The customer still deals only with the shop and still gets the service that was promised. What changes is behind the counter: the job of delivering is no longer locked to one partner, and the courier is paid only once there is evidence that the parcel arrived.

For a transfer to pass between firms, every participant has to read it the same way. The proposal therefore treats each remittance as a standard data record. Its fields would typically include:

• The parties. Sender and beneficiary details, carrying the know your customer (KYC) information the originating firm has already collected.
• The economics. The send amount and currency, the destination currency and a minimum acceptable exchange rate, which caps the FX spread a provider can take.
• The service level. The payout method, such as bank account, cash pickup or mobile wallet, and the latest permitted delivery time.
• The compliance data. The purpose of payment and the results of sanctions screening, so that only firms allowed to serve the corridor ever see the job.
• The completion test. What evidence counts as proof of delivery and therefore releases payment to the provider.

Because the record would carry personal data about senders and recipients, the design assumes a closed network of vetted institutions rather than a public market open to anyone.

In the model, each member firm is onboarded once, through know your business (KYB) checks, licence verification and agreed limits, instead of through separate bilateral deals with every other member. A transfer would then move through a fixed sequence:

1. The originating firm accepts the customer's money and submits the standard contract.
2. The exchange filters members by corridor, licence, payout capability and remaining exposure limit.
3. Eligible providers submit offers, and a matching engine discards any that fail the contract's minimum terms.
4. The originator's own rules rank the remaining offers on rate, speed, reliability and cost, a task that software such as an AI agent could automate.
5. Settlement value is locked, for example through stablecoin escrow, while the winning provider pays the beneficiary.
6. Once delivery is verified, the escrow releases funds to the provider and the record is reconciled.

Ranking on several factors at once is a broader version of least-cost routing, and competition between bidders is meant to produce continuous price discovery for each corridor rather than a single negotiated rate.

Supporters of the concept point to three gains. First, smaller transfer companies could reach many destinations without negotiating a separate agreement with each payout partner. Second, payout firms with strong local connections could win flows from senders they would never reach through their own sales effort. Third, settling each transaction just in time could reduce the idle liquidity that firms hold as prefunding with partners in every corridor, a cost the Committee on Payments and Market Infrastructures discussed in its 2016 report on correspondent banking.

Calling a contract "tradable" leaves open how responsibility actually moves. Depending on the governing law, handing a transfer to another provider could be done by subcontracting, by agency, by assignment of contract or by novation. The choice matters for who remains liable to the customer under consumer rules such as the US Dodd-Frank remittance rule, and for whose licence covers the payment in each country.

Other open points include:

• Depth of the market. An exchange needs enough senders and payout firms active in the same corridors; without them it is only software.
• Risk between strangers. Members that have never dealt with each other face counterparty risk and settlement risk, which escrow and limits are meant to contain.
• Stablecoin dependence. Settling in stablecoins brings issuer, conversion and regulatory risks of its own, discussed under stablecoins for settlements.
• Data protection and compliance duties, which must be clearly allocated when customer data passes from one firm to another.

Similar patterns already exist elsewhere in finance. Securities and currencies are matched on a financial exchange, and payout aggregators let a sender reach many payout networks through one connection. The tradable remittance contract proposal combines these patterns and applies them to individual retail transfers.

• Committee on Payments and Market Infrastructures: Correspondent banking, final report (2016)
• Financial Stability Board: Cross-border payments
• Faisal Khan: Tradable Remittance Contracts: Building an Exchange for Real-Time Cross-Border Payment Routing