
As mentioned in a previous blog post, starting 1 January, the Itsme eSign service is used in OKSign to securely sign documents.
The itsme® eSign service, provided by Belgian Mobile ID NV, enables users to apply a Qualified Electronic Signature (QES) to a PDF document. This is the highest legally recognised signature level under the European eIDAS regulation. A QES has the same legal value as a handwritten signature and is accepted throughout the European Union.
This means that from 1 January 2026, all signatures made via the itsme® eSign service will automatically be qualified signatures, with enhanced legal and technical processing.
Because the Itsme signature is a qualified X.509 signature, it is added at the end of the document on a separate page (see screenshot). At the location where you placed signature fields in the OKSign Editor (or via the API), a message appears indicating that the official signature can be found on the last page of the signed document.
If additional signatures are added later — via Itsme eSign or any other signing method — they will also appear on this final page.
From 1 January onwards, every Itsme signature will automatically be a Qualified Electronic Signature. For OKSign users, nothing changes: you continue defining signature fields in the Editor (or via the API) exactly as before.
For the signer, the experience remains unchanged. The familiar Itsme app workflow stays the same. Only once may the signer be asked to approve the creation of an X.509 certificate, which will then be used during the signing process.
The signing steps remain identical:
In Adobe Acrobat Reader, you can view the certificate details at any time (see screenshot below).
Follow these steps:
Note that the first screenshot shows Signed and all signatures are valid, and the second shows The document has not been modified since this signature was applied.
This confirms that the signature is legally valid and that the document has not been altered after signing.
The signature also includes an embedded timestamp, providing a legally reliable signing date.
The creditsinfo -> subscription value will always be 0, as the cost of the Itsme eSign service is added to the credits parameter. Example:
[
{
"signerid": "bt_00000000-0000-0000-0000-000000000001",
"signingoption": "itsme",
"credits": 4.2,
"subscription": 0
}
]
Do you have questions or need advice on how to best use the itsme® eSign service within your organisation? Our team is ready to assist you (support@betrust.be).