When a user requests a service, the ATM compiles a transaction request packet. A typical message layout includes: Field Segment Description Example Data Identifies the type of message 1 (Consumer Request) Logical Unit Number (LUN) Unique identifier assigned to the ATM terminal 0001 Time Variant Number Security tracking number against replay attacks 3132 Top of Buffer (FS) Field Separator delimiter ASCII 0x1C Card Data String Track 2 data extracted from the magnetic stripe or EMV chip
: Instructions on using Web Exit technology to connect to external web services for non-cash transactions like bill payments or ticket sales, effectively stepping outside the standard NDC transaction flow.
ExitState() : Cleans up pointers and hands control back to the core NDC execution loop.
Developers use specific screen IDs to define layout, text, and interactive elements.
For software engineers, developers, and system integrators tasked with creating custom ATM applications, understanding the is essential. This article serves as a comprehensive guide to mastering this powerful application development environment. 1. Introduction to APTRA Advance NDC aptra advance ndc developer-s guide
Arrays that check whether a card's track data matches specific criteria to allow or deny a transaction locally. Consumer Request Messages (ATM to Host)
State Type A waits for a card insertion, reads the data, and determines the next step. A standard configuration string follows this visual structure:
: Technical details on how the software interacts with physical components like card readers, cash dispensers, and printers.
resp = requests.post(TOKEN_URL, data= "grant_type": "client_credentials", "client_id": "YOUR_ID", "client_secret": "YOUR_SECRET" ) token = resp.json()["access_token"] When a user requests a service, the ATM
Terminal responses to specific host commands (e.g., confirming a configuration download).
Initialize() : Allocates memory and maps peripheral device hooks.
Never log sensitive data (PINs, Track 2) in developer trace files.
When a user requests a withdrawal, the ATM constructs a Transaction Request message containing: Developers use specific screen IDs to define layout,
The ATM uses public keys to verify card authenticity. EMV Configuration Tables
APTRA Advance NDC is a robust, state-machine-driven platform that provides a secure and configurable foundation for self-service banking applications. This guide has outlined the essential components, message flows, and configuration principles that form the basis of any development project. For custom applications, the platform offers a powerful Exit State framework, with Web-exits allowing you to seamlessly integrate external web services into the native NDC transaction flow.
The "Aptra Advance NDC Developer's Guide" is a valuable resource for developers who need to integrate with the Aptra Advance NDC platform. The guide provides comprehensive coverage of the platform's APIs, data model, and security features. However, it assumes prior knowledge of APIs and integration concepts, and may not be suitable for readers who are new to these topics. Overall, a well-structured and informative guide that should help developers successfully integrate with the Aptra Advance NDC platform.
Customizing the user interface (UI) is a crucial part of the development process.
Tracks low-level application errors, system crashes, and memory exceptions.