T1C signing

To perform T1C bulk document signing via API using client-side signing, follow the steps mentioned below. These steps outline the APIs and user actions involved in signing multiple documents directly from the client side.

1. The signatory is identified via the access token provided in the API call, which means authentication is required before initiating the signing process. The access token must be issued directly to the signatory through authentication API.

2. If modifications are needed before signing, the Fill Form Fields API should be called beforehand. Note that any mandatory input fields must be completed for the signing process to succeed.

3. To determine which Signing Servers should be displayed based on a signature field’s level of assurance, the signature application must call the Get Signature Settings API. This API provides details of all available signing servers along with their corresponding levels of assurance.

4. The signature application needs to call Bulk Signing Pre Validation API. This API executes pre-signing validations for each document package and respectively returns any errors along with the list of tasks that the application needs to perform to complete the signing process.

5. To run T1C, you must install the utility by downloading the setup using the Download T1c Setup API.

6. To access T1C APIs for signing, you first need to obtain a token by calling the Get JWT Token API.

7. The T1C utility reads the card reader (USB token) and returns an array of encoded Base64 certificates along with the certificate ID. To display the certificate CN in the Signing Dialogue Get Certificates Detail API endpoint is used to decode the certificate.

8. The signature application calls the Pre Bulk Local Signing API to initiate the processing of all packages. This API returns a transaction ID along with the signing status and any failed packages.

9. If the status is Pending the signature application periodically calls Bulk Signing Status API to check the status. Once the Data to be Signed (D2S) for all packages is received, the process continues.

10. Once the D2S array is available, the application prompts the user to enter a PIN. Then, for each item in the D2S array, the application sends a signing request to the T1C server, including the PIN and corresponding D2S. The T1C server responds with the raw signature bytes for each document.

11. The list of raw signature bytes, along with their corresponding package IDs is then sent to the Post Bulk Local Signing API to complete the signing process.

12. Finally, after signing, the Get Document Verification API can be used to retrieve the verification response.