What is 2 browser trick?

[enharu]

I am confused about what this is when people say they use this to apply for many cards.

Is it to fill up 2 apps completely first, then click submit at same exact moment, so that each bank doesn't see inquiries from the other bank?

Will this work if I'm applying for 2 cards from same bank? I.E. Amex prg and bcp, or chase freedom and csp.

Has anyone done this and worked? Please tell me about your experience.

Thanks!

[Anonymous]

This doesn't work, and people keep recommending it because they don't understand how computer databases update.

If you hit the submit button on both simultenously, the requests for a credit pull will not hit the CRA at the EXACT same instant in time; one request will make it there first. The requests will be queued and processed one at a time. The database will record the inquiry, locking out the other request until it finishes doing so. Then the database will allow the next request to be processed. There is simply no way to have the two inqs recorded in such a way that the second request doesn't see it the first; computer processing speed is much faster than keystrokes or mouse clicks.

[shols44]

Here's a post from boarding area. 5 apps resulted in a single inquiry.http://boardingarea.com/blogs/rapidtravelchai/2012/12/12/barclays-credit-cards-101-and-how-many-can-... 

[Revelate]

Oh boy, well not to get too technically uber geeky, distributed and remote applications are still bound by the speed of light.

Guess I failed on that one.

Same lender: I would suspect lenders have anti-duplicate application code for a whole lot of good reasons (including legal ones); this may prevent in some instances either two inquiries being lodged, or possibly has some have reported an inquiry being dropped later (note, could be a reporting issue or split file too on this second one).

Different lenders: On the assumption the same bureau is pulled, typically the report will be serially accessed; however, there are some distributed applications using database replication technologies vis a vis Oracle Golden Gate, where in theory they could have the application hosted in multipe datacenters in an Active / Active configuration, and then simply replicate transactions back and forth, and that's not necessarily instanteous nor necessarily serial... it has some interesting application design issues I suspect that I'm wholly unfamiliar with, but it's possible there may be some latency in multiple database requests and they may not be processed in such the same way that the inquiry would be immediately seen everywhere else in the infrastructure.

So it's theoretically possible, but I've never seen CRA data architecture, and assuredly smarter minds than mine have been detailed to figure out ways to prevent this sort of thing from happening; in general, I suspect it's pretty hard to accomplish and really you're getting lucky if it works in your favor.  More trouble than it's worth I think, inquiries aren't that big of a deal in the model.

[enharu]

---

@Revelate wrote:

Oh boy, well not to get too technically uber geeky, distributed and remote applications are still bound by the speed of light.

Guess I failed on that one.

Same lender: I would suspect lenders have anti-duplicate application code for a whole lot of good reasons (including legal ones); this may prevent in some instances either two inquiries being lodged, or possibly has some have reported an inquiry being dropped later (note, could be a reporting issue or split file too on this second one).

Different lenders: On the assumption the same bureau is pulled, typically the report will be serially accessed; however, there are some distributed applications using database replication technologies vis a vis Oracle Golden Gate, where in theory they could have the application hosted in multipe datacenters in an Active / Active configuration, and then simply replicate transactions back and forth, and that's not necessarily instanteous nor necessarily serial... it has some interesting application design issues I suspect that I'm wholly unfamiliar with, but it's possible there may be some latency in multiple database requests and they may not be processed in such the same way that the inquiry would be immediately seen everywhere else in the infrastructure.

So it's theoretically possible, but I've never seen CRA data architecture, and assuredly smarter minds than mine have been detailed to figure out ways to prevent this sort of thing from happening; in general, I suspect it's pretty hard to accomplish and really you're getting lucky if it works in your favor.  More trouble than it's worth I think, inquiries aren't that big of a deal in the model.

---

i don't mind the number of inquiries on my report. i have less than 5 in total and after my current applications, i doubt i will be applying anything else for the next 1-2 years, unless some really great sign up bonus for a good card pops up.

what i'm worried about is this:

i will be applying for chase. after i am done with that, i plan to apply for amex bcp/rpg (1 of them). I am worried that amex might see that i have an inquiry just a few minutes ago, and they might decline me because of that  (such as system flagging me for being desperate for credit).

in general, is it bad to apply for another card after immediately? will that lower my chances drastically as well?

[Revelate]

---

@enharu wrote:

---

@Revelate wrote:

Oh boy, well not to get too technically uber geeky, distributed and remote applications are still bound by the speed of light.

Guess I failed on that one.

Same lender: I would suspect lenders have anti-duplicate application code for a whole lot of good reasons (including legal ones); this may prevent in some instances either two inquiries being lodged, or possibly has some have reported an inquiry being dropped later (note, could be a reporting issue or split file too on this second one).

Different lenders: On the assumption the same bureau is pulled, typically the report will be serially accessed; however, there are some distributed applications using database replication technologies vis a vis Oracle Golden Gate, where in theory they could have the application hosted in multipe datacenters in an Active / Active configuration, and then simply replicate transactions back and forth, and that's not necessarily instanteous nor necessarily serial... it has some interesting application design issues I suspect that I'm wholly unfamiliar with, but it's possible there may be some latency in multiple database requests and they may not be processed in such the same way that the inquiry would be immediately seen everywhere else in the infrastructure.

So it's theoretically possible, but I've never seen CRA data architecture, and assuredly smarter minds than mine have been detailed to figure out ways to prevent this sort of thing from happening; in general, I suspect it's pretty hard to accomplish and really you're getting lucky if it works in your favor.  More trouble than it's worth I think, inquiries aren't that big of a deal in the model.

---

i don't mind the number of inquiries on my report. i have less than 5 in total and after my current applications, i doubt i will be applying anything else for the next 1-2 years, unless some really great sign up bonus for a good card pops up.

what i'm worried about is this:

i will be applying for chase. after i am done with that, i plan to apply for amex bcp/rpg (1 of them). I am worried that amex might see that i have an inquiry just a few minutes ago, and they might decline me because of that  (such as system flagging me for being desperate for credit).

in general, is it bad to apply for another card after immediately? will that lower my chances drastically as well?

---

World of difference between two applications (Chase and Amex specifically) and 5 or 10 as in some sprees.

I wouldn't worry about it.  Numerous people including yours truly have been approved for Amex / Chase cards in close succession; to be clear, both Amex and Chase land on EX all the time for me, and Chase almost assuredly saw the HP from Amex in my case this last round.

[Open123]

---

@enharu wrote:

what i'm worried about is this:

i will be applying for chase. after i am done with that, i plan to apply for amex bcp/rpg (1 of them). I am worried that amex might see that i have an inquiry just a few minutes ago, and they might decline me because of that  (such as system flagging me for being desperate for credit).

in general, is it bad to apply for another card after immediately? will that lower my chances drastically as well?

---

No problems with this for Amex.

It's only an issue when it's 5 or 6 apps, and all at once.

[scenery_guy]

It's not two windows, it's two BROWSERS. Firefox and whatever else. But don't bother, you don't need to resort to tricks (and those loopholes are being closed quickly BTW). As I posted in another thread it's the order you app that matters. Always do the easiest for recon LAST and the hardest for recon FIRST. GIve it 5 -10 minutes between apps or hours. It does not matter. Everyone after first app will see the HP. 

[Open123]

Main purpose for this wasn't really to limit the inquiries, but to receive 2 of the Citi AA sign up bonuses.  When they were running the 100K AA bonuses, applying for one and then the other (Visa and Amex versions) would exclude you from the 2nd bonus.

However, applied simultaneously with 2 different browsers would result in two instant approvals with Citi computers coding both with the 100K bonus resulting in 200K AA miles.

Back then, worked like a charm!

[enharu]

ah i see. thanks a lot everyone!