Missing a country or a custom check? Tell us what you need.Book a 15-min call

Signed result (JWS)

A verification result signed by the provider, so anyone can check it hasn't been changed.

A JSON Web Signature (JWS) wraps data with a cryptographic signature. When a verification result comes as a JWS, your systems, or an auditor later, can check with the provider's public key that the result is authentic and unchanged, without having to trust the channel it came through.

Signed results as evidence for FINMA and AMLA record-keeping

The Swiss AMLA requires financial intermediaries to keep records of how they identified customers, in a way that lets competent third parties, such as auditors, understand what was done. FINMA Circular 2016/7 also expects the identification process to be documented. A signed result helps, because anyone can later check that the stored outcome is the one the provider issued and that nobody has edited it.

A JWS is not a qualified electronic signature or seal. Under ZertES and eIDAS, qualified signatures and seals need a qualified certificate from a recognised trust service provider. A signed verification result is technical evidence of integrity and origin, which is what record-keeping needs, but it does not have the legal effect of a handwritten signature.

Keeping personal data out of the signed result also supports data minimisation under the nFADP and the GDPR: the result can be stored, shared and archived without copying identity data into more systems.

Checking a JWS

  • Fetch the provider's public keys, published as a JSON Web Key Set (JWKS).
  • Pick the key whose ID matches the kid in the JWS header, and check that the algorithm is the one you expect.
  • Verify the signature over the header and payload.
  • Only then read the payload and compare it with the session it belongs to.

How secuveri handles it

secuveri issues each result as an ES256 JWS that contains no personal data. You can verify it with the public keys published at /.well-known/jwks.json.

Frequently asked questions

What is the difference between a signed result and a signed webhook?
A webhook signature, often an HMAC with a shared secret, proves that a notification came from the provider when it arrived. Only you and the provider can check it. A signed result uses public-key cryptography, so anyone with the public key, such as an auditor, can verify it years later without access to any shared secret.
What is ES256?
ES256 is the JWS algorithm name for ECDSA signatures on the P-256 curve with SHA-256. It produces short signatures and is widely supported in JWT libraries. Because it uses a key pair, the provider signs with a private key that it keeps secret, and anyone can verify the signature with the published public key.
Contact

Talk to us

Tell us what you’re trying to verify. We’ll show you how secuveri can fit your workflow.

We reply within one business day and use your details only for your inquiry. See our privacy policy.