No credit card required
Browse credit cards from a variety of issuers to see if there's a better card for you.
@Anonymous wrote:
But it will be difficult to get these data-code numbers from a lot of people unless it's made easier through some web-script/program.
Damnit Jim Cassie, I'm a doctor sysadmin, not a programmer...
Fine, fine. Use this:
factorlist = document.getElementById("factor_ph"); //factor_ph div has the reason codes factors = factorlist.childNodes; for (let i = 0; i < factors.length; i++) { reasoncode = factors[i].getAttribute("data-code"); //extract numeric reason code from data-code tag dive = factors[i].childNodes; // yes, this is messy, dive = dive[0].childNodes; // and layout-dependent, dive = dive[0].childNodes; // but the RIGHT WAY is more typing... dive[1].textContent="Code: " + reasoncode + " - " + dive[1].textContent; // prepend real reason code # to friendly text }
Drop that into a javascript console (or use greasemonkey, etc...) while on a Reports->Scores page on myfico.com, and you'll get this:
If we wanted to get really fancy, we could load a list of the "real" text codes, and swap those in, too...
@iv wrote:
@Anonymous wrote:
But it will be difficult to get these data-code numbers from a lot of people unless it's made easier through some web-script/program.Damnit
JimCassie, I'm adoctorsysadmin, not a programmer...
Fine, fine. Use this:
factorlist = document.getElementById("factor_ph"); //factor_ph div has the reason codes factors = factorlist.childNodes; for (let i = 0; i < factors.length; i++) { reasoncode = factors[i].getAttribute("data-code"); //extract numeric reason code from data-code tag dive = factors[i].childNodes; // yes, this is messy, dive = dive[0].childNodes; // and layout-dependent, dive = dive[0].childNodes; // but the RIGHT WAY is more typing... dive[1].textContent="Code: " + reasoncode + " - " + dive[1].textContent; // prepend real reason code # to friendly text }
Drop that into a javascript console (or use greasemonkey, etc...) while on a Reports->Scores page on myfico.com, and you'll get this:
If we wanted to get really fancy, we could load a list of the "real" text codes, and swap those in, too...
I just did it a while ago in C++/XAML for Win10 just so I can store all this stuff in local SQLite. I got a lot of codes here already, but I also have a lot of dupes. I don't have a lot of variety on my credit file so I keep seeing the same old reasons. It's a nice start to the FICO 9 tables though.
You know, I could easily write a Firefox extension too now that you wrote that and gave me the idea. While not a universal solution, this may provide us with enough users to really fill in the missing details on those Industry + 9s.
@Anonymous wrote:
@iv wrote:
If we wanted to get really fancy, we could load a list of the "real" text codes, and swap those in, too...
Oh another thing I should mention is that @Curious_George2 recently found a huge discrepancy between the order of score factors on the Reports tab vs the Scores tab on myFICO. The Scores tab is the only place with the correct order.
That multiset union thing they did there messed up the order on TU/EX. It really makes no difference as far as getting these codes, which is the important thing, just thought I'd make sure everyone knew not to use that TU/EX ordering on the Reports tab.
@Anonymous wrote:
@iv wrote:
@Anonymous wrote:
But it will be difficult to get these data-code numbers from a lot of people unless it's made easier through some web-script/program.Damnit
JimCassie, I'm adoctorsysadmin, not a programmer...
Fine, fine. Use this:
factorlist = document.getElementById("factor_ph"); //factor_ph div has the reason codes factors = factorlist.childNodes; for (let i = 0; i < factors.length; i++) { reasoncode = factors[i].getAttribute("data-code"); //extract numeric reason code from data-code tag dive = factors[i].childNodes; // yes, this is messy, dive = dive[0].childNodes; // and layout-dependent, dive = dive[0].childNodes; // but the RIGHT WAY is more typing... dive[1].textContent="Code: " + reasoncode + " - " + dive[1].textContent; // prepend real reason code # to friendly text }
Drop that into a javascript console (or use greasemonkey, etc...) while on a Reports->Scores page on myfico.com, and you'll get this:
If we wanted to get really fancy, we could load a list of the "real" text codes, and swap those in, too...
I just did it a while ago in C++/XAML for Win10 just so I can store all this stuff in local SQLite. I got a lot of codes here already, but I also have a lot of dupes. I don't have a lot of variety on my credit file so I keep seeing the same old reasons. It's a nice start to the FICO 9 tables though.
You know, I could easily write a Firefox extension too now that you wrote that and gave me the idea. While not a universal solution, this may provide us with enough users to really fill in the missing details on those Industry + 9s.
@Anonymous do the firefox extension that would be awesome! Plenty of users use Firefox or are maybe willing to use it to get the codes for us!
@Anonymous wrote:I just did it a while ago in C++/XAML for Win10 just so I can store all this stuff in local SQLite. I got a lot of codes here already, but I also have a lot of dupes. I don't have a lot of variety on my credit file so I keep seeing the same old reasons. It's a nice start to the FICO 9 tables though.
Yeah, I don't have all that much variation either, and with MyFICO hiding the reason codes when within 50 points of max (and sadly, not visually... the elements aren't in the page at all), I'm pretty limited on the data I can source directly.
On the other hand, I've got 5 years of saved reports here... so there might be some useful data to be found.
But I'm pretty sure that all we'll find is that all versions of Classic still use the same codes, and all versions of the Industry options use the same superset as listed in the FICO doc...
@Anonymous wrote:You know, I could easily write a Firefox extension too now that you wrote that and gave me the idea. While not a universal solution, this may provide us with enough users to really fill in the missing details on those Industry + 9s.
Yeah, it's really an easy drop-in of that code to make an extension for Firefox, Chrome, or even Safari...
(And for that matter, "open the javascript console and paste this in" is a fairly straight-forward set of directions, even without a friendly "click here" button on the toolbar for it...)
@iv wrote:
@Anonymous wrote:I just did it a while ago in C++/XAML for Win10 just so I can store all this stuff in local SQLite. I got a lot of codes here already, but I also have a lot of dupes. I don't have a lot of variety on my credit file so I keep seeing the same old reasons. It's a nice start to the FICO 9 tables though.
Yeah, I don't have all that much variation either, and with MyFICO hiding the reason codes when within 50 points of max (and sadly, not visually... the elements aren't in the page at all), I'm pretty limited on the data I can source directly.
On the other hand, I've got 5 years of saved reports here... so there might be some useful data to be found.
But I'm pretty sure that all we'll find is that all versions of Classic still use the same codes, and all versions of the Industry options use the same superset as listed in the FICO doc...
@Anonymous wrote:You know, I could easily write a Firefox extension too now that you wrote that and gave me the idea. While not a universal solution, this may provide us with enough users to really fill in the missing details on those Industry + 9s.
Yeah, it's really an easy drop-in of that code to make an extension for Firefox, Chrome, or even Safari...
(And for that matter, "open the javascript console and paste this in" is a fairly straight-forward set of directions, even without a friendly "click here" button on the toolbar for it...)
I just scanned the 3B PDF raw and the codes aren't in it behind the scenes, so that's a no-go. I was trying for a drag-and-drop solution on the downloadable PDFs. Hey, I thought I might get lucky. lol Not like anyone else ever looked back there.
I think the whatever-Monkey idea is the way to go now. I like to make things as easy as possible for as large a group as possible, but I think you're right and we'll be fine with a smaller group of more technically inclined users.
There's a x-Monkey for every browser out there and that certainly makes things a lot easier for an average user.
Hello Community!
I would just like to take a moment to thank everyone for their support throughout the General Scoring Primer's first year. Yes, it has been a year, can you believe it?
Happy one year anniversary General Scoring Primer!
The Primer developed from almost nothing to the best resource on the Internet as far as FICO scoring is concerned, in the opinion of many.
A special thanks to @Anonymous for all of her assistance, without which this Primer would not have been possible.
A special thank you to each and every member who has contributed datapoints!
Also very grateful to the Giants from which I've learned so much: @RobertEG @Revelate @Thomas_Thumb
Thanks to the moderators for putting up with us! and to MF for hosting us!
Small dp....
An acct was accidentally reported w a balance under $15. Brought reporting accts to 4 out of 13.
@cr101 wrote:Small dp....
An acct was accidentally reported w a balance under $15. Brought reporting accts to 4 out of 13.
- According to EX's 3-bureau report, the only score that changed was TU. Score dropped 3 points.
- EX is my only clean report. EQ and TU still have a string of late payments from over 5 years ago. EQ doesn't include these in the 'accts ever late' section, though.
- I have an acct reporting at 40%ish util.
- Overall util at 13%.
@cr101 thank you for the data points, does the 13 accounts include closed accounts? Please give total number of open accounts and total number including closed accounts. (We haven't determined whether all algorithms include closed accounts.) TIA!
@Anonymous wrote:
@Duke_Nukem wrote:
@Anonymous wrote:@Revelate OK thank you! AWB is there for dirty cards. And if you don't think new accounts could be in fifth place, then SO must be in a dirty card @Slabenstein. The lack of the new account reason code & having a new account under 18 months is going to demonstrate SO is still in a dirty card, I believe.
@Revelate I would expect AZEO to optimize even if it wasn't because of AWB, because it also optimizes balance, Utilization, ect... btw, thank you! We are trying to figure out at what point do profiles stop returning to clean cards at 2 years on mortgage scores. We believe a 60 day late does, apparently a 120 does not.
So now we need to find out when and if 90 and 120s go back to a clean cards on the mortgage Scores.
Not sure if AWB is there for EX2 on dirty scorecards or not. My scorecard doesn't have many accounts with balances at this time, but my DW's report is nearly full (cycled sockdrawered cards recently and let them report a balance). She has 9 of 11 CC's reporting a balance, most under $10 but I did allow a few larger balances report this month. 1 auto loan with a balance, no other loans. She has a BK7 from 2012 still reporting, no collections or other derogs. Below is her EX2 from today.
Her EX2 had been rock solid for many, many months @ 709 up until her last INQ aged to 1 yr last month, which boosted her score to the present 715 and hasn't budged since. That's after going from 3 accounts with balances reporting last month to the current 10 (9 CC's + 1 auto loan).
@Duke_Nukem we're pretty sure AWB is on dirty cards now. Did you happen to notice when DW went from recent to mature PR card by chance?
Sorry for the late reply, @Anonymous . Been absent from MF for a bit. I would imagine she has been on a mature PR card for a while now, as the BK7 is at 9 years now. No other baddies reporting.