SIGNiX offers a full range of integration options from very lightweight API usage for document disposition, to usage of the SIGNiX platform (Signature Engine™) as a way to get forms filled and signed on customer portals, to a full re-skinning and seamless embedding of the SIGNiX user interface into the customer’s systems.
Not only can every aspect of a transaction be controlled, but the customer can also check the status of an ongoing transaction at any time. Once a transaction is complete, the customer would be notified and can immediately request that the signed document(s) be uploaded into its systems, along with a digitally signed XML or PDF representation of the complete audit trail (TotalAudit™). Information from the XML event history can be parsed and populated back into the enterprise application system to include times and dates of specific signatures, consent acceptances, document views, authentications, and even agreements and acknowledgements of specific documents. The diagram above shows a typical integration process flow.
Systems integrated with SIGNiX first set up a transaction via an initial call to our service (API: SubmitDocument). This call contains all of the information about how a transaction will proceed: signers, authentication, documents, process, preferences, etc. SIGNiX then kicks off the transaction, though the context in which the notification for signature happens depends on the customer’s integration and experience requirements. SIGNiX can deliver emails, or alternatively can provide a signing link back to the customer that can be presented via a pop-up or button (API: GetAccessLink). Several integration examples are described in the Use Cases section of this website.
Throughout the process, SIGNiX will send push notifications back via Web Service as various transaction and party milestones occur. At transaction completion, customer systems can send the API: DownloadDocument call, which retrieves completed, tamper evident signed PDFs as well as the audit trail.
