Feature overview

Three different integration flows are available for signing on the BankID OIDC platform. Each flow offers a subset of features summarized in the table below.
The two full flow alternatives give support for the most advanced use cases through utilization of the SignDoc resource server. The simplified flow is an easier integration alternative but is limited to text signing.



PAdES

SEID-SDO

Simple-text

EnvelopePAdESSEID-SDO
Signature types
  • Combined end user and merchant signature
  • End user signature only
  • Combined end user and merchant signature
  • Combined end user and merchant signature
Document types
  • PDF
  • Text
  • XML
  • PDF
  • Text
Number of documentsMultipleMultipleSingle

Identity Providers

  • BankID netcentric
  • BankID netcentric
  • BankID on mobile (Note: single text only)
  • BankID netcentric
  • BankID on mobile

Multiple end user signatures in same envelope

Serial signing (PAdES increments)



Customization
  • User interface options
  • Timeout for the user signing
  • Configuration of visible seals
  • User interface options
  • Timeout for the user signing

Result content
  • PAdES envelope
  • PAdES appendix
  • Document hash
  • SEID-SDO envelope
  • Basic signature
  • Document hash
  • Basic signature
  • Document hash

A different subset of the signing functionality is available directly through BankID Server implementations. See Signing compatibility matrix for comparison.


A note on BankID on mobile

BankID web client (netcentric) is the default identity provider used for signing. For text-only signing (Simple-text or SEID-SDO) it is possible to use BankID on mobile instead.

In order to use BankID on mobile, the authorization request must contain login_hint=BIM[:[phoneNumber][:birthDate]] as a query parameter.

BankID on mobile has the following limitations: