Implement iOS callbacks

The SDK is connecting to the iProov server.

The SDK is connected and the iProov UI launches.

Hide the progress indicators. The iProov UI is displayed automatically.

The claim is being processed and video streamed to complete the user authentication.

This callback event may be called multiple times. iProov recommends adding the calls to the debug logs.

Display a progress indicator. Descriptive messages are provided by iProov.

The iProov claim was completed successfully.

You must call the validate endpoint to validate this token. See Verify enrolled users API.

• Display a user success message. The user can proceed to the next step in the iOS SDK happy path.

• Consider waiting for a response from the validate endpoint before the journey completes.

The claim was processed resulting in a failure code. May indicate a fraudulent attempt.

Review the failure codes. Some codes will indicate a valid retry attempt with appropriate user guidance. Others will indicate that the GPA or LA claim has been rejected.

Depending on the failure code:

• Offer a retry and provide guidance for completing a claim.

• End the journey.

iProov was unable to process the claim. There was a system failure establishing a connection or capture, or during the processing. The error reason is provided by iProov.

Log as an error. If the error occurred in the allowed number of retry attempts:

• Start a retry flow.

• Map the error reason to the appropriate user guidance messaging.

• Offer a retry journey with guidance for resolving the error, for example, Give permission to access the camera.

• For severe errors this may be the end of the journey.

The user canceled the process by tapping Home or Close.

Offer a retry attempt and provide guidance for completing a claim.

See: Unhappy path