> For the complete documentation index, see [llms.txt](https://brd-digital.gitbook.io/brd-digital-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brd-digital.gitbook.io/brd-digital-docs/getting-started/identity-verification.md).

# Identity Verification

Verification runs through Sumsub. How far you verify sets your limit.

Verification does two things: confirms you are eligible to use BRD, and sets your transaction limit. Both happen through **Sumsub**, inside the sign-up flow.

## How it works

After creating your account you are handed to Sumsub in the browser. You photograph an identity document, complete a liveness check, and submit. Most decisions return in minutes; some document and jurisdiction combinations route to manual review.

You never email documents to anyone. If a request for documents reaches you outside the app, treat it as fraudulent.

## The two tiers

<table><thead><tr><th width="130">Tier</th><th>What you submit</th></tr></thead><tbody><tr><td><strong>Basic</strong></td><td>Government-issued identity document and a liveness check.</td></tr><tr><td><strong>Full</strong></td><td>The basic set, plus proof of address and source-of-funds documentation.</td></tr></tbody></table>

Start at basic and upgrade whenever you need to — upgrading is a document submission on the existing account, not a new application.

{% hint style="info" %}
Your limit is shown in the dashboard, and confirmed before you commit to any transaction that would cross it. Above the full tier, accounts move to the institutional path below.
{% endhint %}

## Country eligibility

Sumsub screens the country of the applicant and their documents. **Applicants from OFAC-blacklisted jurisdictions are declined.** Jurisdictions without an adequate AML/CFT framework, and countries where digital-asset services are prohibited locally, are also out of scope. Full detail in KYC.

## Organizations

Companies verify through **KYB** rather than the self-serve tiers — corporate registration, beneficial ownership down to natural persons, and authorized-signatory identification. It is reviewed rather than automated, so timelines vary. Reach the desk at <institutional@brdcapital.com>.

## Troubleshooting

<table><thead><tr><th width="240">Symptom</th><th>Likely cause</th></tr></thead><tbody><tr><td>Document rejected</td><td>Glare, crop, or an expired document. Retake in even light with all four corners visible.</td></tr><tr><td>Liveness check fails</td><td>Poor lighting or an obstructed camera. Try a different device.</td></tr><tr><td>Declined on country</td><td>The jurisdiction is out of scope. Not appealable through support.</td></tr><tr><td>Transaction blocked by limit</td><td>You are at your tier ceiling — upgrade, or ask about institutional onboarding.</td></tr></tbody></table>

## Next step

→ Connect a Wallet


---

# 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://brd-digital.gitbook.io/brd-digital-docs/getting-started/identity-verification.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.