Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

Signing of documents and text with merchant and user-certificates with both BankID and BankID on Mobile is now supported through the OIDC platform.

Two different flows exist for these signing processes. For a full implementation guide, please see the Signing Implementation Guide.

Simplified flow

Can be used for signing of a text with either BankID (BID) and BankID on Mobile (BIM). 

The simple flow utilizes the authorize-endpoint and is triggered by using the additional scope sign. When the sign-scope is selected, the request must include a sign_txt attribute containing the actual text to be signed.

Full flow

The Full flow alternative offers support for more advanced use cases.  

  • Can be used for signing text, XML-files and PDF-documents.
  • Signing multiple documents in same session.
  • Customization of signing process.

  • This flow can only be used with BankID (BID), and not with BankID on Mobile (BIM).

The full flow makes use a separate resource server, the SignDoc RS, and consists of three steps:

  1. Place the sign order on the SignDoc RS server
  2. Start the end user sign session
  3. Download the result from the SignDoc RS server


PAdES support will soon be added. Read more about the introduction of PAdES in BankID.


For further information, please refer to the following:








  • No labels