Bankd Connect — Protocol Demosimulationhealth checking
simulation controls
bank-aBank A
bank-bBank B

Click a credential to make it the active key — every API call in the walkthrough uses it. No real institutions, keys, or funds: all data is simulated in-app.

Provisioning simulated institutions…

Connect API V1 — protocol walkthrough

Connect is a non-custodial institution API for linking banking-core accounts to externally controlled Bankd wallet identities. This demo walks through the V1 protocol and its trust boundaries using a faithful in-app simulation — no real connect-api, database, or chain is involved. Open the wire viewer (top right) at any time to inspect the exact HTTP envelopes.

Waiting for simulation bootstrap…

1Create a link→

Pick institution, type, visibility, rail, and an opaque provider reference. The reference is sealed at rest and never returned.

2Challenge & sign→

See the canonical bankd-connect-proof:v1 message verbatim, sign it with the simulated EOA (EIP-191), and watch pending → active.

3Dashboard & balances→

Per-source balance cards — public EVM (18 dec) and private Shieldd (6 dec) — never summed, with staleness and explicit source errors.

4Alias publication→

Stage a treasury routing alias (alias_ + 22 base64url chars, 128-bit CSPRNG), follow the desired-vs-observed state machine.

5Boundary probes→

One-click probes for tenant isolation (404), scope enforcement (403), revocation (401), idempotent re-POST, terminal 409s, unsupported rails.

Non-custodial

Connect never holds spending keys or plaintext viewing keys. Links activate only via wallet-signed proofs; payments, debits, and on-chain publishing are out of scope by design.

Tenant-isolated

Institution identity comes only from the verified bearer credential. Unknown, cross-tenant, and revoked resources are indistinguishable 404s.

Scope-enforced

Exact scopes per credential. balances:read and aliases:write are independent and never implied by account-links credentials.

What V1 can and cannot do

  • Proof-backed account links (EVM EOA, EIP-191 personal_sign)
  • Exact public Bankd EVM balances (18 decimals, pinned height)
  • Authorized private Shieldd snapshots (6 decimals, capability-resolved)
  • Durable staging of random treasury routing aliases
  • Cannot initiate transactions or payments
  • Cannot debit/credit accounts or mint/burn assets
  • Cannot publish aliases on-chain (publisher_status: disabled)
  • Cannot accept spending keys, FVKs/IVKs, or custody shortcuts