Application
Java / Spring Boot microservices and Node.js services for ATM driving, the NDC codec and the switch — containerised, on RHEL or Ubuntu LTS.
Gen ATM / Platform
Driving, routing and the estate underneath.
Gen ATM NGK 2.0 is the layer between your terminals and everything else: it speaks NDC to the machine, REST and ISO 8583 to the platform, and configuration to the people who run the estate.
7.1 · Functional specification
What the product does.
| Capability | Specification |
|---|---|
| ATM driving | NDC-based driving with state-machine execution, configurable English and Arabic screen flows, supervisor operations, parameter and configuration download. |
| ATM Service | Handles ON-US continuation to CARD PRIME D 3.0; forwards OFF-US outgoing authorizations directly to T-NET; consults the CMS laterally for cardholder data, status and controls. |
| Estate management | Terminal master data, grouping by region and branch, in and out-of-service control, software and configuration distribution. |
| Device & cash monitoring | XFS-level status per device; per-cassette currency, denomination and thresholds for withdrawal, depositor and recycler units. |
| Electronic journal | EJ synchronisation, central text and card search, retention policy, replenishment recognition. |
| Alerts, SLA & reports | Threshold and event rules with severity, routing and escalation; availability excluding planned maintenance; scheduled report pack. |
Estate
A terminal is a record before it is a machine.
Everything the console does — grouping, distribution, thresholds, screen flows, currency — hangs off terminal master data. Get that right and the rest is configuration.
- Terminal master data: vendor, model, location, branch, region, institution
- Grouping by region, branch or arbitrary label; actions apply to a group
- In and out-of-service control with reason codes, recorded in the journal
- Software and configuration distribution by group, with rollback
- Per-ATM provisioned dispense currency — a single terminal never dispenses two
- Multi-institution: every record carries an institution key; back-office roles are scoped to it
Transaction sets
- Phase 1 · ON-US
- Balance enquiry · Fast cash · Withdrawal · Mini statement · Deposit
- Phase 2 · OFF-US out
- Balance enquiry · Withdrawal
- Phase 2 · OFF-US in
- Withdrawal · Balance enquiry, per scheme rules
- Card types accepted
- Contact · chip · contactless · NFC
- Languages
- English and Arabic, every screen
Currency
One ATM, one dispense currency.
The base currency is the Yemeni Rial, with SAR and USD supported across the platform. Dispense is different: each terminal is provisioned with exactly one currency, and mixed-currency dispense from a single ATM is disabled by design rather than by policy.
| Item | Profile |
|---|---|
| Base currency | USD — Yemeni Rial |
| Multi-currency | USD, SAR, USD |
| ATM dispense model | One provisioned dispense currency per ATM. A single ATM dispensing multiple currencies is strictly disabled. |
| FX | Applied on OFF-US outgoing per scheme or network rates; core banking posting converted per bank policy. |
| Languages | English and Arabic on ATM screens, KIOSK, back office and notifications. |
4.3 · Technology baseline
What it is built on.
Data
PostgreSQL 16 by default, Oracle 19c supported. Separate schemas for card, customer and access, transactions and switching, terminal management and audit.
Messaging & cache
Kafka carries terminal status, events and monitoring. Redis holds sessions and fast-cache lookups on the authorization path.
Interfaces
REST over HTTPS with OpenAPI, and ISO 8583. The API reference and data dictionary are issued as companion volumes.
Next step
Bring your estate onto one console.
Send us your terminal mix, cassette configuration and per-ATM currency plan. We will come back with a driving and monitoring design, a sizing note and a delivery schedule.