H5 web integration
Financial-grade real-person authentication verifies user authenticity by combining technologies such as liveness detection and biometric recognition with identity element verification from authoritative sources. You can also choose whether to retain face images. This topic describes how to integrate the financial-grade real-person authentication service by using H5 web 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 method
The following table outlines the H5 web integration method.
|
Product code |
Integration method |
Authentication process |
Inputs |
Main output |
Output details |
|
ID_PRO |
Web and server-side integration |
liveness detection |
Name and ID card number |
Real-person authentication results and face images |
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 PC and mobile H5 pages.
Authentication process
The following figure illustrates the authentication process for financial-grade real-person authentication using H5 web integration. For detailed integration steps, see Integration Process.
To confirm the user's authenticity, the service verifies the captured face information by using cloud-based liveness detection and face comparison against an authoritative database.Users must grant consent before starting face authentication.
UI reference
The face authentication interface includes an initial verification screen and an error state screen. The initial screen has the title "Face Scan Verification" at the top, a circular area for face recognition in the center, and three prompts below: "Face the screen", "Uncover your face", and "Sufficient light". At the bottom are two buttons: Start Verification and Not Now. If no face is detected, a red "No face detected" prompt is displayed, prompting the user to try again.