iOS identity SDK

With this integration you will embed our technology into your own iOS app. Our UX components blend with yours and the user will go through the necessary steps without leaving your app.

On a high level, this integration has three main steps:
• Create a session using the Session API.
• Start the session in your app using the native SDK and the token created in the previous step.
• Use the Session API to retrieve the identity data when the SDK completes.

Note that there is no sandbox environment for testing, instead, integration and testing is done in production.
When you sign up for an account you can use the Developer plan for this.

Start by creating a new session from your backend system:

Optional properties:
• reference — set a reference to connect the session to any arbitrary identifier, such as a user id or a session id from your own system.
• face_verification — set whether face verification is required or not (false by default).
• passport_only — set whether only passports should be accepted, excluding national ID cards (false by default).

Send the token to your application.

Note that a session is intended to be used for a short period of time to handle a single user. Once a session has been used, it should not be used again.

Download the SDK (PassportReader.xcframework) for iOS and add it to your Xcode project.
Both Swift and Objective-C are supported. Minimum target iOS 16.0.

To add a framework to an iOS application, follow these steps:
• Open the app's Xcode project or workspace.
• Go to the app target's General configuration page.
• Add PassportReader.xcframework to Frameworks, Libraries, and Embedded Content.
• Make sure the framework is embedded and signed by the app target.

The app will need the following entitlement:

And the following entries in Info.plist:

Next, import the SDK and set up a session using the token from the previous step. At some point before starting the session, request permission to use the camera (this is not handled by the SDK).

Start the session.

When the SDK completion callback fires, use the Session API to retrieve the identity data in your backend system.

If face verification was required, an additional property will be available; face — containing an image of the user's face.

Data and metadata returned by the Session API, available for you to use in your application:

• Created — Timestamp for when the session was created
• Expires — Timestamp for when the session expires
• State — Current session state
• Reference — Your own optional reference for the session
• User IP — IP address observed when the user initiated the verification
• User agent — User agent observed when the user initiated the verification
• Given names — Given names as stated on the passport or ID
• Surname — Surname as stated on the passport or ID
• Nationality — Two-letter ISO 3166 code (e.g. “US”)
• Sex — “MALE”, “FEMALE” or “UNSPECIFIED”
• Date of birth — Formatted as YYYY-MM-DD
• Personal number — Personal number, if present in the document
• Place of birth — Place of birth, if present in the document
• Optional data — Additional personal data, if present in the document
• Optional data 2 — Additional personal data, if present in the document
• Document type — The document type (e.g. “PASSPORT”)
• Document number — Document number as stated on the passport or ID
• Expiry date — Formatted as YYYY-MM-DD
• Issuing country — Two-letter ISO 3166 code (e.g. “US”)
• Issuer — Name of the issuing authority
• Portrait image — High resolution digital image from the passport or ID, base64 encoded PNG
• Document integrity verified — Whether passive authentication verified the document data
• Active authentication — Whether active authentication was supported and verified
• Chip authentication — Whether chip authentication was supported and verified
• DSC — Document signer certificate used to verify the document
• CSCA certificate fingerprint — Fingerprint of the trusted country signing certificate authority certificate
• Face — Image of the user's face (if face verification was required), base64 encoded PNG

Possible lifecycle states for a session:

• State CREATED — The session is created
• State INITIATED — The session has been initiated by the user
• State FAILED — The session failed, e.g. because of an NFC read error
• State CANCELLED — The session was cancelled by the user
• State COMPLETED — The session completed successfully