jPOS Users Google Group

Re: [jpos-users] Get packager dynamically using the TPDU content

marksal...@talktalk.net (Mark Salter) — Tue, 10 Nov 2009 09:18:09 UT

Can you give the format of the length (binary and endian, character etc)?
Your vendors way of indicating the message length might not match
NACChannels...
1. Look at the source.
2. Look at the source again 8).
3. extend NACChannel - if that matches your network protocol, the
override getDynamicPackager(header, b) to return the packager based upon

Get packager dynamically using the TPDU content

kelvinwork...@gmail.com (kelvin) — Tue, 10 Nov 2009 05:13:03 UT

Hi all,

Thanks for your opinion in my previous post!

Finally, our system would connect to a NAC vendor to receive the
iso8583 message. The protocol used would be: [2byte Message length]
+[5byte TPDU]+[iso 8583 message], so I think the NACChannel would be a
good starting point for my work.(Please comment if I am wrong).

Re: [jpos-users] jPOS group on Facebook

a...@jpos.org (Alejandro Revilla) — Mon, 09 Nov 2009 14:29:29 UT

Great!

jPOS group on Facebook

jpractitio...@gmail.com (DC) — Mon, 09 Nov 2009 11:04:27 UT

Hi guys, I have cerated jPOS group on facebook. feel free to
join..take care

Re: Problem identifying the source of iso8583

kelvinwork...@gmail.com (kelvin) — Mon, 09 Nov 2009 09:14:37 UT

Hi all,

This is my first post in the group. I really appreciate your reply!
Thanks for sharing~!

Kelvin

Re: Problem identifying the source of iso8583

jcbrunh...@gmail.com (Brunhera) — Sat, 07 Nov 2009 01:14:59 UT

I totally agree with you guys. The first step is understand the ISO
format
for both 2 banks. If they indicate field 32 as a bank ID, the problem
is solved.
If not, the only way is making some header information.

Re: [jpos-users] Re: Problem identifying the source of iso8583

chil...@gmail.com (Chhil) — Fri, 06 Nov 2009 08:35:03 UT

As we all know the thousands of variations between various 8583
implementations. To make it scalable you should probably look into
look into getting some sort of custom header prepended by the
middleman that is forwarding the messages to you after acquiring
transactions from the banks.
Or look into getting a connection per bank message.

Re: [jpos-users] Re: Problem identifying the source of iso8583

marksal...@talktalk.net (Mark Salter) — Fri, 06 Nov 2009 08:07:04 UT

Can I ask you start quoting ISO8583 source and versions and variants
please?
Field 2 - often used for PAN - is also usually variable length. So your
statement is wrong I'm afraid.
As David indicates this is not a universal approach - many things will
stop it working. Having said that, it might work for your vendor's

Re: [jpos-users] Re: Problem identifying the source of iso8583

marksal...@talktalk.net (Mark Salter) — Fri, 06 Nov 2009 08:00:01 UT

All interfaces and message structures vary in format and content, often
there are similarities; they are rarely the same, especially at the
interface level.
Why not check both your banks message specification to test this?
At this stage I 'hear' you do believe that ISO8583 defines the field
content and field use. I would humbly suggest ISO8583 defines the

Re: [jpos-users] Re: Problem identifying the source of iso8583

dbergert...@gmail.com (David Bergert) — Fri, 06 Nov 2009 02:47:40 UT

ISO8583 is not a fixed length format it is bitmapped - that bitmap
indicated what fields are or are not present -- then individual fields
can hold different lengths of values -- look at DE 2 or Field 2 for
PAN -- this typically indicates the length of the pan and then then
pan - up to 19 digits -- then there are the different methods of using

Re: Problem identifying the source of iso8583

kelvinwork...@gmail.com (kelvin) — Fri, 06 Nov 2009 02:37:28 UT

Hi Alan,

According to ISO8583 standard, field 1 to field 31 are all fixed
length fields, so I think we may get the content of field 32 only by
just skipping the first 31 fields' total byte length of the iso
message.(Of course, the premise is that all banks would use field 32)

Kelvin

Re: Problem identifying the source of iso8583

kelvinwork...@gmail.com (kelvin) — Fri, 06 Nov 2009 02:22:54 UT

Hi all,

Thanks you all!
Mark's reply is what I am concerning: whether ALL banks would use
field 32?
If anybody who had seen a bank that did not use field 32, please tell
us.

Kelvin

Re: [jpos-users] Re: Problem identifying the source of iso8583

marksal...@talktalk.net (Mark Salter) — Thu, 05 Nov 2009 18:27:04 UT

'We' may find both kelvin's banks don't use field 32 either.
8)

Re: [jpos-users] Re: Problem identifying the source of iso8583

ahonc...@gmail.com (Alan Honczar) — Thu, 05 Nov 2009 18:02:23 UT

In order to discover the bit 32, you have to unpack the message.
Different banks MAY have different packagers...

2009/11/5 Brunhera <jcbrunh...@gmail.com>

Re: Problem identifying the source of iso8583

jcbrunh...@gmail.com (Brunhera) — Thu, 05 Nov 2009 14:55:06 UT

According to the ISO8583 standard, bit 32 must be the bank ID