Skip to main content

Database Methodology

How the credit bureau pull database is built, what its limitations are, and how we plan to improve it through community verification.

Published 2026-04-26 · Updated 2026-04-27 · Built by an experienced web professional

Why We Built This Database

The single most frustrating part of optimizing a credit card application strategy is not knowing which bureau a bank will pull. That information determines whether a strategic freeze will work, where your inquiries will concentrate, and how many reports you can keep clean for future applications.

The information exists, scattered across forum threads, data point logs, and cardholder agreements. We wanted one place to look it up. So we built this database.

The honest caveat: the data we launched with is a starting point. It reflects publicly known patterns, not a proprietary dataset we collected ourselves. That is what this page explains.

How Data Is Currently Sourced

The current 29 entries in the database were compiled from three types of public sources:

Community forums and data point threads

The credit card hobbyist community has spent years logging which bureau each bank pulled for specific cards and states. The most reliable aggregations live in:

  • r/CreditCards on Reddit, particularly the DataPoints megathread and wiki. Community members report their actual application results including which bureau was pulled and in which state.
  • FlyerTalk, specifically the Credit Card Comparison forum. This community skews toward travel rewards and has extensive issuer-specific threads with pull data going back years.
  • Doctor of Credit (doctorofcredit.com), which maintains issuer-specific pages with community-reported data points organized by card and state.

Cardholder agreements and issuer disclosures

Some issuers disclose their credit bureau preferences in application terms or cardholder agreements. These are not always specific to the card product and may not reflect current practice, but they provide a baseline.

What this means for accuracy

The patterns in this database represent what has been most commonly reported. They are not the result of our own application testing, and they have not been independently verified through a structured process. Treat every entry as a starting reference, not a guarantee.

How Verification Will Work

We are building a community submission system. The goal is to move every entry from "publicly reported pattern" to "verified by multiple independent data points."

The verification roadmap works like this:

  1. Submission: A cardholder submits a data point using our submission form. They report the issuer, card, bureau pulled, state, application date, and source of knowledge.
  2. Review: Each submission is manually reviewed for completeness and plausibility before being added to the verification queue.
  3. Corroboration threshold: An entry needs at least three independent matching data points before it moves from "reference only" to "community verified." Independent means different submitters, ideally from different time periods.
  4. Conflict flagging: If submissions conflict with existing entries (for example, a state that was previously reported as Experian now consistently shows TransUnion), the entry is flagged as disputed pending further data points.
  5. Date-stamping: Verified entries will carry a "last confirmed" date so you can see how recently the pattern was corroborated.

We have not reached that verification threshold for any entry yet. That is why every row currently shows "Reference only." We are being transparent about where we are in the process.

Known Limitations

State variance

Bureau pull behavior varies significantly by state for many issuers. Chase pulls Experian in most states but TransUnion in others. Citi splits between Experian and Equifax depending on your state. The database currently shows the most commonly reported pattern without state-level granularity. This is a limitation we intend to address as more state-specific data points come in.

Policy changes

Banks change their bureau preferences without announcement. A pattern that was accurate six months ago may not be accurate today. High-volume issuers like Chase and Citi are particularly prone to regional adjustments. Any data older than six months should be treated with extra skepticism, especially if your application outcome depends on it.

Soft vs. hard pull confusion

Community reports sometimes conflate soft pulls and hard pulls. American Express commonly does a soft pull for existing cardholders and a hard pull for new applicants. If a community member reports "Amex pulled Experian" without specifying whether they were an existing customer, the data point may not apply to your situation. We flag known soft/hard distinctions in the Notes column.

Product-level variation

Different cards from the same issuer can pull different bureaus. The database tracks pull patterns at the card level where possible, but some issuers show inconsistency even within a single product. Treat issuer-level generalizations as rough guides only.

Credit union and small bank gaps

The database currently covers 11 major issuers. Credit unions and regional banks are largely absent because community data is sparse. Navy Federal and PenFed are included as the largest credit unions, but hundreds of smaller institutions are not represented.

Why This Matters for Credit Card Applications

A hard inquiry typically costs 2 to 5 points on your credit score, and the inquiry remains on your report for two years. For most people applying for one card at a time, this is not a major concern.

For people who apply for multiple cards in a short window, which is a common strategy for earning sign-up bonuses, the bureau question becomes more important. Concentrating all your inquiries on a single bureau means the other two bureaus look completely clean. A bank that pulls only TransUnion will not see the four Experian inquiries you accumulated over the past three months.

A strategic bureau freeze makes this possible. You freeze the bureaus you want to keep clean, apply only with issuers that pull the unfrozen bureau, and unfreeze when you need to apply with a different issuer. Done carefully, this approach can let you apply for more cards with less total visible inquiry load.

Getting the freeze strategy wrong means a denial if the bank cannot pull the bureau it wants. That is why accuracy in this database matters, and why we are transparent about the current state of the data.

Public Sources Referenced

The following publicly available resources informed the initial database entries. These are the best places to check for current, state-specific data points before making application decisions:

Help Improve This Database

The most useful thing you can do after reading this page is submit your own data point. If you recently applied for a credit card and checked your credit report, you know exactly which bureau was pulled, which state you applied from, and which card it was for. That is a real data point.

Submissions are anonymous. No name or email required. We ask only for the issuer, card, bureau pulled, state, application month and year, and your source of knowledge.

Submit a data point →

This tool is for informational and educational purposes only. Credit card application rules, eligibility requirements, and approval odds change frequently and vary by individual circumstances. Always verify current rules directly with the card issuer before applying. We cannot guarantee approval or bonus eligibility. This is not financial advice.