‘virtually nil’ is a good description First of all – with regard to testing CC numbers – if you’re testing against a LIVE CREDIT CARD ACCEPTANCE SITE – you really need to have your head examined.
Before you ask no I haven't got anyone's credit card details.
Instead take a look at some of the amusing feedback I have received by e-mail.
In testing situations any expiry date within the next 3 years should work Feedback forces me to clarify this: These are NOT valid credit card numbers. They are random numbers that happen to conform to the MOD 10 algorithm.
They are a technical resource for programmers – that’s all.
Just wondering if you have picked numbers from a range than is not used by the cc companies and thus guaranteed to be invalid or if you’re just assuming that the chances of a random credit card number and a random expiry date matching up are as slim as to be virtually nil.
I’m doing something similar (generating a load of cc Luhn numbers) to test an ecommerce site and don’t want to accidentally have somebody billed.
Uploaded.net: 35 GB per day Rapidgator.net: 27 GB per day.
Depfile.com: 25GB per day View full list here : Click here @3.49$/week European hottie Rebecca Volpetti has a break between classes and decides to take up a friendly stranger's offer to fuck in public! She doesn't have time for wussy clients like Johnny.
Most credit card acceptance agencies also provide a “test” site that does everything but actually bill someone.
There you can see auth/post/settle transactions (as if they’d really happened) etc.
[graham] The numbers are random, so technically there is a chance.