- Deborah Cross (Unlicensed) to agree 'legacy' terminology and message with Michael.
...
...
The iFrame solution is no longer offered to customers (Jan 2015), this documentation to support existing users.
iFrame integration was deprecated in January 2015. New customers should integrate using either greenID Web or greenID API. |
|
...
Existing customers are encouraged to upgrade the integration method - contact support to find out |
|
...
more. This documentation remains to support existing customers with an iFrame integration. |
|
The greenID application hosts a series of web pages that may be used to verify certain details about an individual. The greenID application also offers a set of Web Services methods to allow remote clients to access greenID's verification services programmatically.
...
- The individual registers with the client organisation, which collect some basic information about the person such as name, address, date of birth, etc.
- The client organisation makes a Registering a user registration Web Service call to greenID to request that greenID carry out a series of automatic checks on the person’s details.
- greenID returns the result of these automatic checks to the client organisation.
- The person is re-directed to the greenID website where additional checks are performed in an interactive manner.
- Once the verification process is complete, greenID returns the person to the client organisation’s website.
- The client organisation invokes a Web Service to query greenID for the outcome of the verification process for the person. This can be invoked at any time. It can be triggered by the user returning to the site, or by an optional notification call from greenID which occurs whenever a person is verified.
- The client organisation takes appropriate action at their website based on the outcome reported by greenID.
The diagram below illustrates the flow.
...