ISO-8583 Packager

[Passion Java]

Why we have different Packager in JPOS, I believe ISO-8583 is a standard protocol which is widely accepted then why we need custom packager in JPOS.

[Mark Salter]

Passion Java wrote:
> Why we have different Packager in JPOS, I believe ISO8583 is a

> standard protocol which is widely accepted then why we need custom
> packager in JPOS.

What you believe and what happens in the real world appear to be different.

I was going to start talking about forming a crack commando ISO8583 team
of enforcement officers with your help, but didn't want to give anyone
any ideas.

Instead I will suggest that we have different packagers available
because different systems bend the ISO8583 guidelines in different
directions. Every organisation likes to make *their* messages their
own, and not just because of the character set used by their systems
architecture.

--
"Variety is the spice of life."
Mark

[Aissa.Slimani]

Hi,
ISO8583 is a standard for financial institutions, and

The International Organization for Standardization (ISO) differentiates
between standards and regulations as follows:

Standard : « A document approved by recognized body that provides, for
common and repeated use, rules, guidelines, or characteristics of products,
processes or services with which compliance is not mandatory »

Regulation : « A document which lays down product, process or service
characteristics, …, with which compliance is mandatory »

That's why we have so many ISOs, and that's why JPOS has so many packagers.



-----Message d'origine-----
De : jpos-...@googlegroups.com [mailto:jpos-...@googlegroups.com] De la
part de Mark Salter
Envoyé : lundi 17 novembre 2008 11:08
À : jpos-...@googlegroups.com
Objet : Re: ISO-8583 Packager

[Passion Java]

ｷ         Thanks mark, for your quick reply. I can see few private fields in ISo-8583 message (like field 52 which is a personal fields) which can be customized by this packager?

ｷ         Can we also customize the fields which are fixed by the ISO Team like Primary account number (PAN) can I change this fields number 3 (as per ISO it should be field 2)?

[Passion Java]

That’s really great definition. For example Visa Card will have lot of other partners who will communicate with then using ISO-8583 protocol. Every partner will have a different standards with visa card or it is common for all the partners ?

---------- Original message ----------
From:Aissa.Slimani< aissa....@gmail.com >
Date: 17 Nov 08 16:45:17
Subject: RE: ISO-8583 Packager
To:

[Mark Salter]

Passion Java wrote:
> ｷ Thanks mark, for your quick reply. I can see few private fields in

> ISo8583 message (like field 52 which is a personal fields) which can

> be customized by this packager?ｷ

There is nothing to stop you using the fields in your message to carry
any data you feel you want them to.

> Can we also customize the fields
> which are fixed by the ISO Team like Primary account number (PAN) can
> I change this fields number 3 (as per ISO it should be field 2)?

If you want to, there is no one that will stop you.
It may cause initial confusion to those people that expect the PAN to be
in field 2, and also mean your system will take 'more' work to connect
to existing systems, but your message format is up to you.

Can you take a look at your text wrapping settings, your follow-up
postings are very hard to read.

--
Mark

[Mark Salter]

Passion Java wrote:
> That’s really great definition.

It is indeed, thank you Aissa.

> For example Visa Card will have lot of other partners who will

> communicate with then using ISO8583 protocol. Every partner will have

> a different standards with visa card or it is common for all the
> partners ?

It really depends who controls (owns) the interface.

If "Visa Card" are the owners of the interface (and the system behind
it) and the "partners" want to connect to them, then "Visa Card" will
define and control the message standard into *their* system. This seems
the most likely situation in your example.

--
Mark