Full Credit Card Number in e-mail

Hello,

I am just wondering if anyone can tell me how I can set up the cart to send the full credit card details via e-mail for manual processing instead of having it split?

My client insists on having it this way, even though I have stressed the high risks involved.

Thanks

If you search the board....you'll find this has been addressed.....I'm not sure that anyone in good conscience will tell you how......It also may violate their processors TOS and could put their processing in jeopardy......good luck

Ask your Client is he is going to be responsible for the possible interception of this information?

Hi Barco,

I spent a good couple of hours searching all throughout the board and couldn't find the answer.

I fully agree with you re: it being the wrong thing to do, I have had a few conversations with my client trying to get them to change their mind.

you will not find that information here,
it will violate the user agreement

does your client also intend for the exp date and cvv in this same email,

can we possibly have the URL so that we all know to steer clear of this site?

Merlinpa1969:

Ask your Client is he is going to be responsible for the possible interception of this information?

already been through that with him. The answer is yes he has told me he will be.

I meant that you would find that when this has been asked in the past the answers have been pretty much the same as what your gonna get in this thread........:no:
Have your client pull out the TOS for their processor and read it or go to their processors website and read it there in case its been updated.....as cc security has become a very large issue and the processor are auditing and coming down hard on violators......

How can you in good conscience even consider writing code that will violate the contract the merchant has with his credit card processing company?

Perhaps point your client here - http://usa.visa.com/merchants/risk_management/cisp.html

Kim:

How can you in good conscience even consider writing code that will violate the contract the merchant has with his credit card processing company?

Good conscience? You are making assumptions that are very unfounded. I am extremely unhappy that my client wants to do this, and have spent a good deal of time (unpaid for) locating articles and information on the web to try and deter him from doing so as I am very against him doing so. Anyone that ever deals with customers knows how stubborn some clients can be, no matter what you say to them.

barco57:

Have your client pull out the TOS for their processor and read it or go to their processors website and read it there in case its been updated.....as cc security has become a very large issue and the processor are auditing and coming down hard on violators......

Thanks Barco, I have done so.

Any idea if my business will be liable for setting it up this way if I have done everything in my power to dissuade my client? - I have put everything in writing so that he can't ever come back and say I didn't advise him.

agreed quantum however there are times where you need to tell the client that you will NOT do this,

<< has done it a few times,
client will either come to senses or they will find someone else thats willing to do the work.

Kim:

Perhaps point your client here - http://usa.visa.com/merchants/risk_management/cisp_overview.html?it=c|/merchants/risk_management/cisp.html|CISP%20Basics

Thank you for this link by the way.

Im not Barco,
however I can pretty much assure you that IF he gets in trouble they will bring you in,
whether you tried to talk em out or not, if you provide the code that causes harm then yes you can be held accountable......

you are aware that there are rules and laws in place and to do this you would knowlingly be in violation

<< not barking just trying to keep people outta trouble

:blink: interesting wording of your last there merlin....:huh: we all know your "not Barco"....your not good looking enough......

Merlinpa1969:

Im not Barco,
however I can pretty much assure you that IF he gets in trouble they will bring you in,
whether you tried to talk em out or not, if you provide the code that causes harm then yes you can be held accountable......

you are aware that there are rules and laws in place and to do this you would knowlingly be in violation

<< not barking just trying to keep people outta trouble

Sorry Merlina, getting confused with all the posts coming through. Unfortunately as far as things go, I am at the end of this project (he threw this in last minute as we were about to launch) and this is holding me up beign paid.

Anyway, if I will be held liable in anyway, that makes this simple and I won't code it so that it will do so.

Andrew-

I used the words "in good conscience" because you are still considering it. Just because the client is paying, does not make them the law. Providing code that sends a virus wouldn't be something you would write is it? Changing the code to leave a huge potential security risk is just as bad.

:clap: Andrew - we must have been typing at the same time. Thank you.

Kim:

Andrew-

I used the words "in good conscience" because you are still considering it. Just because the client is paying, does not make them the law. Providing code that sends a virus wouldn't be something you would write is it? Changing the code to leave a huge potential security risk is just as bad.

Hi Kim,

In Australia it isn't the law (apparently after just talking to my clients bank), and I just got off the phone from his bank that the merchant facility is through and they have no terms and conditions in place to say a merchant cannot do that.

That is unfortunate, as it would have been an easy way to say no to doing this.

You have my sympathy...He won't pay you? :cry:

I've had similar situations in the past. In fact, I posted here in the forum on a former client that insisted this very issue. They wouldn't pay me :censored:

I ended up sending a certified letter to them absolving me of any responsibility, asked them to sign it, and return to me. Their response? Denial of liability, laugh at me and call me paranoid.

As said before, this is clearly a violation of TOS with the major credit card companies and PCI (payment card industry) you can google PCI terms of service and get the same strict compliance rules.

What the bank says may not matter.....Its more about the card issuer (sp?) visa, mastercard, amex.....etc.....they would have policies in place regarding this......dig deeper past the bank.....