KYC Match API

In a digital environment that demands speed, security, and regulatory compliance, Plusmo's Know Your Customer (KYC) Match API offers the definitive solution for validating your customers' identity. This revolutionary tool simplifies compliance with KYC and AML (Anti-Money Laundering) regulations by verifying the customer's identity directly against the most reliable data source: the mobile network operator (MNO).
‍
Our API verifies the identity data you have about a customer, instantly comparing it with the information the mobile operator has registered for the associated phone number. If the level of match is sufficient, the identity is validated, and the business process can continue without friction.
More Information

How Real-Time Data Matching Works?

Plusmo's KYC Match API establishes a secure verification channel between your customer database and the mobile operator's database, without revealing confidential data on either side.

The Customer Validation Flow

  • Data Capture and Query: Your institution collects key customer data during the onboarding process or a sensitive operation (e.g., full name, ID/Passport number, date of birth) and their phone number (MSISDN).

  • Call to the KYC Match API: Your system sends the following query to the Plusmo API, including the number and the customer's data.

  • Cross-Verification: The API securely contacts the mobile operator associated with that number and performs the verification: Do the customer data you sent match the data the operator has registered for that phone number?

  • Match Level Response: The operator returns a response indicating the match level (e.g., total match, partial match, or no match).

  • Risk-Based Decision:

    -Total or sufficient match:     the user is automatically validated and continues with the normal process.

    -Partial or no match: your system implements additional measures (e.g., video call, document verification) to validate the user or, in high-risk cases, the request is rejected.

  • This process not only verifies that the number is valid but also confirms that the person using it is the registered legitimate holder.

Strategic Benefits of Integrating Plusmo KYC Match API
Fraud reduction: by cross-referencing data with a trusted source (the MNO), you eliminate identity uncertainty and minimize exposure to fraud.
Accelerated onboarding: by automating identity verification, the time required to onboard a new customer is reduced, improving experience and conversion rate.
Cost Optimization: decrease operational costs associated with manual document review and fraud management.
Reinforced Compliance: provide regulators with a robust, real-time, and auditable layer of identity verification.

Frequent Asked Questions

What level of match is considered "sufficient"?
The "sufficient match level" is defined by your institution based on its risk matrix. The API can return different levels (e.g., total match of name and ID/Passport number; partial match of last name, etc.). A total match is generally the threshold for low-risk operations, while a partial match may require an additional verification step to mitigate risk.
Does the API share complete customer data between my company and the mobile operator?
No. The API is designed to be a secure, privacy-compliant verification bridge. Your institution sends the data to the MNO. The MNO simply checks if that data matches its records and returns a match status (Yes/No/Partial). At no time are personal data (e.g., name, ID/Passport number) transferred between databases or visible to Plusmo.
What happens if the customer recently changed their number or name?
The API queries the most recent information registered by the operator. If the customer has legally updated their name or changed their number, that information will be the basis for the match. If the information your company has is outdated, the result will be a "partial match" or "no match", alerting you to the need to update your database.
What identity data is needed for verification?
The necessary identity data varies by region and agreement with the operator, but generally includes the phone number (MSISDN), full name, and Identification Document number (DNI/ID). The more data you send, the more precise the cross-verification will be.
Is this API a replacement for other identity verifications?
The KYC Match API is a complement and often a primary substitute for other less reliable or slower verifications. However, it does not replace your institution's obligation to collect and store documentation required by law. It simply automates and secures identity validation during the onboarding process.