What is NDC+?

NDC+ is the terminal control application from NCR. It is table-driven and can be customized to meet your own requirements.

NDC+ is the 4th generation version of NDC, and has been developed for NCR’s 4th generation SSTs and Account Services Terminals. It allows you to run 4th generation and Personas terminals in your network, in either Diebold Emulation of Native mode.

Ø   NDC+ Software System

The NDC+ software system is made up of two parts:

Terminal application

Central application

§     Terminal Application

The terminal application gathers transaction details from the cardholder and sends these details in a transaction request message to the Central

When a terminal receives a transaction reply from the central, it completes the transaction.

The terminal application responds to terminal commands from the central, such as go-in-service or go-out-of-service, and requests for information, such as tallies, by sending solicited status messages to central.

An unexpected event can be reported to central using an unsolicited status message.

§     Central Application

The central application receives transaction request messages from the terminal, and determines whether the transaction should be approved or declined. It controls the terminal by sending terminal commands to it and acting on responses received.

The central application must be able to decode and act on the messages it receives from the terminal.

The central application must also be able to code the messages in the form that the NDC+ software in the terminal understands.

Ø   Customization Data

§     State Tables

States control the information-gathering part of cardholder transactions. NDC+ includes a set of standard states.

The state table is made up of the state number, state type and state data. Most state includes a screen number and a next state number as part of the table data.

In the following table, we list each of the standard state table types that control transaction processing.

No.	State Table Type	Description
1	A	Card Read
2	B	PIN Entry
3	C	Envelope Dispenser
4	D	Pre-set Operation Code Buffer
5	E	Four SDK Selection Function
6	F	Amount Entry
7	G	Amount Check
8	H	Information Entry
9	I	Transaction Request
10	J	Close
11	K	FIT Switch
12	_	Expanded FIT Switch
13	L	Card Write
14	M	Enhanced PIN Entry
15	N	Cameral Control
16	P	Courtesy Amount Verification
17	Q	DPM Document Accept
18	R	Enhanced Amount Entry
19	S	Language Code Switch
20	T	Card Read – PIN Entry Initiation
21	W	FDK Switch
22	X	FDK Information Entry
23	Y	Eight FDK Selection Function
24	Z	Extension State
25	B	Customer Select PIN State
26	d…g	Available as identifiers for Exit State
27	I	Audio Control State
28	K	Smart FIT check state

Figure 7-1 NDC+ state table

§     Screen Data

A screen is a string of characters that defines what is to be displayed and where to display it. There are two types of screen:

Customized – screens that you create

Reserved  -- screens that are already defined within the terminal software.

A customized screen is a screen that you create. You decide on the text to be included, and any pictures or logos to be used. The data is downloaded to the terminal in a screen data load message. All the screens that are accessed by the state tables are stored in the screen table. Each screen in the table has a unique number from 000 to 999. It is this number that referenced by parameters in the state tables during transaction processing.

A reserved screen is a screen that is already defined within the terminal software. Reserved screens have four fixed functions, such as display supervisor prompts and menus, and are only displayed at pre-defined times, such as when the terminal is in out-of-service or off-line mode

§     Keyboard Data

The keyboard is an interface between the cardholder and the terminal.  NDC+ supports full touch screen keyboards and four/eight FDKs. It may be customized to suit customers’ requirements.

§     Printer Data

The NDC+ SST software supports printing on five different devices:

Receipt

Journal

Statement

Programmable printing depository

DPM

The data to be printed on a particular printer, or printers, must be placed in a printer data field contained in a Transaction Reply Command Message.

The length of printer data field is variable, and depends on the amount of data and data compression performed, the printer characters, and the overall message length limitation. There are 13 printer data fields.

On the receipt and journal printers, the uncompressed data length is restricted to 500 characters per printer data field.

§     Supervisor Messages

The supervisor messages are output to CRT, VEROP, basic/enhanced operator interfaces, and the receipt and journal printers. These supervisor messages are rules as following:

Character set

Control codes

Screen size limitations

CRT layout

Printer layout

Automatic screen editing

Media status messages

Test cash report

Check CDM report

Note: It is not supported by the YDC.

§     Configuration Parameters

In addition to states, screen and printer data, you can further customize the way the terminal operates by downloading configuration parameters.

The configuration parameters are downloaded to the terminal in the following two messages:

Configuration parameters load message – this is a message compatible with Diebold and only contains parameters necessary for Diebold Emulation mode.

Enhanced configuration parameters load message – this messages contains the full range of configuration options and timers for Native mode.

§     Financial Institution Table(FIT)

The financial institution table(FIT) is an important part of the customization data for an NDC+ system. FITs may be also downloaded to the terminal by a message from central. The FIT contains specific information about how a particular institution’s transactions should be processed.

Every institution the terminal supports must have a FIT. Institutions which have more than one type of card must have a FIT for each card type.

When a card is read, the FIT is searched to find the FIT entry which matches the FIID on the card. Parameters in this FIT entry and following linked FITs are then used for all subsequent PIN processing.