A bank can to some degree use Ambita’s signing service (Esignering.no) for customer signing of documents. The use of Esignering.no requires onboarding the bank in both Etinglysing.no and Esignering.no, installing of the bank’s business BankId certificate at Ambita, and a contractual agreement with Ambita.

Pantedokument (mortgage)

When generating a Pantedokument, the options field sendToCustomerSigning can be set to true (see https://ambita.atlassian.net/wiki/spaces/DOC/pages/1202192544/Generate+pantedokument#Using-Ambita%E2%80%99s-signing-service ). All parties that should sign the document must be set (at generation time) and have an email address.

The bank can poll for document status changes using HendelseWs (see https://ambita.atlassian.net/wiki/spaces/DOC/pages/1296662701 )..

When all parties have signed the document, the status of the Pantedokument will change to PART_SIGNERT and the webservice tinglys can be called. The document will again change status when tinglyst (or if tinglysing fails). When tinglysing, a cover letter will be automatically generated and signed using the bank’s business BankId certificate by Ambita.

Sletting (delete mortgage)

The Sletting can be generated using the DokumentWs webservice, but automatic signing and tinglysing is not allowed on Sletting. To tinglys a Sletting, this must be done in the Etinglysing.no GUI - it cannot be don e through webservice integration.