Note that the algorithm used here is freely available across the web even
A valid credit card number has several fields and each of them has a meaning.
Anyone can make a website with a form and require you to insert valuable and sensitive information which requires you to give up your privacy.
You should use these numbers only to test your validation strategies and for bogus data.
Without a valid owner name, an expiration date and a valid CVV code, they can't be used for real transactions.
"Violating the PCI requirements can result in a substantial fine and the loss of your ability to accept credit card payments.
If the information gets into the wrong hands, you also risk losing your constituents' trust." Violating the PCI requirements can result in a substantial fine and the loss of your ability to accept credit card payments.
For instance, using a card imprinter (described below) will require that you document and enforce procedures for handling and subsequently destroying imprinter slips, whereas using a terminal or online payment method will require fewer security measures because your payment service provider will be handling the credit card information directly.
In the case of payment gateway integrations there is another drawback.
Fees are always incurred when processing an electronic payment.
Unfortunately, while helpful in demonstrating how an API works, it fails to demonstrate a real world implementation of the API or that sample code.
What the authors of those tutorials and sample code forget is that many people who are searching for pre-existing code and tutorials are doing so because they are not experienced enough in their programming language of choice to be able to implement the API on their own.