Coding hints and tips

Getting started

1. Make sure you have access to an Experian WASP certificate (UAT or Live).

You can do this by installing the certificate to your local user certificate store or by making sure the certificate file is available to your project.

2. Write the code to perform WASP authentication.

This must reference the correct certificate and the correct service URL. There is a different URL for the test and live services. Experian will send you the URL you must use with your software.

3. Write the code to perform the identity check request.

This must reference the correct service URL and use the WASP token retrieved in step 2. There is a different URL for the test and live services. Experian will send you the URLs you must use with your software.

Message header

All messages sent to Identity Hub must include a message header. The items you must include in the header are:

• ClientUser - this is the end user or business application that is accessing Identity Hub using the XML interface
• ReferenceId - this is a unique identifier for you application, typically this is your account number.

Both of these items are used for traceability and logging purposes.

Dealing with service messages

Any service error messages, such as timeout errors, are returned in the EIHErrorMessage structure. You should check this structure for messages after every call to Identity Hub.

Identifying your call

All responses generated by Identity Hub include a unique reference number (URN). Your application should extract the URN and store it. You can also display it to your users as required.

If you ever need to contact Experian support, you should quote the URN so that Experian can find the related information in the support logs.

If you have access to the Identity Hub user interface and have the correct permissions, you can use this URN to access the query reports related to the check.

Next step: Implementation steps

See also

• Before you start
• Client error messages
• Sending requests to Identity Hub