Pay an invoice once, and prove it
Fixed-amount payments that carry the invoice number with them, so a retry can never become a double payment.
When an agent or an app owes a known amount, an exact payment sends that amount against a payment reference and nothing else. The reference travels with the money and appears on the receipt.
Most payment mistakes are not fraud. They are the same invoice paid twice because a request timed out and someone, or something, tried again. Exact payments remove that whole category. The payment reference is part of the payment, and the network refuses to settle the same reference a second time, no matter who sends it or when.
For software that pays on its own this matters more than it does for people. An agent that pays 400 suppliers a day will hit a dropped connection every day. With exact payments the right response to a timeout is simply to send again.
How it compares with what you do today
| Bank transfer | Card on file | Exact payment | |
|---|---|---|---|
| Carries the invoice number | In a free-text memo, often truncated | Not at all | As part of the payment itself |
| Duplicate protection | Your own controls | Issuer disputes, weeks later | Refused by the network |
| Time to confirmed funds | Hours to days, cut-off times apply | Days to settle, months to be sure | Within about a second |
| Proof of payment | A statement line | A processor record | A signed receipt naming the reference |
What the reference buys you
A supplier issues invoice 2026-0471 for $1,250. Your agent pays exactly $1,250 against that reference. The payment either settles in full or does not happen; there are no partial amounts to chase. The receipt that comes back names the reference, so your supplier's software matches it to the invoice without a human reading a memo field.
- Pay once: a second payment against the same reference is refused, even from a different machine.
- Pay the right amount: you state the figure, and nothing else can move.
- Pay in time: give the payment an expiry and a late settlement simply does not occur.
- Pay with proof: the receipt carries the reference and is verifiable by anyone you hand it to.
Reconciliation stops being a job when every payment already knows which invoice it belongs to.
Built for the people who close the books
A finance lead sees a ledger where each line matches one invoice. An auditor checks a receipt without calling your bank. A founder stops writing the retry logic that caused the problem in the first place. And a supplier gets paid in the time it takes to read this sentence, with the remittance detail already attached.
If a payment with a given reference has settled, no payment with that reference will ever settle again. That is enforced by the network, not by your code.
Related
Pay your first invoice
Exact payments work from any of the SDKs, the CLI, or an assistant connected over MCP.