|
Posted by Marc on April 10, 2007, 1:21 pm
Please log in for more thread options : quoted-printable
Todd,
=20
According to Vital, the downgrade occurs at the register by RMS, before =
it is sent to Vital, eliminating Vital, FD and card type as part of the =
problem. The tech I spoke to said the transactions we reviewed came into =
Vital marked as hand swiped. The answers to your question are below.
I believe Glenn Adams was also looking into this issue for a client and =
he may have more information that could help determine the cause.
Thanks,=20
Marc
=20
> Good morning Marc,
>=20
> Thank you for the update.
> =20
>=20
> 1. If Vital does not know why the cards were downgraded does First =
Data?
The card is ALREADY MARKED AS HAND SWIPED BY RMS when Vital gets it.
>=20
> 2. If First Data is able to let you know what is causing the downgrade =
can=20
> you also find out the card type(s)?
N/A
>=20
> 3. Do you accept corporate credit cards?
N/A
>=20
> 4. If you do not know which specific transactions are being downgraded =
how=20
> do you know that the issue is happening at all registers?
When I checked into the issue I called Vital and had them pull a few =
transaction that came through as hand swiped from that morning. I was =
told by Vital that the downgrade to hand swiped status originated from =
RMS - they do not know why and they just pass it on to FD. These =
downgraded transactions were from both registers.
>=20
> 5. Are all fields filled in and showing the correct information in =
Store=20
> Operations Administrator | File | Configuration | EDC | Advanced =
Options on=20
> each computer?
YES
>=20
>=20
> Thank you in advance.
>=20
> Todd Berger
> Microsoft Online Support Engineer
>=20
> Get Secure! - www.microsoft.com/security
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
> When responding to posts, please "Reply to Group" via your newsreader =
so=20
> that others may learn and benefit from your issue.=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
> This posting is provided "AS IS" with no warranties, and confers no =
rights.
>=20
>=20
> --------------------
> Subject: Re: Repost for Managed: credit card qualification
> Date: Mon, 9 Apr 2007 10:17:56 -0400
>=20
> Todd,=20
> I just added the news account to managed on my account right before =
posting=20
> this message. Please let me know if marc_mg@beverlyspet.com never got=20
> registered to me as a managed account.
> Below are the answers as I can best determine to your questions. =
Please=20
> bear in mind that this porblem was not present for 20 years with the =
same=20
> credit card/customer base while using Zon dial-up terminals. The =
problem=20
> presented only upon switching to built-in credit card processing.
> Thanks,=20
> Marc Rosenberg
> Beverly's Pet Center
> 954.322.1112
>> Good afternoon Marc,
>>=20
>> Thank you for posting your credit card processing question.
>>=20
>> NOTE: Sorry for the delay but your posts are not showing up as =
managed >=20
> because the email address you are posting under does not match the =
email=20
>> address listed in CustomerSource | Discussions | Access the Managed=20
>> Newsgroups Registration for your account.
>>=20
>> As far as the credit card qualification question it may be hard to=20
> diagnose=20
>> since there is a small number of transactions that this is happening =
on;=20
>> and it could be related to issues with the card itself or the MSR not =
>> getting all data.
>>=20
>> Can you please let me know:
>>=20
>> 1. What build of Store Operations are you using?
> 1.3.0203
>>=20
>> 2. Is there any connection between the types of cards that are =
showing up=20
>> as hand keyed vs those that are showing up as swiped? For example, =
Visa=20
> or=20
>> MC, issued from a particular bank, debit/credit cards, etc.
> No pattern I can discern, but I cannot tell what charges are being=20
> downgraded from my statement, I only get a count/dollar value.
>>=20
>> 3. Does this happen at all registers?
> Yes
>>=20
>> 4. What did Vital say is the cause of it showing as hand keyed? A =
number=20
> 0=20
>> vs a number 1 in the request file?
> All they could tell me is that the of hand keyed status was being sent =
from=20
> RMS, it was not determined by them.
>>=20
>> 5. Are you using the built in credit card processing or a 3rd party =
such=20
> as=20
>> Mercury, PC Charge, etc?
> Built-in processing. FD thru Vita
>> 6. Have you tried keeping a log of the transactions where a credit =
card=20
> was=20
>> actually hand keyed; and comparing that to what is actually showing =
up as=20
>> hand keyed?
> The amount of charges we hand key is virtually non-existent. We only =
hand=20
> key several charges a year.
>=20
>> 7. Are there times when the swipe does not automatically send the =
credit=20
>> card information for approval and the enter key must be pressed? This =
may=20
>> show as hand keyed.
> There are times the cashier gets an erorr message about bad data and =
must=20
> cancel out and re-swipe the card. I am not aware of the situation you=20
> descibe occuring.
> It seems that RMS will often allow the cashier to continue and will =
process=20
> a charge even after the error message occurs. We thought this was the =
cause=20
> of the issue so we re-trained all cashiers to cancel first, then =
re-swipe=20
> card. There was no change in the number of mis-labled transactions.
>>=20
>> 8. Are there times when the swipe does not fill in the complete =
credit=20
> card=20
>> number or expiration date; and this needs to be hand keyed?
> No
>> =20
>> 9. What is the model number of the MSR?=20
>=20
> MagTek Mini USB 2104108
>>=20
>> Thank you in advance.
>> =20
>> Todd Berger
>> Microsoft Online Support Engineer
>>=20
>> Get Secure! - www.microsoft.com/security
>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
>> When responding to posts, please "Reply to Group" via your newsreader =
so=20
>> that others may learn and benefit from your issue.=20
>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
>> This posting is provided "AS IS" with no warranties, and confers no=20
> rights.
>>=20
>> =20
>> --------------------
>> Subject: Repost for Managed: credit card qualification
>> Date: Thu, 29 Mar 2007 14:30:01 -0400
>>=20
>> This message has been posted by me before, this is a repost under my=20
>> managed=20
>> account for a response by MS.
>>=20
>>=20
>> About 2% of my credit card transactions are clearing as 'hand keyed', =
> which
>> of course bumps them up to some outrageous discount rate. We rarely =
hand=20
> key
>> any transaction, so I have been trying to track down the cause of =
this
>> downgrade. I spoke with the folks at Vital and we checked out a few =
of the
>> offending transactions. According to them, the hand keyed status=20
> originates
>> from RMS, it is not done at their end end for 'lack of data'.
>>=20
>> I am using the Mini-Mag and swiped a card in Notepad and it matched
>> perfectly with the expected info, per theKnowledgebase article, but =
then
>> again, only 2% of the cards are failing. I did not have this problem =
with
>> the old Zon dial-up terminals.
>>=20
>>=20
>> Marc
>> Beverly's Pet Center
>>=20
>>=20
>>
>
------=_NextPart_000_000B_01C77B73.2A014410
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16414" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#ff0000 size=3D2>Todd,</FONT></DIV>
<DIV><FONT face=3DArial color=3D#ff0000 size=3D2> </FONT></DIV>
<DIV><FONT face=3DArial color=3D#ff0000 size=3D2>According to Vital, the =
downgrade=20
occurs at the register by RMS, before it is sent to Vital, =
eliminating=20
Vital, FD and card type as part of the problem. The tech I spoke to =
said=20
the transactions we reviewed came into Vital marked as hand swiped. The =
answers=20
to your question are below.</FONT></DIV>
<DIV><FONT face=3DArial color=3D#ff0000 size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#ff0000 size=3D2>I believe Glenn Adams =
was also=20
looking into this issue for a client and he may have more information =
that could=20
help determine the cause.</FONT></DIV>
<DIV><FONT face=3DArial color=3D#ff0000 size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#ff0000 size=3D2>Thanks, </FONT></DIV>
<DIV><FONT face=3DArial color=3D#ff0000 size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#ff0000 size=3D2>Marc</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>> Good morning =
Marc,<BR>> <BR>> Thank=20
you for the update.<BR>> <BR>> <BR>> 1. If Vital =
does not=20
know why the cards were downgraded does First Data?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#ff0000 size=3D2>The card is ALREADY =
MARKED AS HAND=20
SWIPED BY RMS when Vital gets it.</FONT><BR><FONT face=3DArial=20
size=3D2>> <BR>> 2. If First Data is able to let you know =
what is=20
causing the downgrade can <BR>> you also find out the card=20
type(s)?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><FONT color=3D#ff0000>N/A</FONT></DIV>
<DIV><BR>> <BR>> 3. Do you accept corporate credit =
cards?</DIV>
<DIV> </DIV>
<DIV><FONT color=3D#ff0000>N/A</FONT><BR>> <BR>> 4. If you do =
not know=20
which specific transactions are being downgraded how <BR>> do you =
know that=20
the issue is happening at all registers?</DIV>
<DIV> </DIV>
<DIV><FONT color=3D#ff0000>When I checked into the issue I called Vital =
and had=20
them pull a few transaction that came through as hand swiped from that =
morning.=20
I was told by Vital that the downgrade to hand swiped status originated =
from=20
RMS</FONT> <FONT color=3D#ff0000>- they do not know why and they just =
pass it on=20
to FD. These downgraded transactions were from both=20
registers.<BR></FONT>> <BR>> 5. Are all fields filled in and =
showing=20
the correct information in Store <BR>> Operations Administrator | =
File |=20
Configuration | EDC | Advanced Options on <BR>> each computer?</DIV>
<DIV><FONT =
color=3D#ff0000>YES<BR></FONT>> <BR>> <BR>> Thank=20
you in advance.<BR>> <BR>> Todd Berger<BR>> Microsoft =
Online=20
Support Engineer<BR>> <BR>> Get Secure! - </FONT><A=20
href=3D"http://www.microsoft.com/security"><FONT face=3DArial=20
size=3D2>www.microsoft.com/security</FONT></A><BR><FONT face=3DArial =
size=3D2>>=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<BR>> When responding to=20
posts, please "Reply to Group" via your newsreader so <BR>> that =
others may=20
learn and benefit from your issue. <BR>>=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<BR>> This posting is=20
provided "AS IS" with no warranties, and confers no=20
rights.<BR>> <BR>> <BR>> --------------------<BR>> =
From:=20
face=3DArial=20
size=3D2>marc_mg@beverlyspet.com</FONT></A><FONT face=3DArial =
size=3D2>><BR>>=20
Subject: Re: Repost for Managed: credit card qualification<BR>> Date: =
Mon, 9=20
Apr 2007 10:17:56 -0400<BR>> <BR>> Todd, <BR>> I just added the =
news=20
account to managed on my account right before posting <BR>> this =
message.=20
Please let me know if </FONT><A =
face=3DArial size=3D2>marc_mg@beverlyspet.com</FONT></A><FONT =
face=3DArial size=3D2>=20
never got <BR>> registered to me as a managed account.<BR>> Below =
are the=20
answers as I can best determine to your questions. Please <BR>> bear =
in mind=20
that this porblem was not present for 20 years with the same <BR>> =
credit=20
card/customer base while using Zon dial-up terminals. The problem =
<BR>>=20
presented only upon switching to built-in credit card =
processing.<BR>>=20
Thanks, <BR>> Marc Rosenberg<BR>> Beverly's Pet =
Center<BR>> =20
954.322.1112<BR>> "Todd Berger [MSFT]" <</FONT><A=20
size=3D2>tberger@online.microsoft.com</FONT></A><FONT face=3DArial =
size=3D2>> wrote=20
in message <BR>> </FONT><A=20
face=3DArial=20
face=3DArial=20
size=3D2>...<BR>>> Good afternoon Marc,<BR>>> <BR>>> =
Thank you=20
for posting your credit card processing question.<BR>>> =
<BR>>> NOTE:=20
Sorry for the delay but your posts are not showing up as managed > =
<BR>>=20
because the email address you are posting under does not match the email =
<BR>>> address listed in CustomerSource | Discussions | Access the =
Managed=20
<BR>>> Newsgroups Registration for your account.<BR>>> =
<BR>>>=20
As far as the credit card qualification question it may be hard to =
<BR>>=20
diagnose <BR>>> since there is a small number of transactions that =
this is=20
happening on; <BR>>> and it could be related to issues with the =
card=20
itself or the MSR not <BR>>> getting all data.<BR>>> =
<BR>>>=20
Can you please let me know:<BR>>> <BR>>> 1. What build of =
Store=20
Operations are you using?<BR>> 1.3.0203<BR>>> <BR>>> 2. =
Is there=20
any connection between the types of cards that are showing up =
<BR>>> as=20
hand keyed vs those that are showing up as swiped? For example, Visa =
<BR>> or=20
<BR>>> MC, issued from a particular bank, debit/credit cards, =
etc.<BR>>=20
No pattern I can discern, but I cannot tell what charges are being =
<BR>>=20
downgraded from my statement, I only get a count/dollar =
value.<BR>>>=20
<BR>>> 3. Does this happen at all registers?<BR>> =
Yes<BR>>>=20
<BR>>> 4. What did Vital say is the cause of it showing as hand =
keyed? A=20
number <BR>> 0 <BR>>> vs a number 1 in the request =
file?<BR>> All=20
they could tell me is that the of hand keyed status was being sent from =
<BR>>=20
RMS, it was not determined by them.<BR>>> <BR>>> 5. Are you =
using=20
the built in credit card processing or a 3rd party such <BR>> as =
<BR>>>=20
Mercury, PC Charge, etc?<BR>> Built-in processing. FD thru =
Vita<BR>>>=20
6. Have you tried keeping a log of the transactions where a credit card =
<BR>>=20
was <BR>>> actually hand keyed; and comparing that to what is =
actually=20
showing up as <BR>>> hand keyed?<BR>> The amount of charges we =
hand key=20
is virtually non-existent. We only hand <BR>> key several charges a=20
year.<BR>> <BR>>> 7. Are there times when the swipe does =
not=20
automatically send the credit <BR>>> card information for approval =
and the=20
enter key must be pressed? This may <BR>>> show as hand =
keyed.<BR>>=20
There are times the cashier gets an erorr message about bad data and =
must=20
<BR>> cancel out and re-swipe the card. I am not aware of the =
situation you=20
<BR>> descibe occuring.<BR>> It seems that RMS will often allow =
the=20
cashier to continue and will process <BR>> a charge even after the =
error=20
message occurs. We thought this was the cause <BR>> of the issue so =
we=20
re-trained all cashiers to cancel first, then re-swipe <BR>> card. =
There was=20
no change in the number of mis-labled transactions.<BR>>> =
<BR>>> 8.=20
Are there times when the swipe does not fill in the complete credit =
<BR>>=20
card <BR>>> number or expiration date; and this needs to be hand=20
keyed?<BR>> No<BR>>> <BR>>> 9. What is the model =
number of=20
the MSR? <BR>> <BR>> MagTek Mini USB 2104108<BR>>> =
<BR>>>=20
Thank you in advance.<BR>>> <BR>>> Todd =
Berger<BR>>>=20
Microsoft Online Support Engineer<BR>>> <BR>>> Get Secure! - =
</FONT><A href=3D"http://www.microsoft.com/security"><FONT face=3DArial=20
size=3D2>www.microsoft.com/security</FONT></A><BR><FONT face=3DArial =
size=3D2>>>=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<BR>>> When=20
responding to posts, please "Reply to Group" via your newsreader so =
<BR>>>=20
that others may learn and benefit from your issue. <BR>>>=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<BR>>> This posting=20
is provided "AS IS" with no warranties, and confers no <BR>>=20
rights.<BR>>> <BR>>> <BR>>>=20
--------------------<BR>>> From: "Marc MG" <</FONT><A=20
size=3D2>marc_mg@beverlyspet.com</FONT></A><FONT face=3DArial=20
size=3D2>><BR>>> Subject: Repost for Managed: credit card=20
qualification<BR>>> Date: Thu, 29 Mar 2007 14:30:01 =
-0400<BR>>>=20
<BR>>> This message has been posted by me before, this is a repost =
under=20
my <BR>>> managed <BR>>> account for a response by =
MS.<BR>>>=20
<BR>>> <BR>>> About 2% of my credit card transactions are =
clearing=20
as 'hand keyed', <BR>> which<BR>>> of course bumps them up to =
some=20
outrageous discount rate. We rarely hand <BR>> key<BR>>> any=20
transaction, so I have been trying to track down the cause of =
this<BR>>>=20
downgrade. I spoke with the folks at Vital and we checked out a few of=20
the<BR>>> offending transactions. According to them, the hand =
keyed status=20
<BR>> originates<BR>>> from RMS, it is not done at their end =
end for=20
'lack of data'.<BR>>> <BR>>> I am using the Mini-Mag and =
swiped a=20
card in Notepad and it matched<BR>>> perfectly with the expected =
info, per=20
theKnowledgebase article, but then<BR>>> again, only 2% of the =
cards are=20
failing. I did not have this problem with<BR>>> the old Zon =
dial-up=20
terminals.<BR>>> <BR>>> <BR>>> Marc<BR>>> =
Beverly's Pet=20
Center<BR>>> <BR>>> =
<BR>>><BR>></FONT></DIV></BODY></HTML>
------=
|