Transaction: BalanceInq

[queo1987]

Dear,
Now, I am doing with a transaction is Balance inq, withdraw,....
I want to create message iso8583 verison 1987 for transaction balance inq.
how to create it?
please help me
if you have any document ,please share me
Thank a lot
:drunk:

-----
----Cheer :drunk: ---
mail: queo...@gmail.com
Yahoo: queo1987
--
View this message in context: http://old.nabble.com/Transaction%3A-BalanceInq-tp26489781p26489781.html
Sent from the jPOS - Users mailing list archive at Nabble.com.

[Mark Salter]

queo1987 wrote:
> Now, I am doing with a transaction is Balance inq, withdraw,....
> I want to create message iso8583 verison 1987 for transaction balance inq.
> how to create it?

You will need to select or make a packager for jPos that matches the
network interface you wish to send the message to. Each interface may
conform with iso8583, but the values they use in the various fields
often varies.

> if you have any document ,please share me

Ask your target systems owners for their documentation?


--
Mark

[queo1987]

Dear,
How to know which fields are needed for each transactions.Example is
BalanceInq,Withdraw,...?
I don't know means of fields in JPOS. please show me?

Please help me.
Thanks.

queo1987 wrote:
>
> Dear,
> Now, I am doing with a transaction is Balance inq, withdraw,....
> I want to create message iso8583 verison 1987 for transaction balance inq.
> how to create it?
> please help me
> if you have any document ,please share me
> Thank a lot
> :drunk:
>


-----
----Cheer :drunk: ---
mail: queo...@gmail.com
Yahoo: queo1987
--

View this message in context: http://old.nabble.com/Transaction%3A-BalanceInq-tp26489781p26545427.html

[Mark Salter]

queo1987 wrote:
> How to know which fields are needed for each transactions.Example is
> BalanceInq,Withdraw,...?
> I don't know means of fields in JPOS. please show me?

I cannot show you.

The documentation for the interface/system you wish to connect with
holds the details.

That system's use of the various fields and values within those fields
is the detail you seek.

What system are you connecting to? Does it or the company have a name?
Have you asked them how to 'talk' to their system?

--
Mark

[queo1987]

Dear,
Thank you for your reply.
I can explain that I am writing services for a bank as:
BanlanceInq,Withdraw,ChangePin,Transfer,...
My system is using IFX Message to comunicate from Termnal Client to Switch,
but can't go out internet bs not wright ISO 8583 standard.
IFX is active ok. and i and converting from ifx to iso8583. but i don't know
where to start.
So, I need know that iso8583 have what fields coresponse with ifx.

Please show me, which fields for each transactions.

Pleas help me.

> --
> 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

>
>


-----
----Cheer :drunk: ---
mail: queo...@gmail.com
Yahoo: queo1987
--

View this message in context: http://old.nabble.com/Transaction%3A-BalanceInq-tp26489781p26568343.html

[chhil]

Do you have the IFX specs? If not they are freely downloadable from the web. You may also need IFX specs of the message coming from the ATM as people usally extend the standard IFX to add their services to it.

e.g. you will be getting IFX  Bank service requests of Fundstransfer or a DebitAdd request.

You will need the ISO8583 spec  that you will be converting to, this will give you data elements that should be sent to the entity you are talking to.

e.g. it will indicate that data element 3 is a processing code and is fixed length of 6 ascii,

Data element 2 is the pan and is in LLVar ascii.

Then you will need to determine the channel of communication between you and the entity i.e. its eaw TCP with some length 

bytes appended to the stream.

Getting down to the mapping:

When you see a debit add IFX , you would get the "CardAcctId" that contains the card num  and the account type would contain thing like DDA. An IFX element of DebitAuthType would indicate the transaction type e.g. cash withdrawal for instance.

So from above information you would get a pan (data element 2), processing code code (data element 3 ).

Processing code is made up of transaction type, from account type and to account type. transaction type would be  cash witdrawal mapped to your ISO8583 value of withdrawal. From account would be a ISO8583 mapping of DDA. To account can be a default value as determined by your ISO8583 spec.

So you wold basically get all the elements that you need to send in an ISO8583 message and get appropriate values for it from your IFX message. We cannot tell you what the mapping can be as it varies from each entities implementation of ISO8583.

Also everyone usally customizes their IFX too so keep that in mind. Also I believe IFX can send a bunch of services in one call so you would have to split those up into separate ISO8583 requests.

-chhil

[queo1987]

Dear,
Thank your for your answer.
Example: Withdraw transaction. Iso8583 needs some field as: Message type
(0200), PAN (field 2), Processing Code (field 3: 010000). but DebitAuthType
of IFX is "DDA" not NUmber . It is not suit.
Please help me.

>> jpos-users+...@googlegroups.com<jpos-users%2Bunsu...@googlegroups.com>

>> > For more options, visit this group at
>> > http://groups.google.com/group/jpos-users
>> >
>> >
>>
>>
>> -----
>> ----Cheer :drunk: ---
>> mail: queo...@gmail.com
>> Yahoo: queo1987
>> --
>> View this message in context:
>> http://old.nabble.com/Transaction%3A-BalanceInq-tp26489781p26568343.html
>> Sent from the jPOS - Users mailing list archive at Nabble.com.
>>
>> --
>> 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<jpos-users%2Bunsu...@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 "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
>


-----
----Cheer :drunk: ---
mail: queo...@gmail.com
Yahoo: queo1987
--

View this message in context: http://old.nabble.com/Transaction%3A-BalanceInq-tp26489781p26577012.html

[David Bergert]

You might want to considering reviewing and or using the jpos CMF message format which is based on ISO 8583 v2003.

http://jpos.org/blog/2009/08/jpos-cmf/
'
a Balance Inquiry Transaction is defined in it as well.

David Bergert, CISSP, CISA, CPISM/A
www.paymentsystemsblog.com

[chhil]

DDA is a string and you would map it to checking account type in 8583.

Pan could be obtained from the "CardAcctId".

-chhil

[queo1987]

Dear,
Thank you for your reply.

I will explain more clearly. My mind is about data type between IFX and
ISO8583. The most, ISO8583 field is number type and IFX is not. How to
convert data type from ifx to iso.
Example: Field 3 of iso: processing code (data type:N3) but ifx's
DebitAuuthMod (datatype: String).
How to convert? and some else others field......
Thank a lot

>> <jpos-users%2Bunsu...@googlegroups.com<jpos-users%252Buns...@googlegroups.com>

>> >
>> >> > For more options, visit this group at
>> >> > http://groups.google.com/group/jpos-users
>> >> >
>> >> >
>> >>
>> >>
>> >> -----
>> >> ----Cheer :drunk: ---
>> >> mail: queo...@gmail.com
>> >> Yahoo: queo1987
>> >> --
>> >> View this message in context:
>> >>
>> http://old.nabble.com/Transaction%3A-BalanceInq-tp26489781p26568343.html
>> >> Sent from the jPOS - Users mailing list archive at Nabble.com.
>> >>
>> >> --
>> >> 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<jpos-users%2Bunsu...@googlegroups.com>

>> <jpos-users%2Bunsu...@googlegroups.com<jpos-users%252Buns...@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 "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<jpos-users%2Bunsu...@googlegroups.com>
>> > For more options, visit this group at
>> > http://groups.google.com/group/jpos-users
>> >
>>
>>
>> -----
>> ----Cheer :drunk: ---
>> mail: queo...@gmail.com
>> Yahoo: queo1987
>> --
>> View this message in context:

>> http://old.nabble.com/Transaction%3A-BalanceInq-tp26489781p26577012.html
>> Sent from the jPOS - Users mailing list archive at Nabble.com.
>>
>> --
>> 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<jpos-users%2Bunsu...@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 "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
>


-----
----Cheer :drunk: ---
mail: queo...@gmail.com
Yahoo: queo1987
--

View this message in context: http://old.nabble.com/Transaction%3A-BalanceInq-tp26489781p26585133.html

[David Bergert]

You first need to identify what IFX Transaction you want to convert - and then use a sample message for this upcoming exercise - from there you need to build an ISO 8583 message - I would start on paper and do a mapping exercise that performs the following:


1) Find the ISO message that closely fits your IFX tran type.
2) What data elements or fields exist in a IFX Transaction that are common, different, or exist in one but not both - between IFX and ISO ?
3) Which are similar but will have values that need to be translated or based on software logic or lookup tables ? like you asked in your email below.
4) What values are Constant for all messages, Constant per entity (Issuer,Merchant, Terminal,Acquirer - these could be configuration based.)-, and are based on the data mappings that you define above.

Once you perform this analysis - you can write software translation routines and build and use lookup tables as well as other helper methods to convert an IFX to ISO.

The answer to your question is that you need to perform an analysis and document the variances and data elements - and perform a mapping exercise and write classes and methods to support the translation.

David Bergert, CISSP, CISA, CPISM/A
www.paymentsystemsblog.com

[queo1987]

Dear,
Today, I start with first message with ifx to iso8583. I have listed a
following fields:

Message: BalanceInqRq (IFX -->ISO): Fields of ifx depends on fields of
iso8583 (v1987)
===================================================================
IFX object include :
-SigonRq:
+SignonMagPIN (Signon with a magnetic stripe card and PIN pad)
CardMagData (Card Magnetic Stripe Data): MagData2
PINBlock (Pin pad data)
+ClientDt (Client date time)
-DebitInqRq
+RqUID
+ DepAcctId (AcctId,AcctType,BankInfo)
Require: RqUID,CardAcctId



MTI: 0200
-ISO001: bitmap (don't know)

ISO IFX
-ISO 002-------------------------------MagData2
-ISO 003(N6)-------------------------------DebitAuthType (not suit about
data type).Help
-ISO 004 (n12)-------------------------------Amt
-ISO 007-------------------------------ClientDt
-ISO 011-------------------------------RqID
-ISO 012-------------------------------ClientDt
-ISO 013-------------------------------ClientDt
-ISO 015-------------------------------ClientDt
-ISO 018 (n4)-------------------------------TerminalType(Character). HELP
-ISO 022-------------------------------??? (HELP)
-ISO 025-------------------------------?????? (HELP)
-ISO 032------------------------------- BinData(=> BIN)
-ISO 033-------------------------------????
-ISO 035-------------------------------MagData2
-ISO 037-------------------------------??????
-ISO 041-------------------------------TerminalId
-ISO 043-------------------------------NetworkOwner,City,PostalCode
-ISO 049-------------------------------CurCode
-ISO 060-------------------------------??????
===================================================================

There some field in object ifx not suit with field of iso message. Help me
Please help me.
Thank a lot

View this message in context: http://old.nabble.com/Transaction%3A-BalanceInq-tp26489781p26601336.html

[Mark Salter]

queo1987 wrote:

> There some field in object ifx not suit with field of iso message. Help me
> Please help me.

Please read and follow the advise already kindly given by David and Chhil.

The good news is that between them they have told you all you need, and
have even given you the steps you need to take. To ignore this guidance
and choose to plead for assistance is the wrong approach.

The bad news is *you* are going to have to do some work. There is no
fixed translation from IFX to ISO8583. This is because IFX and ISO8583
implementations can and do vary from interface to interface. You don't
appear to have the specific details of your 'from' and 'to' interfaces,
so this is where you need to begin.

--
Mark