Move · Payments
Payment on evidence, not on assurance.
The verified reading lands and the payment is released, under a rule agreed before the project started.
Results-based finance only works if the result and the payment are the same record.
Payments sit inside the work, not beside it.
The payment and the record of it usually live in two systems, so someone matches them up every Monday. Here they are written together.
The payment happens inside your own service, not on a page the customer is sent away to. A housing association collects its charges in the portal residents already use.
The reason and the payment are written together, so your finance team can see why the money moved: a depot scan, a sign-off, a meter reading.
Every payment knows why it happened.
Each payment is written with the identity that acted and the condition that released it — one entry, not two systems kept in step.
Six months on, an auditor traces a housing charge back to the resident, the agreement and the date it cleared.
One record at the end.
Define the rule
A delivery confirmation, a signed milestone, a date, a meter reading.
The condition is met
The scanner reports, the inspector signs off, the meter submits a reading.
Value moves
The checkout takes the payment, the milestone pays out, the AI agent pays for what it used.
It settles and records
Who paid, how much and under which rule, in one place when your auditor asks.
The payment and its record share one timestamp.
- ConditionDelivery is confirmed
- SettlementPayment is released
- RecordBoth share one timestamp
When it cannot wait for a person.
The same payment works wherever waiting for a person is not an option: the pallet at the depot, the market stall with no signal, the data an AI agent pays for.
A payment nobody approves is worth making at sizes where approving it would have cost more than the payment.
Three things payments do on their own.
A machine paying its own way, a payment that waits for proof, money that moves with no signal. Start with the one you need.
Let machines and agents pay
An AI agent pays for each thing it uses, and never goes over the budget you set.
Read more Payments for AI agentsRelease payment on condition
A subcontractor is paid the moment the inspection is recorded.
Read more Milestone and conditional payment eventsMove value without a network
A stall and a customer exchange value with no bars showing.
Read more Wallet and offline payment operationsThe parts of the payment layer.
Explore the modules
Cash that moves without a network
Value passes straight from one device to another in a basement or a tunnel.
Wallet operationsAutomatic payments
A scan, a signature or a sensor reading releases the money instead of a person.
Rules that release a paymentMachine & agent payments
A charge point pays for the power it draws; an AI agent pays for the tool it uses.
Payments for AI agents How you would build on itPeer-to-peer transfers
A supplier abroad is paid directly, with nobody sitting in between.
Wallets and payment flowEmbedded payments
Your members pay inside the app they already use, online or at a card terminal.
Start a payment integrationMicropayments
One article, one megabyte, one minute of access.