The following table shows a list of the functionality in the BankID sign service, and an overview of supported platforms and envelope formats.
|BankID Server||BankID OIDC|
|Function||SEID SDO||PAdES||SEID SDO||PAdES|
|Both end user signature and merchant signature|
|Merchant signature only|
|End user signature only|
|Multiple end user signatures in the same envelope|
|PAdES turnkey mode||N/A||N/A|
|PAdES self assembler mode||N/A||N/A|
Note that the end result of multiple end user signatures in the same envelope is achieved in different ways for the two envelope formats. For SEID SDO flows, signatures must be gathered from multiple independent signing sessions over the same documents, then assembled into a SEID SDO. Since every signatory signs over the exact same bytes, the order does not matter, and the signings can happen in parallel. This is therefore also referred to as parallel signing.
For PAdES flows, the signed PDF output from one signing session is simply used as input for the next signing session. For a given session, any and all signatures that already exist in the document, are part of the data that is signed over. Because of this, the order in which the signatories sign the document matters. This is therefore also referred to as serial signing.