Rutba
Start free

Blog · Workspace

A receipt in your hand before anybody else has signed

In an agreement with five parties, the first to sign may wait weeks for the last. Until now they held nothing for it. Each party now leaves with proof of their own act, countersigned by Rutba the moment they acted.

· 3 min read

Share this

Picture a supply agreement with five parties across three time zones. The first signs on Monday. The last, somebody on leave, signs three weeks later. For those three weeks the Monday signer has done their part of a legal act and holds nothing to show for it — no document, no certificate, nothing but an email saying they are waiting on others.

Usually that does not matter. It matters a great deal when it does: when the agreement is disputed before it completes, when the envelope is cancelled, or when a party later claims the terms they signed are not the terms that went round.

Proof of your own act, at the moment you act

Each party to a Rutba Sign agreement now leaves with a receipt of their own act. It says who signed, what they signed — the document pinned by its hash — and when. And it is countersigned by Rutba at that moment, not at completion.

That second part is what makes it worth holding. A receipt you issue to yourself proves nothing to anybody. A receipt countersigned by the platform the instant you acted is independent evidence that you did it, and that what you signed is byte-for-byte what you were shown.

  • Signed in a room, each person leaves the table with their own — nobody waits for the last signature before they have proof.
  • Signed remotely, the receipt arrives the moment you finish, whether you are first or fourth.
  • Checked by anybody, it verifies publicly by digest, exactly as a completed agreement does — no account, no key, no charge.

A receipt you issue to yourself proves nothing. One countersigned the instant you acted is evidence.

Why the platform countersigns, and not your organisation

Rutba Sign runs on two backends on purpose. Envelopes are created and sealed inside the organisation’s own Rutba instance; verification is served by the platform. The countersignature on a receipt comes from the platform side, which is the point: a receipt countersigned only by the organisation that sent the envelope is a receipt the other party has to trust that organisation about.

The countersignature makes a narrow claim and makes it exactly. It says this party performed this act on this document at this time. It does not claim the agreement is complete, and it cannot be mistaken for the sealed record the whole agreement gets once the last party signs.

What it changes in practice

SituationHolding nothingHolding a receipt
Envelope cancelled after you signedNo record you ever actedProof of what you signed and when
Another party disputes the termsYour word against theirsThe document hash you signed
Signing in personWait for the last signatureLeave the table with proof

Check a receipt or a sealed agreement

Paste a digest into the public checker. It answers valid, tampered, or unknown.

Verify a document

Read next

Business Suite

A page of zeroes is a worse claim than nothing at all

The promoter’s page on the storefront is deliberately thin: it says where you stand, and nothing else. A dashboard of zero earnings would tell an approved promoter they have earned nothing — a different and much worse statement than "this does not exist yet".

3 min read

How we build

A page for every Rutba app, drawn from the app itself

A product page named its apps in a sentence each, which cannot tell you whether a till handles returns. Forty apps now have a page of their own, listing every screen in them — read from each app’s own menu — with screenshots of it running.

3 min read

Share this

One family

The rest of Rutba

One account across all of it. Sign in once and the products know each other.

PORTAL-BLOG-DETAIL · be079a8