Skip to main content

Transaction status

This article describes the different statuses that a transaction in Signhost can have.

Updated over 2 weeks ago

From the dashboard, the transaction overview, and the transaction details in the web portal, you can view the status of the transaction. Do you want more information about the technical statuses and activities in the API? Please refer to our API documentation.

Once a transaction is created, it cannot be modified or restarted. Understanding the status of your transaction is important to follow the process correctly.

Below you will find an overview of the possible transaction statuses in Signhost:

Status 5: Waiting for document

This status is visible only briefly and indicates that the system is waiting for the document that needs to be signed to be uploaded to the transaction.

  • Please note: Normally, this process is very short. If a transaction remains in the "Waiting for document" status for more than 5 minutes, please read this article.

Status 10: Pending

This is the most common status during a transaction. As long as at least one signatory still needs to sign the documents, this status will be visible.

  • Questions? If you are wondering whether the invitation email has already been sent or which signatory(ies) still need to sign, you can consult the Transaction Details in the web portal.

  • If a transaction has the status 10: "Pending", you can manually reshare the signing link(s) with the signatory(ies).

Status 20: In progress

When the Signhost server is processing the transaction (for example, after sending an invitation or after placing a signature), the transaction will have the status "In progress".

  • Please note: Normally, this process is very short. If a transaction remains in the "In progress" status for more than 5 minutes, please read this article about this status.

Status 30: Signed

This is the final status where all documents in the transaction have been successfully signed by all required parties.

  • Both the signed document(s) and the transaction receipt can be downloaded for up to 30 days after full signing via the link in the email or via the Transaction Details in the web portal.

Status 40: Rejected

If a signatory rejects the offered transaction during the signing process, the status of the transaction will become "Rejected".

  • The signatory is required to provide a reason for rejection. This reason for rejection is communicated both via email and displayed in the Transaction Details.

Status 50: Expired

When a transaction remains open longer than the predefined period, the status will automatically change to "Expired".

Status 60: Cancelled

The status "Cancelled" indicates that the transaction has been manually cancelled by the sender of the signing request.

Status 70: Failed

The status "Failed" indicates a technical problem that prevented the transaction from being completed successfully.

  • When a transaction fails, a notification with information about the cause is sent to the sender's email address.

We hope this overview helps you better understand the different transaction statuses in Signhost. If you have any further questions, please do not hesitate to contact us.


Our support team is happy to assist you via chat or via support@signhost.com


Did this answer your question?