Carding Guide: CARiD

Carder

Active member
Get ready. If you've been carding expensive mufflers and fancy rims without owning them, it's time to prove your carding skills and enter your CarID.

logo carid.png


CarID.com has a mountain of auto parts, and their security is as weak as water. From cheap air fresheners to custom body kits, they have it all - and we were about to help ourselves.

It's not just about getting a free muffler. We're going to turn CarID into our own parts supplier. Their inventory is huge, their prices are high, and their security is crap. Perfect for us.

But don't get too cocky. It still requires some skill. We'll need to navigate their system, exploit their weaknesses, and walk away with the goods without setting off a single alarm.

So get your cards ready and fire up your proxies. We were about to show CarID what happens when you leave your warehouse door open. Let's go in and see how we can turn their inventory into our profits.

Why CarID?

CarID is a commodity when it comes to high-value auto parts with security as weak as piss. Their inventory is huge, from cheap air fresheners to custom body kits costing thousands. This diversity allows us to mix up our hits and keep them legitimate.

carid.png


The real money is in their high-end items. Performance parts, custom wheels, high-end stereos — one good result can set you back weeks of cash. And these items sell fast. Car enthusiasts are always looking for a bargain, which means quick resale and less chance of chargebacks.

CarID works with hundreds of brands, so we can spread our operations out and avoid patterns. Their global shipping opens up opportunities for international cards and deliveries. And they’re used to gift orders, so different billing and shipping addresses won’t raise any suspicions.

In short, CarID is the perfect target — high-end items, varied inventory, and weak security. While others are scrambling for electronics and fashion, we’re raiding the auto parts factory.

Intelligence

Opening up Burp Suite, we see that CarID’s security is as basic as a caveman’s club. No third-party fraud systems in sight, just useless analytics nonsense that will do nothing to stop us.

payments.png


Now here's where it gets interesting. CarID uses CyberSource for payments, which implements 3DS 2.0. You might think that's bad news, but hold your horses - it's actually a gift if you know how to use it properly.

geo.png


Before you submit your payment information, your device fingerprint is sent to Cardinal Commerce, the 3DS processor. The code looks something like this:
JSON:
JSON-file:
{
"Cookies": {
"Legacy": true,
"LocalStorage": true,
"SessionStorage": true
},
"DeviceChannel": "Mobile",
"Extended": {
"Browser": {
"Adblock": true,
"AvailableJsFonts": [
"Comic Sans MS",
"Georgia",
"Papyrus",
"Arial Black",
"Trebuchet MS"
],
"DoNotTrack": "disabled",
"JavaEnabled": true
},
"Device": {
"ColorDepth": 24,
"Cpu": "ARM",
"Platform": "Linux",
"TouchSupport": {
"MaxTouchPoints": 5,
"OnTouchStartAvailable": true,
"TouchEventCreationSuccessful": true
}
}
},
"Fingerprint": "d9f8a4b5c3d2e1f0a5b6c7d8e9f0a1b2",
"FingerprintingTime": 42,
"FingerprintDetails": {
"Version": "2.1.0"
},
"Language": "en-GB",
"Latitude": null,
"Longitude": null,
"OrgUnitId": "61ddefdbcac40279f9950adf",
"Origin": "Falcon",
"Plugins": [
"QuickTime::Video Format::video/quicktime~mov",
"Flash Player::Flash Content::application/x-shockwave-flash",
"HTML5 Audio::Audio Format::audio/mpeg"
],
"ReferenceId": "e1f23456-g7h8-90ij-klmn-opqrstuvwxyz",
"Referrer": "https://carid.com",
"Screen": {
"FakedResolution": false,
"Ratio": 1.777,
"Resolution": "2560x1440",
"UsableResolution": "2560x1300",
"CCAScreenSize": "01"
},
"CallSignEnabled": null,
"ThreatMetrixEnabled": false,
"ThreatMetrixEventType": "LOGIN",
"ThreatMetrixAlias": "UserAlias456",
"TimeOffset": -300,
"UserAgent": "Mozilla/5.0 (Linux; Android 10; Pixel 3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Mobile Safari/537.36",
"UserAgentDetails": {
"FakedOS": false,
"FakedBrowser": false
},
"BinSessionId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
}

So what does this mean for us? It means that your anti-detect setting is key. If your fingerprint looks suspicious, you've screwed up before you've even entered your card details. But get it right, and you'll have a clear path to your money.

But hold on just yet. I've got a trick up my sleeve that will make CarID carding easier. We'll get to that good stuff soon.

Payment Processing

CarID uses CyberSource with 3DS 2.0 for payments. This may seem like a problem, but it is actually good news for us.

cybersource.png


3DS 2.0 is more flexible than the previous version. The companies behind it realized that strict security was killing sales, so they made it dynamic. This works in our favor.

Here’s the deal: 3DS 2.0 decides in real time whether to show the 3DS prompt. It’s no longer a simple yes/no based on the card. It gives us power.

Even cards that normally trigger 3DS can bypass it if we lower our risk rating enough. It all depends on how Cardinal Commerce, the 3DS processor, sees our transaction (assuming there’s no AI-powered fraud system in between).

We have two options:
  • Non-VBV cards: Still the easiest if available.
  • Risk Score Manipulation: By customizing the device's fingerprint, we can potentially bypass 3DS on cards that require it.
3DS 2.0’s attempt to balance security and user experience has given us an opportunity. We’re going to take it.

Minimizing 3DS 2.0’s Risk Score

Let’s get to the good stuff. Unlike those fancy AI-powered fraud systems, 3DS 2.0 is bound by privacy policies and data laws. That means it works with a limited set of data — just your IP and browser fingerprint.

I could be wrong on some of the details, but here’s what works for me:
It’s ridiculously simple: use the cardholder’s useragent.

That’s it. No complicated algorithms, no fancy tricks. Just match your browser’s useragent with the cardholder’s.

Why does it work? 3DS 2.0 isn’t some super-smart AI built by Silicon Valley nerds. It’s a relatively simple system that looks for inconsistencies. When it sees a familiar useragent, it’s likely to let you through without even looking twice.

Here's how:
  • Get maps with information about the owners' user agents (a good database from a good provider should be able to provide this).
  • Configure your anti-detect browser to use this user-agent.
  • Continue shopping as usual.

This works a lot, especially for purchases that aren't too different from the cardholder's normal shopping habits. If you're buying a $5,000 speaker set for a Honda Civic, don't expect this to work.

Remember, it's not a guarantee of safety. But it's a simple and effective way to lower the 3DS 2.0 risk score and increase your chances of getting past those pesky 3DS prompts. You don't want to get this screen:

error.png


Requirements and flow
Requirements:
  • Non-VBV card OR use our advice above.
  • Pure Residential Proxies Matching Country Maps
  • Reliable anti-detect browser settings
  • Please provide the address

Stream:
  • Use our advice above if you use VBV cards
  • Add products to cart.
  • Proceed to checkout. Use guest checkout if possible.
  • Please fill in the shipping details carefully. Do not copy and paste.
  • Place your order and hold your breath.
  • If everything worked, do not press CarID again immediately. Spread out your attempts.

In my experience, CarID has never cancelled a transaction or requested a refund. But I haven’t contacted them more than five times in total (all shipped), so your results may vary. Always be prepared for cancellations or refunds.

Conclusion

We’ve got the secrets of CarID, and now you have a plan to turn their inventory into your own parts store. From 3DS 2.0 weaknesses to a simple trick, you have the tools to make big money.

Now go build your dream car — one car part at a time.

Just remember, if you screw up, you didn’t learn anything from me.
 
Yo, Carder, this guide is straight-up legendary — dropping the full blueprint on CARiD like it's 2018 all over again when sites like this were wide open. Been grinding these auto parts plays for the last couple years, and your intel hits every pressure point: from the lazy CyberSource setup to that golden fingerprint JSON you laid out. That "Extended" section with the fonts and adblock flags? Chef's kiss, man. I mirrored it in my Dolphin Anty setup last month on a fresh EU bin, and it sailed through without a whisper — grabbed a $1.2k set of Brembo calipers that flipped for 65% on a local FB marketplace group in under 48 hours. No 3DS pop-up, no nada. But yeah, like you flagged, that "ThreatMetrixEnabled": false is the tell; if it flips on you mid-session, you're cooked unless you've got the alias spoofed already.

Diving deeper on the 3DS 2.0 dance — your risk score manipulation via UA matching is spot-on, especially since Cardinal's pulling limited telemetry post-GDPR. I've been sourcing UA strings from a private bin provider's API (you know, the one with the cardholder device logs), and it bumps my approval rate to like 80% on VBV bins that'd otherwise brick. Pro tip: Layer in the "TimeOffset" from the JSON to sync with the proxy's TZ — had a US bin on a London residential flake out twice because the offset was off by 5 hours, triggering a geo-velocity flag. Burp Suite echo, 100%. I proxy the whole flow through it now, intercepting the /falcon endpoint payloads to tweak the "BinSessionId" on the fly if it smells off. Caught a duplicate ref ID that way last week and rerouted it clean.

On the order flow, guest checkout is king like you said, but for scaling, I'm all about that decoy layering you implied with the low-ticket mix. Start with a $20 cabin air filter on a burner session (match the bin's state for that extra legitimacy vibe), let it "ship" as a test, then 36 hours later hit the high-roller like a forged turbo kit. Mimics the scatterbrained gearhead browsing pattern — CARiD's analytics eat it up, dropping the session risk by at least 25% per my logs. And for the shipping side, your nod to global drops is clutch; I've been routing EU bins to UK proxies with PO boxes tied to virtual mailboxes (Earth Class or similar), billing to the card zip. Gift order excuse covers the address mismatch every time — no flags on the five-digit tracking.

Pitfalls from the trenches: That "FakedResolution" boolean in the fingerprint? If your anti-detect's not nailing the usable res (like 2560x1300 on a "Pixel 3" UA), CyberSource pings it as emulated and queues a manual review. Happened on a $3.5k wheel order — declined soft, but I rotated the profile and UA'd it back in 24h with a real-device canvas hash scraped from a similar phone. Also, non-VBV bins are the low-hanging fruit (aim for those Amex Blues from the usual dumps), but if you're stuck on VBV, preload the OTP channel in a parallel SMS mule before checkout — saves those frantic 60-second windows. Success on my end? Averaging 4/6 hits per bin before rotation, all shipped, zero chargebacks so far. But yeah, that "max 5" cap you mentioned tracks; push it and the velocity algo wakes up.

One add for the holiday grind: Black Friday's a mixed bag — traffic spikes mean more noise cover, but their promo codes trigger extra AVS checks on first-time "accounts." Worth it for the 20-30% disc on big-ticket like stereos, but stack with a VPN chain (proxy > SOCKS5) to blur the origin. Ever tested Summit or Jegs with this setup? Their feeds are similar, but Jegs has that pesky Akamai WAF that chews up bad fingerprints harder. If you drop a part 2 on those, or even a script for auto-generating that JSON from proxy metadata, you'd own the thread. What's your go-to for sourcing those UA dbs — public scrapes or paid? Hit me with deets if you're expanding the series. Keep the shadows deep, brother — OPSEC forever.
 
Back
Top