KYC Match

Allows service providers to programmatically validate a user’s identity attributes
Available in flag-for-spain

In a nutshell

Enhancing user verification with Operator’s trusted data

The KYC Match – CAMARA API allows service providers to programmatically validate a user’s identity attributes by matching them against the KYC data held by the user’s mobile network operator.

This ensures data consistency and integrity, enabling the secure provisioning of services based on verified user information.

Benefits

Fraud Prevention

Utilizing the KYC-Match API allows you to mitigate identity-related risks for your customers, including synthetic identity fraud and fraudulent transactions stemming from identity theft.

Data Integrity and Compliance

By matching user-provided data against trusted operator records, the API ensures data consistency and integrity, enabling the secure provisioning of services based on verified user information.

Streamlined Digital Onboarding

The KYC-Match API enables validation of customer-provided contact information against trustworthy data from mobile network operators, facilitating convenient digital onboarding while minimizing identity fraud risks.

Test and explore our APIs with API Playground

Discover the API Playground: your interactive environment for testing and exploring Network APIs with ease! Prototype, validate, and experiment in real-time without impacting your live systems.

Get started today and bring your projects to life!

Test in API Playground

Explore documentation

Use cases

Identity theft prevention

As online transactions like shopping, banking, and social interactions rise, personal information becomes dispersed across various digital platforms and databases. Implementing strong cybersecurity measures is essential to combat synthetic identity fraud and phishing. The KYC-Match API enables validation of customer-provided contact information against trustworthy data from mobile network operators, facilitating convenient digital onboarding while minimizing identity fraud risks.

Frequently Asked Questions

KYC Match is a Network API that helps you verify whether user-provided KYC details match the mobile-operator data associated with a phone number, to strengthen onboarding controls and reduce identity-related fraud.

It reduces exposure to identity mismatch scenarios (e.g., stolen/borrowed identities, synthetic profiles, mule onboarding) by adding an operator-backed consistency check as an input to your KYC/AML decisioning.

No, treat it as a risk signal that can reduce manual review or trigger step-up checks. Your regulatory obligations and risk appetite still determine whether documentary/biometric KYC is required.

KYC Match checks identity-data consistency against operator data.
KYC Tenure checks whether the phone number tenure is longer than a threshold date (a stability/age signal).
They answer different questions and are often complementary in onboarding risk models.

Use it as part of a rule set such as:
Match → proceed (or reduce friction)
No match / insufficient confidence → step-up (doc check, liveness, manual review)
Unavailable → fallback policy (do not auto-approve high-risk actions)
This helps control false positives and supports auditable decisions.

SIM Swap is focused on recent SIM change risk (often used to protect OTP/SMS-based flows).
KYC Match is focused on identity-to-number consistency for onboarding/compliance.
Use SIM Swap for ATO/OTP risk; use KYC Match for identity assurance.