ATM 911 protocol (banking)
Jerome Jacobsen
However, this is the only newsgroup where I've found any information on
this before.
I'm trying to find information on the Automated Teller Machine 911/912
protocols. Where does one get the specification? I've searched the
internet to no avail. Also, are these industry standard or Diebold
specific? Any info greatly appreciated.
------------------
email: jacobsen<at>aedar<dot>com
Sent via Deja.com http://www.deja.com/
Before you buy.
Shaun Baker
To my knowledge, 911/912 is very specific to Diebold, and the only source
for doco I have ever found is Diebold themselves.They do have a CD-ROM
containing much of the ATM related stuff, including the 911/912 spec, but it
is rarer than toilet paper in the army - if you can get it, let me know how
you managed!
Regards
Shaun
Jerome Jacobsen <jjac...@my-deja.com> wrote in message
news:7tvfmr$pia$1...@nnrp1.deja.com...
Jerome Jacobsen
ATM and host. I've been told there are many protocols for this: IBM
3275 bisync, SNA, TCP/IP, 911/912, MDS1000, and on and on. What I
don't understand is the layering. Which run on top of which? Which
are application protocols? Are there many application protocols or is
there a standard? For example, I assume there is an application
protocol that deals with ATM transactions (e.g. a Verify Withdraw
message).
Utterly confused.
Jerome Jacobsen
jacobsen<at>aedar<dot>com
In article <3803...@news2.prserv.net>,
--
---------------
Shaun Baker
It looks something like this (on traditional OS/2 based ATMs - the ones I am
familiar with)
TCS - terminal control software - top level application layer - handles
display, devices etc - this is the bit that knows about 911/912
CSS - communications subsystem - handles the comms - doesn't know 911/912
but routes data between TCS and devices (including the comms device, cash
dispenser, display etc). TCS writes and reads CSS, as do all the bits of
hardware.
Network protocol driver - your SNA LU0, 3600 loop, TCP/IP, etc
Comms hardware - in the machines I have worked on this has always been async
using a DLC adapter, but it is entirely possible to use X.25 and token ring
hardware.
In a nutshell then - CSS abstracts the comms from TCS using its network
protocol driver. 911/912 is the application layer carrying the transaction
requests/responses (cash withdrawal request). The ATM host (big iron,
Tandem, Stratus or whatever) will also talk 911/912 to control the ATM and
authorise transactions.
I hope this helps.
Shaun
Jerome Jacobsen <jjac...@my-deja.com> wrote in message
news:7u0073$76h$1...@nnrp1.deja.com...
Mike Fry
wrote:
> I'm actually trying to understand the data communications between the
> ATM and host. I've been told there are many protocols for this: IBM
> 3275 bisync, SNA, TCP/IP, 911/912, MDS1000, and on and on. What I
> don't understand is the layering. Which run on top of which? Which
> are application protocols? Are there many application protocols or is
> there a standard? For example, I assume there is an application
> protocol that deals with ATM transactions (e.g. a Verify Withdraw
> message).
To the best of my knowledge (having done a little bit in this area), at
the application level is ISO 8583 Financial Transaction Card Originated
Messages - Interchange Message Specifications. Be aware that although
ISO 8583 is supposed to be an International Standard, both Mastercard
and Visa use slightly different 'interpretations' of the standard. Also,
each financial institution (i.e. Bank) is free to interpret the
specification in their own way, so long as they adhere to the
specification when passing messages through the international networks.
This means that each Bank probably will have their own implementation
when communicating with their own ATMs.
I have C dlls for packing and unpacking the ISO 8583 messages. These are
set up for calling from COBOL programs.
Regards,
MIKE FRY
mailto:mik...@iafrica.com
Shaun Baker
Your name rings a bell somehow.
Standard Bank of SA uses exclusively 912 between their Stratus host and the
ATMs. 8583 is implemented to switch transactions to third parties
(Visa/MasterCard for example). AFAIK, Diebold do not supply an ISO8583
wrapper for their ATM's that run OS/2, but have a later platform that runs
NT (ugh!) and provides more modern, less proprietary protocol support.
Regards
Shaun.
Mike Fry <mik...@iafrica.nospam.com> wrote in message
news:EdHxIHxd9CDV-pn2-Ow732E5yJ1md@minitower...
Jerome Jacobsen
Your info has been very helpful. Thanks. I was wondering if you know
about how ATMs with Smart Card option work. Is there a purse
application on the card that gets updated by the ATM? Is the balance
on the Smart Card passed in any 911/912 messages to the host? It would
seem that the operation with a Smart Card would change the messaging
with the host.
What I'm hoping is that as soon as the Smart Card is placed in the ATM
a message goes to the host identifing the card (e.g. card id#). Then
after the ATM does PIN verification and the user selects a withdraw
transaction, then the next message to the host indicates a withdraw
transaction with current balance and withdraw amount. The host returns
OK. The ATM prompts customer to continue or cancel. Customer
continues and ATM messages host to commit the transaction. Host
messages ATM that transaction is committed. ATM updates balance on
Smart Card. When customer is done with all transactions, ATM messages
host to end session.
In article <3804...@news2.prserv.net>,
--
---------------
jacobsen<at>aedar<dot>com
Shaun Baker
I am afraid the smartcard issue may be out of my depth. The flow of messages
will depend on three things - the chip implementation, the host and the
software on the ATM. I have had a brush with Mondex (MultOS) but not
VisaCash or any of the other 'standard' implementations.
I will mail you directly with some further info since I suspect we are
getting a little off topic here.
Regards
Shaun.
Jerome Jacobsen <jjac...@my-deja.com> wrote in message
news:7u2617$p8a$1...@nnrp1.deja.com...