No credit card required
Browse credit cards from a variety of issuers to see if there's a better card for you.
When would the creditor use either and which is more accurate?
Both are as "accurate" as the credit report, but I don't know of any creditors that actually use Vantage, despite their claims to the contrary.
They are as different as the dozens of various FICO scoring models, weighing certain items higher than others. For instance, FICO considers Authorized User accounts, Vantage 3.0 does not. There's others, that's just one example.
From what I've read the most common place to see VS 3.0 used is with things like utility companies, cell phone providers, landlords, etc. Almost all creditors out there use the FICO models from what I've seen.
yep, same here.
@Anonymous wrote:Both are as "accurate" as the credit report, but I don't know of any creditors that actually use Vantage, despite their claims to the contrary.
They are as different as the dozens of various FICO scoring models, weighing certain items higher than others. For instance, FICO considers Authorized User accounts, Vantage 3.0 does not. There's others, that's just one example.
VantageScore 3.0 does consider AU accounts - but only positive activity. Fico 8 may or may not consider AU accounts (my AU account is NOT factored in). Two of the three CRAs factor in negative AU account information, the CRA does not. Can't recall which one does not from memory.
It must be included in 3.0 then beause everything I'm finding says they don't factor AU at all and never have, but those sources are a few years old.
@Anonymous wrote:It must be included in 3.0 then beause everything I'm finding says they don't factor AU at all and never have, but those sources are a few years old.
Probably, they had the benefit of hindsight seeing the uproar from millions of angry spouses that suddenly lost all access to credit in FICO 8 because they were just AU's on their SO's card.
FICO backtracked on that in a hurry and implemented their anti-abuse algorithm so AU's may or may not be counted; VS 3 was released after that, it'd foolish of them not to learn from the prior issue so I assume that it was indeed put into VS 3.