9. Signing Types
Actors can use one or more of the following signing types, depending on whether they have been enabled in the Configuration Index (see section 6.3 for a call to retrieve the currently enabled types):
Manual
The end user needs to “manually” draw a signature using the mouse or stylus.
BeId
The end user must sign using a Belgian eID.
This signing type requires a third-party smart card reader.
Note: in the previous version of the documentation the "BeId" signing type was called "Digital".
ManualBeId
The end user will sign using a Belgian eID but before doing so draw their signature using the mouse or stylus.
Note: in the previous version of the documentation the “ManualBeId” signing type was called “ManualDigital”.
SmsOtp
A one-time code will be sent to the signer's phone. Depending on the configuration, users may need to complete the last digits of their phone number which was passed in the original request or entered in the Portal's Contact screen. Entering the right code received per sms will initiate the signing.
Server
The eSignatures solution will sign this field autonomously as soon as the package is set to status ‘Pending’.
Note: this signing type can only be used when all locations use the Server signing type, and it cannot be used in combination with choice of signing. It is also restricted to the Instant Package Creation call.
MailOtp
A one-time code will be sent to the signer's email address. Depending on the configuration, users may need to complete their email address which was passed in the original request or entered in the Portal's Contact screen. Entering the right code received per email will initiate the signing.
Idin
Signing by means of Dutch bank card through iDIN.
BeLawyer
The end user must sign using a Belgian lawyer card. This signing type requires a third-party smart card reader.
Biometric
Signing by means of a biometric signature pad. The drivers of a supported biometric signature pad must be correctly installed on your computer.
Itsme
Signing via the Belgian Modile ID itsme app.
Attention: when using the itsme signing type, the following conditions must be met:
- The TargetType must be PdfA1A or PdfA2A. See the parameter's description in 5.7.6. Note that this is the user's responsibility. Connective does not check whether this TargetType has been selected in combination with itsme.
- XML documents cannot be signed with the itsme signing type due to Belgian Mobile ID's terms and conditions.
- A Signature Policy is required. A default signature policy will be configured by the system admin in the Config Index. This signature policy will be applied if the SignaturePolicyId parameter is left empty. If you want to use a customized signature policy, see Appendix IV of Connective – eSignatures 5.5.x – Configuration Documentation to learn how do so.
OpenIdConnect:[Unique Name]
As of eSignatures 5.1 you can add a custom signing type through OpenID Connect. To do so, the OpenIDConnect settings must be enabled and correctly configured in the Configuration Index. See Connective – eSignatures 5.5.x – Configuration Documentation.
Important: always use the ‘OpenIdConnect:’ prefix, then add the Name that was configured in the Configuration Index in the OpenIdConnect settings group.