Payment Method Check Advanced allows you to confirm ownership of a particular payment method and prevents you from:

• Fraudulent transactions
• Sending funds to third parties
• Sending funds from suspicious accounts

In particular, you will be able to handle the situations in which some payment transfer systems do not require the name and surname of an applicant while sending funds to another person, but you still want to make sure the payment method belongs to the applicant. For additional confirmation, Sumsub requests such data from applicants to verify the transfer and payment source.

Additionally, for crypto wallets, Sumsub performs risk analysis using the Crystal provider, a blockchain intelligence solution that helps detect risky or suspicious wallet activity. This makes it possible to screen wallets directly within the WebSDK, even without a backend integration.

No matter what payment method should be processed, with the payment source check, you can identify it and specify the fields that should be requested and checked.

How Payment Method Check Advanced works

Payment Method Check Advanced consists of performing an applicant action that is linked to a particular applicant profile:

1. You provide the name of the institution along with the key identifiable details, like a unique number, email, phone, and full name associated with the payment source.
2. An applicant uploads a payment method to their profile (for example, a screenshot of their payment methods section in the profile or wallet address).
3. Sumsub compares the fields specified for confirmation via AI data systematization and OCR, and initiates a crypto wallet risk screening through Crystal.
4. The result of the check is based on data matching, risk screening, or both, depending on the payment method type:
   • Fields that you have provided earlier (that is, a unique number and email).
   • Data stored on the applicant page (that is, name and phone).
   • Expiration date, if applicable.
   • Crypto wallet risk level and risk score, if applicable (according to the result from Crystal).

👍

Tip

Use payment templates to test payment checks.

Get started with Payment Method Check Advanced

To start checking payment sources, you will need to complete the following steps.

Step 1: Create verification level

Create a verification level to be used with the WebSDK 2.0 and set up the following configuration:

1. In the verification level settings, select the Enable WebSDK 2.0 for this level toggle.
2. From the Type drop-down list, select Applicant actions.
3. Add Payment method as a required step. Choose whether to skip the ownership or risk check by selecting the corresponding checkboxes.

📘

Note

To enable crypto wallet screening via Crystal, make sure the Skip risk check option is not selected. If you prefer to run the crypto screening via API, refer to this article.

🚧

Attention

Payment Method Check Advanced works only in the WebSDK 2.0.

Step 2: Submit applicant data

Now that you have configured your verification level, you can submit the applicant data using either of the following methods:

• Submit the data using this API method.
• In the Dashboard, go to the applicant profile, open the Transaction monitoring tab -> Payment source, fill in the fields, and click Submit fields.

Step 3: Review results

Review the results with this API method or go to the applicant profile and scroll down to the Payment source check section that refers to Payment Method Check Advanced.

There are three matching points indicating the results of the check:

• Expired/Unexpired. Stands for the expiration status of a payment source.
• Fixed info matched. Stands for matches with the data sent by you during the payment source request.
• Applicant info matched. Stands for matches with the data available in Sumsub within the applicant profile.
• Risk level. Stands for the overall risk category of a crypto wallet (Low, Medium, High), if provided.
• Risk score. Stands for the numerical risk score of a crypto wallet (ranging from 0 to 1), if provided.

📘

Note

If one field does not match the corresponding field in the source of comparison, the entire matching check (that is, Fixed info matched or Applicant info matched) will be highlighted in red.