> For the complete documentation index, see [llms.txt](https://help.hippoly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hippoly.com/using-hippoly/e-signing/signing-methods.md).

# Signing methods

When sending a document for e-signing, you choose a signing method for each signer. The signing method determines how the signer verifies their identity before signing. The available methods depend on the level of assurance your organisation requires.

## Available methods

| Method                         | Country | Verification                                                                                                                               |
| ------------------------------ | ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Swedish BankID**             | Sweden  | The signer verifies their identity using Swedish Mobile BankID. Their personal identity number (personnummer) is required.                 |
| **Norwegian BankID**           | Norway  | The signer verifies their identity using Norwegian BankID.                                                                                 |
| **Danish MitID**               | Denmark | The signer verifies their identity using Danish MitID. Their CPR number is required.                                                       |
| **Finnish FTN**                | Finland | The signer verifies their identity using Finnish Trust Network (FTN).                                                                      |
| **SMS**                        | Any     | The signer receives a PIN code by SMS and enters it to confirm their identity. A mobile phone number is required.                          |
| **No additional verification** | Any     | The signer signs without additional identity verification. Use this when the signer's identity is already established through other means. |

## Default signing method

Hippoly automatically suggests a signing method for each signer based on how they sign in to Hippoly. For example, if a user logs in with Swedish BankID, Swedish BankID will be pre-selected as their signing method. This saves time and ensures consistency, but the person initiating the signing can always change the method for any signer before sending.

## Choosing the right method

The best method depends on the document and your organisation's requirements:

* **For legally sensitive documents** such as board resolutions, contracts, or annual reports, use a strong verification method like **BankID** or **MitID**.
* **For internal documents** where signers are already known and trusted, **SMS** or **no additional verification** may be sufficient.
* **For cross-border signing** where signers are in different countries, you can mix methods, for example Swedish BankID for Swedish signers and SMS for international signers.

{% hint style="info" %}
Your workspace administrator can configure whether personal identity numbers are shown or hidden in the signing evidence log, depending on your organisation's privacy requirements.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.hippoly.com/using-hippoly/e-signing/signing-methods.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.