Consumer Finance · Kaggle / LendingClub
LendingClub Loan Data (Kaggle Mirror)
Datadory delivers consumer finance loan-level data covering the LendingClub Loan Data (Kaggle Mirror): about 2.26 million accepted personal loans from June 2007 through 2018 Q4 plus 2.76 million rejected applications, 151 documented fields each, grades, rates, FICO ranges, DTI and full repayment outcomes. Delivered daily, weekly, or hourly - your call.
API, files, or your warehouse. Daily, weekly, or hourly.
- Where it covers
- United States, all states - borrower-reported state on accepted loans, three-digit zip codes on the rejected-application side
- How far back
- Originations June 2007 through 2018 Q4, frozen at version 3 (April 2019) - a fixed eleven-year laboratory
- How fine
- One row per loan application; monthly performance and settlement fields accumulate on the accepted-loan rows
What is the LendingClub Loan Data (Kaggle Mirror)?
The LendingClub Loan Data (Kaggle Mirror) preserves the loan-level record of LendingClub's peer-to-peer personal lending platform: about 2.26 million accepted loans issued from June 2007 through 2018 Q4, plus roughly 2.76 million rejected applications from the same window. Accepted loans carry the full LoanStats schema - 151 documented fields spanning origination terms, borrower attributes, credit-file snapshots and settlement outcomes, each defined in the lender's own official data dictionary and verified during our research pass.
Two design features make this the reference panel for consumer-credit modeling. First, closed-loop outcomes: every loan resolves to Fully Paid, Charged Off, Default or Current, with payments received and post-charge-off recoveries on the same row, so probability-of-default and loss-given-default models train on one single already-joined table. Second, an expert baseline built in: the LC-assigned grade ladder, A through G, subdivided into subgrades A1-G5, sits beside the interest rate actually charged. On the Consumer Finance shelf it scores 7/10 on our quality rubric against a catalog average of 7.81 across all 1,744 datasets we hold.
What do sample rows look like?
One row per loan application, wide and flat: origination terms up top, borrower attributes beneath them, outcome columns resolving to the right as the loan seasons. Two formatting conventions matter before you parse anything. Percent signs were stripped from int_rate and revol_util at the file level - 11.44 means 11.44 percent - and term collapses to a bare integer, 36 or 60, never anything else.
The block below reproduces one accepted loan end to end, using values exactly as they appear in the file. Origination facts first, the bureau-derived block in the middle, and the settlement trio - payments received, recoveries, final status - closing the row.
What fields does the mirror carry?
Think of the 151 columns as four blocks. The terms block fixes the deal: amount applied for, 36- or 60-month term, interest rate, monthly installment. The borrower block describes who asked: employment length, home ownership, self-reported annual income, verification status, debt-to-income ratio, and the FICO range pulled at origination. The credit-history block adds recent delinquencies and revolving utilization. The assignment block records the platform's judgment - grade and sub-grade - while the outcome block settles the story with total payments received, post-charge-off recoveries and final loan status.
The dictionary below lists the twenty-one columns that do most of the modeling work. The remaining payment and settlement fields, and the whole nine-column rejected-application sheet, fold out with your sample.
Where does coverage run, and at what grain?
Geographically this is a national book: borrowers from every U.S. state appear, with the state code reported by the borrower on the accepted side and three-digit zip codes on the rejected side. Temporally, originations run June 2007 through 2018 Q4 - eleven full calendar years of unsecured consumer lending. The snapshot is frozen at version 3, dated April 2019, which is precisely what makes it useful: a fixed laboratory where no later print can revise your backtest.
Granularity is one row per loan application. Accepted loans additionally accumulate monthly performance and settlement fields on that same row, so a vintage table needs no reshaping before it groups.
How is the data delivered?
API, files, or your warehouse. Daily, weekly, or hourly.
You pick the channel and the cadence; the field dictionary above travels unchanged across all three. Full-history loads suit a team calibrating a model once against the whole 2007-2018 book. Cohort-scoped feeds suit dashboards and feature stores tracking one grade band, one state, or one purpose code. Warehouse delivery lands typed one-row-per-loan tables next to your own portfolio data so the joins stay local. Cadence changes are a settings conversation, not a re-integration project.
Who uses this data, and for what?
- Default-prediction benchmarks. Train probability-of-default models against terminal loan_status labels and score every challenger against the LC grade baseline.
- Loss-given-default and recovery work. Payments received and post-charge-off recoveries settle each charged-off loan on the same row, with no outside servicing data needed.
- Vintage and cohort analysis. issue_d slices the book into monthly vintages; grade, purpose and state cut each vintage thinner.
- Reject inference and policy research. The rejected-application book pairs amount requested, risk score, DTI and geography for loans that never funded.
- Rate-setting forensics. Interest rate against sub-grade quantifies, in basis points, what one notch of assigned risk was worth at origination.
Which personas get the most value?
Data Scientists & ML Engineers get the cleanest classification target in consumer credit: 151 candidate features, a labeled outcome, a benchmark everyone recognizes (their use cases). Investors & Quants rebuild marketplace-lending economics - rate setting, grade migration, realized losses - origination to settlement (their use cases). Market Researchers & Consultants read borrowing behavior straight from stated purposes, income bands and state distributions instead of survey panels. Developers & Data-Product Builders prototype credit products against realistic loan shapes - terms, installments, outcomes - before wiring production systems. Journalists, Academics & Students cite actual loan-level outcomes, millions of them, instead of anecdote.
What should I know before requesting a sample?
Four honest caveats. First, the book is frozen: nothing originates after 2018 Q4, so treat this as a fixed laboratory for backtesting and benchmarking, and pair it with a live source when current-vintage work matters. Second, formatting ships as-is: percent signs are gone from int_rate and revol_util, and term is a bare 36-or-60 integer - parse types deliberately rather than trusting defaults. Third, label maturity: a loan issued in mid-2018 cannot yet read Fully Paid or Charged Off, so outcome-ready cohorts run earlier than origination-ready ones, and mixing the two inflates apparent performance. Fourth, asymmetric halves: the rejected side carries nine descriptive fields and no outcome, ever - use it for reject inference and policy research, never for loss modeling. None of these bite unexpectedly; they ship flagged against the analysis you plan to run.
Why request this through Datadory
Because the raw artifact is a multi-part archive of period-split compressed CSVs behind a 151-column header, assembled for interactive notebooks rather than pipelines. Datadory reshapes it into typed, one-row-per-loan tables with the data dictionary attached, cuts the cohort you name - grade band by issue years by state by status - and keeps consecutive deliveries reconcilable in your warehouse. Browse the rest of the shelf on the Consumer Finance data hub, see how the surveyed side complements it in the Federal Reserve Survey of Consumer Finances, or read the Kaggle source profile for the wider mirroring catalog.
Field dictionary
Every field below is documented against real records. The full dictionary ships with the sample.
| field | type | definition | example |
|---|---|---|---|
loan_amnt | number | The listed amount of the loan applied for by the borrower; reflects any credit department reductions. | 12000 |
term | integer | Number of payments on the loan; only 36-month or 60-month values occur. | 36 |
int_rate | number | Interest rate on the loan; percent symbols were stripped in this mirror, so 11.44 reads as 11.44 percent. | 11.44 |
installment | number | Monthly payment owed by the borrower if the loan originates. | 394.87 |
grade | enum | LC-assigned loan grade on the A-G ladder, the platform's headline risk verdict. | B |
sub_grade | enum | LC-assigned subgrade within the grade, A1 through G5; one notch finer than grade. | B3 |
emp_length | string | Employment length in years; 0 means less than one year and 10 means ten or more. | 5 |
home_ownership | enum | Home ownership status provided by the borrower or obtained from the credit report: RENT, OWN, MORTGAGE, OTHER. | MORTGAGE |
annual_inc | number | Self-reported annual income provided by the borrower during registration. | 72000 |
verification_status | enum | Whether income was verified by the platform, not verified, or whether the income source was verified. | Verified |
issue_d | date | The month in which the loan was funded - the key that slices the book into vintages. | 2016-06 |
loan_status | enum | Current status of the loan: Fully Paid, Charged Off, Current, Default - the modeling target for default prediction. | Fully Paid |
purpose | enum | Category supplied by the borrower for the request: debt_consolidation, credit_card, home_improvement and others. | debt_consolidation |
dti | number | Ratio of the borrower's total monthly debt payments excluding mortgage and the requested loan to self-reported monthly income. | 18.42 |
fico_range_low | integer | Lower boundary of the borrower's FICO score range at loan origination. | 705 |
fico_range_high | integer | Upper boundary of the borrower's FICO score range at origination. | 709 |
revol_util | number | Revolving line utilization rate: credit used relative to all available revolving credit; percent symbol stripped in this mirror. | 43.7 |
delinq_2yrs | integer | Number of 30-plus days past-due delinquencies in the borrower's credit file over the past two years. | 0 |
total_pymnt | number | Payments received to date against the total amount funded. | 13245.66 |
recoveries | number | Post charge-off gross recovery - the loss-given-default input. | 0 |
addr_state | string | U.S. state provided by the borrower in the loan application. | CA |
Additional fields on request | - | The remaining LoanStats columns - funded-amount detail and the rest of the payment and settlement block - plus the nine-field rejected-application sheet (amount requested, application date, risk score, DTI, three-digit zip, state, employment length, policy code) pin down when your sample is cut. | - |
What teams do with it
- Default-prediction benchmarks Train probability-of-default models against terminal loan_status labels across eleven origination years, and measure every challenger against the LC grade baseline built into the file.
- Loss-given-default and recovery modeling Payments received and post-charge-off recoveries settle each charged-off loan on the same row, so severity models need no outside servicing data.
- Vintage and cohort analysis issue_d slices the book into monthly vintages; grade, purpose, term and state cut each vintage thinner, and the outcome columns age in place on the same row.
- Reject inference and policy research The rejected-application book pairs amount requested, risk score, DTI and geography for roughly 2.76 million loans that never funded - the other side of the approval gate.
- Rate-setting forensics Interest rate against sub-grade quantifies, in basis points, exactly what one notch of assigned risk was worth at origination.
Questions buyers ask
What is the LendingClub Loan Data (Kaggle Mirror)?
A loan-level record of LendingClub's peer-to-peer personal lending: about 2.26 million accepted loans issued June 2007 through 2018 Q4 under the 151-field LoanStats schema, plus roughly 2.76 million rejected applications on a nine-field sheet, with repayment outcomes carried on every matured loan.
How far does lendingclub loan data kaggle mirror data cover?
Origination months from June 2007 through December 2018 - eleven full years of American unsecured personal lending. The accepted-loan book closes at 2018 Q4 and the snapshot is frozen there, which makes it a fixed laboratory for backtesting rather than a moving current-vintage feed.
What fields does the LoanStats schema include?
151 documented fields per accepted loan: requested amount, 36- or 60-month term, interest rate, installment, LC grade and sub-grade, employment length, home ownership, income and verification status, DTI, FICO range at origination, revolving utilization, delinquencies, purpose, state, and the payment, recovery and final-status outcomes.
Is this dataset suitable for default prediction?
It is the standard public benchmark for it. Every loan resolves to Fully Paid, Charged Off or Default, payments received and post-charge-off recoveries ride the same row, and the assigned grade supplies an expert baseline. Expect class imbalance toward fully paid loans - handle it deliberately rather than reading raw accuracy.
Are rejected applications included?
Yes, as a separate book of roughly 2.76 million declined applications carrying nine fields each: amount requested, application date, risk score, DTI, three-digit zip, state, employment length and policy code among them. No outcomes exist on that side, so it serves reject inference and policy research, never performance modeling.
Can Datadory cut the data to my cohort?
Yes. Name the slice - grades B through D, 2013-2016 issues, debt-consolidation purpose, charged-off status only - and the sample arrives as typed one-row-per-loan records with the field dictionary attached, as files, over the API, or landed directly in your warehouse.
Datasets that pair with this one
- Federal Reserve Survey of Consumer Finances (SCF) Household-level balance sheets and demographics - the surveyed counterpart to these originated loans.
- FFIEC HMDA Data Browser and Dataset Downloads Loan-level mortgage applications under federal reporting - the secured cousin of this unsecured book.
- CFPB Consumer Complaint Database Case-level friction after servicing begins - pair it with the origination attributes recorded here.
- Federal Reserve G.19 Consumer Credit The aggregate view of the same borrower - monthly totals where this file holds one row per loan.
- Kaggle The mirroring shelf this record sits on, and whatever else lives there.
See the rows before you pay anything.
Name this dataset and we send real records from it — scoped to the fields you asked for.