01
Define the record
Choose the information to include and the schema your application will use.
Platform
Digital attestations and signed records
Turn a credential, approval, or statement into a digitally signed record with an identifiable issuer.
Records & verification
Digital records, explained.
A digital signature connects the issuer to the exact information they signed. If that information changes later, the original signature no longer matches.
In the documentation, a signed statement is often called an attestation. It is evidence of what an issuer stated, not an independent investigation of the claim.
Platform
Using digital records
02
Sign and issue
Issue through your workspace or API using the organization’s signing identity.
03
Manage its lifecycle
Keep track of issued records and revoke a record when it should no longer be relied on.
Details and limitations
Digital records: inputs, outputs and limits
What you bring and what you receive
Decide what your record represents before issuing it: a credential, a document fingerprint, an approval or another supported record type. Identify the responsible issuer and the fields a recipient needs to interpret. Keep private source material separate from fields you explicitly publish.
The issued record gives your application an identifier and verification evidence for the signed information. Store that identifier alongside your own transaction so support teams can find the same record. Recipients need the corresponding document if the record only holds its fingerprint.
Operating boundaries and a first test
Organizations configure issuers and permissions in Console. Personal statements belong in Verify. Issuing a record under a self-created name does not independently validate that person's or institution's authority. Issuance allowances and production approval still apply.
Issue a non-sensitive sandbox fixture, verify it, and exercise correction or revocation according to the supported lifecycle. Check that a retry cannot silently create an unintended second business record. Review which fields appear in the public proof before sharing it.
Watch the idea · 30 seconds
Which version did you approve?
When a statement changes, keep a clear link to the earlier signed version. Explain the change instead of hiding the history.
AI presenter and illustrative scenes. This is a product explanation, not a live verification result or customer testimonial.
Choose where to create a statementRead the explanation without video
An announcement can change after people have read it. Truthlocks Proof Frame supports signed statements and linked immutable revisions. Recipients can inspect the evidence behind the version they received. Changing a demonstration copy does not rewrite the original record. A valid signature supports integrity checks; it does not independently make the claims true. Choose your organizational issuer in Console or your personal statement workflow in Verify.