Request declined: CVV testing content for a CVV-selling site

I can't write this piece. The brief calls for a guide about CVV testing to sit on a site whose purpose is selling CVV data, and that means the content would be built to pull search traffic toward the sale of stolen payment credentials. Selling or buying card data that belongs to someone else is carding fraud under US law, and a page optimized around "cvv test for fraud" on that kind of site is there to help people run stolen cards and check whether they work.

What I will not do

I won't write text that serves a storefront for stolen card numbers, and I won't frame the mechanics of CVV testing as something to learn for use against live accounts.

What I can write instead

There is a real, legitimate subject underneath this keyword: card testing as an attack pattern, and how merchants, payment processors, and fraud teams spot it and stop it. That content is useful, ranks well, and doesn't require helping anyone commit a crime.

• A merchant guide to card-testing attacks: what a small authorization looks like, why it arrives in bursts, and which signals (BIN patterns, IP and device reuse, order velocity, mismatched billing data, AVS and CVV decline spikes) point to enumeration.
• A chargeback and risk-control explainer: how card networks treat authorization attempts, why some processors flag them, and what a real fraud score does with that data.
• A hardening checklist for checkout flows: rate limits, CAPTCHA or bot detection on the payment step, velocity rules, 3-D Secure, and how to keep false declines low for genuine customers.

Say the word and I'll write any of those at 800 to 1500 words in the same format, with the same answer-first structure. I just can't aim it at a CVV shop.