> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hocdoc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Acceptance and certificate

> How the recipient accepts an offer without an account, what happens afterwards and how the certificate can be verified.

The recipient accepts an offer on the public page. They need no account for this: name, email address and a code that arrives by email. The acceptance produces a certificate as a PDF. If you turned on additional signers, a countersignature or a signature when sending, acceptance works differently: see "Several signers and countersignature" below.

## What the recipient sees

At the top is a bar with your logo (without a logo, with the brand and the workspace name), "Offer for" with the recipient's name and "Valid until" with the date. Below follow the offer's sections. The **Acceptance** section contains the form. It appears exactly once in every offer. Below the offer are:

* the link **Download the offer as PDF**,
* a card "Summary for decision makers" (see below),
* the sender's details: company, address, contact, website, legal notice and terms, as far as you maintain them in [Settings](https://docs.hocdoc.com/en/guides/settings.md).

The public page has no button to decline. The recipient can only accept. If the offer provides packages or add-ons to choose from, they choose before accepting (see "Recipient's choice"). More about the section: [Sections](https://docs.hocdoc.com/en/guides/sections.md).

## Acceptance without an account

**1. Name and email address**

The form in the Acceptance section has the fields **Your name** and **Your email address**. They are not prefilled. A checkbox is added: "I accept this offer as binding and agree to electronic processing." All three entries are required.

**2. Request a code**

A click on **Request code** sends a 6-digit code to the address given. The email's subject begins with "Your confirmation code:" and names the code. The code is valid for 15 minutes.

**3. Enter the code and accept**

The page shows "We've sent a 6-digit code to" with the address. The recipient enters the code under **Confirmation code** and clicks the button that carries the offer title in quotation marks with the word "Accept" in front (or your own text, see "Text of the accept button"). If no code arrived, **Request code again** helps.

On acceptance, name, email address, time, IP address and browser identifier are recorded, plus the check value of the offer content and an image of the accepted offer.

### Limits for codes

| Limit | Value |
| - | - |
| Validity of a code | 15 minutes. After that: "This code has expired. Request a new code." |
| Wrong entries per code | 5. The page names the remaining attempts. After that: "Too many attempts. Request a new code." |
| Code requests per address and offer | 5 per hour |
| Different addresses per offer | at most 3 within 24 hours |
| Requests per IP address | 10 per hour, across all offers |

If one of the three limits for requests applies, it says: "Too many requests. Please try again in an hour." If you send the offer again, codes already requested expire.

An offer can only be accepted once. Anyone who opens the link afterwards sees "Offer already accepted". If the offer has expired or been withdrawn, acceptance is no longer possible.

## Text of the accept button

You set the text of the button in the third step ("Enter the code and accept") in the settings (tab "Sender", card "Accept button", see [Settings](https://docs.hocdoc.com/en/guides/settings.md#accept-button-card)). This means the button that triggers acceptance or signature after the code is entered. It applies to the simple flow and to the flow with signatures.

* **Without your own text:** The button shows the word "Accept" and the offer title in quotation marks. As soon as the process has more than one signature (additional signers or countersignature), it says "Sign".
* **With your own text:** The text appears on the button. If the process has several signatures, it appears for every external signer instead of "Sign". A long text wraps onto several lines on a phone and stays inside the card.
* **Recorded when sending:** The text applies as it was set when sending. Later changes to the default do not change sent offers. They only apply to offers you send afterwards. An offer that was sent without a text keeps the standard text, even if you set a text later. If you send it again, the text set at that time applies.
* **Stays unchanged:** **Request code** and the text of the checkbox ("I accept this offer as binding and agree to electronic processing.") cannot be set. The button's text appears in neither the certificate, nor the offer PDF, nor any email.
* **Builder and preview:** There the text from the **Accept button** field of the Acceptance section still appears. Your text from the settings only appears on the recipient's page, and the **Accept button** field only in the builder and in the preview.
* **Countersignature:** The countersignature in the app stays unchanged.

## Recipient's choice

If an offer has several packages or at least one add-on in the [Pricing](https://docs.hocdoc.com/en/guides/sections.md#pricing) section, the recipient chooses before accepting. A single package without add-ons is a fixed price. There is nothing to choose, and everything works as described above.

### How the recipient chooses

* The page shows the packages as cards. When opened, the recommended package is chosen, otherwise the first. A click on another card chooses it. Exactly one package is always chosen.
* Add-ons appear as rows with a checkbox below. They are only ticked if you ticked them in the builder for opening. The recipient ticks or unticks them.
* A line below the packages shows the choice and the total, for example "Your choice: Complete + Support". The box in the **Acceptance** section also names choice and total.
* The page adds up amounts with the same wording of billing (for example "one-time") and the same currency. One-time and monthly amounts stand side by side. Amounts are never rounded: an amount with cents shows with cents.
* If the offer has several Pricing sections, the recipient chooses in each. The box in the Acceptance section then names the choice and its total per Pricing section. The totals across all sections ("Overall") only appear after acceptance: on the detail page, in the certificate, in the offer PDF, in the emails and on the "Offer already accepted" page.

### When the choice is locked

As soon as the recipient chooses **Request code**, the choice is locked. The cards and checkboxes can no longer be clicked. The code is valid only for exactly this choice. The code email names it with the words "The code is valid for this selection". If the recipient wants something different, they click **Change choice** ("You can change your choice now. The previous code is no longer valid, you'll receive a new one."). The page does not need to be reloaded for this. The choice is free again, the previous code also expires on the server, and the next code applies to the new choice. In a process with several signers too, a new choice needs a new code. Wrongly entered codes keep counting: **Change choice** does not lift a lock after too many failed attempts. If it does not work, it says: "Your choice can't be changed right now. Please try again." In the flow with signatures (see "Several signers and countersignature"), **Change address** also leads back to the form. The choice is then free again, and the next code applies to the new choice.

If you send the offer again between code and acceptance, nothing is accepted. The old code no longer applies, and it says: "There is no code for this process. Request a new code." (for several signers with a bound address the combined message "The code isn't correct or is no longer valid. Please check the code and email address or request a new code."). "The offer has changed. Please reload the page." only appears once the recipient then requests a code with **Request code again** for a choice that no longer fits the new version, or if the new send turned on signatures. The recipient reloads the page and chooses again.

### Several signers

With several signers, the first external signer chooses. Their choice is saved with their signature. All further signers see it fixed and cannot change it. The countersignature in the app signs the same choice. The choice is therefore fixed before the offer counts as accepted.

### What is saved and where you see it

The choice is saved with the acceptance (in a process, with the first signature) and never changed afterwards. Names, prices, wording of billing and totals are saved as the recipient saw them. They are part of the image covered by the snapshot hash. You see it here:

| Place | What it shows |
| - | - |
| Detail page | **Recipient's choice** card ("Which package and which add-ons were chosen.") with **Package**, **Add-ons** and **Total**, and for several sections also **Overall** |
| Certificate | "Selected services" section before the check values |
| Offer PDF | The choice in the header, with names and "Total" |
| Confirmation email to the recipient | The choice and its total |
| "Accepted:" email to you | The choice under the label "Selected" |
| Invitation to further signers | The sentence "The selection for this offer has already been made:", plus "Selected: …" and "Total: …" (see below) |
| Timeline on the detail page | The entry "Selected: …" (see below) |
| API and webhooks | The `choice` field (see below) |
| Page after acceptance | Choice and totals |

Before acceptance, the offer value in the list, overview and pipeline value is calculated with the preselection (package plus preselected add-ons with the same currency and the same wording of billing). As soon as the choice is fixed (at acceptance, for several signers with the first signature), the actual choice counts. In both cases only the first visible Pricing section counts, and of the add-ons only those with the same currency and the same wording of billing as the package.

> [!NOTE]
>
> An offer can only be sent if the choice can be saved later: at most 20 Pricing sections with a choice and a selection that is not too extensive. The builder reports it before sending.

Accepted offers and versions from before the choice existed stay unchanged and have no **Recipient's choice** card. An offer that was already sent with several packages now also requires a choice.

### Timeline, invitation, API and webhooks

#### Timeline on the detail page

The **Timeline** card has an entry that begins with "Selected:" and names the chosen package and add-ons, for example "Selected: Basic + Support (total: €1,500 one-time · €290 per month)". It appears at acceptance under "Accepted". There is at most one entry per sent version, namely for every version for which a choice was made. If the offer is sent again after the first signature, the old version's entry stays, and the new version gets its own as soon as a choice is made there. If the offer has no choice, for example a fixed price, it is missing.

With several signers, the entry already appears after the first signature, under "Signed by … (1 of 2)", not only at acceptance. Names and amounts stay as the recipient saw them.

#### Invitation to further signers

The email "Your signature for …" to the next signer names the fixed choice: "The selection for this offer has already been made:", followed by "Selected: …" and "Total: …". It does not say who chose. If the offer has no choice, the email stays unchanged.

#### API and webhooks

The choice is also in the offer's `choice` field. You read it through the [API](https://docs.hocdoc.com/en/api/introduction.md#choice-of-the-recipient) and get it in every [webhook](https://docs.hocdoc.com/en/api/webhooks.md) with `data.offer`. Without a choice it is `null`. With several signers it is set from the first signature on. The messages to Slack and Teams do not name the choice.

## Acceptance by another person

With exactly one external signer, the form is not bound to the recipient's address. With several signers, every signature is bound to an address (see "Several signers and countersignature"), and this section does not apply.

If the recipient forwards the link, another person can accept too. The code goes to the address they give. The name and address from their input count as the signer.

If the address differs from the recipient address in the send, the timeline says "Code requested from a different address". The **Acceptance** card on the detail page shows who accepted.

## Several signers and countersignature

If you turned on additional signers, the countersignature or the signature when sending (see [Sending](https://docs.hocdoc.com/en/guides/sending.md)), a different flow replaces the form in the Acceptance section. All signers open the same link. They sign one after the other, and the offer only counts as accepted after the last signature.

### What the public page shows

Above the form is the "Signatures" list. It shows every visitor the same thing:

| Entry | Content |
| - | - |
| Signer | The name from the send. |
| Countersignature | "Countersignature by" with your workspace's name. |
| Status | "signed on" with date and time, "next to sign" or "pending". Times are in the sending workspace's time zone. |

The list shows no email addresses and never another person's signature. The page's header line still names the recipient, even if another signer is reading. After acceptance the page no longer shows the list.

### How everyone signs

**1. Name, address and consent**

The fields are called **Your name** and **Your email address**, plus the checkbox "I accept this offer as binding and agree to electronic processing." With several signers, above it says: "\[Name] signs next. Please use the email address this offer was sent to." with the name of the person whose turn it is. The **Your name** field is then prefilled with the name from the send. If the signature is required, the **Your signature** field sits in between (see below).

**2. Request a code**

**Request code** sends a 6-digit code to the address. The page shows: "If this address is intended for the signature, we've sent a 6-digit code to" followed by the address. Without binding to addresses it says: "We've sent a 6-digit code to" followed by the address.

**3. Enter the code and sign**

The code goes into the **Confirmation code** field. The button is called **Sign**. If there is only one signer (for example, if only the signature is required), it is called as in the simple flow: "Accept" and the offer title in quotation marks. If you set your own text for the accept button, it appears on the button for every external signer, instead of "Sign" and instead of "Accept" with the offer title (see "Text of the accept button"). There are also **Request code again** and **Change address**.

Afterwards the page shows the card "Your signature has been received" with the text "The offer counts as accepted once everyone has signed. You will then receive a confirmation by email." and the current list. If only the countersignature is missing, it says: "All signatures are in. The countersignature by" followed by your workspace's name "is still missing." Whoever opens the page in this state sees the list and this sentence, but no form.

### Own address and own code

If several external signers are planned, each signs with the address from the send and with a code that goes to that address. The first signer's address is the recipient's. If the offer has only one external signer (signature or countersignature without additional signers), the address stays open as described under "Acceptance by another person".

For the page this means:

* Only the address of the person whose turn it is gets a code. If someone gives a different address, the page answers exactly as with the right address. But no code goes out. A mistyped address therefore leads to neither an email nor an error message. With **Change address** the signer enters it again.
* A code is valid only for the address it went to.

### When the next person is notified

The next signer gets their email only once the person before them has signed. The subject is "Your signature for", then the title in quotation marks and the workspace in parentheses. The email has the heading "Your signature is needed", names the deadline and has the button **View offer**. It names neither the send's personal message nor the names or addresses of the others.

If the countersignature is next, an email with the subject "Countersignature needed:" and the title goes to your workspace instead. It has the button **View the offer** and goes to the person who created the offer (as long as they are a member, otherwise to the owners). If one of these emails fails, the signature is still saved. You then pass on the link yourself.

If another signer does not react, HocDoc can remind them once by email via the rule "Signature is pending", if your workspace has switched it on. The countersignature is not reminded. See [Automatic follow-ups](https://docs.hocdoc.com/en/guides/automatic-follow-ups.md).

### Wrong code

With several signers, the same message appears for every error in the code check. This applies to a wrong, expired, locked or missing code and to an address that is not next:

"The code isn't correct or is no longer valid. Please check the code and email address or request a new code."

The number of remaining attempts is not shown there. The limits themselves still apply: 15 minutes of validity and 5 wrong entries per code. With an open address, the messages from "Limits for codes" above apply, for example "The code isn't correct." with the remaining attempts.

Further limits:

| Limit | Value |
| - | - |
| Code requests in a process with several signers | 10 per IP address and hour, 5 per link and address and hour. After that: "Too many requests. Please try again in an hour." |
| Attempts to sign per IP address | 30 in 10 minutes. After that: "Too many attempts. Please try again in a few minutes." |
| New send during signing | "The offer has changed. Please reload the page." |

### Draw or type a signature

If the signature is required, every signer needs it in addition to name, address and code. The **Your signature** field has two tabs. The active tab determines what is saved.

| Tab | How it works |
| - | - |
| **Draw** | The signer writes in the field with mouse, finger or pen. The note reads: "Sign in the field with your mouse or finger. Without a pointing device, choose "Type"." **Clear** empties the field. At most 100 strokes and 3000 points. |
| **Type** | The **Your name as signature** field is prefilled with the name, at most 80 characters. A preview shows the text in a script font. This tab can be operated entirely with the keyboard. |

A drawn signature is saved as a list of points, not an image. The preview of a typed signature looks different on each device, because the script font comes from the system. If the signature is missing, it says: "Please sign in the field or type your name." The signature must be there before the code can be requested.

### Countersign in the app

If the countersignature is turned on, a member of your workspace signs last in the app.

* **Who may:** Members, admins and owners. Viewers do not see the button.
* **Where:** On the offer's detail page in the **Signatures** card, with the **Countersign** button. It only appears if the offer has the status "Sent" and all external signatures are in.
* **Dialog:** "Countersign offer" with the field **Your name** (prefilled with your display name), if a signature is required with the field **Your signature** (tabs **Draw** and **Type**), and the checkbox "I countersign this offer with binding effect on behalf of" plus the workspace name. With **Countersign** you complete it. There is no code. Your account's address counts as the address.

| Message | When |
| - | - |
| "Please enter your name and tick the checkbox." | Name empty or checkbox missing. |
| "Please sign in the field or type your name." | The signature is missing or invalid. |
| "Countersigning is not possible right now. Please reload the page." | Any other error, for example a changed state after a new send. |
| "Too many attempts. Please try again in a few minutes." | More than 10 attempts per account in 10 minutes. |
| "No connection to the server. Please try again." | The request did not arrive. |

### When the offer counts as accepted

The offer counts as accepted with the last signature. With a countersignature, that is the countersignature. Before that the status stays "Sent". Only with the last signature do acceptance, certificate and confirmations come into being.

* Whoever signs last on the public page sees the card "Offer accepted" with **Download certificate**, as in the simple flow.
* Every external signer also gets the certificate by email. If the process ends with the countersignature, the email is the only way to the certificate for the external signers.
* If the offer is withdrawn or expires before everyone has signed, the signatures stay saved. The offer does not count as accepted, not even if only the countersignature was missing.
* A new send starts the process over.

### Timeline and detail page

Every signature appears as its own entry in the timeline, for example "Signed by" with the name and "(2 of 3)", for the countersignature "Countersigned by" with the name. With the last signature, "Accepted" follows. If an intended signer requests their code, it says "Confirmation code requested". "Code requested from a different address" only appears for addresses that are not among the signers.

The **Signatures** card on the detail page shows "Who has signed and who is still missing." At the top it says, for example, "2 of 3 signed". For each signer there are name, address (as far as known) and status ("signed on" with time, "next to sign" or "pending"). After a signature, name and address from the signature are shown. Drawn and typed signatures appear next to the entry. The open countersignature is called "Countersignature". If the offer was withdrawn or expired before everyone signed, it says "Process ended:" with the number of signatures present.

For several signatures, the **Acceptance** card names the last one, for a countersignature therefore the member who countersigned.

### Limits

* The order is fixed. There is no parallel signing, no substitution and no forwarding of the signature.
* There is no interim confirmation by email. A reminder only exists through the rule "Signature is pending" for additional signers (once, if the workspace has switched it on). The countersignature is not reminded.
* Overview, offer list, Deal coach and analytics show an offer with partial signatures as "Sent".
* IP address and browser identifier of the countersignature come from the request to the app.

## After acceptance

The page shows the card "Offer accepted" with the text "Thank you. A confirmation has been sent to your email address." It includes:

* the button for the step after acceptance, if you entered a link when sending (see [Sending](https://docs.hocdoc.com/en/guides/sending.md)). It opens in a new tab,
* the **Download certificate** button.

If the certificate could not be created, the button is missing. The page then shows "The certificate will be sent to your email address shortly." The confirmation email arrives without a certificate in that case and says so. The acceptance itself is recorded anyway.

If the recipient opens the link again later, they see "Offer already accepted" with the date, the button for the step after acceptance and the PDF link.

### Emails

| Email | To | Content |
| - | - | - |
| Subject begins with "Confirmed: your acceptance of" | Signer, in the flow without a process | Time of acceptance, certificate as `certificate.pdf` attached, the accepted offer as a PDF attached, the button if a link is set |
| Subject begins with "Accepted:" | Whoever created the offer (as long as a member of the workspace), otherwise the owners | Name and address of the signer (with several signatures the last person, with a countersignature therefore the member), time, button **View in dashboard** |
| Subject "Confirmed:", title in quotation marks, "has been accepted" | Every external signer in a process (additional signers, countersignature or signature), once per address | Time, certificate as `certificate.pdf` and the accepted offer as a PDF attached, the button if a link is set |

The offer then has the status "Accepted". On the detail page, the **Acceptance** card shows the fields "Signer", "Email" and "Accepted on", plus the **Download certificate** link. The link is valid for 5 minutes from loading the page, after which you reload the page. If there is no file, it says "No certificate available."

## Onboarding form after acceptance

If you turned on the onboarding form when sending (see [Sending](https://docs.hocdoc.com/en/guides/sending.md)), the offer page asks your questions after acceptance. You maintain the questions in [Settings](https://docs.hocdoc.com/en/guides/settings.md) in the "Sender" tab.

* The form appears below the card "Offer accepted". With several signers it appears after the last signature. If the process ends with the countersignature in the app, the form appears on the open page by itself: with a visible tab, the page checks about every 45 seconds and reloads as soon as there is a form. When switching back to the tab, it checks immediately. Offers without a form keep waiting without the page changing.
* If the recipient opens the link again later, the form is also on the "Offer already accepted" page, as long as it has not been submitted.
* The recipient sees "A few more details to get started" and the note line "To get started, your point of contact asks for the following details." Required fields carry an asterisk. Short answers have at most 200 characters, long ones at most 2000. For a file question, the recipient uploads files (see [Files after acceptance](https://docs.hocdoc.com/en/guides/file-upload-after-acceptance.md)).
* The button is called **Submit details**. It is submitted once per offer, so with several signers not per person. Afterwards the page only shows "Thank you. Your details have been submitted." and never the answers. If someone submits the form after it has already been filled in, instead of a success message it says: "This form has already been filled in. It can only be submitted once. To make changes, please contact your point of contact directly." The first answers stay unchanged.

You find the answers on the detail page in the **Onboarding form** card ("The recipient's answers after acceptance.") with "Submitted on" and the date. Before submitting it says "Not submitted yet." A question without an answer shows "Not stated". For a file question, the uploaded files appear under the question with name, size and time and the **Download** button, without a file "No file". You open images and PDFs in a preview via the file name (see [Files after acceptance](https://docs.hocdoc.com/en/guides/file-upload-after-acceptance.md#view-and-download-files)). The [timeline](https://docs.hocdoc.com/en/guides/analytics.md) carries the entry "Onboarding form submitted".

You also get an email with the subject "Onboarding form submitted:" and the offer's title. It does not name the answers, for files only the number of files, never a name. It goes to the same person as the "Accepted:" email.

The form is not part of the proof of acceptance. The image of the accepted offer and the certificate contain neither questions nor answers. Versions sent before the form existed, and offers already accepted, do not get a form retroactively.

## The final certificate

The certificate is a PDF with the heading "Certificate of acceptance". Below it is your workspace's name. Times are in your workspace's time zone. In the flow without a process it has one page and contains:

| Field | Content |
| - | - |
| Offer, Offer ID, Version | Title and identifier of the offer, number of the accepted version |
| Signer, Email | Name and address from the acceptance |
| Sent on | Time of sending |
| First opened on | Time of the first visit to the link |
| Code requested on | Time of the last code request |
| Accepted on | Time of acceptance, once in the workspace time zone, once in UTC |
| IP address, User agent | Details from the acceptance request |
| Document hash (SHA-256) | Check value of the version's offer content |
| Snapshot hash (SHA-256) | Check value of the image saved at acceptance (offer content, title, provider, signer, time, links to legal notice and terms) |
| Verify authenticity | Address of the verification page |

If a time or detail is missing, it says "not recorded". Title and sender correspond to the state at sending. The link after acceptance is not part of the certificate.

If the offer had a choice, the certificate contains the "Selected services" section before the check values: for each Pricing section the label, the package, the add-ons and the total. For the add-ons, all those that were available are listed with "selected" or "not selected". This applies to proofs created from now on. Saved proofs stay unchanged. The section continues onto the next page if needed.

### Certificate for a process

If you turned something on under **Signatures (optional)** when sending, the certificate looks different. This also applies if only one person signs. The header contains these lines:

| Field | Content |
| - | - |
| Offer, Offer ID, Version | as above |
| Signatures | Number of signatures |
| Sent on, First opened on | as above |
| Accepted on | Time of the last signature, once in the workspace time zone, once in UTC |
| Document hash (SHA-256), Snapshot hash (SHA-256) | as above. The snapshot contains all signatures. |
| Verify authenticity | Address of the verification page |

The lines "Signer", "Email", "Code requested on", "IP address" and "User agent" are not in the header. "Code requested on" is dropped entirely. Each signature has its own block. It is called, for example, "Signature 1 of 3" or "Countersignature" and contains:

| Field | Content |
| - | - |
| Name, Email | Name and address of the signature. For the countersignature the account's address. |
| Signed on | Time, twice: workspace time zone and UTC |
| IP address, User agent | Details from the request |
| Type of signature | "drawn", "typed" or "none" |
| Signature hash (SHA-256) | Check value of the signature, if there is one |

A drawn signature appears as a drawing in a frame below the block, a typed one as text in a line. If the text is too long, first the font gets smaller, then the text is shortened and ends with three dots. The full spelling is in the snapshot. A block is never split across two pages, so the certificate has more than one page. It is verified like any certificate, see "The verification page" below.

## Offer PDF

The offer is also available as a PDF: for the recipient via **Download the offer as PDF**, for you on the detail page per version in the **Sent versions** card. The PDF is text-based, without logo and primary color. It contains the images of the sections (see [Sections](https://docs.hocdoc.com/en/guides/sections.md#images)), and columns appear stacked in it. It names title, sender, recipient, send and expiry date and the version. In the footer of every page are the version and its SHA-256. The public PDF names only the recipient's name.

| Limit | Behavior |
| - | - |
| More than 40 pages | The PDF ends with "Shortened: limit of 40 pages reached. The full version is on the offer page." |
| Withdrawn or expired | The link reports "This offer is no longer available (withdrawn or expired). Please reload the page." |
| Too many requests in a short time | The link reports "Too many requests in a short time." and names when a new attempt is possible. |

The PDF is generated anew on every request. Via the public link it is available for open and for accepted offers. An accepted offer remains available as a PDF even after the deadline. The verification page only checks certificates, not the offer PDF.

## The verification page

At `/verify` anyone can verify a certificate without signing in. The page is called "Verify document". There are two ways.

### Check a file

The verifier chooses the file under **Certificate (PDF)** with **Choose file** (at most 25 MB) and clicks **Check a file**. The file's SHA-256 is created in the browser. The file itself is not transferred, only its value.

### Enter a hash

Alternatively they enter the 64 characters from the certificate under **Snapshot hash (SHA-256)** and click **Check hash**. Spaces and upper case do not matter. The document hash cannot be verified there.

### What the results mean

| Result | Meaning |
| - | - |
| **Confirmed** | "This file is unchanged since the acceptance." It shows "Accepted on" (in UTC) and "Provider". This only exists if the file was checked and a file value is stored for the acceptance. |
| **Acceptance found** | An acceptance exists for the hash entered. This confirms the acceptance, not the content of a document at hand. This applies to older acceptances without a stored file. Here too, time and provider appear. |
| **Please check the file** | An acceptance exists for the hash whose certificate is stored as a file. Whether a document is unchanged is then only shown by checking the file. Time and provider do not appear. |
| **Not found** | Nothing exists for this file or hash. |
| **Check not possible** | Too many checks (30 in 10 minutes per IP address) or the check is not reachable right now. |

The check never names the offer or signer.

### Older certificates

For certificates from before the verification page, no file is stored. They lack the line "Verify authenticity". They can only be checked by hand via the snapshot hash. The result is "Acceptance found" and says nothing about whether the file is unchanged. Checking such a file gives "Not found".

## Summary for co-decision makers

The summary is a short page the recipient can forward to everyone who co-decides. It sits under the offer link with the suffix `/summary`. There is no separate secret: whoever has the link also gets to the full offer.

The recipient finds the link in the card "Summary for decision makers" below the open offer (**Copy link**, **View summary**). You find it on the detail page under the note "Summary for co-decision makers: one screen to forward, with its own entries in the timeline." Card and line only appear if the summary has at least one block.

The page is derived from the sent offer. You do not maintain it. It has up to five blocks. For each block the first visible section of the type counts:

| Block | Source |
| - | - |
| Problem | Text of the "Current situation" section, plus up to 3 points if the section shows points |
| Outcome | Headline and introduction (otherwise the titles of the points) of the "Goal and outcome" section if there is one, otherwise headline and subheadline of the "Intro" section |
| Price | Up to 3 packages of the "Pricing" section with name and price, the recommended one with "Recommended". Plus introduction, detail lines and note of the pricing. If the choice is already fixed in a process with several signers, the block also names it |
| ROI | Three figures of the "ROI calculator" section with the starting values, only for an added value above zero |
| Assurance | Up to 4 commitments of the "Assurance" section, for more plus "and N more commitments" |

The summary shows no images. Texts are shortened. All other sections are missing (Cost of waiting, Schedule, Scope of work, References, FAQ, Team, Next steps, Video, Custom calculator, Free text, Image, Columns, Divider), as are add-ons and the features of the packages. At the bottom are **View the full offer** and the PDF link. Nothing is accepted there.

A visit appears in the timeline as "Summary viewed". It does not count as an opening of the offer and triggers no email for the first opening. For expired, withdrawn and accepted offers, the page shows the status notice instead of the summary.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.