How it works
From signature to settlement, automatically.
The Obligation moves through six states. Every transition appends a hash-chained audit entry you can export and verify.
- 01
Create
A seller defines the Obligation: parties, milestones, amounts, and the condition that releases each milestone. Pick a template or use the API.
- 02
Sign
Both parties sign. The legal contract is rendered and bound to the obligation by SHA-256 (Ricardian). KYB gates signing — a leaked link can't be signed by a stranger.
- 03
Fund
The buyer funds escrow at a regulated partner via a virtual IBAN. Funds are held by the partner, never by Pontis.
- 04
Verify
A condition is proven — dual sign-off, time, document hash, API webhook, oracle, or accredited verifier. The verification is signed.
- 05
Release
Pontis instructs the partner to disburse; the milestone settles only on confirmation. A double-entry ledger keeps the books balanced.
- 06
Complete
When every milestone is released, the Obligation completes. Both parties export the same tamper-evident audit trail.