β„π•†π•Ž 𝕋𝕆 𝔼𝕍𝔸𝔻𝔼 β„π•†π•ƒπ”»π•Š & β„‚β„π”Έβ„π”Ύπ”Όπ”Ήπ”Έβ„‚π•‚π•Š

mrdean

0
Rep
3
Likes
Junior Carder
Posts
11
Threads
1
Joined
Jan 2022
Sign Up or Login to view this post and enjoy everything our site has to offer!
I can boldly claim that no seasoned carder worth their stuff can claim they've never had to endure the pain of a charge back at any point in their fraud path. This' so since chargebacks are the last line of defence antifraud systems have after we successfully manage to evade just about all flags and filter to protect the victim from us. We all want to ensure that breads lands home, especially following a smooth god-mode hit. So let's dive into it...

First thing you need to remember is that avoiding a charge back involves reducing bank - victim successful coordination within the time frame from the bread being dispatched and it landing safely into your hands. From my experience, if you can cause enough controlled chaos between the parties within this window, you're golden

Type of bread
If you've double in carding both goods (physical items) and direct $$ transfers, you've probably noticed how sensitive money transfers are compared to physical goods. That's because for physical goods, liability is distributed among three parties (shop/merchant , bank & card owner), whereas in the direct transfers, the primary focus is between the bank and card owner. Since the bank bears nearly all the losses in the later, they're extra keen to trap fraud-risks & exalt high chargeback flags. So if you'll want to mess around with ecommerce websites for physical goods, as opposed to direct $$ transfers. as a sure way to reduce chargeback chances.

Understand the target payment gateway
Every payment gateway (Stripe/Payoneer/Shopify/Paypal etc etc) has its own unique features & implementation for antifraud and therefore creating a chargeback handling spectrum. The more sensitive a gateway, the more robust their chargeback triggers. You'll want to research for such things as sensitive bins, 3D vs 2D transfer window, chargeback penalties (policies & fees). If you can narrow all these details down, you'll be able to combine some of the tacts below to manage the chaos we talked about. For example, Stripe is less alert towards fully verified accs, 6months+ old & having made undisputed transactions before.

withdrawing/transfering from drop
Regardless of the gateway, 1 red flag that cuts across is rushing to move $ from one acc to another immediately after the drop. For example, if you were to send an amount from an account to another on the same service, say Paypal, & immediately hop on to the recipient account to withdraw, trust you me, if there's was any other suspicious flag or filter you might have navigated around before, you'll def land into a situation of a hold or chargeback on the spot. However, note that fast withdrawal is only a flag if the sending & receiving service are the same or are directly affiliated in a way that incorporates fraud inter management. For example, playing stupid around Xoom & Paypal is a no no. Bt if you were doing international wire transfers, this wouldn't count. As a rule of the thumb, let the bread sit for a while, pref 1hr+ before touching it

Use solid drop with history
Another sure way to avoid a hold or follow up chargeback is ensuring to use a solid drop account. By this, I mean, ensure it's fully verified, all misc profile details provided and with some transactions having been done on it at least 2 weeks before the drop. Additionally, the account being aged is a power move. These variables vary from service to service, so like I mentioned, you'll need to do some personal recon of your particular service to understand exactly how to play around this.

Spoofing the bank
This one on its own can decrease chargeback risk by 70%, trust me. It's as simple utilizing your victim's fullz and background profile data as an arsenal to call their card issuer before the transaction and indicating that you'll be making a particular transaction. You can come up with a variety of bluff reasons for calling, then proceed to mention the expected transaction as a by the way. For example, you might call asking that they send you your monthly statement, or enquire about your standing credit score etc etc, be creative...then finalize by preparing them for the transaction. So then the bank won't be that keen into the transaction, and if the actual cc owner calls to enquire about the charge, the chaos from an already previously greenlighted transaction should buy you some time to get you by the charge back window.

Transaction amount
Yet another point of consideration to pay attention to is the transaction amount. You should keep in mind that banks will readily ignore fraud risk for =< $200 transaction's whilst being super vigilant on $10k transactions. That implies higher chances of chargebacks for higher amounts. To circumnavigate this, you could consider the alternative approach: instead making multiple small amounts transactions, separated by decent time intervals. Additionally, avoid common sense traps like giving an unplausible reason, relative to the transaction amount. for example; don't claim to be making a 'Family & Friends Gift' worth $10k, thats just asking for trouble. Common sense!

Like any other scheme in the fraud game, bleaching solves 99% of the problems. Once done with the transaction, delete any accounts, emails, transaction records, misc info etc that you can - that the victim can use to follow up on the transaction in an attempt to request for a chargeback/hold. The less data they have to go by, the less they can prove to their banks that they didnt make the transaction themselves.


Ok guys, that's long enough a post for today. Will be making more occasionally. As I sign out, I'm open to mingle with any season carders in the house & for the noobs in here, dont shy away, hit me up for any assistance/guidance that I may be able to offer. cheers!!