QATrax
View as Markdown

Signatures and bundles

Have your certificates timestamped by a qualified provider — the bundle, the sending, failure, the signed document.


What a signature is

Each certificate you issue is already sealed by qatrax: the JSON of the deliverable is signed, and its PDF carries the service seal and a timestamp. This is the everyday proof of integrity, included in the subscription.

A signature is one step further: the same PDF receives a qualified timestamp, applied by a qualified trust service provider within the meaning of the eIDAS regulation. The date is then presumed accurate (art. 41): it is up to whoever disputes it to prove otherwise. The certificate remains a single document: its original seal is kept intact, and the qualified timestamp is added to it.

The bundle

Send a certificate

  1. Open the Signatures tab of your space (just after Deliverable). The To sign list shows your issued deliverables that have not yet been signed.
  2. Tick those to send, then the confirmation box: one signature is deducted per ticked deliverable.
  3. Click Send to the qualified provider. Each certificate comes back timestamped within a few seconds and moves to the Signed list, from which it can be downloaded.

Nothing is ever sent on its own: sending is a human action, done in your space. The CI key can neither send a certificate nor buy a bundle. The same certificate is never deducted twice, even if you click twice.

If the provider fails

qatrax first retries, for about a minute. If the provider keeps failing, the signature is given back to your balance, and the screen tells you so: nothing is lost, you can send the certificate again later. As long as the service is not open on your space, the tab says so ("service in preparation") and nothing is deducted.

Verify, keep

The full terms are in the general terms of sale.