For the complete documentation index, see llms.txt. You can also append .md to any page URL to get its markdown version.
Skip to main content
For the complete documentation index, see llms.txt.

For the complete documentation index, see llms.txt

LTV-SDO changes for Enterprise signing

When your Enterprise signing solution receives its upgraded signing engine, you can continue using the Enterprise Sign API (Sign API v1) with the same request structure. The upgraded engine is the one used by our Sign API v2 on our Digital Trust Platform (DTP). Your API integration continues to work, but the long-term validation signed data object (LTV-SDO) returned for each signed document changes.

These changes apply when Signicat upgrades the engine behind your existing Sign API v1 integration. If you are migrating your integration directly to Sign API v2, use the Sign API v2 integration guide.

The LTV-SDO is the signed evidence file for a document and its signer. If you only archive it, you need no changes. If you parse or validate its contents, check which changes affect you.

Do I need to act?​

Yes. If you use the Enterprise Sign API (Sign API v1), this upgrade affects you. Read this page to find out whether you need to change your integration.

For authentication-based signing, use the authentication-based signing checklist. For the BankID methods below, check the required actions in this table.

When will this change take place?​

We upgrade customers in waves. Your pre-production environment is upgraded before your production environment, so you can test your integration before the production upgrade.

  1. We email you the upgrade dates for your pre-production and production environments.
  2. We upgrade your pre-production environment and email you to confirm. Test your integration and send us your feedback before the production upgrade.
  3. We upgrade your production environment on the announced date.

Use the before and after examples in this guide to prepare your integration.

Does this affect existing signing sessions?​

No. In each environment, only signing orders created after the upgrade return the new LTV-SDO. Orders created before it return the current LTV-SDO for all their sessions, including sessions still in progress and sessions created after the upgrade.

The engine is chosen when the signing order is created. All later operations on that order, including signing, use the same engine. LTV-SDOs you have already received do not change.

Signing methods​

Read the page for each signing method you use, in addition to the common changes on this page.

Method names vary between integrations. Common names are nbid-sign and nbid-csc-sign for Norwegian BankID, and sbid-sign for both Swedish BankID methods. To find the page that applies to you, check the method type. In the REST API, it is the type of each entry in signatureMethods:

Method type in the REST API
"signatureMethods": [
{
"type": "SIGNED_STATEMENT"
}
]

Authentication-based signing applies to any eID. Its dedicated page also covers the changes shared by Signed Statement methods. Read it alongside the Swedish BankID Signed Statement page if you use that method.

What stays the same​

For the BankID methods listed above:

  • The signed document, DocumentDigest and DocumentMimeType.
  • The signer details: SignerDisplayName, SignerNationalId, SignerNationalIdType and SignerUniqueId. For the exception affecting SignerNationality, see Other authentication-based signing changes.
  • SignatureTypeFriendlyName and SignatureFormatFriendlyName for PDF documents with third-party signing. For Signed Statement, SignatureTypeFriendlyName is always Signicat Sign after the upgrade.
  • The LTV-SDO version, signature policy and packaging policy.
  • The native eID signature is still included in the LTV-SDO.

Common changes​

These changes apply to the BankID methods listed above, unless marked Third-party signing only. For authentication-based signing, follow the dedicated page.

XML examples are simplified: namespace declarations are omitted and ... marks shortened values.

LTV-SDO seal​

Signicat seals every LTV-SDO with an XML signature (ds:Signature). After the upgrade, the seal uses a new certificate and a different signature structure.

Seal algorithms before the upgrade
<ds:SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/>
Seal algorithms after the upgrade
<ds:SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha256"/>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>

Third-party signing only: The long-term validation data changes from OCSP to a signature timestamp, CRL and OCSP.

If you validate the seal with your own code:

  • Make sure your library supports ECDSA, XAdES 1.4.1, exclusive C14N, XPath Filter 2.0 and SigningCertificateV2.
  • If you pin the seal certificate, add the new certificate to your trust configuration. Keep the current certificate to validate LTV-SDOs from signing orders created before your upgrade.

Before your upgrade, contact Signicat Support to request the new LTV-SDO seal certificate and trust chain for each environment you use. The new engine also uses this seal key and certificate to sign embedded SAML responses, so use the same certificate when configuring trust for those signatures.

Signature context components​

SignatureCreationContext and SignatureVerificationContext list the software components that built the result. After the upgrade, component names and versions reflect the new engine. The context Type and the user-agent component stay the same.

Don't make your code depend on specific component names or versions.

Transaction ID​

Third-party signing only: The transaction-id reference in the signature context and audit trail changes from 64 hexadecimal characters to a 36-character UUID.

Transaction ID formats
Before: 64 hexadecimal characters
After: 3b9f6c1e-8a2d-4f5b-9e3a-7c1d2b4a6e90

If you store or validate this value, accept both formats and make sure your storage fits both.

Audit trail​

Third-party signing only: The started-transaction event no longer contains document-artifact. This internal ID has no equivalent after the upgrade.

Audit trail events also differ between the engines, and some BankID events are removed. The page for your signing method lists the removed events and fields. If you read audit events, don't require a fixed set of events.

Document references​

After the upgrade:

  • DocumentTitle contains the file name or Document instead of the description from your order.
  • ExternalContext contains a Signicat task ID instead of a reference you set.

Identify documents with your own order or document reference instead.

Timestamps​

Timestamps can use any UTC offset and can include fractional seconds. For example, 2026-10-29T21:31:46Z and 2026-10-29T22:31:46.000+01:00 represent the same instant.

Parse timestamps as ISO 8601 and compare the parsed times, not the strings.

Checklist​

  • Your seal validator supports ECDSA, XAdES 1.4.1, exclusive C14N, XPath Filter 2.0 and SigningCertificateV2.
  • Your trust configuration contains both the current and the new seal certificate.
  • Your storage and validation accept both transaction ID formats.
  • You identify documents with your own reference, not DocumentTitle or ExternalContext.
  • You parse timestamps as ISO 8601.
  • Your code handles removed audit events and changed context components.
  • You have checked the page for each signing method you use.
  • You have tested your integration in pre-production and sent us your feedback.

Support​

If you have questions about your integration, contact Signicat Support.