Credit Card information not to appear in a table 1

[LearnersPermit]

Good afternoon - I have been working on a form which will include payment information in a sub-form. I do have not included the credit card number or expiry date in any tables. What I am seeking to do is have a user input the credit card and expiry date on the sub-form and be able to print the information. So far I have created two unbound text boxes, however when I print the form the credit card and expiry date information are not printed. Any suggestions?

Thank you

 

[MichaelRed]

Hmmmmmmmmmmm,

Eventually, you MUST keep track of the credit info, including the card #, Exp Date AND auth. If you DO NOT, you will have BIG troubles. You need to be able to do returns and 'prove' that tranactions were authourized. It is ppossiblt -on a VERY small scale to keep this info only on paper and file in manually, -as the tic-tac ad says - " ... however I don't recommend it! " You probablt SHOULD keep this indo in a seperate table and encrypt is pretty strongly. Add as much protection as you want, but do keep it in a table.

MichaelRed
m.red@att.net

There is never time to do it right but there is always time to do it over

 

[LearnersPermit]

Thank you MichaelRed for this interesting point of view. I will raise your suggestion with my Manager. We were thinking along the lines that we didn't want anyone to access this information. The user storing the information only wanted to keep a hard copy in a secured filing cabinet.

For curiosity's sake, any suggestions on how to enter information in a field and have it appear on the printed version only?

Thanks

 

[MichaelRed]

Store the fields sepratly (a seperate table) and restrict access to the table with the db security. Of course, you will need to have a link fromt he 'normal' part of the transaction record to the credit details, but if only the authourized (bonded managers?) have permission to read the table, it will nnot be available to anyone but them and the db ADMINs.

Encrypt the field(s) except the transaction link. Even if someone does access the data, it will be gibberish without the encryption codes.

On the other side, if the 'information' is aqvailable in the printed versions, how is that "protecting" it? Are the printouts going to be in a secure "Vault"? Who would have access to the vault? Under what circumstances?

The whole question of storage of sensitive information is a 'slippery slope'. It gets down to basically how much are you willing to pay for the security of the information and what will that buy you in terms of security. Rember that NO ONE will pay more for the lock than they think the value of what is being locked with it. the other issue, of course, is what is your liability if the information is revealed impropperly?

MichaelRed
m.red@att.net

There is never time to do it right but there is always time to do it over