link

# MobileID InApp electronic signatures

For electronic signatures through Signicat's electronic signature solution, MobileID InApp can be used in two ways; Authentication-based signing and native signing.

# Use case

With Signicat's electronic signature solution, you can use MobileID InApp to sign (as well as view or upload) one or more documents, such as loan applications or contracts (authentication-based signing) or sign general consent texts (such as GDPR consent forms (native signing).

# Authentication-based signing

The first alternative, authentication-based signing, offers mobile device-based signing of documents. This functionality uses Signicat's electronic signature solution, with MobileID acting as an authentication-based signing method just like other ID methods used in a signing process.

For more information about getting started with electronic signatures, the different signing methods and more, refer to our electronic signature documentation.

The input for MobileID authentication-based signature is typically a PDF file. The document is displayed in the browser and the signing process takes place on the mobile device, where a signing title text that connects to the document is shown.

# Signing output

The authentication-based signing process always results in an LTV-SDO, an implementation of XAdES in Signicat's solution, ensuring a unified output format in accordance with EU specifications as well as a scalable, responsive signing interface supporting all modern device standards.

You can find an example of an LTV-SDO as a signing result, with authentication-based signing and MobileID as the authentication method here:

Download Signed LTV-SDO example

# Native signing

The second alternative, native signing, offers signing of text elements such as consent messages. This functionality uses Signicat's electronic signature solution, with MobileID acting as a native (third-party) signing method just like other ID methods used in a signing process.

For more information about getting started with electronic signatures, the different signing methods and more, refer to our electronic signature documentation.

The input for MobileID native signature is a text file with the text to be displayed in the MobileID-enabled app.

# Signing output

Depending on how it is configured by Signicat, the native signing process results in a response in the form of either a signed JSON Web Token (JWT) or an LTV-SDO with a signed JSON Web Token as the payload.

You can find an example of an LTV-SDO as a signing result of a MobileID native signing operation here:

Download Signed LTV-SDO example

# Optional parameters

# Push notifications

It is possible to use push notifications to bring the user's attention to the mobile device. If you have configured these, you can optionally pass additional information back to the merchant's app on the mobile device using the pushPayload property.

# Metadata

It is possible to include metadata about the MobileID authentication-based or native signature transaction to be passed back to the merchant's application.


Usage

To pass additional information regarding push or metadata, include the metaDataor pushPayload parameter in the subject in the signing request, as below:

externalRef=<ACCOUNT_NAME>
deviceName=<DEVICE_NAME>
metaData=<TYPICALLY_BASE64_JSON>
pushPayload=<URL_ENCODED_PUSH_PAYLOAD>

# Further reading

Last updated: 8/17/2021, 4:55:21 PM