A signing session is a request sent to the signer gateway with one document or one or more hashes for the purpose of getting them signed. A unique reference is maintained for each signing session and gateway counters are deducted for successful signing sessions.
The signer gateway accepts a document or a list of Hashes in either PDF or XML or Data formats for the purpose of getting them signed. If PDF documents are sent, the signer gateway automatically pads the visual appearance of the signature type selected back to the document
In the signer gateway, all transactions are associated with the user that purchased the signer gateway subscription (typically your administrator). Gateway logs are available on the dashboard for the purpose of reporting.
The signer gateway authenticates incoming requests through a combination of app secret keys and user auth tokens.
The signer gateway only accepts encrypted requests. All documents sent to the signer gateway must be encrypted with a random session key. Documents are also hashed and encrypted. The signer gateway validates that data has not been tampered in transit before allowing users to sign on documents.