RFC 3161
Source describes RFC 3161-compliant time stamping.
DEVELOPERS · CHECKID
RFC 3161 TSA — Related Capability
Related CheckID/Trusted Hub TSA capability, separated from core CheckID identity verification.
CONTRACTVersioned API / SDK
AUTHOAuth2 / environment
OUTPUTResponse · result code · evidence
RELATED CheckID / TRUSTED HUB CAPABILITY
RFC 3161 Time Stamping Authority
TSA is separated from core identity verification to preserve the product boundary.
Source contractSection 6 · Time Stamping Authority
Authentication
Basic authentication in source TSA profile.
Hash algorithms
SHA-256 · SHA-384 · SHA-512.
Usage control
Source describes flexible sign-package / per-user usage limits.
SOURCE STATUS
TSA integration contract
Not publicly specified
Status
The baseline ZIP does not contain an authoritative contract sufficient to implement this operation.
Required source
timestamp endpoint/profile, authentication, RFC 3161 mapping, evidence retention
Publication rule
Do not invent endpoints, fields, retry policies or sample JSON.
Integration impact
Developers require the partner/API specification before production integration.