Customers increasingly expect to open an account, rent a car or activate a line without queueing for the identity step. Organisations want the same thing, as long as remote does not mean weaker. The mobile SDK is built to give them both.
What changes when the check moves to a phone
A phone cannot light a document in ultraviolet or read it in infrared, so a remote check cannot simply copy the counter. It shifts the weight to what a phone does well: reading the chip over NFC, where the document carries one, and proving with a live selfie that the person holding the phone is the person on the document.
What the phone captures
The native SDK captures the document and a live selfie on the customer's phone. Where the phone and the document allow it, it also reads the chip over NFC. Everything is encrypted on capture and sent to the same cloud models used at the counter.
The phone is a conduit, like the scanner and the Station. It captures and encrypts; it does not analyse or keep.
The same models as the counter
A remote check that runs on a different engine from the branch check creates two standards of identity inside the same organisation. Here the document verification, the biometric match and the liveness detection run on the same cloud models, with the same verdict format and the same audit record.
- Document capture and authenticity checks against the same references as the counter.
- A live selfie, matched to the document photograph, with liveness detection.
- NFC chip reading where the phone and the document support it.
Built into your app, not beside it
The SDK sits inside your own application and your own journey. It uses the same API, the same authentication and the same JSON as every other capability on the platform, so adding remote onboarding does not start a separate integration project.
What it does to the visit
In banking, the customer arrives at the branch already verified, ready to sign rather than ready to queue. In hospitality and car rental, the guest verifies before arrival and the desk has only the handover left. In telecom, the order placed from home is verified with the same confidence as the one placed in store.
The counter does not disappear. It stops being the place where identity is proven, and goes back to being the place where the relationship happens.
Questions about remote onboarding
Is remote verification as reliable as the counter?
It runs on the same cloud models, with the same verdict format and the same audit record. The capture differs, so the remote check relies more on the chip and on liveness detection.
Does the phone keep the images?
No. Like the scanner and the Station, the phone captures and encrypts; it does not analyse or keep anything once the session ends.
What if the phone or the document has no NFC?
The check runs on the document capture and the live selfie with liveness detection, and the chip is read whenever the phone and the document both allow it.
Is the SDK a separate integration?
No. It uses the same API, the same authentication and the same JSON as every other capability on the platform, inside your own app.