The originating app launches SIGNATUS via an explicit Intent and passes either:
- A PDF file to be signed (opened immediately in SIGNATUS).
- JSON metadata used to populate a document template inside SIGNATUS.
After the signing ceremony, SIGNATUS returns control (and, if applicable, the signed PDF) to the originating app through the Activity-for-Result callback.
Who can benefit from this type of integration? #
Teams that already maintain a proprietary mobile app but need to add secure, biometric-quality handwritten signatures with workflows without building their own signing component.
What has to be done to make it work in the other application? #
The external application must implement intent-based communication to send and receive documents or metadata. Signing is typically triggered via button click or other in-app actions. The integration supports both direct document signing and data-based document creation using the SIGNATUS wizard.
The sections below include code examples in Java and JSON.