How to add one or more scenarios and configure different authentication schemes for the scenarios-ID Verification(ID Verification)-阿里云帮助中心

In the financial-level ID Verification service, authentication scenarios refer to different scenarios in which your users use the financial-level ID Verification service to complete user ID Verification, such as logon and payment. You can add one or more scenarios and configure different authentication schemes for different scenarios.

Procedure

Note

Before you perform the following steps, make sure that the financial-grade ID Verification service is activated. For more information, see Activate the financial-level ID Verification service.

Log on to the Financial ID Verification console. In the left-side navigation pane, click Access scene settings.
On the Access scene settings page, click New Scene or Add Scene. In the Add Scenario dialog box, set the following settings and click Determine.
- Scene Name: Enter a name that is easy to identify.
- Number of Stored Face Images: By default, one best face photo is returned.
- Stored Video Duration (s): By default, videos are not returned. To enable video retention, you must configure the following parameters. After you configure the parameters, 1s videos are returned by default.
  - APP(SDK) Access: Set the client extParams parameters to return videos.
  - H5 web page access: Configure true for VideoEvidence parameters in the InitFaceVerify.
  Note
  If you want to specify the number of photos to be retained and the duration of a video, the following conditions must be met:
  - APP(SDK): The client SDK version is 2.3.43 or later.
  - H5 Webpage Access: supported by default.
  - Alipay H5 website, Alipay mini program, or server-only access: not supported.
- Store Authentication Materials in OSS: Specifies whether to save facial photos and detection videos generated during ID Verification. If you select Yes, you must complete OSS authorization. If not, the authentication process can be performed normally. However, the photos and videos collected during the authentication process are not saved to OSS.
- Bind Mini Program Configuration: If the access scenario is a mini program, select Yes and configure the Mini Program Platform and Validation File. For more information, see Connect a third-party mini program to a face.

OSS authorization

If you want to retain authentication data, you must authorize the financial ID Verification to create a storage space for face photos. For more information, see Activate and authorize Object Storage Service (OSS).

Important

If you enable OSS to store certified photos and videos, you will incur corresponding storage fees.

In the lower part of the Access scene settings page, follow the instructions to Open OSS and To authorize.
In the Region section, select the region of the OSS bucket and click Generate Bucket. After a bucket is created, do not delete it.

Enable enhanced device detection

When you edit an authentication scenario, you can enable the Enhanced Device Detection to improve the security Fraud Detection capability of the authentication device environment, which is suitable for business systems with high security requirements.

When enabled, DeviceRisk fields are returned in the authentication result, which provide device risk labels (such as VirtualBrowser, Emulator, and ROOT) for evaluating device security. For more information about risk tags, see Device risk tags.

Billing: If you enable this feature, additional fees (CNY 0.05 per time) are incurred. For more information, see Device Assistant.
Enable: On the Access scene settings page, turn on Enhanced Device Detection.

Next Steps

Integrate SDKs for different access methods of financial-grade ID Verification services on the application client and server. For more information, see Access financial-grade ID Verification services.

Important

The account used to add the scenario and the account used to access the service must use the same account. Otherwise, the added scenario cannot be queried.

FAQ

How can I prevent the ID Verification for Financial Services service from being invoked or incurring charges?

The ID Verification for Financial Services service cannot be shut down directly. To stop using the service or prevent it from being invoked, you can delete the corresponding verification scenario on the Access scene settings page.

Must the webhook address (CallbackUrl) be the same as the request address domain name?

No, it does not. However, the webhook address must meet the following conditions:

Starts with the HTTPS protocol.
Supports public network access.
Returns an HTTP status code of 200 after receiving a callback.

Can the same AccessKey be used for multiple verification scenarios?

Yes, you can use the same AccessKey for multiple verification scenarios. Different connection types, such as apps, H5 pages, and mini programs, can share a verification scenario or use separate ones. Billing is not affected by the number of verification scenarios.