From: "Dale E. Reed Jr." <email@example.com> Subject: RE: [Emerald] Using ICVerify w/AVS and Emerald 2.5 Date: Thu, 5 Jun 2003 09:48:44 -0700 Message-ID: <EFEHJGKHFGPNMBOJINBFMELDCAAA.firstname.lastname@example.org>
> > Appendix A of the Emerald 2.5 Admin docs lists what Emerald writes
> > out and what it needs back for each CC processor format.
> Thanks Dale. I found the Appendix. However, our version of
> ICVerify (ver 3.0
> for Vital) does not return the transaction ID, and the response code is a
> single entry with 20 characters and not "six fields, comma
> delimited" as the
> Appendix suggests. Consequently, when executing "Batchin" in Emerald, it
> fails. The first character in the response field is a Y for an approved
> transaction, not an A as suggested by the Appendix. Is there a log that I
> can look to see where the information that Emerald need is collected?
The formts for Emerald 2.5 are hard coded and not modifiable like
4.0. I believe the IC Verify format can be modified within the
application. Emerald sends the TransactionID as the InvoiceID.
You'd need to modify IC Verify to return the fields in the order
Emerald is looking for.