Credit Header Results - How to Read

If your service is configured to use Australian Credit Header Data as a potential matching source for KYC checks, then you must also be aware of your obligations under section 35C of the AML/CTF Act 2006.

If the full name, address and or date of birth on file at the credit bureau does not match the details supplied, then you must inform the customer that they have the right to review and update their details with the bureau in question.



  1. Just because the customer doesn’t have matching data at the credit bureau, does not mean the overall KYC check has failed. It’s just the one possible matching source and is often just an out of date address.
  2. This also does NOT mean the customer has failed a credit check of any kind. Checking to see if personal details match those on file at the bureau have zero impact on a customer’s credit history or credit worthiness.

How to determine if you have to let the customer know?

There are 2 ways you’re informed that this mismatch may have occurred. These will be found in the response from a CreateCheckEntity or UpdateCheckEntity API response (or also in the result of a GET /entity/checks response).

In the entityProfileResult clause



The following section will only apply if you’re using entity profiles/recipes.

In the entityProfileResult clause of a response, you’ll find a section called creditHeaderFailures

"creditHeaderFailures" : [ 

In there you will find the name(s) of the bureau(s) that returned a mismatch result. It is possible for there to be more than one entry in the array if you have more than one credit bureau in your configured source cascade.

Valid values include

  • Equifax
  • Experian
  • others upon request

In the checkSummary clause



This following section will apply in all cases

In the checkSummary clause of a response, you will find the following keys in the CheckResults Key Value Pair Array:







True / False

Indicates a match/fail with a credit header source that may require notification be sent to the customer.

If set to true, the match was successful

If set to false, the match failed and the customer may need to be notified of this fact.

The XXX would be replaced with the reporting bureau. Valid values are:

  • Equifax
  • Experian

There are other bureaus available as well.

It is possible for there to be more than one of these, depending on how your failover/cascade works.

You can see more information on this and other KVPs in the CheckResults array here: Understanding CheckSummary Results

Did this page help you?