Skip to main content
POST
Revokes a record you delivered, with a statement signed by your signing key. Use it when the verification no longer stands, was issued in error, or is replaced by a new one. The statement names the record by its recordDigest and its wallet. The envelopeId is not used.

What a revocation does

  • The record becomes REVOKED, with your reason. Trusset deletes the ciphertext if it still holds it.
  • The bank receives a customer.kyc_record_revoked event.
  • From then on the record no longer supports listing the wallet on the bank’s whitelists.
A revocation removes nothing on chain. A wallet the bank already listed stays listed until the bank signs the removal with its own wallet. Trusset shows the bank that a removal is due and builds the transaction, but cannot send it. If the removal is urgent, tell the bank directly.
A record that is RECEIVED, OPENED, APPROVED, EXPIRED or SUPERSEDED can be revoked. A record that is REJECTED or UNCLAIMED stays as it is: the call answers 200 with that status and replayed: false. Revoking a record that is already REVOKED answers 200 with replayed: true. A paused source can still revoke.

The statement

The header carries exactly the 8 keys below, as compact JSON, and travels as base64url without padding. See Revocations for the rules and the signature.
reason is EXPIRED, WITHDRAWN, SUPERSEDED, INVALID or OTHER. Trusset treats the five the same way and passes the code to the bank as revokeReason. What each one means in your process is for you and the bank to agree. The statement has no free-text field.

Path Parameters

string
required
Your source ID, from the invite.

Body Parameters

string
required
The revocation header bytes as base64url without padding. issuedAt must not be older than 24 hours and at most 10 minutes ahead.
string
required
Your 64-byte Ed25519 signature over the UTF-8 bytes of trusset-kyc-revocation-v1 and a line feed, followed by the SHA-256 hash of the header bytes. Standard base64 with padding.

Response Fields

object

Error Codes