Epic:
SM-38
-
ONB: Provide necessary data for onboarding
Done
User story:
SM-1214
-
ID scanning and verification for 6 IDs supported by AAI
Done
User story: As a customer I want to scan my ID (up to 10 types) so that my identity can be confirmed.
Role: Customer, System.
Objective: Customer will provide ID for scanning and AAI system will extract data from ID via OCR algorithm and app will fill data in UI. Document forgery is applied along with.
ID scan is stored in DB.
Reason: Getting Customer’s data from ID, verifying document and storing ID scan in DB.
Functional requirements:
These IDs must be supported by all parties for ID scanning, data extraction and verification:
01. UMID (both old and new)
02. SSS ID (social security system)
03. TIN ID (taxpayer identification number, old version)
04. TIN ID (new version)
05. Passport (Front side only)
06. Driving License
07. Voter's ID
08. PRC ID
09. Premium Postal ID
10. PagIbig ID
11. Philsys National ID
UI requirements: n/a
Process flow: n/a
Execution steps:
Customer provides ID for scanning
AAI API provides extracted data from scanned ID (via OCR)
AAI API will return document forgery result (just collecting this data, the whole KYC flow will continue regardless this result, to the final Success or vKYC screen)
ID scan is stored in DB
Data is filled in respective UI fields
Fields are enabled for manual entry
Internal dependencies: Google file storage
External dependencies: AAI API to support all IDs from the list
Alternative scenarios:
1. No data from AAI is fetched → Customer will fill all fields manually in
Acceptance criteria:
Data from ID is filled in UI for supported IDs
Fields are enabled for manual entry
Links to wireframes/UI: From https://www.figma.com/file/dkDQHRa1zq7tU58MiL6hBR/SaFi---UI---MVP-(Shared)?node-id=484%3A7998 to https://www.figma.com/file/dkDQHRa1zq7tU58MiL6hBR/SaFi---UI---MVP-(Shared)?node-id=484%3A7579