EPFO + CRIF Combined

Endpoint Overview

POST /api/v1/epfo-crif-combined/fetch

Description

The EPFO + CRIF Combined API delivers a unified financial and employment profile of an individual in a single API call, using just their mobile number. It simultaneously fetches data from the Employees' Provident Fund Organisation (EPFO) and CRIF High Mark, India's leading credit bureau.

The EPFO data provides a verified employment history including employer details, UAN, PF contributions, and service duration — while the CRIF data surfaces the individual's credit score, active loan accounts, repayment behaviour, and bureau summary. Together, this combined signal enables lenders and fintechs to make high-confidence credit and underwriting decisions without requiring separate API calls or manual document collection.

Key Benefits

Fetch employment history and credit bureau data in a single, low-latency API call

Verify income stability through EPFO contribution trends before credit decisioning

Detect employment gaps or job-hopping patterns that may signal repayment risk

Enrich thin-file applicants using EPFO data where CRIF bureau history is limited

Use Cases

Banking & Lending

Fintech & Payments

Enterprise & Compliance

Assess salaried borrower eligibility by combining employment tenure with credit score

Underwrite personal loans and credit lines faster using verified PF salary proxy data

Flag high-risk applicants with irregular PF contributions or poor bureau repayment history

Technical Implementation

Authentication

All API requests require authentication using your Finpass API credentials passed as request headers.

Obtain API Credentials: Register with Finpass to receive your X-API-KEY and X-API-SECRET.

Include in Requests: Add both keys to every request as HTTP headers.

Header	Value
`X-API-KEY`	Your assigned API Key
`X-API-SECRET`	Your assigned API Secret

Base URL: https://api.finpass.ai

Request Parameters

Request Headers

Header	Required	Description
`Content-Type`	Yes	Must be `application/json`
`X-API-KEY`	Yes	Your Finpass API Key
`X-API-SECRET`	Yes	Your Finpass API Secret

Request Body

Parameter	Type	Required	Description
`mobile_number`	string	Yes	The 10-digit mobile number of the individual (e.g., `9876543210`). Must be a valid Indian mobile number registered with EPFO and/or the credit bureau.

Example Request

{
  "mobile_number": "9876543210"
}

Process Response

Response Parameters

Top-Level

Parameter	Type	Description
`success`	boolean	Indicates whether the request was processed successfully
`message`	string	Human-readable status message
`data`	object	Contains both EPFO and CRIF data objects

`data.epfo` — EPFO Employment Data

Parameter	Type	Description
`uan`	string	Universal Account Number linked to the individual's PF account
`name`	string	Full name as registered with EPFO
`date_of_birth`	string	Date of birth as per EPFO records (YYYY-MM-DD)
`mobile`	string	Mobile number linked to EPFO account
`kyc_verified`	boolean	Whether Aadhaar/PAN KYC is verified with EPFO
`total_employers`	integer	Total number of employers on record
`employment_history`	array	List of all employment records
`employment_history[].employer_name`	string	Registered name of the employer
`employment_history[].establishment_id`	string	EPFO establishment ID of the employer
`employment_history[].date_of_joining`	string	Date of joining the employer (YYYY-MM-DD)
`employment_history[].date_of_exit`	string	Date of exit from the employer; `null` if currently employed
`employment_history[].pf_account_number`	string	PF account number for that employment
`employment_history[].employee_share`	number	Total employee PF contribution (in INR)
`employment_history[].employer_share`	number	Total employer PF contribution (in INR)
`employment_history[].service_duration_months`	integer	Duration of employment in months

`data.crif` — CRIF Bureau Data

Parameter	Type	Description
`credit_score`	integer	CRIF bureau credit score (range: 300–900)
`score_version`	string	Version of the scoring model used
`report_date`	string	Date on which the bureau report was generated (YYYY-MM-DD)
`total_accounts`	integer	Total number of credit accounts on record
`active_accounts`	integer	Number of currently active credit accounts
`closed_accounts`	integer	Number of closed/settled credit accounts
`overdue_accounts`	integer	Number of accounts with overdue payments
`total_outstanding`	number	Total outstanding loan amount across all active accounts (in INR)
`total_sanctioned`	number	Total credit sanctioned across all accounts (in INR)
`enquiries_last_30_days`	integer	Number of hard bureau enquiries in the last 30 days
`enquiries_last_6_months`	integer	Number of hard bureau enquiries in the last 6 months
`dpd_history`	string	Summary of Days Past Due history (e.g., `"0"` = no defaults)
`accounts`	array	List of individual credit account details
`accounts[].account_type`	string	Type of credit account (e.g., `Personal Loan`, `Credit Card`, `Home Loan`)
`accounts[].lender_name`	string	Name of the lending institution
`accounts[].account_number`	string	Masked credit account number
`accounts[].sanctioned_amount`	number	Original sanctioned loan amount (in INR)
`accounts[].outstanding_amount`	number	Current outstanding balance (in INR)
`accounts[].emi_amount`	number	Monthly EMI amount (in INR)
`accounts[].open_date`	string	Date account was opened (YYYY-MM-DD)
`accounts[].close_date`	string	Date account was closed; `null` if still active
`accounts[].account_status`	string	Current status (e.g., `Active`, `Closed`, `Settled`)
`accounts[].overdue_amount`	number	Current overdue amount, if any (in INR)
`accounts[].dpd`	string	Days Past Due on the most recent payment cycle

Example Successful Response

{
  "success": true,
  "message": "EPFO and CRIF data fetched successfully",
  "data": {
    "epfo": {
      "uan": "100987654321",
      "name": "RAHUL SHARMA",
      "date_of_birth": "1990-03-14",
      "mobile": "9876543210",
      "kyc_verified": true,
      "total_employers": 3,
      "employment_history": [
        {
          "employer_name": "INFOSYS LIMITED",
          "establishment_id": "MHBAN0012345",
          "date_of_joining": "2021-07-01",
          "date_of_exit": null,
          "pf_account_number": "MH/BAN/12345/001/0001234",
          "employee_share": 187200,
          "employer_share": 187200,
          "service_duration_months": 33
        },
        {
          "employer_name": "TATA CONSULTANCY SERVICES LIMITED",
          "establishment_id": "MHBOM0054321",
          "date_of_joining": "2018-04-10",
          "date_of_exit": "2021-06-30",
          "pf_account_number": "MH/BOM/54321/001/0054321",
          "employee_share": 396000,
          "employer_share": 396000,
          "service_duration_months": 38
        },
        {
          "employer_name": "WIPRO TECHNOLOGIES LIMITED",
          "establishment_id": "KABAN0067890",
          "date_of_joining": "2016-06-15",
          "date_of_exit": "2018-03-31",
          "pf_account_number": "KA/BAN/67890/001/0098765",
          "employee_share": 208800,
          "employer_share": 208800,
          "service_duration_months": 21
        }
      ]
    },
    "crif": {
      "credit_score": 762,
      "score_version": "CRIF v3.0",
      "report_date": "2024-11-15",
      "total_accounts": 5,
      "active_accounts": 3,
      "closed_accounts": 2,
      "overdue_accounts": 0,
      "total_outstanding": 1245000,
      "total_sanctioned": 2500000,
      "enquiries_last_30_days": 1,
      "enquiries_last_6_months": 3,
      "dpd_history": "0",
      "accounts": [
        {
          "account_type": "Home Loan",
          "lender_name": "HDFC BANK LIMITED",
          "account_number": "HDFC****7823",
          "sanctioned_amount": 2000000,
          "outstanding_amount": 1100000,
          "emi_amount": 18500,
          "open_date": "2020-09-01",
          "close_date": null,
          "account_status": "Active",
          "overdue_amount": 0,
          "dpd": "0"
        },
        {
          "account_type": "Personal Loan",
          "lender_name": "BAJAJ FINANCE LIMITED",
          "account_number": "BJFN****4421",
          "sanctioned_amount": 300000,
          "outstanding_amount": 145000,
          "emi_amount": 9200,
          "open_date": "2023-03-15",
          "close_date": null,
          "account_status": "Active",
          "overdue_amount": 0,
          "dpd": "0"
        },
        {
          "account_type": "Credit Card",
          "lender_name": "ICICI BANK LIMITED",
          "account_number": "ICIC****9934",
          "sanctioned_amount": 200000,
          "outstanding_amount": 0,
          "emi_amount": 0,
          "open_date": "2019-11-10",
          "close_date": null,
          "account_status": "Active",
          "overdue_amount": 0,
          "dpd": "0"
        },
        {
          "account_type": "Personal Loan",
          "lender_name": "AXIS BANK LIMITED",
          "account_number": "AXIS****1102",
          "sanctioned_amount": 150000,
          "outstanding_amount": 0,
          "emi_amount": 0,
          "open_date": "2017-05-20",
          "close_date": "2019-05-20",
          "account_status": "Closed",
          "overdue_amount": 0,
          "dpd": "0"
        },
        {
          "account_type": "Two Wheeler Loan",
          "lender_name": "HERO FINCORP LIMITED",
          "account_number": "HEFC****3310",
          "sanctioned_amount": 85000,
          "outstanding_amount": 0,
          "emi_amount": 0,
          "open_date": "2016-08-01",
          "close_date": "2018-07-31",
          "account_status": "Closed",
          "overdue_amount": 0,
          "dpd": "0"
        }
      ]
    }
  }
}

Possible Error Responses

Invalid Mobile Number

No Record Found

Partial Data

Unauthorized

{
  "success": false,
  "message": "Invalid mobile number format. Please provide a valid 10-digit Indian mobile number.",
  "error_code": "INVALID_INPUT"
}

Returned when the provided mobile number is not a valid 10-digit Indian number.

Integration Best Practices

Security Recommendations

Never expose your X-API-KEY and X-API-SECRET in client-side or mobile app code; always route calls through a secure backend service

Obtain explicit user consent before fetching EPFO or bureau data, as this constitutes processing of sensitive personal financial information

Mask sensitive fields (e.g., PF account numbers, loan account numbers) before logging or storing API responses

Rotate your API credentials periodically and revoke compromised keys immediately via the Finpass dashboard

User Experience Guidelines

Validate that the mobile number is exactly 10 digits on the client side before making the API call

Handle the partial data response gracefully — display available data while informing the user if EPFO or CRIF data could not be retrieved

Do not block the onboarding flow solely on absence of CRIF data for thin-file users; use EPFO employment data as a supplementary signal

Cache responses for a short duration (e.g., 12–24 hours) to avoid repeated bureau hits, which can negatively impact the user's credit score

Code Samples

cURL

Python

Node.js

Compliance and Legal Considerations

Data fetched through this API includes sensitive personal financial information sourced from EPFO and CRIF High Mark. You must obtain prior, explicit, and informed consent from the individual before initiating this API call. Ensure your data usage complies with the Digital Personal Data Protection Act (DPDP), 2023, the RBI Master Direction on KYC, and CRIF's permissible use policy. Bureau data must only be used for credit underwriting, identity verification, or risk assessment purposes as disclosed to the end user. Do not share, sell, or repurpose this data with third parties without appropriate legal basis. Retain consent records and API call logs for the period mandated by your regulatory framework. Access to this endpoint requires the EPFO_CRIF_COMBINED permission on your Finpass account.

EPFO-CRIF Combined Report

EPFO + CRIF Combined#

Description#

Use Cases#

Technical Implementation#

Request Headers#

Request Body#

Example Request#

Response Parameters#

Top-Level#

data.epfo — EPFO Employment Data#

data.crif — CRIF Bureau Data#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses