>> Postilion knowledge could help out with a case I am having. >> >> >> On the client's environment, I turned on Terminal trace to monitor >> transactions

Mark > Postilion just ends up with a lot of 91 response codes, which means they > didn't get a response back from the service within the expected time. I'm > using all

act of Postilion being recycled (are these for maintenence of some sort ?) would start a new connection but also allow the old to breifly drain so that no in-flight transactions are bothered

request to postilion. > > Kind regards > > Flavian > > On Tue, Nov 7, 2023 at 9:41 AM 'Mark Salter' via jPOS Users < > jpos-users@googlegroups.com

got from Postilion. And you would use that key, to translate the pin blocks to your zone key for validation if you are an issuer. Or to translate the PIN blocks captured by the terminal

blocks in Postilion HSM and configure key > exchange? > > -- > -- > jPOS is licensed under AGPL - free for community usage for your > open-source project. Licenses

How do i go about this,SSL configuration on ACI Postilion usign ATALA HSM?

experience with Postilion so here is my take on it. > > The flow is usually > external network ->source node -> Postilion Transaction Manager -> Sink > Node ->

when i run locally both client and server everything works fine . pls see below : 1. client app connected successfully. 2. client send msg server

of you postilion messages that works. Spot the differences and fix. Or re-read the Thales spec and understand the message formats. In your CA command what made you choose 49? I understand

I am not sure what you changed but the new packager and hex dump you previously provided still don't work in the test code I had provided. There

seems tatt postilion instance is not expectin ICCData in xml format >>>> (how you are trying to send it), but in bitmap format. >>>> >>>> Hope

Thanks @chillum@gmail.com, TransactionManager is what I am looking at right now. Still looking through the documentation to understand it. Venon

in a Postilion ISO8583 message. ------------- Hello , anyone who can assist with how a packager that can handle this type of message: 127.022.VasApplication [vmobile-ussd] 127.022

my clients POSTILION >> >> 49534F383538332D31393933303231303030303030 >> >> >> >> >> >> * * >> >> >> >

Postilion packager and NACChannel (2 byte length header) usually go hand in hand. What channel are you using? Make sure sender and receiver are configured to use the same channel (how

wrote the Postilion channel/packager in 1999, for Postilion 3.5 ISOBridge. I can imagine much has changed since then :) If it's not too much trouble, please create a new version

lets say Postilion. How do I implement the > reverse. Is there any development around this. Any sample code. > > Basically when Postilion requests for a key exchange message

be a Postilion issue. I would suggest you have them look into it. Before doing that make sure you used the NACChannel to send this message so that the appropriate 2 byte length header was

Follow this thread, it too is position related and somewhere in there there is a how to do hexdump analysis. https://groups.google.com/forum/m/?

talk to Postilion guys. You can dump the hexdump and parse the message by hand for bitmap for field 127 and see what bits are enabled. -chhil On Thu, Sep 19, 2019 at 3:20 PM ccav tech wrote

From your postilion logs, field 127 starts with >>>>> >>>>> [LLVAR ans ..32 010] 127.002 [0000348641] >>>>> >>>>

provided by Postilion for the interface you are connecting to and determine the channel to use. Either you will be able to pick one JPOS provides or you will need to extend JPOS' basechannel

no need for StringBUilder if using Collectors.joining() public static byte[] decodeHexDump(String s) { return ISOUtil.hex2byte( Arrays.stream(s.split(

thanks Andres,its working now. On Tue, Jun 18, 2019 at 3:52 AM Andrés Alcarraz wrote: > Hi ccav > > You are not defining the bitmap subfield

>> postilion 8583 packager. Call it finnacle8583 or something. >>> >>> Take some hints from the sample code provided on how to use loggers and >>>

asked the Postilion side on what is wrong? >> Have you looked at your Postilion spec and constructed your message as >> required? >> >> You cannot put a snippet

integration with Postilion host (TermApp.ISO interface) , there is a requirement to send the DE48 sub fields in the request. I had defined the sub field packager and i am able to construct

ISOMsg in postilion format using PostPackager. While creating isomsg, getting exception while adding the field 127 as it is subfield. Below is code snippet: ISOMsg isoMsg = new ISOMsg

> on postilion card > > On Tuesday, January 2, 2018 at 11:55:22 PM UTC+1, aissa wrote: >> >> Hi, >> Run a test case with pin verification on postillon and