Frequently asked questions and troubleshooting for Uanataca Timestamp (TSA) end users and integrators. Short answers are given below; for more technical details, see Developer documentation — Usage reference.
Billing credentials are the credentials used by the platform to meter and bill your usage of Timestamp (and other services such as One-Shot and SignBox). You use them as HTTP Basic Auth (username and password) when sending timestamp requests to the TSA endpoint.
To obtain billing credentials, contact your commercial contact or Operations directly.
Yes. The full workflow with OpenSSL and curl is documented in the Usage reference. It covers:
- Hash generation — Create a timestamp query (
.tsq) from your file with OpenSSL (e.g. SHA-256). - Timestamp request — Send the
.tsqto the TSA endpoint withContent-Type: application/timestamp-queryand your Billing credentials. - Verification — Inspect the timestamp response (
.tsr) with OpenSSL.
All commands and parameters are in that page. For prerequisites and Billing authentication, see Get started.
You can timestamp any data you can represent as a hash. The TSA does not receive the original content—only a SHA-256 digest. So you can timestamp:
- Files — PDFs, documents, images, binaries (OpenSSL can hash the file and build the
.tsq). - Any binary or data — As long as you produce a SHA-256 hash and build a valid RFC-3161 timestamp query from it.
The timestamp proves that a given hash existed at a specific time; you keep the original data and the .tsr for proof. See Usage reference for the exact workflow.
Use the following TSA endpoints with HTTP POST, Content-Type: application/timestamp-query, and HTTP Basic Auth (Billing username and password):
| Environment | Endpoint |
|---|---|
| Production | https://tsa.uanataca.com/tsa/tss03 |
| Sandbox | https://tsa.sandbox.uanataca.com/tsa/tss03 |
For the full request format and examples, see Usage reference and Get started.
For more technical details, see Developer documentation — Usage reference.