Before you start

Skills required

To be able to implement Bank Wizard, you must:

• know your environment and web server
• know your programming language
• be able to implement applications within your web services environment.

Accessing the services

To implement Bank Wizard you must have a connection to the Bank Wizard service. Experian provides two hosted Bank Wizard services:

• UAT service - you use this when you need to test your application, for example during initial development. This service uses static test data which has been designed to return most messages.

• Live service - you use this when your application goes live. This service accesses the real Bank Wizard data used to validate and verify account and personal details and the real AVS/CVV card service. This data is updated regularly.

To be able to develop and test your application using the UAT service you must have:

• WASP certificates for the UAT service
• URLs for the UAT WASP and Bank Wizard services
• configured your firewall to allow connections to both WASP and Bank Wizard UAT services.

To make sure you have connectivity, telnet to the server using port 443.

Once you have developed and fully tested your application and you are ready to go live, you need to change from the UAT service to the Live service.

To change from UAT to live, you must:

• obtain and use the WASP certificates for the Live service
• change the URLs to the URLs for the live WASP and Bank Wizard services
• configure your firewall to allow connections to the live WASP and Bank Wizard services.

To make sure you have connectivity, telnet to the server using port 443.

Getting started

1. Make sure you have access to the Experian WASP certificate (UAT or live).

To do this either install the certificate to your local user certificate store or make the certificate file available to your project.

2. Create a new project, including references to your project's assembly.
3. If used, add the source files provided to the release package of your project.
4. Write the code to perform WASP authentication.

This must reference the correct certificate and the service URLs for either UAT or the live service. Experian will send you these URLs.

5. Write the code to perform the account or card check required.

This code must reference the correct service URL (UAT or Live) and use the WASP token retrieved in step 4. Experian will send you the URLs to access the Bank Wizard Hosted service.

The software package includes example classes that you can use to help you develop your application. The files are:

• BankWizardCardOnDemand.cs - this is the code you can use to access the card verification services
• BankWizardOnDemand.cs - this is the code you can use to access the Bank Wizard services
• WASPToken.cs - this is the Experian.Payments.BankWizardHosted.WASPToken class which defines the WASP token wrapper to use during Bank Wizard requests.

Dealing with client error messages

All client error messages (exceptions) generated by Bank Wizard include a unique ID (requestID). Your application should trap these errors and extract the unique ID. You should then store this ID and display it to your users with an appropriate error message.

If you need to contact Experian support, you should quote the unique ID so that Experian can find the related information and messages in the support logs.

Next step: Implementation steps

See also

• Client errors

For more information about WASP, see the Experian WASP documentation