ATM estate
EPP key injection under dual control with the ATM vendors, XFS validation per model, NDC download verified, EJ format confirmed for each vendor.
Gen ATM / Integration
Integration is a project, not a footnote.
Every external interface gets its own plan, its own environments, its own test cases and its own exit criteria. The workstream runs in parallel with the product phases and gates each go-live.
4.2 · Communication matrix
What talks to what.
| Source | Destination | Protocol | Purpose |
|---|---|---|---|
| ATM | Gen ATM NGK 2.0 ATM Service | NDC over TCP/TLS | Terminal driving, transactions, EJ |
| ATM Service | CARD PRIME D 3.0 | REST / internal ISO 8583 | Cardholder, status and limits lookup (lateral) |
| ATM Service | T-NET | ISO 8583 / internal API | ON-US continuation, OFF-US outgoing forwarding |
| T-NET | Scheme / network | ISO 8583 certified link | OFF-US incoming and outgoing, clearing |
| CARD PRIME D 3.0 | HSM | Host command channel | PIN, CVV and key operations |
| CARD PRIME D 3.0 | SMS / e-mail gateway | SMPP / SMTP / REST | Advice, OTP, alerts |
Workstreams
Nine of them, each with an owner.
| Workstream | Scope | Interface | Responsibility |
|---|---|---|---|
| ATM (NCR, GRG) | Configuration, NDC download, EJ formats, EPP key injection, XFS validation | NDC / XFS | TantraFino + ATM vendors |
| HSM | Readiness, key ceremonies, PIN and CVV services, key loading | Host commands | TantraFino + HSM vendor |
| Core banking | Authorization, posting, reversals, GL mapping, end of day | ISO 8583 / REST | TantraFino + CBS vendor |
| Scheme / network | Incoming and outgoing authorization and clearing certification | ISO 8583 certified | TantraFino + scheme |
| AML | Screening hook, alert routing | REST / ISO hook | TantraFino + AML vendor |
| SMS / e-mail | Advice, OTP, alerts | SMPP / SMTP / REST | TantraFino + provider |
| KIOSK | Onboarding, KYC and issuance journey | REST | TantraFino + KIOSK vendor |
Certification
What has to pass before anyone goes live.
Scheme
Certification for OFF-US incoming and outgoing authorization and clearing, scheduled against the scheme calendar.
EMV
Card profile certification for personalized and instant cards, contact and contactless.
PCI DSS
Alignment of the cardholder data environment, with formal assessment by the institution's QSA and support from our side.
What we need from you
Connectivity and firewall rules per the communication matrix; vendor contacts and contracts for core banking, scheme, AML, gateways, KIOSK and embossing; non-production environments and test data; and named participants for each certification.
Dependencies
Two honest caveats.
XFS depth varies by model
How much a terminal reports about its own devices depends on the model and firmware. EJ formats are confirmed per vendor during the design phase, and the monitoring profile follows what the estate can actually tell us.
Phase 2 follows the scheme calendar
OFF-US dates depend on scheme certification slots, not on our readiness. We plan against the published calendar and book slots as early as the membership allows.
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.