Contributions

Automatically mask credit card numbers as they are logged into the database.
*This Contrib only requires the modification of two files.
*Installation Time: 5-10 min.
*No changes to Database configuration.
*Includes screen shots, v1.1 & v1.2
Example: xxxxxxxxx1234

If you're using a payment gateway like Authorize.net, the gateway stores credit card numbers and has all the liability.
There is no point in keeping a copy in your database...unless you like to live dangerously.

What it does:
1. Button below credit card number.
2. Click > Masks all but last 4 digits of CC# in DB.
3. Email sent to store owner with masked numbers.

This Contrib only requires the modification of two files.
It places a button under the credit card information of an order.
Once the button is clicked, the all but the last four digits of the credit card number will be masked in the database.
The numbers that are masked are sent to the store owner via email.

1. Moved CC# Mask function out of Order Update function and created new function.
2. Added Mail process to send masked numbers to store owner.
3. Added email text & message stack to language file to explain the process.

Installation Time: 5-10 min.
No changes to Database.

Check box was not working correctly, added tep_draw_form so that it would post correctly.

I took two other contributions and combined the ideas from both. This contribution allows you to mask the credit card number from within the order screen. It will then save the masked cc number in the database. This is for those store owners that want to minimize security risks. Keep in mind that this contribution does over write the cc number for that order. You may want to keep a hard copy of the order for your records.