Paid twice
The same invoice goes through two approval paths. Coco catches the second payment before it runs.
Solutions
Agentic Payments
Stop the wrong payment before it leaves.
Coco checks every agent payment against your rules and the live state behind it. The payment runs only when the rules clear it.
Every step passes. The payment still goes wrong.
Accounts payable is where agents first reached money movement. One agent reads the invoice, another matches it to the purchase order and a third submits the payment. Each step passes its own checks. The failure sits between them. A supplier you have paid for years sends a real invoice with new bank details. The PO matches and every validation passes. None of those checks asks whether the new account belongs to the supplier. Without a check at the moment of payment, the money leaves.
Coco checks at the moment of payment.
Coco sits between your agent and the payment. Before the signer or the send, Coco checks the payment against your rules and the current state of the payee and the purchase order. A new payee is held for review until someone verifies it. Your reviewer sees the change, the invoice behind it and the rule it triggered. Every decision is recorded, whether the payment passed, was held or was blocked. Coco works across card rails, account to account and onchain.
Other scenarios
Order already cancelled
The purchase order was cancelled after the invoice arrived. Coco blocks payment against it.
More than the contract says
The invoice amount is higher than the agreed PO value. Coco holds the payment for review.
Limits split across payments
Repeated instructions add up past a spend cap. Coco counts them together and stops the payment that breaches it.
Paid before it’s due
An agent settles an invoice ahead of the agreed terms. Coco checks the terms and stops early settlement.
