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

# Switzerland Credit Bureau

> Credit Header data obtained from the Credit Bureau in Switzerland. Authoritative real-time identity lookup for Switzerland. Real-time lookup, pay-per-call.

<div hidden data-didit-db-validation-defaults="{&#x22;issuing_state&#x22;:&#x22;CHE&#x22;,&#x22;services&#x22;:&#x22;che_credit_bureau&#x22;,&#x22;consent&#x22;:&#x22;true&#x22;,&#x22;first_name&#x22;:&#x22;John&#x22;,&#x22;last_name&#x22;:&#x22;Doe&#x22;,&#x22;date_of_birth&#x22;:&#x22;1990-01-01&#x22;,&#x22;address&#x22;:&#x22;{\&#x22;street_1\&#x22;:\&#x22;123 Sample Street\&#x22;,\&#x22;street_2\&#x22;:\&#x22;Unit 4\&#x22;,\&#x22;city\&#x22;:\&#x22;Sample City\&#x22;,\&#x22;region\&#x22;:\&#x22;Sample State\&#x22;,\&#x22;postal_code\&#x22;:\&#x22;10001\&#x22;,\&#x22;country\&#x22;:\&#x22;US\&#x22;}&#x22;,&#x22;vendor_data&#x22;:&#x22;user-1234&#x22;}" />

Credit Header data obtained from the Credit Bureau in Switzerland. Didit exposes this service through `POST /v3/database-validation/` so you can verify the submitted data against the authoritative source and receive normalized match results.

## Coverage

* **Coverage:** \~ 85%
* **Country:** Switzerland
* **Service ID:** `che_credit_bureau`
* **Data domain:** Financial
* **Category:** CreditBureau

## Inputs

| Field                 | Required | Example             |
| --------------------- | -------: | ------------------- |
| `first_name`          |      Yes | `John`              |
| `last_name`           |      Yes | `Doe`               |
| `date_of_birth`       |      Yes | `1990-01-01`        |
| `address.street_1`    |      Yes | `123 Sample Street` |
| `address.postal_code` |      Yes | `10001`             |
| `address.street_2`    |       No | `Unit 4`            |
| `address.city`        |       No | `Sample City`       |
| `address.region`      |       No | `Sample State`      |
| `vendor_data`         |       No | `user-1234`         |

* **Required inputs:** `first_name`, `last_name`, `date_of_birth`, `address.street_1`, `address.postal_code`
* **Optional inputs:** `address.street_2`, `address.city`, `address.region`, `vendor_data`
* **Consent:** Required
* **Workflow availability:** Available in workflow
* **Coverage:** \~ 85%
* **Price:** \$2.00 per successful query

## Body parameters

<ParamField body="issuing_state" type="string" required default="CHE" placeholder="CHE">
  ISO 3166-1 alpha-3 country code for this database service.

  Example: `CHE`
</ParamField>

<ParamField body="services" type="string" required default="che_credit_bureau" placeholder="che_credit_bureau">
  Array containing this service ID. Pinning the service keeps the request scoped to this exact database.

  Example: `che_credit_bureau`
</ParamField>

<ParamField body="consent" type="boolean" required default="true" placeholder="true">
  Explicit end-user consent for this service.

  Example: `true`
</ParamField>

<ParamField body="first_name" type="string" required default="John" placeholder="John">
  Given name to validate.

  Example: `John`
</ParamField>

<ParamField body="last_name" type="string" required default="Doe" placeholder="Doe">
  Family name to validate.

  Example: `Doe`
</ParamField>

<ParamField body="date_of_birth" type="string" required default="1990-01-01" placeholder="1990-01-01">
  Date of birth in `YYYY-MM-DD` format.

  Example: `1990-01-01`
</ParamField>

<ParamField body="address" type="object" required default="{&#x22;street_1&#x22;:&#x22;123 Sample Street&#x22;,&#x22;street_2&#x22;:&#x22;Unit 4&#x22;,&#x22;city&#x22;:&#x22;Sample City&#x22;,&#x22;region&#x22;:&#x22;Sample State&#x22;,&#x22;postal_code&#x22;:&#x22;10001&#x22;,&#x22;country&#x22;:&#x22;US&#x22;}" placeholder="{&#x22;street_1&#x22;:&#x22;123 Sample Street&#x22;,&#x22;street_2&#x22;:&#x22;Unit 4&#x22;,&#x22;city&#x22;:&#x22;Sample City&#x22;,&#x22;region&#x22;:&#x22;Sample State&#x22;,&#x22;postal_code&#x22;:&#x22;10001&#x22;,&#x22;country&#x22;:&#x22;US&#x22;}">
  Structured residential address object. Use `street_1`, `street_2`, `city`, `region`, `postal_code`, and `country`. A complete legacy address string is still accepted but not recommended.

  Example: `{"street_1":"123 Sample Street","street_2":"Unit 4","city":"Sample City","region":"Sample State","postal_code":"10001","country":"US"}`
</ParamField>

<ParamField body="vendor_data" type="string" default="user-1234" placeholder="user-1234">
  Your stable user reference for this person, such as your internal user ID. Didit uses it to link standalone checks to the same end user and reduce duplicate-detection noise.

  Example: `user-1234`
</ParamField>

## Input rules & validation notes

* For address services, send structured address fields instead of a single `address` string when possible.
* `address.street_1` is the street address, including street number and street type.
* `address.street_2` is apartment, unit, building, floor, or extra address line. Send it only when you have it.
* `address.city` is city, suburb, district, locality, or neighborhood.
* `address.region` is state, province, region, or town.
* `address.postal_code` is postcode or postal code.
* Address-based database services require at least street address and postal code; requests rejected before source lookup are not charged.

## How to call it

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://verification.didit.me/v3/database-validation/" \
    -H "x-api-key: YOUR_API_KEY" \
    -F "issuing_state=CHE" \
    -F "services=che_credit_bureau" \
    -F "vendor_data=user-1234" \
    -F "consent=true" \
    -F "first_name=John" \
    -F "last_name=Doe" \
    -F "date_of_birth=1990-01-01" \
    -F 'address={"street_1":"123 Sample Street","street_2":"Unit 4","city":"Sample City","region":"Sample State","postal_code":"10001","country":"US"}'
  ```
</RequestExample>

<ResponseExample>
  Every successful call returns HTTP `200`. The **`outcome_code`** field tells you what actually happened — distinguishing, for example, a real biometric mismatch (`BIOMETRIC_NO_MATCH`) from a selfie that could not be read (`BIOMETRIC_IMAGE_UNUSABLE`). The `status` shown is the default feature status; your configured [Partial Match / No Match actions](/core-technology/database-validation/database-validation-warnings) can override it.

  **`MATCH`** — The registry confirmed the identity and every checked field matched.

  ```json 200 OK — MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "Approved",
    "issuing_state": "CHE",
    "match_type": "full_match",
    "validations": [
      {
        "outcome_code": "MATCH",
        "service_id": "che_credit_bureau",
        "service_name": "Switzerland Credit Bureau",
        "source_data": {
          "address": "123 Sample Street",
          "date_of_birth": "1990-01-01",
          "first_name": "John",
          "last_name": "Doe"
        },
        "validation": {
          "address": "full_match",
          "date_of_birth": "full_match",
          "full_name": "full_match"
        }
      }
    ]
  }
  ```

  **`PARTIAL_MATCH`** — The identification number was found but one or more personal fields (usually name or date of birth) did not fully match.

  ```json 200 OK — PARTIAL_MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "In Review",
    "issuing_state": "CHE",
    "match_type": "partial_match",
    "validations": [
      {
        "outcome_code": "PARTIAL_MATCH",
        "service_id": "che_credit_bureau",
        "service_name": "Switzerland Credit Bureau",
        "source_data": {
          "address": "123 Sample Street",
          "date_of_birth": "1990-01-01",
          "first_name": "John",
          "last_name": "Doe"
        },
        "validation": {
          "address": "full_match",
          "date_of_birth": "full_match",
          "full_name": "no_match"
        }
      }
    ]
  }
  ```

  **`NO_MATCH`** — The registry returned no match for the submitted data.

  ```json 200 OK — NO_MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "Declined",
    "issuing_state": "CHE",
    "match_type": "no_match",
    "validations": [
      {
        "outcome_code": "NO_MATCH",
        "service_id": "che_credit_bureau",
        "service_name": "Switzerland Credit Bureau",
        "source_data": {
          "address": "NO_MATCH",
          "date_of_birth": "NO_MATCH",
          "full_name": "NO_MATCH"
        },
        "validation": {
          "address": "no_match",
          "date_of_birth": "no_match",
          "full_name": "no_match"
        }
      }
    ]
  }
  ```
</ResponseExample>

## Returned data

The exact fields surfaced in `source_data` depend on what the registry returns. The generated example for `che_credit_bureau` currently documents this normalized shape:

* `address`
* `date_of_birth`
* `first_name`
* `last_name`

## Pricing & SLAs

Switzerland Credit Bureau queries are billed only when Didit receives a conclusive result from the validation source.

* **Per-call price:** \$2.00 USD.
* **Billing:** per successful query. You are not charged when the registry is unreachable, when required fields are missing, or when the request is rejected before reaching the source.
* **Latency:** typical p95 \< 2 s.
* **Availability:** 99.9% per quarter on Didit's side; downstream source availability varies by country and dataset.

## Continue reading

* [Switzerland Database Validation overview](/api-reference/database-validation/switzerland)
* [Database Validation overview](/core-technology/database-validation/overview)
* [Outcome Codes](/core-technology/database-validation/database-validation-outcome-codes)