Available on iOS. Android support is in progress.
nfc_read step (mobile only): the SDK reads the chip of the applicant’s passport or ID card over NFC, opens it with the MRZ of the identity document captured earlier in the same flow, and uploads the raw chip files. The platform verifies them server-side — Passive Authentication against the ICAO CSCA trust store, Active Authentication on a server-issued challenge.
The app never shows or receives an authenticity verdict: it arrives with the rest of the session result on your backend.
Enable it
1
Link LegalTalentNFC
Add the
LegalTalentNFC product next to LegalTalentUI. It is separate because it brings NFCPassportReader and OpenSSL; LegalTalentUI does not depend on it.2
Register the reader
nfcReader, a workflow that contains an nfc_read step cannot complete it.3
Add the capability
Xcode → Signing & Capabilities → Near Field Communication Tag Reading. The entitlements must contain:
4
Declare the Info.plist keys
What the applicant goes through
An intro page (what the chip is, the symbol to look for, what comes next), the reading page while the system NFC sheet is up, a short upload, and a done page with the chip photo and name. The chip opens with the document’s MRZ — the lines with<<<. The applicant never sees or types them: the SDK takes them from the on-device OCR of the identity document photographed earlier in the flow, or from the server’s extraction of that document when the session is resumed.
Chip coverage varies by country and document. Check with your Legal Talent contact which documents are supported before putting an
nfc_read step in a production workflow.