For developers maintaining older APTRA Advance systems, the guide dedicates Chapter 11 to migration strategies.
Validating a national identity number against a localized database before proceeding to the standard cash withdrawal cycle. Open-Enhanced NDC (OEN)
When standard state flows are insufficient for complex logic—such as integrating a third-party contactless biometric reader or barcode scanner—developers must use .
: Allows developers to extend standard NDC functionality with custom logic.
Developers use PC-based software simulators (such as NCR's APTRA Simulator or third-party tools like Radia and Paragon) to emulate the ATM runtime environment. These tools let you visually inspect states, mock peripheral hardware responses (e.g., simulating a jammed presenter), and trace network payloads. Analyzing Log Files aptra advance ndc developer-s guide
When troubleshooting, the primary source of truth is the local application logs.
Sensitive cardholder data must never be written to custom log files generated by custom exit routines.
Execute third-party web services or localized business logic within the ExTask.
: Instructions for setting up hardware and software environments, including support for Windows-based operating systems. Transaction Development For developers maintaining older APTRA Advance systems, the
Advance NDC operates using a state table driven approach. The host downloads a configuration file containing sequential operational states to the ATM. Each state defines: The screen data to display to the user.
Key Takeaway: The guide assumes you understand NDC schemas ( AirShoppingRQ , OrderCreateRQ ). Its value lies in showing you how APTRA Advance wraps these schemas with proprietary headers and security artifacts.
Advance NDC relies on a host-controlled architecture. The ATM itself does not hold business logic or make transactional decisions. Instead, it behaves as a state machine that executes specific commands sent by the host.
Detail the API communication between the APTRA software and the hardware drivers. Use these if a device fails to react to an NDC command. 5. Security Best Practices : Allows developers to extend standard NDC functionality
: Options like Option 76 for controlling note dispensing behavior.
The guide recommends configuring HTTP client pools for outbound NDC calls:
Always check the REAR.LOG or JOURNAL files for a play-by-play of the hardware and software actions.