Why are there two callbacks after all parties have signed a document?

Scrive digitally seals each document twice, resulting in two callbacks.

First, Scrive seals the document using Guardtime.

The second sealing is done with a block chain-based keyless digital signature that makes the document independent of Scrive and Guardtime. You can see this as a bonus sealing. This happens around the middle of each month and only applies to documents that are in the Scrive E-archive at that time.

Which callback are you receiving?

To detect which callback your integration is receiving, it is necessary to keep count of the number of callbacks that have been made for every distinct document ID with the flag:

signed_and_sealed=true

Digital signing details

A digital signature (in the computational/cryptography sense) is applied to the document as soon as all parties have signed. This signature can be used to verify the integrity of the document using the Scrive web page or other means that can verify seals by Scrive’s suppliers certificate (GuardTime is the current supplier).

On approximately the 15th of each month, i.e., usually within 30 days, the document is re-sealed in a process called “extension” as explained below, provided that the document is still stored in the Scrive E-archive.

A hash of the document is included in the block chain that GuardTime supplies. The top level hash key for this block chain is published in the Financial Times every month. With access to a Financial Times issue published about a month after a document has been sealed, it is possible to mathematically verify the document’s integrity independently of Scrive or GuardTime using the key found in Financial Times.

This second sealing triggers a second callback, as the document status has been updated.