iamdentity Web Service

The iamdentity web service allows on-line vendors to request information from the iamdentity database. Each vendor is issued with a username, password and vendor key which can be used to interact with the iamdentity web service.

No information can be requested from the iamdentity web service without a session key which is issued to the vendor when the consumer (customer) has approved the Transaction Pin requested by the vendor.

The web service can either be used to fully manage the consumer's details (no personal information is stored at the vendor) or as a data update service where the consumer's personal information is requested from the iamdentity database but stored in the vendor's database.

Security

You can have the best product or service to handle information, but if it's not secure, then it's useless. Although they say that the only secure computer is the one that is switched off and plugged out, we have left no stone unturned to make our solution as safe and secure as possible.

Apart from the obvious, we have implemented the following to protect your personal information:

Database Encryption

All your information - and we mean all your information - is stored in an encrypted form. Even if someone (and it's highly unlikely) manages to get hold of our database, they will not be able to do anything with the information. Have a look at an extract of our database below. If the image below makes sense and you can decrypt it, contact us for a job because then you are the best of the best.

database encryption

Transaction and Session Pin Numbers

If you use your iamdentity credentials on-line you will be presented by a 2nd factor credential (transaction and session pin) making sure that nobody else is using your iamdentity details. This 2nd factor credential will be emailed (or sent via SMS) to you and only you. You will need to verify this pin number before any information can be retrieved from our database.

Three-way vendor authentication

A vendor wanting to retrieve your personal information will need:
1. Their unique credentials (username, password and unique key);
2. An authentication id to request the transaction pin to be sent to the user; and
3. A session key (issued after the transaction key has been verified) to retrieve your personal information.

Without these authentication methods, the vendor will not be able to access your personal information.

Secure Connection

Both our user and vendor sections can only be accesses over a secure connection, protecting your information from wandering eyes.

View the iamdentity web service integration manual