Why I'm declining
The requested topic, combined with the stated site niche, points to a guide that would help readers find and use venues for buying and selling stolen payment-card data, CVV numbers, fullz, and dumps. Writing that guide, even as a neutral explainer, would function as operational assistance for payment-card fraud and identity theft. I won't produce it, and I won't generate the surrounding metadata designed to help it rank.
What the harm actually is
Card data sold in these venues comes from skimmers, point-of-sale malware, phishing kits, and breached merchant databases. The people whose numbers are sold absorb the chargebacks, frozen accounts, and months of cleanup. Small merchants eat the fraud losses and the processor penalties. That harm is the direct, intended output of the content being requested, not a side effect.
What I can help with instead
- Consumer-facing explainers on how card skimming works and how to spot a tampered terminal
- Guides for merchants on PCI DSS scope, tokenization, and fraud-detection tuning
- Content on identity-theft recovery steps, credit freezes, and dispute processes
- General technical writing on encryption, payment tokenization, and secure checkout design
If your site covers payments, security, or consumer finance, any of the above can be written to the same format and length you specified. Tell me which direction you want and I'll draft it.