On Tue, 2010-06-01 at 19:39 -0700, Michael Shadle wrote:
> Is this a joke?
>
> Better hope your merchant provider isn't lookin...
>
>
> On Jun 1, 2010, at 7:17 PM, Brandon Rampersad
> wrote:
>
> > I store CC # in plain text on my custom ecommerse website script so
> > i can
> > compare it
Is this a joke?
Better hope your merchant provider isn't lookin...
On Jun 1, 2010, at 7:17 PM, Brandon Rampersad
wrote:
I store CC # in plain text on my custom ecommerse website script so
i can
compare it with others. That way it's easier to convert to different
hashes
when i decide to
I store CC # in plain text on my custom ecommerse website script so i can
compare it with others. That way it's easier to convert to different hashes
when i decide to integrate an encryption system. So far i havent had any
problems.
On Tue, Jun 1, 2010 at 11:15 AM, Paul M Foster wrote:
> On Tue,
On Tue, Jun 01, 2010 at 10:42:11AM -0400, tedd wrote:
> At 9:24 PM -0400 5/31/10, Paul M Foster wrote:
>> On Mon, May 31, 2010 at 05:06:23PM -0400, tedd wrote:
>>
>>> At 12:36 PM -0400 5/31/10, I wrote:
That's Okay, but I'm simply telling you what I KNOW to be true. You
may either acc
On Tue, Jun 01, 2010 at 04:17:21PM +0200, Peter Lind wrote:
> On 1 June 2010 15:58, Paul M Foster wrote:
> > On Tue, Jun 01, 2010 at 09:52:54AM +0200, Peter Lind wrote:
> >
> >> Just wondering: seems there's a bit of a misunderstanding going on
> >> here. Are you talking about storing credit card
At 9:52 AM +0200 6/1/10, Peter Lind wrote:
Just wondering: seems there's a bit of a misunderstanding going on
here. Are you talking about storing credit card information in a way
such that customers can do online transactions without entering that
information? Or are you talking about storing thi
At 9:21 PM -0400 5/31/10, Paul M Foster wrote:
On Mon, May 31, 2010 at 12:36:55PM -0400, tedd wrote:
> What data are used in credit card transactions are the: name of the
card holder, credit card number, expiration date, CCV number, and zip
code. I have not dealt with any credit card processo
At 9:24 PM -0400 5/31/10, Paul M Foster wrote:
On Mon, May 31, 2010 at 05:06:23PM -0400, tedd wrote:
At 12:36 PM -0400 5/31/10, I wrote:
That's Okay, but I'm simply telling you what I KNOW to be true. You
may either accept what I have to say, or reject it, but to reply
that what I say is "
On 1 June 2010 15:58, Paul M Foster wrote:
> On Tue, Jun 01, 2010 at 09:52:54AM +0200, Peter Lind wrote:
>
>> Just wondering: seems there's a bit of a misunderstanding going on
>> here. Are you talking about storing credit card information in a way
>> such that customers can do online transactions
On Tue, Jun 01, 2010 at 09:52:54AM +0200, Peter Lind wrote:
> Just wondering: seems there's a bit of a misunderstanding going on
> here. Are you talking about storing credit card information in a way
> such that customers can do online transactions without entering that
> information? Or are you t
Just wondering: seems there's a bit of a misunderstanding going on
here. Are you talking about storing credit card information in a way
such that customers can do online transactions without entering that
information? Or are you talking about storing this information so your
own company can fill in
On Mon, May 31, 2010 at 05:06:23PM -0400, tedd wrote:
> At 12:36 PM -0400 5/31/10, I wrote:
>> That's Okay, but I'm simply telling you what I KNOW to be true. You
>> may either accept what I have to say, or reject it, but to reply
>> that what I say is "Not true" is somewhat offensive and
>> confr
On Mon, May 31, 2010 at 12:36:55PM -0400, tedd wrote:
> At 1:38 AM -0400 5/31/10, Paul M Foster wrote:
>> On Sun, May 30, 2010 at 10:50:05AM -0400, tedd wrote:
>>
>> > Besides, most credit card processing agencies even require that you
>>> use the customer's data (cc number, expiry date and CCS)
Billing Address (at least the street number) is used in conjunction
with the zip code for AVS checks.
On 5/31/10, tedd wrote:
> At 1:38 AM -0400 5/31/10, Paul M Foster wrote:
>>On Sun, May 30, 2010 at 10:50:05AM -0400, tedd wrote:
>>
>> > Besides, most credit card processing agencies even requir
At 12:36 PM -0400 5/31/10, I wrote:
That's Okay, but I'm simply telling you what I KNOW to be true. You
may either accept what I have to say, or reject it, but to reply
that what I say is "Not true" is somewhat offensive and
confrontational. I hope you didn't mean it that way. :-)
My apologie
At 1:38 AM -0400 5/31/10, Paul M Foster wrote:
On Sun, May 30, 2010 at 10:50:05AM -0400, tedd wrote:
> Besides, most credit card processing agencies even require that you
use the customer's data (cc number, expiry date and CCS) to make the
sale and then immediately dispose of it afterwards,
On May 31, 2010, at 1:24 AM, Paul M Foster
wrote:
On Sun, May 30, 2010 at 03:30:28PM -0400, Phpster wrote:
I work with some of the largest retailers in north America if not the
world, and I can confirm that the security measures taken to enforce
pci compliance are not something lightl
On Sun, May 30, 2010 at 10:50:05AM -0400, tedd wrote:
> At 12:43 PM +0200 5/30/10, Peter Lind wrote:
>>> On 30 May 2010 07:49, Paul M Foster wrote:
>>> -snip-
>>>
>>> Does anyone have a better solution?
>>
>> I'm sorry if the following sounds a bit harsh, but in matters like
>> these I prefer bl
On Sun, May 30, 2010 at 03:30:28PM -0400, Phpster wrote:
>
> I work with some of the largest retailers in north America if not the
> world, and I can confirm that the security measures taken to enforce
> pci compliance are not something lightly undertaken.
>
> If those entities choose to store t
On Sun, May 30, 2010 at 03:12:10AM -0400, Adam Richardson wrote:
> On Sun, May 30, 2010 at 2:16 AM, Ashley Sheridan
> wrote:
>
> > On Sun, 2010-05-30 at 01:49 -0400, Paul M Foster wrote:
> >
>
> Hi Paul,
>
> When you describe one-way or two-way encryption, what are you describing?
> Are you
On May 30, 2010, at 10:50 AM, tedd wrote:
At 12:43 PM +0200 5/30/10, Peter Lind wrote:
On 30 May 2010 07:49, Paul M Foster wrote:
-snip-
Does anyone have a better solution?
I'm sorry if the following sounds a bit harsh, but in matters like
these I prefer blunt directness.
A few notes. 1
On Sun, May 30, 2010 at 11:50 AM, tedd wrote:
> At 12:43 PM +0200 5/30/10, Peter Lind wrote:
>
>> On 30 May 2010 07:49, Paul M Foster wrote:
>>> -snip-
>>>
>>>
>>> Does anyone have a better solution?
>>>
>>
>> I'm sorry if the following sounds a bit harsh, but in matters like
>> these I prefer
At 12:43 PM +0200 5/30/10, Peter Lind wrote:
On 30 May 2010 07:49, Paul M Foster wrote:
-snip-
Does anyone have a better solution?
I'm sorry if the following sounds a bit harsh, but in matters like
these I prefer blunt directness.
A few notes. 1) one-way encryption means "no decrypting" - t
On 30 May 2010 07:49, Paul M Foster wrote:
> This question is for people who take and store credit card information
> for customers.
>
> Credit card companies, in an attempt to lessen fraud, are tightening the
> screws on merchants who take credit cards. One aspect of this is a
> requirement to st
On Sun, May 30, 2010 at 2:16 AM, Ashley Sheridan
wrote:
> On Sun, 2010-05-30 at 01:49 -0400, Paul M Foster wrote:
>
> > This question is for people who take and store credit card information
> > for customers.
> >
> > Credit card companies, in an attempt to lessen fraud, are tightening the
> > scr
On Sun, 2010-05-30 at 01:49 -0400, Paul M Foster wrote:
> This question is for people who take and store credit card information
> for customers.
>
> Credit card companies, in an attempt to lessen fraud, are tightening the
> screws on merchants who take credit cards. One aspect of this is a
> req
26 matches
Mail list logo
