Re: [Emerald] ICVerify and Credit Card exp date
Ted Beckwith ( email@example.com )
Mon, 16 Aug 1999 20:15:12 -0400
"Dale E. Reed Jr." wrote:
> Ted Beckwith wrote:
> > "Dale E. Reed Jr." wrote:
> > >
> > > Ted Beckwith wrote:
> > > >
> > > > We just batched our first billing with Emerald using ICVerify and were
> > > > unpleasantly surprised to find that ICVerify needs the expiration date
> > > > reversed (YYMM instead of MMYY) for any date past 01/00. I spoke to IEA
> > > > support and their only comment on the issue was "emerald only puts out
> > > > what you enter into it". I really don't want to go into emerald and
> > > > change all of the expiration dates to be backwards.
> > >
> > > Backwards is from the perspective of what you need. From IC Verify's
> > > perspective, you are entering the dates backwards. :(
> > >
> > > > What are others doing to get around this problem? why can't iea-software
> > > > just change the way it creates the text file for ICVerify?
> > >
> > > Because each CC processing system has different requiresments.
> > > Thats how IC Verify wants it, and there isn't a lot we can do
> > > about it. This is a known issue that has been around for a while
> > > now (since CC companies starting issuing year 2000 and higher
> > > expiring dates).
> > How hard would it be to make emerald come up with the format that
> > ICVerify requires? Emerald already modifies the date, e.g. by changing
> > 9/01 into 0901. why not take the extra step and make it 0109? You could
> > even make a seperate CC Batch format that wouldn't conflict with the
> > existing ICVerify format.
> Emerald doesn't specify the format for the expiration, so assuming
> that its in MMYY format (although the most popular) is not cast
> in stone. I don't understand the difference between saying "expiration
> dates must be entered in MMYY format" and "expiration dates must be
> entered in YYMM format". Emerald still can't enforce either. :(
While it's true that Emerald can't enforce the format, it is Emerald
(and not ICVerify) that can allow me to use expiration dates that follow
an established format in our database.
Surely you have recieved dozens of complaints with regards to this
issue. (I personally wasted 30 minutes of your support staff's time on
the phone today, not to mention the time it will take to reverse the
expiration dates in our database). Why not just create a "fix", as I
have suggested above, by adding a new CC Batch format that would that
would flip MMYY to YYMM?
I didn't hear from any other ISPs about what they have done to solve
this problem. I can't believe everyone using ICVerify has to enter exp.
dates in the Emerald database in a YYMM format.
For more information about this list (including removal) go to: