Page Comparison

...

1. Call registerVerification with the person's basic details.  Some background sources may pass, but the person requires further verification.
2. The customer's back-end application stores the verificationId and associated it with their record for the person.
3. The customer's back-end application generates some form of token or code and associates it with the verificationId.
4. Direct the person to resume the verification process using the customer's native mobile app.
5. The person resumes the verification process using the customer's native mobile app by entering the token or code generated in step 3.
6. The native mobile app sends the token or code to the back-end application, which finds the associated verificationId and uses it to call getGreenIdWebVerificationToken (TODO - add link).  The verificationToken is passed back to the native mobile app.
7. The native mobile app initialises the greenID Mobile SDK in "returning user" mode and supplies the greenIdWebVerificationToken.
8. The greenID Mobile SDK guides the person through the rest of the verification process.  The person achieves a level of verification sufficient to satisfy the rule the customer configured on their greenID account.
9. The greenID Mobile SDK hands off to the controlling application.
10. The customer's mobile application sends the details to the customer's back-end application, which uses the verificationToken to query the results of the verification process by calling getVerificationResult.
11. The customer's back-end application communicates with their native mobile application to determine the next step in the workflow for the person, based on the results of the verification process.

Example with GBG Trust: Alert Only

1. Call registerVerification with the person's basic details. Any alerts raised will be returned in the verificationResult section of the response.
2. Call getVerificationResult to query the result.