Freight & logistics
- Obligation
- Free time per stop, measured between contractual points
- Evidence
- GPS geofence, facility gate records, RFID portals, TMS stops, EDI 214
- Adjacent charges
- Demurrage, storage, layover, redelivery, equipment use
Solutions
One verification architecture, many contract domains
Every contract-based transaction has the same shape: a contract creates obligations, obligations have conditions, conditions are satisfied by real events, and events can be evidenced. Only the condition templates and evidence sources change.
Domains
Where this applies
Available now — detention
Procurement
- Obligation
- Delivered quantity, specification and delivery-window terms
- Evidence
- Goods receipt records, scale tickets, inspection reports, ASN data
- Adjacent charges
- Price-break tiers, rebate thresholds, service credits
Construction
- Obligation
- Milestone completion conditions that trigger progress payments
- Evidence
- Site telemetry, inspection sign-off, dated site imagery, delivery logs
- Adjacent charges
- Delay claims, standby time, retention release
Insurance
- Obligation
- Coverage triggers and policy condition thresholds
- Evidence
- Sensor telemetry, weather observations, loss documentation
- Adjacent charges
- Deductible application, sub-limit calculation
Manufacturing
- Obligation
- Throughput, tolerance and uptime commitments
- Evidence
- Machine telemetry, QA records, batch documentation
- Adjacent charges
- Service-level credits, scrap allocation
Only the freight detention path is implemented today. The other domains describe how the architecture is designed to extend, not features you can use right now.
Have an obligation type in mind?
The fastest way to find out whether ObligePay fits is to describe one charge you cannot currently verify, and what data you hold about the underlying event.