Now that we have gotten past the Emerald -> PC authorize problem with
the newest binaries, we're having a problem going from PC Auth ->
Emerald. We are using PC Authorize CardService edition "V 1,1,2,0" that
uses a binary file format for its batch files. We are able to Import
into PC authorize using its built in import feature, however the problem
is now getting that back out into Emerald. Again we have to use PC
Authorizes' Export feature to get it to a text file. The emeraldadm.doc
has a very poor listing of what Emerald is looking for in the batch out
file.
The document says that we need field 1 to be Transaction ID, Field 3 to
be the response code and Field 4 to be the approval code. It also says
there are a total of 7 fields and doesn't give any description of the
others. I assume emerald ignores them.
PC authorize doesn't use the exact names of the fields that is listed in
the document so I assuming for the moment my problem is I'm having
trouble choosing which fields to export back to emerald. What i need to
know is what exactly is emerald looking for in those 3 fields so I can
choose the right fields from PC Auth to send back to Emerald.
Thanks,
Alex
Online Gateway
For more information about this list, including removal,
please see http://www.iea-software.com/maillist.html