[LLLLLVAans 99999 00886] 127.022.ThirdPartyBillPayment
[<ThirdPartyBillPayment>
<BillPaymentRequest>
<ReferenceId>1111111111</ReferenceId>
</BillPaymentRequest>
</ThirdPartyBillPayment>]
What I noticed is that 127.022.ThirdPartyBillPayment appears to have ThirdPartyBillPayment as another subfield.
Kindly assist as I do not know how to successfully implement this.
Thank you.
127.22 has a fromat tag length value and if you have their SDK documentation please refer to it.
-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
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.
For more options, visit https://groups.google.com/groups/opt_out.
Please refrain from posting copyrighted material on this list.
Andy
I have gone through the documentation and I seem to have a fair idea of what is required.The problem I have is how to set additional subfield such as 127.22.ThirdPartyPayemnt using JPOS.The documentation extract can be seen below:Description
This is a Postilion specific addition to the ISO 8583 standard.
This field uses a key/value pair structure to represent data. The idea behind the field is to provide a flexible mechanism with which to transport data through Postilion. There is therefore no limitation to what either the key or value may contain, provided of course that the format of the field is adhered to.
The physical layout of the field is as follows:
1 byte length indicator of the key length indicator
Length indicator of the key
Key
1 byte length indicator of the value length indicator
Length indicator of the value
Value
The table above describes the physical layout of a single key/value pair, it is therefore repeated for each key/value pair in the field. There is no limitation to the number of key value pairs that may be used, besides the overall field length.
Note: As of Postilion 4.0 service pack 5, this field is stored in the Postilion transaction table.
Postilion defines DTDs for the following:
XML that conforms to the structure described in the these DTDs is inserted into this field using a tag comprising the DTD name prefixed with the string
- StatementData
- CardManagementUpdateData
- CardManagementUpdateLoad
- PrepaidMerchandise
- PurchasingCardData
- FleetCardData
- CheckData
- AirlineItineraryData
- VehicleRentalData
- LodgingData
Postilion:. For example, when inserting statement data in XML form, the key will bePostilion:StatementDataand the value associated with it would be the well-formed XML that conforms to the StatementData DTD.Postilion defines the following key/value pairs for use with this field.
Key
Description
Present in message
Postilion:UserDomain
The 'value' consists of the domain of the user currently logged in to the PostCard User Interfaces.
0320, 0322
Postilion:UserID
The 'value' consists of the ID of the user currently logged in to the PostCard User Interfaces.
0320, 0322