Skip to main content
POST
Acknowledges that you hold the decrypted record. The proof is openProof, a random value the source placed inside the sealed record. Trusset holds only its SHA-256 hash, in the header’s openCommitment, so only someone who decrypted the envelope can send the matching value. Your local tool calls this from trusset-kyc open, after it has verified the record and written the files to disk. You call it yourself only when you open envelopes with your own implementation.
When the proof matches, Trusset deletes the ciphertext and the record becomes OPENED. The envelope cannot be downloaded again. Store the decrypted record first and acknowledge second, as the tool does. The only way to get the file again is a new delivery from the source.

What opening does

  • The record becomes OPENED and held becomes false.
  • The record is linked to the customer record of your instance that holds the wallet. When no customer holds it, a customer record is created for the wallet with the record’s profileKey as its investorType. It holds the wallet and the profile only. Nothing from the KYC file is added, because Trusset cannot read it.
  • A customer.kyc_record_opened event goes to your customer webhooks.
Sending the proof again for a record that is already OPENED or APPROVED changes nothing and answers with the record, so a retry after a lost response is safe. Nothing is written on chain and no whitelist changes here. The next step is Approve KYC Record or Reject KYC Record.

Path Parameters

string
required
The record id from List KYC Records.

Body Parameters

string
required
The openProof field of the decrypted record document: 32 bytes as 64 lowercase hex characters.

Response Fields

object

Error Codes