

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.
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.
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.
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.
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.