FAQs

Document Verification

---

Question: How does Document Verification work?

Answer: Document Verification works on the basis of a Document (typically a national ID) as input and getting details around the content of the document like personal information (Name, DoB, Gender, Address etc) along with authenticity indicators of the document around forgery, tamper detection as output.

---

Question: Does Document Verification have Global Coverage?

Answer: Currently Document Verification is supported in India. We will soon be live in US, SEA and the Middle East.

---

Question: Can I use Document Verification in the Bureau Platform?

Answer: Yes. Document Verification results can be used on the Bureau Platform.

---

Question: Can I build rules on the Bureau Platform using Document Verification results?

Answer: Yes. You can use the output and results of Document verification such as OCR results to build custom rules on the Bureau Platform.

---

Question: Is confidence score given on the OCR of documents? If yes, what is this based on?

Answer: Yes confidence score is given on the OCR of document.

---

Government Checks

---

Question: How does Government Checks work?

Answer: Government Checks work on the basis of an ID number (typically a national ID number) as input and getting details around the personal information associated with that ID present in the Government Source or any such trustworthy source (Name, DoB, Gender, Address etc) along with validity indicators of the ID such as issue, expiry etc.

---

Question: Does Government Checks have Global Coverage?

Answer: Currently Government Checks is supported in India. We will soon be live in US, SEA and the Middle East.

---

Question: Can I use Government Checks in the Bureau Platform?

Answer: Yes. Government Check results can be used on the Bureau Platform.

---

Question: Can I build rules on the Bureau Platform using Government Checks results?

Answer: Yes. You can use the output and results of Government Checks such as Validity of the document, Personal attributes - Name, DoB, Address etc to build custom rules on the Bureau Platform.

---

Verification Insights

---

Question: How does Verification Insights work?

Answer: Verification Insights takes digital footprints of an individual such as Phone, Email, etc.

---

Question: Does Verification Insights have Global Coverage?

Answer: Currently Document Verification is supported in India. We will soon be live in US, SEA and the Middle East.

---

Question: Can I use Verification Insights in the Bureau Platform?

Answer: Yes. Government Check results can be used on the Bureau Platform.

---

Question: Can I build rules on the Bureau Platform using Verification Insights results?

Answer: Yes. You can use the output and results of Verification Insights such as Match Scores, Risk Scores, etc., to build custom rules on the Bureau Platform.

---

Face Similarity

---

Question: How does Verification Insights work?

Answer: Face Similarity compares human faces across documents or images and gives a similarity score which indicates if the face belongs to the same individual.

---

Question: Does Verification Insights have Global Coverage?

Answer: YES. Bureau’s Face Similarity capability has global coverage.

---

Question: Can I use Verification Insights in the Bureau Platform?

Answer: Yes. Face Similarity results can be used on the Bureau Platform.

---

Question: Can I build rules on the Bureau Platform using Verification results?

Answer: Yes. You can use the results of Face Similarity to build custom rules on the Bureau Platform.

---

Watchlists

---

Question: How does Watchlists work?

Answer: Bureau’s Watchlists takes basic personal attributes (Name, DoB etc) of an individual and concludes if that person exists across watchlists like PEP (Politically Exposed Person), AML (Anti-money laundering), Sanctions.

---

Question: Does Watchlists have Global Coverage?

Answer: Yes. Watchlists is supported globally.

---

Question: Can I use Watchlists in the Bureau Platform?

Answer: Yes. Face Similarity results can be used on the Bureau Platform.

---

Question: Can I build rules on the Bureau Platform using Watchlist results?

Answer: Yes. You can use the output and results of Watchlists to build custom rules on the Bureau Platform.

---

Question: What happens in a scenario where no record found for a person, what does that mean and how do we handle that case?

Answer: When no record is found for a person, it implies that the specified data was not found in any of the watchlists that this solution leverages.

---

Question: While using firstName and lastName as part of input, what happens in case of common names like (John, Mohammed, Kumar etc)?

Answer: In case of common names, all such occurrences (if any) in the watchlists will be presented in the results.

---

Question: Can this service be used to verify entities or businesses apart from individuals?

Answer: The current offering verifies individuals and also provides information on Associated Entities linked to profiles of those individuals.

---

Integration FAQs

---

Question: What are REST APIs?

Answer: REST is an architectural style or design pattern for APIs. When a client request is made through a RESTful API, it transfers a representation of the state of the requested resource. Web services that follow the REST architectural style are called RESTful web services.

A RESTful web application exposes information about itself in the form of information about its resources. It also enables the client to take actions on those resources, such as creating new resources (for example, creating a new user) or changing existing resources (for example, editing a post).

---

Question: What are the different HTTP Methods?

Answer: HTTP defines a set of request methods, also known as HTTP verbs, to indicate the desired action for a given resource.

---

Question: What are the different Parameters?

Answer: Parameters are options you can pass with the endpoint to influence the response.

There are four types of parameters:

• Path Parameters: Path parameters are part of the endpoint itself and are not optional.
• Query Parameters: Query parameters appear after a question mark (?) in the endpoint. Each parameter is listed in the query string right after the other, with an ampersand (&) separating them.
• Request Parameters: Request parameters are included in the request body and are used to send data via the REST API.
• Response Parameters: Response parameters represent the response to a request.

---

Question: What is API Authentication?

Answer: The API authentication process validates the identity of the client attempting to make a connection by using an authentication protocol. If there is no security with the API, users could make unlimited amounts of API calls without any kind of registration. And there wouldn’t be a way to protect against requests from malicious users that might misuse another user’s data.

At Bureau we follow Basic Authentication Protocol, which is a method for an HTTP user agent to provide a username and password when making a request. When employing Basic Authentication, users include an encoded string in the Authorization header of each request they make.

• The user’s username and password are combined with a colon.
• The resulting string is base64 encoded.
• Example: Basic base64 clientID:clientSecret

---

Question: What is a callback URL with respect to an API?

Answer: A callback URL is a notification endpoint used to notify a concerned entity that the API is finished executing provided the callback URL is already given to the API service prior to calling it.

---

Phone Insights (User Insights & Phone Name Attributes)

---

Question: What is the business name? How does it impact the end customer?

Answer: When the Business Name flag is True, it means that we have found a business entity name against the phone number. This flag suggests that the user might not be a Salaried customer.

---

Question: What is the source of the Business name? What is the source of this data?

Answer: There is a list of 400 common business names (like enterprise, store, hardware, etc), among all the names against the phone number, we run this check and if any of these 400+ names is found, we flag the business name as TRUE. The sources of this data is multifold, collected from a lot of public listing, as well as collected via Telco relationships, etc.

---

Question: What is digitalAge of a phone number?

Answer: We take the combination of the phone number and the input name, and check when was the first time we saw this combination for the first time (let's say XX) in our data universe. Further, the output would be in the number of days, which would be Today’s day-XX.

---

Question: How is it different from Age of the Phone number?

Answer: The age of the phone number takes just the phone number as input, and hence only checks for that, and gives you the output as the First seen date of the phone number. Mostly the Age of the phone number would be higher than the digitalAge output.

---

Question: firstName, lastName - When should we pass that optional field? - What is mandatory, what is not?

Answer: Ideally, we prefer the name as a single string, else when given as the firstName and lastName, we combine it as our own. For the phone-name-attributes, we will need either of two ways of name (full name as a string or in form of first name and last name.

---

Question: Name match score band data/logic.

Answer: The following table shows the band interpretations:

---