Match (CAMARA)0.2.1

Match (CAMARA) is a CAMARA-Compliant API that reduces fraudulent transactions and makes it harder to create fake or synthetic identities.

Customers are increasingly using their devices to get things done online, whether for shopping, travel or banking.

Many of these involve them having to set up an initial account, which can be time-consuming. What's more, in the past, it's been possible to set up accounts fraudulently by using other people's details.

Match provides signals based on the data provided by the customer that help you create a fraud risk score.

CAMARA is an open-source project to publish standardized definitions of telco network APIs that work across multiple networks in a single country.

CAMARA enables easy and seamless access by making the APIs available across telco networks and countries. This approach also simplifies telco network complexity, reduces costs, accelerates technology development, and supports application portability.

Changelog

Version: v1 | Release Date: Oct 2024 | Status: Coming Soon

Protocol

HTTPS

URLs for Sandbox environment

Sandbox:

The sandbox environment is currently work in progress, please use the following Postman collection in the interim. KYC Match Postman Collection

• Match your customer's data instantly against first-party KYC (Know Your Customer) attributes held by Vodafone: Given Name, Family Name, Date of Birth, First line of address, Postal Code.
• This service works for Vodafone mobile numbers (MSISDNs) only. 
• No user information is shared
  • The API will respond with True/False and Match Score of 0%-100% in case of False
  • It checks if the submitted attributes match with the data that we hold against the phone number
  • This is similar to a credit check

• What’s New in the Latest Version?

  With the new version of the Match API, we’re moving from exact matching to a more flexible, score-based matching system using Yaro-Winkler fuzzy logic. Instead of a binary true/false result, the API now returns a match score from 0 to 100. This allows for a nuanced view of matching results, giving you more control over what you consider a successful match. The higher the score, the closer the match, and you’ll have the flexibility to interpret these scores in a way that best suits your business needs. With this new model, we anticipate higher match rates, which will be invaluable for identity verification while reducing false negatives and enhancing customer onboarding experiences.

Example Workflow

A new customer is shopping online at an online clothes retailer and wants to pay for the items in instalments.

1. The customer goes to checkout from the website and pays for the goods they want to purchase.
2. The website (or app) asks them to register their details for the first time.
3. The app sends a request to Vodafone's Match API.
4. The API compares the attributes submitted by the user with the details that Vodafone holds against that user and sends a response for each of the API attributes. For example:

If the details don't match, further identity checks may be required, so that the retailer can ensure that the user is real.

• Enrolling a customer on to new services (by re-using the validated user identity that Vodafone has previously captured).
• Banks that need to verify new users by using Remote ID checks.
• Banks that need to refresh their Know Your Customer (KYC) records.
• Mobile wallet card enrolment.
• Mobile wallet ID verification.
• Compliance check for online gambling.