Obligations, not line items
ObligePay reads the contract to identify the obligation behind a charge — the free time, the rate, the increment, the measurement points — and stores it as structured parameters rather than prose.
The evidence layer for commercial obligations
Verify What's Owed.
Before It's Paid.
ObligePay connects contractual obligations to independently verifiable evidence—helping businesses determine whether commercial charges are actually supported before payment.
Starting wedge: freight detention verification. Architected for procurement, construction, insurance and manufacturing obligations.
Reality Certificate
Detention — stop 2
- Billed
- $2,400.00
- Free time
- 120 min
- Observed dwell
- 97 min
- Supported
- $0.00
UnsupportedEvidence: GPS · Facility gate · EDI
Potential recovery
$2,400.00
The workflow
- 01
Contract
The agreed terms
- 02
Obligation
What must be true
- 03
Evidence
Independent sources
- 04
Reality
Reconstructed events
- 05
Certificate
Recorded result
- 06
Payment
Decision
The difference
“An invoice tells you what was billed.
Evidence tells you what happened.”
ObligePay doesn't merely read invoices. It identifies the contractual obligation behind a charge, determines what evidence is required to establish whether that obligation's conditions were met, reconstructs the relevant events from independent sources, compares the evidence against the contract conditions, performs the calculation deterministically, and records the result.
How it is built
Four commitments that shape the platform
Independent evidence
An extensible evidence layer pulls from GPS, RFID, EDI, TMS, facility gate systems, weather, documents and manual attestation. Provenance and reliability travel with every observation.
Deterministic calculation
Financial arithmetic runs in ordinary code on integer cents. Same inputs, same number, every time. AI never decides an amount.
A record that survives the argument
Each verification produces a Reality Certificate with its evidence sources, event timeline, calculation steps and a content hash. New facts create a new version; history is never overwritten.
Starting wedge
Freight detention, verified end to end
Detention is a good place to start because the obligation is narrow, the arithmetic is unambiguous, and independent evidence is unusually available. A carrier bills for driver and equipment time held beyond the contractual free-time allowance. Whether that charge is supported is a question about a physical event — and physical events leave traces.
ObligePay reconstructs the movement from telematics geofences, facility gate records, RFID portal reads, TMS stop records and EDI status milestones, resolves disagreement between them deterministically, and evaluates the result against the free-time clause the contract actually contains.
The same architecture — obligation, required evidence, reconstruction, condition evaluation, deterministic calculation, immutable record — extends to demurrage, storage, procurement quantity terms, construction milestones, insurance coverage triggers and manufacturing commitments.
Explore the domainsWorked example
Simulated demo- Carrier bills detention$2,400.00
- Contract allows free time120 minutes
- Evidence shows dwell of97 minutes
- Contractual condition satisfied?No
- Supported amount$0.00
- Potential recovery$2,400.00
Figures above are a simulated illustration, computed live by the same deterministic engine the product uses. They do not represent a real customer or shipment.
Bring evidence to your payment decisions
We're running early pilots on freight detention. If you pay accessorial charges and hold operational data you aren't yet using, we'd like to talk.