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.

  1. 01

    Create

    A seller defines the Obligation: parties, milestones, amounts, and the condition that releases each milestone. Pick a template or use the API.

  2. 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.

  3. 03

    Fund

    The buyer funds escrow at a regulated partner via a virtual IBAN. Funds are held by the partner, never by Pontis.

  4. 04

    Verify

    A condition is proven — dual sign-off, time, document hash, API webhook, oracle, or accredited verifier. The verification is signed.

  5. 05

    Release

    Pontis instructs the partner to disburse; the milestone settles only on confirmation. A double-entry ledger keeps the books balanced.

  6. 06

    Complete

    When every milestone is released, the Obligation completes. Both parties export the same tamper-evident audit trail.

What Pontis is not

A bank — regulated partners hold and move the money.
A CLM tool — we execute after signature, we don't manage contract drafts.
A blockchain or crypto platform — Swiss law is the trigger, not a chain.
A payment rail — we instruct rails; we don't replace them.