THE LINUX FOUNDATION PROJECTS

Know Your Customer Match

API Description
Use Cases
  • Digital Onboarding and Account Creation: Banks, fintechs, marketplaces, mobility services and digital platforms can use KYC Match during account creation to check whether the identity information provided by the user matches the operator-held KYC record associated with the mobile line.
  • KYC Refresh and Customer Profile Verification: Regulated or trust-sensitive services can use the API to periodically validate whether selected customer attributes still match operator-held records, helping maintain more accurate customer profiles.
  • Fraud Prevention and synthetic Identity Detection: Service providers can compare user-provided attributes against verified operator records to detect inconsistencies that may indicate synthetic identities, identity theft or fraudulent account creation.
  • Account Verification before sensitive Actions: Applications can call KYC Match before account recovery, profile changes, payment method updates or other sensitive actions where confirming user-provided identity information reduces risk.
  • E-Commerce and Marketplace Trust: Online retailers and marketplaces can use the API to validate buyer or seller identity attributes during registration, checkout, high-value purchases or seller onboarding.
  • Regulated Service Access and Compliance Support: Financial services, insurance providers and other regulated businesses can use KYC Match as one signal within their broader KYC, compliance and customer due diligence processes, subject to local regulation and provider policy.

See also at GSMA:

Benefits
  • Lower-Friction Identity Checks: Helps service providers validate user-provided identity attributes without forcing every user through manual document review or intrusive checks.
  • Improved Data Accuracy: Confirms whether selected information provided by the user matches the operator-held KYC record associated with the mobile line.
  • Fraud Risk Reduction: Helps detect inconsistencies that may indicate synthetic identities, identity theft, false account creation or suspicious profile changes.
  • Privacy-preserving Validation: Returns match results rather than the underlying operator-held customer data.
  • Better Onboarding Conversion: Reduces unnecessary friction in account creation and verification journeys while still allowing the service provider to apply identity checks.
  • Operational Efficiency: Helps automate identity-data validation and reduce manual review, back-office correction and support costs.
  • Developer-friendly Integration: Provides a standardized CAMARA API that can be integrated into onboarding, KYC refresh, fraud prevention, account verification and e-commerce workflows.

API Portfolio: Authentication and Fraud Prevention

Sub Project Wiki: Know Your Customer
(incl. how to meet the team)

API Wiki: Know Your Customer Match

API Repository: Know Your Customer Match

API Repository Status: Incubating

API Status: Initial

API Version(s) and Release Date(s):

  • v0.2.1 (11.12.2024), Fall24 meta-release
  • v0.3.0 (10.03.2025), Spring25 meta-release
  • v0.4.0 (14.09.2025), Fall25 meta-release

API availability: Information which APIs are available in which country and network, and how to get access can be found on the GSMA public launch status page.

Be part of a collaborative community driving the future of global Telco APIs.

Join Today