BANKABIL · Developers
For platform & infra teams

Evidence as a primitive.

Native SDKs, deterministic canonicalization, an offline verifier, and open schemas. No hidden state. No silent mutation.

BANKABIL ships Ink Receipts as a documented format with reference implementations in Rust, TypeScript, and Python. Issue, hash, bundle, and verify from any service — without trusting the platform that produced the decision.

BANKABIL
FOR DEVELOPERS · SDKs & SCHEMAS
  • bankabil-rs
    Reference issuer and verifier in Rust.
  • bankabil-ts
    TypeScript SDK for Node and edge runtimes.
  • bankabil-py
    Python SDK for data and ML pipelines.
  • bankabil verify
    CLI verifier — runs anywhere, offline.
  • Open schemas
    Versioned JSON Schema + canonical test vectors.
inkreceipts.dev
What developers need

Evidence that survives independent review.

01

A real format

Open, versioned schemas — not a vendor blob.

02

Determinism

Same input, same bytes, same hash. Every time.

03

Local verification

A verifier you can run in CI, on a laptop, or air-gapped.

04

Boring primitives

Canonicalize, hash, sign, bundle. No magic.

05

Workflow integration

Issue receipts from the same path that emits the decision.

06

No platform lock

Receipts outlive your tenancy, your vendor, and your stack.

What BANKABIL provides

Designed for developers.

Deterministic

Canonicalization yields identical bytes across runtimes.

Open

Schemas, test vectors, and a verifier in the open.

Embeddable

Drop into existing services, no sidecar required.

Inspectable

Every receipt is human- and machine-readable.

Build on evidence, not assertion.