One flow, three SDKs
Web, Android and iOS walk the user through the same verification journey. This page shows the steps, who does what, and where your code comes in.
- 3
- SDKs
- 8
- steps
- 1
transactionId
Every SDK walks the user through the same steps
Pick a platform to see what each step is called in its SDK.
Pick a document, see which steps run
You choose the steps when the transaction starts. The combinations below are the ones each SDK's documentation lists.
Your server is in charge at both ends
The SDK handles the camera, the chip and the uploads. Credentials and the final decision never leave your backend.
- 1Sign in with your API credentials
- 2Hand the app a short-lived token
- 3SDK uploads the document and face captures
- 4App sends the transactionId to your backend
- 5Query the results with the transactionId
- 6Control results and scores: you decide
Same journey, different level of control
<techsign-kyc>
- One custom element: plain HTML, React, Vue or Angular
- Screens and step order are built in
- On desktop, a QR code moves the user to their phone
- No NFC: browsers cannot read the chip
com.techsign:rkyc-cnn
- You design the screens and the order of the steps
- Camera Fragments, NFC reader and service client included
- Android 7.0 (API 24) and later
- NFC on devices that have it
pod 'techsigncloudlibs'
- You design the screens and the order of the steps
- Camera views, NFC reader and liveness controllers
- Services through ProveIDApiClient, generated from the OpenAPI spec
- NFC on devices that have it
Four rules every integration follows
Credentials stay on the server
Never ship the API username and password in a web page or an app package; they are easy to extract.
The decision is made on the server
What the app shows is for the user. Approve a customer only after your backend has queried Prove ID.
Don't keep captured media
Document images and liveness videos are not saved to the gallery and are deleted from the device once sent.
Test on real devices
iOS Safari and Android Chrome for the web; several manufacturers, low light, and phones with and without NFC.
Need access credentials?
To call the API you need your organisation's credentials. Your Techsign representative can set them up for you.