ISO87 GICC - DE55 - LTV

[Stefano Bonù]

Hi,

we are evaluting JPOS product in order to manipulate messages in ISO87 GICC protocol. In particular field DE55 has the LTV format. Is it possible to manage it using JPOS ?

In the source we found the org.jpos.tlv% packages and classes, but we haven't found anything about LTV.

Regards

Stefano

[chhil]

Hi,
We have written a custom parser for this. We treat the field as opaque,  that is,  get the data and parse it using your custom parser.
It's pretty straight forward writing one.

I haven't looked at some of the  current additions for emv support to jpos, it may be available.

-chhil

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: sa...@jpos.org
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to jpos-...@googlegroups.com
To unsubscribe, send email to jpos-users+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jpos-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/7906f182-5663-4f25-9b14-7bab0dc8e611%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Alejandro Revilla]

Perhaps something like IFEP_LLCHAR is what you need:

    https://github.com/jpos/jPOS/blob/master/jpos/src/main/java/org/jpos/iso/IFEP_LLCHAR.java

In order to deal with GICC, I had to create a special subfield packager for field 60 and I use classes based on IFEP_LLCHAR (had to create an IFEP_LLLCHAR and IFEP_LLLBINARY). I'm not dealing with bit 55 though as in my case I'm dealing with MOTO transactions.

--

@apr

--

[Stefano Bonù]

many thanks for answering. So that means that it's better to create a custom subfield packager for field 55 instead of treat it as opaque and manipulate it using something like TLV methods ?

About IFEP_LLLCHAR and IFEP_LLLBINARY: does it mean that they are/will available in the JPOS library ?

Thanks

You received this message because you are subscribed to a topic in the Google Groups "jPOS Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jpos-users/JN7nVBTbhXc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jpos-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DmTe1efwD732M1ugr9WUn516%2B-3HRBt9X8FXUKjMK8p_g%40mail.gmail.com.

[chhil]

​​As I understand it, IFEP_LLCHAR and its variants, will handle a single LTV field.
The problem will arise when you have a field with multiple LTVs in it and the number of LTVs are variable (emv data).
Someone can please correct me if I am wrong but you will need to go the opaque route.

The custom ones with 3 L's are not in the repo, which means you would need to write them yourself (unless Alejandro decides to contribute it :) ).

-chhil​

 

To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAMO8mHbW0Z8de%2BXMvLzNQ4n2r0irn4S2FOE7byQuf30Vmnz-eQ%40mail.gmail.com.

[Alejandro Revilla]

Just contributed them, see https://github.com/jpos/jPOS/commit/c615a1d

I’m forcing a nightly build, so in a few minutes you’ll get those in 2.0.1-SNAPSHOT (off the jPOS maven repo, http://jpos.org/maven).

I know field 60 is not what you want, but perhaps it helps you as an example, the configuration would look like this:

 <isofieldpackager id="60" length="999" name="GICC 60" class="org.jpos.iso.IFE_LLLBINARY" 
     packager="org.jpos.iso.packager.GICCSubFieldPackager">
      <isofield
          id="0"
          length="9"
          name="DUMMY"
          class="org.jpos.iso.IF_CHAR"/>
      <isofield
          id="30"
          length="4"
          name="CVV2"
          class="org.jpos.iso.IFEP_LLLBINARY"/>
      <isofield
          id="31"
          length="49"
          name="Address Verification Data Request"
          class="org.jpos.iso.IFEP_LLLBINARY"/>
      <isofield
          id="32"
          length="2"
          name="Address Verification Data Response"
          class="org.jpos.iso.IFEP_LLLBINARY"/>
      <isofield
          id="35"
          length="30"
          name="Additional Merchant Data"
          class="org.jpos.iso.IFEP_LLLBINARY"/>
      <isofield
          id="36"
          length="30"
          name="Additional Cardholder Data"
          class="org.jpos.iso.IFEP_LLLBINARY"/>
      <isofield
          id="37"
          length="24"
          name="Dynamic currency conversion data"
          class="org.jpos.iso.IFEP_LLLBINARY"/>
      <isofield
          id="40"
          length="2"
          name="ECommerce Indicator"
          class="org.jpos.iso.IFEP_LLLBINARY"/>
      <isofield
          id="41"
          length="2"
          name="Recurring or Installments"
          class="org.jpos.iso.IFEP_LLLBINARY"/>
      <isofield
          id="42"
          length="0"
          name="UAT Indicator"
          class="org.jpos.iso.IFEP_LLLBINARY"/>
      <isofield
          id="50"
          length="999"
          name="Duplicate data"
          class="org.jpos.iso.IFEP_LLLBINARY"/>
      <isofield
          id="61"
          length="20"
          name="XID"
          class="org.jpos.iso.IFEP_LLLBINARY"/>
      <isofield
          id="62"
          length="20"
          name="CAVV"
          class="org.jpos.iso.IFEP_LLLBINARY"/>
      <isofield
          id="63"
          length="32"
          name="UCAF"
          class="org.jpos.iso.IFEP_LLLBINARY"/>
 </isofieldpackager>

You may want to take a look at the contributed package org.jpos.emv to pick some inspiration too, I didn’t use that one yet, but Vishnu may be able to help (see the original pull request #52 https://github.com/jpos/jPOS/pull/52)

​

BTW, also added a GICChannel, that you may have to use (along with one of the OneShotChannelAdaptors)

--

@apr

To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAPazefD0bN3_XO4%3DyD-sn8%2BpoVKK06tJ_-WuAnL6Hrt24dMBZQ%40mail.gmail.com.

[Stefano Bonù]

many thanks ! We are going to download new snapshot version, try with your suggestion and we'll let you know asap.

bye

Stefano

To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAAgSK%3D%3DAyWQ4CLXHQaXFGiDJ_wFrcNoEbKw_Q2JFzdUrV34o2w%40mail.gmail.com.

[Stefano Bonù]

hi again,

snapshot version succesfully installed. With the new updates we are able now to handle GICC special format for field 55 (and 60) and we keep on testing.

thanks a lot

[Alejandro Revilla]

Great, good luck with your tests!

While implementing GICC, I found very cryptic the flow related to field 57, encoding is easy, but the re-synchronisation dance using 0800s in the middle of your flow is annoying, to say the least. Hope you plan for that in your higher level flow implementation.

--

@apr