Socure iOS SDK v5 Integration Guide

Getting started

• Install the latest version of the Digital Intelligence iOS SDK.
• Get a SDK key from GD to initialize and authenticate the DocV iOS SDK.
• Check that your development environment meets the following requirements:
  • Xcode version 14.1+
  • Support for iOS 13 and later

GitHub iOS library for Socure's Document Verification Product

Step 1: Generate a transaction token and configure the Capture App

To initiate the verification process, generate a transaction token (docvTransactionToken) by calling the IDV socure capture URL

POST /programs/{programCode}/accounts/{accountIdentifier}/socureDocumentRequest

Step 2: Add the DocV iOS SDK

You can use either CocoPods or Swift Package Manager to add the DocV iOS SDK to your project. Depending on the dependency manager you want to use, follow the steps in one of the installation sections below.

CocoaPods

To install the DocV iOS SDK using CocoaPods, add the following to your Podfile:

pod 'SocureDocV'

Next, install the Pod from the terminal:

pod install

Note: You must close the project and open the xcworkspace file after you install the pod for it to properly reflect in your project.

Swift Package Manager

To install the DocV iOS SDK using Swift Package Manager, add the following package repository URL:

https://github.com/socure-inc/socure-docv-sdk-ios

Camera permissions

The DocV SDK requires camera permissions to capture identity documents. Upon the first invocation of the SDK, the app will request camera permission from the user. If the app does not already use the camera, you must add the following to the app’s Info.plist file:

Note: We recommend you check for camera permission before calling the DocV SDK launch API.

Import SocureDocV

Add the following line to import the SocureDocV SDK into the view controller:

import SocureDocV

Initialize and launch the SDK

To enable the DocV SDK functionality, add the following code to your app:

func onButtonTapped() {
    let options = SocureDocVOptions(
        publicKey: "da3e907d-c5dd-41cb-80ee-xxxxxxxxxxxx",
        docVTransactionToken: "78d1c86d-03a3-4e11-b837-71a31cb44142",
        presentingViewController: self,
        useSocureGov: false
    )

    SocureDocVSDK.launch(options) { 
        (result: Result<SocureDocVSuccess, SocureDocVFailure>) in
        
        switch result {
        case .success(let success):
            print(
                "Flow succeeded: \(success)"
            )
        case .failure(let failure):
            print(
                "Flow failed due to \(failure)"
            )
        }
    }
}

options parameters

The following table lists the options parameters:

Handle the response

Your app can receive response callbacks using a switch statement when the flow either completes successfully or returns with an error. The SDK handles both responses through the SocureDocVSDK.launch(options) function.

Success

If the consumer successfully completes the flow and the captured images are uploaded to Socure's servers, the result is .success and a message containing the deviceSessionToken is printed. This result contains a deviceSessionToken, a unique identifier for the session that can be used for accessing device details about the specific session.

public struct SocureDocVSuccess {
    public let deviceSessionToken: String?
}

Failure

If the consumer exits the flow without completing it or an error occurs, the result is .failure and a message is printed with the deviceSessionToken and specific error details.

public struct SocureDocVFailure: Error {
    public let error: SocureDocVError
    public let deviceSessionToken: String?
}

When the DocV SDK returns a failure, it provides a SocureDocVError enum with specific error cases relevant to the Capture App flow:

public enum SocureDocVError {
    case sessionInitiationFailure
    case sessionExpired
    case invalidPublicKey
    case invalidDocVTransactionToken
    case noInternetConnection
    case documentUploadFailure
    case userCanceled
    case consentDeclined
    case cameraPermissionDeclined
    case unknown
}

The following table lists the error values that can be returned by the SocureDocVError enum:

Note: The SocureDocV SDK also returns the backend API error codes and messages as received (for example, access denied or insufficient permission).

Step 3: Fetch the verification results

When the consumer successfully completes the document capture and upload process, call the Partner API to verify the IDV result.

After waiting, then you will upload the completed event and then call below API to verify the IDV result:

POST /programs/{programCode}/accounts/{accountIdentifier}/users/{userIdentifier}/kycGates/idvsocure

Refer to IDV Socure request