Electronic Signatures
There are four general flows you can use to sign documents with eID Easy, ordered by implementation complexity from left to right (simplest first):
| ✍️ | eID Easy Signing Page Flow | API Based Flow | API Based Flow With File Hashes for .asice | API Based Flow With File Hashes for PDF |
|---|---|---|---|---|
| Integration guide | Read more | Read more | Read more | Read more |
| Document contents get sent to eID Easy | yes | yes | no | no |
| Input | any file | any file | any file | |
| Output | .pdf or .asice | .pdf or .asice | .asice | |
| Use cases | Redirect the user to the eID Easy signing page where they can review the document and sign it. This flow is super easy to implement and gets you up and running in just a couple of API calls. | Build your own UI and use the eID Easy API endpoints only to create signatures. This flow is best suited for cases where you wish to build (or already have built) your own signing view or user interface. | Build your own UI and send only the SHA-256 of the file to the eID Easy API for signing. This means that you can collect qualified electronic signatures in your own server without sending the document contents to any third parties. | Build your own UI and send only the SHA-256 of the file to the eID Easy API for signing. This means that you can collect qualified electronic signatures in your own server without sending the document contents to any third parties. |