India’s Central Database of Fraudulent and Suspicious Customers
Detect, flag, and verify suspicious users with confidence. Built for banks, NBFCs, and insurers to protect against fraud during onboarding and beyond.
How will this data be shared?
By VideoCX.io VKYC system
- New status introduced in VideoCX.io system called Suspicious
- It will have its own set of dispositions, which will be common across companies
- Once an Agent or Auditor marks it as Suspicious, selective data of that customer will be added FraudCheck.io
By any other Regulated Entity system
- An independent API service using which Regulated Entities can share information about fraudulent customers from any other application
- Regulated Entity can share the data during onboarding, or post onboarding. So for NTB or ETB also
What data
will be shared?
No PII data of the customer is shared and stored in the central database. Any other data fields to make the database more relevant and informative can be easily added.
Regulated Entity name
.svg)
Customer name Hash value
.svg)
Mobile number Hash value
.svg)
PAN number Hash value
.svg)
VKYC system disposition
.svg)
IP Address
.svg)
Lat Long
.svg)
Customer address
.svg)
Customer category
.svg)
Notes by agent or auditor
How can Regulated Entities search in FraudCheck.io?
API request
Regulated Entity can send either of the below fields of the customer they want to run the FraudCheck for in the API request
- Regulated entity ID
- Hash value of mobile number
- Hash value of PAN number
- IP address
- Lat Long
API response (if match)
- Mobile number match (Yes / No)
- PAN number match (Yes / No)
- IP address match (Yes / No)
- Lat Long match (Yes / No)
- Regulated Entity name
- Fraud marking date
- Disposition (if done in VKYC)
- Customer category (Suspicious / Fraud etc)
- Customer address
- Notes
Data returned will be for all attempts made under that mobile, PAN, IP address and Lat Long combinations, which could be from multiple Regulated Entities.
UI Module for Search
Regulated Entities will have a UI based module to enter mobile number and PAN number and check if they are a part of the FraudCheck.io database. The module can be given to bank branches and internal teams.
What API integrations are needed?
01
01
Add Data API
An API to add data to FraudCheck.io from any of RE systems. For Regulated Entities using VideoCX.io VKYC system, the addition through VKYC will be a part of the VideoCX.io system itself.
02
02
Search API
An API to search data from FraudCheck.io database, which Regulated Entities can integrate in their onboarding systems, CRM, Fraud systems etc.
No PII data will be shared
Actual mobile number and PAN number will not be shared with FraudCheck.io. They will be Hashed at source and the hash values will be shared and stored at FraudCheck.io. API request will also be sent with the Hashed values.
What will be the additional security?
- FraudCheck.io is hosted in AWS Mumbai region.
- API response will also NOT contain any PII data.
- API request will be authorized using a secret and key which will be unique for each Regulated Entity.
- API request will only be allowed from specific whitelisted IP addresses.
- API will also have payload level encryption.
- All other standard security measures will also be applied like Rate limiter, WAF, HTTPS.
Who Can Contribute to FraudCheck.io?
FraudCheck.io is built on collaboration. We empower trusted institutions to report and verify fraudulent behavior across the ecosystem.
Banks
.svg)
NBFCs
.svg)
Micro Finance Institutions
.svg)
Insurance Companies
.svg)
Mutual Funds
.svg)
Law Enforcement Agencies
Contact us to know more
FraudCheck.io is a new initiative by VideoCX.io, India’s most used Video Banking and Video KYC platform. To know more, please write to us on contact@videocx.io