> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/product-guides/identity-verification/document-check/document-sides-per-type.md).

# Expected sides per type

Depending the country and document type, ComplyCube may require one or both sides of the document.

Depending on the issuing country and document type, ComplyCube may require submission of either one or both sides of the document, for processing.

The table below specifies the number of sides expected for each document type.

{% hint style="info" %}
The ComplyCube **Web SDK**, **Mobile SDKs**, and **Hosted Solution** automatically capture the required document sides during the verification process.
{% endhint %}

<table><thead><tr><th width="227">Document Type</th><th width="87.48177083333331" align="center">Sides</th><th>Exceptions</th></tr></thead><tbody><tr><td>Passport</td><td align="center">1</td><td>-</td></tr><tr><td>Driving License</td><td align="center">2</td><td>-</td></tr><tr><td>Residence Permit</td><td align="center">2</td><td>-</td></tr><tr><td>National Identity Card</td><td align="center">2</td><td><p>Only one side for the following:<br></p><ul><li>🇦🇷 Argentina</li><li>🇨🇱 Chile</li><li><span data-gb-custom-inline data-tag="emoji" data-code="1f1e8-1f1fe">🇨🇾</span> Cyprus </li><li>🇸🇻 El Salvador</li><li>🇨🇮 Ivory Coast</li><li>🇲🇾 Malaysia</li><li>🇵🇪 Peru</li><li>🇷🇴 Romania</li></ul></td></tr><tr><td>Visa</td><td align="center">1</td><td>-</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.complycube.com/documentation/product-guides/identity-verification/document-check/document-sides-per-type.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.