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

# Testing Error Scenarios

This guide explains how to deliberately trigger error scenarios in your test environment. We'll cover two main testing approaches:

1. Forcing credit header failures
2. Forcing non-ID check failures

## Simulating Credit Header Failures

<Callout icon="star" color="#3DD892" iconType="regular">
  You can simulate credit bureau failures by using specific street names in your test payload.
</Callout>

To force a credit header failure, simply set the street name in the address to one of the following bureau names:

* `Equifax`
* `Experian`

The service will then return a failed credit header response for the specified bureau.

<CodeGroup>
  ```json Credit Header Failure Example theme={null}
  {
    "entity": {
      "entityProfile": "default",
      "entityType": "INDIVIDUAL",
      "name": {
        "familyName": "KINSELLA",
        "middleName": "JOHN",
        "givenName": "ERIC"
      },
      "dateOfBirth": {
        "dateOfBirth": "1952-02-28"
      },
      "addresses": [
        {
          "addressType": "RESIDENTIAL1",
          "country": "AUS",
          "streetNumber": "17",
          "streetName": "Experian", // [!code highlight] This will trigger an Experian credit header failure
          "streetType": "STREET",
          "suburb": "",
          "town": "ELLIOT",
          "state": "VIC",
          "postalCode": "3104"
        }
      ],
      "extraData": [
        {
          "kvpKey": "consent.general",
          "kvpValue": "true",
          "kvpType": "general.bool"
        },
        {
          "kvpKey": "consent.docs",
          "kvpValue": "true",
          "kvpType": "general.bool"
        },
        {
          "kvpKey": "consent.creditheader",
          "kvpValue": "true",
          "kvpType": "general.bool"
        },
        {
          "kvpKey": "customer_reference",
          "kvpValue": "20210531_2020",
          "kvpType": "id.external"
        }
      ],
      "identityDocs": [
        {
          "country": "AUS",
          "idType": "DRIVERS_LICENCE",
          "idNumber": "028021259",
          "region": "VIC"
        }
      ]
    }
  }
  ```
</CodeGroup>

## Testing ID-Only Verification

<Info>
  This scenario is useful when testing cases where a user should only pass based on their ID verification.
</Info>

To force all non-ID checks to fail:

1. Set the middle name to `FailNonID`
2. Ensure all ID-related fields (name, date of birth, ID details) are correct
3. Submit the payload

<CodeGroup>
  ```json ID-Only Verification Example theme={null}
  {
      "entity": {
          "entityProfile": "default",
          "entityType": "INDIVIDUAL",
          "name": {
              "familyName": "KINSELLA",
              "middleName": "FailNonID", // [!code highlight] This triggers non-ID check failures
              "givenName": "ERIC"
          },
          // ... rest of the payload remains the same
      }
  }
  ```
</CodeGroup>

<Callout icon="bell" color="#FFCA16" iconType="regular">
  For ID-only verification to work properly, ensure that:

  * The name matches the ID exactly
  * The date of birth is correct
  * All ID details (number, type, region) are valid
</Callout>

These test scenarios are available in both **Demo** and **UAT** environments.