> For the complete documentation index, see [llms.txt](https://doc.youverify.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.youverify.co/guides-and-solutions/build-tiered-kyc-for-digital-banking.md).

# Build Tiered KYC for Digital Banking

This guide shows how to onboard a customer at a minimal tier and deepen verification on the same entity record as they request higher account functionality.

{% stepper %}
{% step %}

### Complete authentication and connection check

Before creating any entity, authenticate your API session and confirm connectivity. Every request carries your API secret token in the header; a failed auth check here is the most common cause of downstream 401 errors that look like data problems but aren't.
{% endstep %}

{% step %}

### Add the entity at Tier 1

Tier 1 typically requires only a name and phone number. Choose the creation method that matches the data you hold.

* **Add with PII (first name, last name, country, phone)**. The standard Tier 1 entry point.

```json
POST {{baseUrl}}/v2/api/entities
{
  "entityType": "individual",
  "firstName": "Jane",
  "lastName": "Doe",
  "nationality": "NG",
  "phone": "+2348012345678",
  "isSubjectConsent": true
}
```

* **Add with a Nigerian eIDv identifier (Phone Number / NIN-by-phone)**. Starts the entity with a resolved identity, useful if you want to move straight toward a higher tier.

```json
POST {{baseUrl}}/v2/api/entities/:entityId/identity
{
  "entityType": "individual",
  "isSubjectConsent": true,
  "identity": {
    "countryCode": "NG",
    "idType": "nin_phone",
    "mobile": "+2348012345678"
  }
}
```

* **Add with a South African eIDv identifier (SAID number)**.For South African onboarding.

```json
POST {{baseUrl}}/v2/api/entities/:entityId/identity
{
  "entityType": "individual",
  "isSubjectConsent": true,
  "identity": {
    "countryCode": "ZA",
    "idType": "zaSAID",
    "id": "8001015009087"
  }
}
```

References: [Create Entity](/api-reference/api-reference/entity-management/create-entity.md), [Verify Entity (KYC)](/api-reference/api-reference/entity-management/verify-entity-kyc.md)
{% endstep %}

{% step %}

### Upgrade tiers on the same entity

When the customer reaches a transaction limit or requests more functionality, run the next verification on the *same* entity ID, no new record is created.

* **Tier 2 — verify with NIN and BVN:**

```json
POST {{baseUrl}}/v2/api/entities/:entityId/identity
{
  "entityType": "individual",
  "isSubjectConsent": true,
  "identity": {
    "countryCode": "NG",
    "idType": "bvn",
    "mobile": "11111111111"
  }
}
```

```json
POST {{baseUrl}}/v2/api/entities/:entityId/identity
{
  "entityType": "individual",
  "isSubjectConsent": true,
  "identity": {
    "countryCode": "NG",
    "idType": "nin",
    "mobile": "11111111111"
  }
}
```

{% endstep %}

{% step %}

### What happens in the background?

The moment the entity is created, the platform automatically runs a full AML screen — Sanctions, PEP, Watchlist, and Adverse Media — against it. This always runs, on every plan, and produces the entity's initial risk score.

At this stage the score reflects AML data only. A newly created entity has no session or behavioral history yet, so Fraud Insight — which scores device and behavioral signals — has nothing to evaluate. As the customer transacts and generates signals, Fraud Insight enriches the profile into a fuller risk score on the same entity record. This enrichment happens over the customer's lifecycle, not at creation.

```mermaid
flowchart LR
    T1[Tier 1<br/>POST /entities<br/>name + phone] --> AML{{Auto AML<br/>on creation}}
    AML --> S[Initial risk score]
    T1 --> T2[Tier 2<br/>POST /entities/:id/identity<br/>NIN or BVN]
    T2 --> T3[Tier 3<br/>POST /entities/:id/identity<br/>premiumBVN + selfie]
    T3 --> V[Full functionality]
    Note[Same entityId throughout<br/>no new record created]

```

{% endstep %}
{% endstepper %}


---

# 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, and the optional `goal` query parameter:

```
GET https://doc.youverify.co/guides-and-solutions/build-tiered-kyc-for-digital-banking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.