For security reasons, a touch FDK (Function Display Key) cannot be used as the "Enter" key in the PIN Entry State.
The Config ID is the "handshake." It tells the host which version of the state/screen database the ATM is currently running. If the IDs don’t match, the host will typically trigger a full download of the configuration. State Tables
Standard Advance NDC configurations handle typical cash withdrawals and balance inquiries perfectly. However, implementing unique features like cardless transactions, dynamic currency conversion (DCC), or custom marketing graphics requires explicit developer intervention. Modifying Configuration Files
Mapping out state transitions on paper or in architecture diagrams.
You can pause the execution of an NDC state to run a local executable or script (e.g., verifying a local biometric scan) before returning control to the standard host flow. Graphic User Interface (GUI) Customization aptra advance ndc developer-s guide
: Guidance on using the Aptra Advance Ndc Developer-s Guide to create custom states, screens, and operational logic tailored to specific banking needs. Key Technical Sections
: Instructions for integrating APTRA Advance with host networks, including message formatting and state table management.
Financial Institution Tables define how the ATM parses tracks on a card. Ensure your offset and length values are precise to avoid card-reading errors.
When standard NDC logical states are insufficient, developers can program custom "Exit States." These states hand over execution control from the main NDC engine to a localized object-oriented script or compiled C#/.NET library. For security reasons, a touch FDK (Function Display
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)
Encrypt all inbound and outbound host communications using TLS 1.3 to prevent man-in-the-middle packet manipulation.
Unlike older protocols, APTRA Advance NDC emphasizes rapid deployment of new functionality through: Enhanced Configuration Loads: Technical details on timer settings (e.g., barcode reader timeouts) and printer-independent margin controls Graphical Interface Management: Guidance on configuring rich multimedia presentations customizing screens to improve the consumer experience. Security Integration: Specifications for meeting PCI PA-DSS validation, EMV Level 2 certification, and supporting Remote Key Management Arthur Van Der Merwe Related Documentation Developers often use this guide in conjunction with: Advance NDC Developer's Guide | PDF - Scribd
The system's behavior is almost entirely defined by configuration parameters, which are stored in configuration files. This design allows you to modify functionality without recompiling core software, enabling rapid deployment of new features. You can pause the execution of an NDC
What or custom extensions (like cash recycling or biometrics) are you trying to implement? Share public link
Communication happens through specific message classes. As a developer, you will primarily work with: A. Terminal-to-Host (Requests)
The logic flow of the application (e.g., PIN entry, amount selection).