Contact

CC Generator is run by a small independent team, and we read everything that comes in. There is no contact form here — the site is fully static, with no server to receive one — so email is the way to reach us. Pick the address that matches your subject and you will get to the right person faster.

Most messages get a reply within 2–3 business days. Privacy requests and abuse reports have their own timelines, listed at the bottom of this page.

Where to write

Before you write

Some questions arrive often enough that the answer is already on the site, usually in more detail than an email reply would give:

• “Why don’t the generated cards work for payments?” — because there is no issuing bank behind them, so no one can authorise a transaction. The FAQ has the short answer and the Disclaimer walks through the full authorisation path.
• “How do I get a real virtual card?” — from a bank or a licensed provider that is authorised to issue them, not from a generator. We cannot help with that.
• “Is this legal?” — yes, for testing. Our Terms of Service set out exactly what is and is not permitted, and the Disclaimer explains where the line sits.
• “Do you store what I generate?” — no. Generation runs entirely in your browser and nothing is transmitted to us. The Privacy Policy explains how to verify that yourself in your browser’s developer tools.
• “Can you add support for a specific card network?” — quite possibly. Write to the bugs address above and tell us which network and which IIN/BIN ranges and lengths it uses. A link to the network’s published specification helps a lot.

Reporting a technical error

If the generator misbehaves, a useful bug report saves a round trip. Please include:

• Browser and version (for example, Firefox 141 or Safari 18.2)
• Operating system and whether you are on desktop or mobile
• Which page you were on, and the URL
• Which settings were selected — card network, single or bulk mode, quantity
• What you expected to happen, and what actually happened
• Any console errors — open developer tools, look at the Console tab, and paste anything red

A screenshot is welcome. If the problem involves specific generated output, paste it: it is synthetic test data, so there is nothing sensitive about sharing it.

Send bug reports to the bugs address in the table above.

Reporting misuse

If you have found this site referenced in a fraud attempt, a phishing campaign, or any other misuse, tell us at . We take these reports seriously and will cooperate with legitimate law enforcement requests.

Include a URL, a screenshot, or a copy of the message if you can. We investigate every report, block access where we are able to, and respond to lawful requests from payment networks and law enforcement. This tool was built for engineers, and we would rather hear about misuse than not.

Corrections and factual accuracy

Payment standards change, and we get things wrong sometimes. If you spot an error in a guide, a BIN range, or a technical explanation, tell us at the editorial address — and please include a source if you have one, such as an ISO standard, an EMVCo or PCI SSC publication, or a card network’s own documentation.

We check reported errors against primary sources, correct what needs correcting, and note substantive changes on the page with the date. Our editorial policy describes how content is written, reviewed, and updated.

Legal and takedown

For copyright, trademark, or other legal notices, write to the legal address and include:

• Your name and the organisation you represent, if any
• The exact URL of the page or material at issue
• What right you hold and the basis for the claim
• Contact details we can reply to
• A statement that you believe in good faith the use is not authorised

Complete notices get a substantive reply. We would usually rather fix a problem than argue about it, so tell us what outcome you are looking for.

Response times

We reply to every legitimate message. If a week has gone by with no answer, it is worth checking your spam folder and then writing again — occasionally a reply does not get through.