Logo
Login

KYC Match

Know Your Customer

Check name, address, date of birth or email against the verified records of your customer's mobile operator. You get a match result for each personal detail, while the operator's data stays private.

Powered by:
Telekom

What is KYC Match?

Mobile operators keep verified identity records for their subscribers (KYC, Know Your Customer). With KYC Match, you send the personal details a customer gave you, such as name, address, date of birth or email, and the operators compare them with the record  keep for their mobile number. You get true, false or not available for each of them. This works for customers whose mobile number is with a covered operator in your market.

How it works


Your application submits a mobile number and either a look-back period or a request for the latest change date; the API returns the matching SIM-change information available for that line.

Your backend calls one of the SIM Swap API operations when a customer attempts a sensitive action. You can check whether a SIM change occurred within a defined number of hours, or request the latest change date. Your application then uses the response in its own risk assessment—for example, to continue the journey, request additional verification or pause the action.

The API provides information to support your decision. It does not determine whether a transaction is fraudulent or take action on an account by itself.

How it works

The operator checks every personal detail you send and returns a separate result for each.

Why KYC Match?

Your identity checks gain an operator-backed signal for each personal detail.

What you can check

The mobile number identifies your customer. You can check one or more of these personal details, and each gets its own result. Availability depends on your market and the operator's data.

Exemplary Use Cases

Check personal details at sign-up, in fraud-sensitive journeys and before account changes.

Deep Technical Capabilities

KYC Match follows the CAMARA standard: one REST call, one result per attribute.

_KYC Match Technical Flow.png

Simple, RESTful and built on the CAMARA standard

KYC Match processes personal data, so every integration starts with your use case and its legal basis. The technical setup follows standard OAuth2 and REST.

Before you integrate

  1. Define the customer journey and its business purpose.
  2. Confirm with us that your market, and the attributes you need are covered.
  3. Complete the commercial and legal approval for your use case.

Integration steps

  1. Register your application and subscribe to KYC Match.
  2. Configure the agreed authorization flow.
  3. Test with approved test data: matches, mismatches and unavailable attributes.
  4. Complete the acceptance checks, go live and monitor usage and match quality.


After registration, you receive credentials, endpoints and authentication instructions.

Access requirements

  1. A user-bound access token with the scope kyc-match:match
  2. A supported API version and endpoint for your market
  3. At least one attribute to compare besides the mobile number
  4. An approved legal basis and data-processing model for your market and use caseons.
     

Application Approval Process

Each CSP must assess and approve an application’s intended use of its network APIs before granting access; TMF931 provides the standard way to submit the application and record each CSP’s decision.

Application Approval Flow.png

Book a KYC Match Solution Workshop

Together we define the customer journey, select the personal details to verify, confirm operator and market coverage, align the legal and consent model and agree on test scenarios and decision rules. Fill out the form and a Deutsche Telekom expert will get back to you..