Skip to main content
The tool calls the bank’s KYC inbox for you. To build the envelope in your own system instead, that page has the format.
1

Create the signing key

Send the public key to the bank. A keystore holds one signing key, and the command refuses to overwrite it. Back up the key file and the passphrase.
2

Store the invite

The bank registers your key and gives you an invite string over a confidential channel. The invite comes through Trusset, so the key in it proves nothing on its own. Call the bank over a channel that does not run through Trusset, for example by phone, and have them read you the fingerprint of their recipient key from trusset-kyc key show on their machine. Never take it from the invite or from anything Trusset serves. Read them the fingerprint of your signing key in the same call. Then store the invite with the bank’s fingerprint:
The command first checks that the recipient key in the invite has exactly this fingerprint. If it does not, it stores nothing and exits with 2: do not use that invite, it may carry a key that is not the bank’s. If it does, it stores the invite and asks the inbox for the bank’s key as a consistency check. Spaces and case in the fingerprint do not matter. Without --fingerprint nothing is stored.invite list shows stored invites without the token, and the recipient key, its key ID and its fingerprint only for a confirmed invite. A new invite for a source you already stored replaces the old one only with --replace, and needs the bank’s fingerprint as well.Invites stored by version 1.1.0 or earlier were never checked against the bank’s fingerprint, and seal and send refuse them. Confirm each with trusset-kyc invite confirm --source <sourceId> --fingerprint '<fingerprint the bank read out>'. A wrong fingerprint leaves the invite stored but not confirmed.
3

Seal a record

Sealing works offline. It writes <envelopeId>.envelope.json, which holds the delivery body: the clear header, the encapsulated key, the ciphertext and your signature. It contains no key and no plaintext. --out <file> chooses another name, and an existing file is never overwritten.Keep the record digest. A revocation names the record by it.
4

Send it

Before it sends, the tool asks the inbox for the bank’s key again. If that key differs from the key your invite pins, or the envelope is sealed to another key ID, it sends nothing and tells you the bank must issue a new invite. seal --send seals and sends in one step with the same check.An envelope must be sent within 24 hours of sealing. Sending the same envelope twice is safe: the second call returns the same record and stores nothing new.
5

Follow the record

It prints the fields of Get Delivery Status: the status, when the bank opened, approved or rejected the record, the reject reason, and whether the wallet is admitted.

The record file

The file given to --record is a JSON object. Its content is free: the tool does not interpret it, and Trusset never sees it. Agree the fields with the bank. For example:
Attachments are files of any type, added with one --attach each. A name must be a plain file name of at most 120 characters, without a path separator or a leading dot, and unique within the record in any letter case. The whole sealed record, attachments included, may be at most 6 MiB (6,291,456 bytes). Attachments are base64 encoded inside the record, so about 4.5 MiB of files fit. seal refuses a larger record and states its size.

Dates

--valid-until is required. --verified-at defaults to the current time. Both take a full timestamp such as 2026-11-10T09:30:00.000Z or a date. A date given as YYYY-MM-DD means the start of that day in UTC for --verified-at and the end of that day in UTC for --valid-until. validUntil is the date until which you vouch for the record. When it passes, the record expires at the bank and the bank is asked to remove the wallet from its whitelists.

Revoke a record

Reasons are EXPIRED, WITHDRAWN, SUPERSEDED, INVALID and OTHER. The tool signs the revocation with your signing key.
A revocation changes the record at the bank and notifies the bank. It removes nothing on chain: a wallet the bank already listed stays listed until the bank’s own wallet signs the removal. See Revoke Record.

When the bank replaces its key

send then refuses with a message that the reported key differs from the pinned one. Ask the bank for a new invite and for the fingerprint of its new key from trusset-kyc key show, store the invite with invite add --replace --fingerprint '<new fingerprint>', and seal the waiting records again. An envelope sealed to the old key cannot be delivered.