Skip to content

Release Notes for BankID Signing WYSIWYS

Noteworthy changes in BankID Signing WYSIWYS.

Only important bugfixes, API changes and new features are listed here.

WYSIWYS API Releases

2026-07-02 (PreProd: 2026-06-23)

  • Increased the allowed size of PDF documents in a PAdES sign order to 20 MB per document (Base64-encoded size).
  • Increased the maximum number of documents allowed to 30 per sign order.
  • Introduced a maximum allowed document package size of 100 MB per sign order. This is necessary for system stability and to keep the impact on user experience tolerable. We are working to extend this limitation. Only merchants actively using the increased document sizes and numbers should be concerned by this.
  • Added new field padesSignProperties.extendToLT to the PAdES-V1-API that allows to extend signatures to PAdES-B-LT containing an additional timestamp in order to improve recognition of short-lived certificates by Adobe Reader.

2026-04-29

Added showing of the merchant name on the index page (first page).

This is done automatically for all sign orders and does not require any merchant-side actions. The name registered to the merchant´s client and provided with the access token will be used for this (field clientName in the token).

2026-03-19 (PreProd: 2026-03-12)

  • Increased the allowed size of PDF documents in a PAdES sign order to 10 MB per document (Base64-encoded size).

2026-03-05

  • Added content to the already existing signerInfo field in the PAdES-V1-API´s DELETE-call. It contains a JSON Web Token signer information if the data was requested during sign order creation.

2026-02-18

  • Added new field signProperties.continueButtonTargetText to the PAdES-V1-API that will enable merchants to influence how the "Continue"-button on the finish-page is labelled. This way it will be possible to add a target to be displayed in the UI, e.g. by adding "MyMerchant´s Portal". Instead of "Continue" the button would be labelled "Continue to MyMerchant´s Portal".
  • Added new field signProperties.merchantWorkflowState to the PAdES-V1-API that allows WYSIWYS to differentiate between a stand-alone sign order and a merchant workflow. For stand-alone sign orders nothing will change. If a sign order is marked as part of a workflow, the WYSIWYS UI will show a notification on the finish page that will remind the user that others still have to sign and they should download the final documents from the merchant´s website when everyone has signed.
  • Slightly reduced the base-seal-size used for seal-position-validations to make defining a valid position easier. Note: The actual seal size remains unchanged.

2026-01-18

  • Fixed HTTP-500 error when calling GET endpoints (e.g. /v1/signdoc/pades).
  • Corrected validation of seal position parameter to allow closer positioning on the Y-axis.

WYSIWYS (User Interface) Releases

2026-04-29 (version 5.3.0)

  • Translated the failure and the success page to Norwegian when the language is set to Norwegian. The "failure" and "success" pages are now "feil" and "oppsummering" respectfully.
  • If the document does not have a ".pdf" in the description or name, we add it to the file name when it is downloaded by the user
  • The merchant name is now visible on the index page of the app.
  • The timed out state is now handled as should be and shows a proper message to the user when the session has timed out.
  • Switching language when signing big documents should now work better. We have added a loading spinner to show that the app is working on switching the language and we have also optimized the code to make it faster.

2026-03-19 (PreProd: 2026-03-12) (version 4.6.3)

  • Make sure the app can handle big documents by only loading the first 15 pages and then lazy loading the rest of the document when the user scrolls down.

2026-03-05 (version 4.6.1)

  • The warning message about attachments on a document have been toned down.
  • The continue button on the success page can only be clicked once to prevent multiple requests being sent.
  • Added an error_code parameter if it is present to the redirect URL when an error occurs during signing. This will allow merchants to handle errors better on their side.

2026-02-18

  • Implementation of the new API fields mentioned above.
  • In case of errors during the signing process the same error code that is shown to the user in the front-end will be returned as parameter with the callback URL to the merchant.

2026-01-15

  • Added dark-mode to the application (activation based on system preferences).