jPOS ISO8583 fields

[allo...@gmail.com]

hello all,
I've been reading for a while about the jPOS and the ISO 8583 standard
from the programming guide, Wikipedia, and some websites on the web,
but I didn't find the following:

-ISO 8583 fields description: some useful info about each field.
-the value range for each field(if any), and the meaning of each
value.
-the format of each field's value (how it's represented). I've found
some info about the types in Wikipedia but didn't fully understand it.
-what are the mandatory fields for an auth request, response and other
messages?

can anybody help me where i can find some information ??

[Victor Salaman]

Hi:

You need to get that information from your POS vendor and their
implementation. After that you need to develop a packager and channel that
implements their spec. Without the POS communications specifications and

their "unique" implementation details it'd be very difficult to move
forward.

What is the exact vendor and model info of the POS terminal?

/V

On Thu, Apr 30, 2009 at 8:23 AM, Victor Salaman <sal...@vmantek.com> wrote:

Hi:

You need to get that information from your POS vendor and their implementation. After that you need to develop a packager and channel that implements their spec. Without the POS communications specifications and their "unique" implementation details it'd be very difficult to move forward.

What is the exact vendor and model info of the POS terminal?

/V

[allo...@gmail.com]

isn't there a common ground for the values of the fields between POS
vendors specific implementation??
when i need to connect to a POS I'll know what channel and packager
and used dynamically by my system.
for the values: for example the POS entry mode field can have value of
022 which is 'swiped card', what about other possible values and their
meaning?

[Victor Salaman]

Every vendor decides what to use and how to implement it. They then "make a spec". As mentioned before, you need the spec. I'm sorry, there is no other way.

Four (4) different times on this thread people have asked you for VENDOR and MODEL, which you have avoided to answer. Without you having the spec, or finding someone on the list which knows about your POS vendor or model, we can't be of much help.

/V

[Mark Salter]

allo...@gmail.com wrote:
>
> isn't there a common ground for the values of the fields between POS
> vendors specific implementation??

Yes but these are more similarities than a standard. You are looking
for something that does not exist. Perhaps a surprise it often is for
people.

> when i need to connect to a POS I'll know what channel and packager
> and used dynamically by my system.

I hope so; you will also need to know with fields to use for 'receipt
transport' and what values will need to be placed in which fields;
which is really likely to vary as below...

> for the values: for example the POS entry mode field can have value of
> 022 which is 'swiped card', what about other possible values and their
> meaning?

It will vary from scheme to scheme, system to system, interface to
interface and from time to time.

--
Mark

[allo...@gmail.com]

I'm trying to make my system more general and to communicate with
different POS devices, not a specific model.
so i understand that i MUST know what POS vendor and model to develop
the system for before start building it,

question: when I send a message to the POS device, there is a an
entity in the middle(gateway, router) that will relay the request to
the desired POS device, right?

[Mark Salter]

allo...@gmail.com wrote:
>
> I'm trying to make my system more general and to communicate with
> different POS devices, not a specific model.
> so i understand that i MUST know what POS vendor and model to develop
> the system for before start building it,

Good, so this detail will come and you are working on a theory at present.

>
> question: when I send a message to the POS device, there is a an
> entity in the middle(gateway, router) that will relay the request to
> the desired POS device, right?

Possibly.
It is your solution, you will need to find out. We cannot know and
could only guess.

--
Mark