Integrate Financial-grade Identity Verification
To verify user identities with Financial-grade Identity Verification, you must first integrate the service into your application. This topic describes the integration process for the Financial-grade Identity Verification service. After integration, you can begin calling the Financial-grade Identity Verification service.
Prerequisites
You have activated the Financial-grade Identity Verification service. For more information, see Activate the Financial-grade Identity Verification service.
You have added an authentication scene. For more information, see Add an authentication scene.
If you use a RAM user to develop and manage related services, create and authorize the RAM user in advance. For more information, see Authorize a RAM user to access the service.
WarningAn Alibaba Cloud account has full permissions for all cloud products. Leaked account credentials pose a major security risk. We recommend following the principle of least privilege: create and use a RAM user to access the Financial-grade Identity Verification service.
Procedure
Go to the AccessKey page and get your AccessKey.
Optional: Create an API signature. For details, see the sample code in native HTTPS call.
ImportantAn API signature is required for a native HTTPS call to secure your requests. If you use an SDK provided by Financial-grade Identity Verification, you do not need to create a signature.
Review the product components to understand the use cases for each solution and select the most appropriate one.
See the following integration guides for each solution:
Financial-grade Identity Verification solution integration guide
Financial-grade Multi-factor Willingness Authentication solution integration guide
Financial-grade Liveness and Facial Comparison solution integration guide
Financial-grade Liveness Detection solution integration guide
Financial-grade Facial Comparison solution integration guide
Financial-grade NFC Authentication solution integration guide
Next steps
If you choose a solution that requires willingness authentication, configure the required settings in the console. For more information, see Configure willingness authentication.
To view authentication statistics and records, see Query call data and Query authentication records.