App (SDK) integration
The financial-grade Real-person Authentication solution uses technologies such as liveness detection, biometric recognition, and ID document OCR recognition. It combines these with identity verification APIs from authoritative sources to verify a user's identity. You can also configure whether to retain face images based on your business requirements. This topic describes how to integrate the financial-grade Real-person Authentication service using App (SDK) integration.
Limitations
The Financial-grade Real-Person Verification solution currently verifies only residents who hold one of the following ID documents:
Chinese mainland residents: Second-generation Resident ID Card.
Hong Kong and Macao SAR residents: Residence Permit for Hong Kong and Macao Residents.
Taiwan residents: Residence Permit for Taiwan Residents.
Exception handling
Changes to the authoritative data source may cause authentication to fail for some users because their identity information cannot be retrieved. Include a manual review option in your business flow as a fallback mechanism.
Supported permanent residence and travel permits
To authenticate the following certificates, use the solution in Alipay H5 page integration or Alipay Mini Program integration. No other solutions are supported.
Foreign Permanent Resident ID Card
Mainland Travel Permits for Hong Kong and Macao Residents
Mainland Travel Permit for Taiwan Residents
Unsupported certificates
Exit-Entry Permit for Travelling to and from Taiwan
Exit-Entry Permit for Travelling to and from Hong Kong and Macao
Foreigner's Exit-Entry Permit
Billing
You are charged based on the number of successful calls. For more information, see Billing overview.
Integration methods
The App (SDK) integration method works as follows.
|
Product code |
Integration method |
Authentication process |
Required materials |
Main outputs |
Output details |
|
ID_PRO |
Mobile SDK + server-side integration |
liveness detection |
Name, ID card number |
Real-person Authentication result, face image |
|
|
ID_PLUS |
Mobile SDK + server-side integration |
Capture an ID card image + liveness detection |
None |
Real-person Authentication result, OCR-recognized ID document information, face image, and ID document image |
Returns photos: Subject to legal and compliance requirements, this solution can return the user's face images. After you authorize the solution to access an OSS bucket, it automatically stores the returned face images in that bucket. For instructions on how to authorize access, see Enable and authorize OSS.
Compatibility: Compatible with iPads and other tablets.
Authentication process
The following figure shows the authentication process of the financial-grade Real-person Authentication solution when using App (SDK) integration. For detailed integration steps, see Integration process.
-
ID_PRO solution: The captured face data undergoes both on-device and cloud-based liveness detection and is then compared against faces in an authoritative database to verify the user's identity. During the authentication process, your users must grant consent before starting the face verification.
Preview
The face verification process consists of two stages. First, on the Face Verification page, the user confirms their portrait photo, agrees to the Authentication Service Agreement, and then taps Start Authentication. They can also tap Do Not Authenticate Now to skip the authentication. Next, on the Liveness Detection page, the user follows on-screen prompts, such as "Hold up your phone and blink", to complete the liveness detection.
-
ID_PLUS solution: The solution captures the user's ID document and face data. The data undergoes both on-device and cloud-based liveness detection and is then compared against faces and ID photos in an authoritative database to verify the user's identity. During the authentication process, your users must grant consent before starting the face verification.
Preview
The authentication process consists of four steps. Step 1: Capturing the portrait side. The user can either take a new photo or select one from their album. Step 2: Capturing the emblem side. Step 3: Face verification. The user agrees to the Authentication Service Agreement and taps Start Authentication. Step 4: Liveness detection. The user follows on-screen prompts to perform actions, such as blinking, to complete the process.