> For the complete documentation index, see [llms.txt](https://software-help-docs.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://software-help-docs.gitbook.io/knowledge-base/software-guide/troubleshooting/order-form-fingerprint-is-missing-error.md).

# Order Form Fingerprint is Missing Error

If you ever run into the fingerprint is missing error we created this article to guide you through what it is and known solutions for this problem.

Here is an example of this error when submitting an order form:

{% embed url="<https://lh5.googleusercontent.com/BWHHXwoCtIUQvraeUiLI-9qet3QG2VzvWFRU3wUdYTgRJIsw9TRia2WEpZnUSqtZkdLv9ptSpcHQqUAqribH_pH-N40p3jFEspwehmoj9GFuG2N4rhaWjW88PCkFOTQDXwD6M46lLTtSvLm_R53f7W0>" %}

{% embed url="<https://lh5.googleusercontent.com/SYTVJmKJFX5XhbV-1B-iSgoBJ5Ix4G-v2HnuhUVb_VDnf3djHwEFbOLn-xKqFkgR_EQGNeUY_yG-PSq5uvgPRHjwPu1i_JKIR9hZ22jvPSSFkgnLFG4_3-5h9AdSMpKkXtUowEYxN_kx6lyhU5Qt7jk>" %}

***Please Note:** If you only experience this with some of your customers randomly this means it is likely due to the customer's browser settings and we are not able to access cookies for the purchase. A quick fix for this would be to guide the customer to update their browser settings and enable cookie access.*

If a client faces this issue **every time** on every device & multiple browsers, it means the **funnel domain is not configured correctly**.

Per our current implementation, we are using iFrame to render funnel pages inside WordPress. For payment, we need web browser cookies (storage) access & the web browser may not be allowing access over a cross-domain.

Make sure the URL matches the one in the funnel. Either that or double check it's embedded full iframe in WordPress settings (Lead Connector tab in WordPress).

The issue is that the slug needs to match the path to the funnel. So in the funnel settings, you need to add the domain and in WordPress the same slug. They used to be set up on subdomains as a fix. Now we can take a funnel and put it on a path on the root domain (see screenshots below)

{% embed url="<https://lh6.googleusercontent.com/ffnHixAHG5b53z-YclvothPRF8EYaq_un1GQDxTVea-IKRNjuJsTiCCZFc0Q6vW2qqWtUFASa-bJZXeeNiMHoeCzOQ4wnomR2ucJ405zzfrKD3etXRHfZcDzHs2bhanr8TyM07cTuYBw0Edp5RqE-F8>" %}

{% embed url="<https://lh3.googleusercontent.com/7tk1860qYQBP5kg7mkTbxQRl-fMzDXemkNG81enC5H2dW8bT8LYdNkgSlFkjB19C_Gf4UxdTWr4J5nxNylRaJKtmOI680qGN7ydqW6hd5XEGvt2wMkpmHf0mp2xmAnB_cTIvaSAzmNwYawrIFe4hMu0>" %}

Worst case solution: If the website is hosted on WordPress & they are using our order form funnel inside that as a separate path and the above steps did not resolve the issue, then the WordPress website domain & funnel domain should be the same but the subdomain should be different. Suppose your WordPress website is configured with [www.example.com](http://www.example.com/), and the non-www version example.com is your domain & www is the subdomain. You should not use [www.example.com](http://www.example.com/) or example.com as a funnel domain for this. Use different subdomains (e.g. funnels.example.com ) in the funnel.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://software-help-docs.gitbook.io/knowledge-base/software-guide/troubleshooting/order-form-fingerprint-is-missing-error.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.