Sign-on
The link comes up and is announced. Key exchange runs on the same message pair.
T-NET / Switch
ISO 8583-1:1987 with a data-driven packaging profile. The field map, the message-type matrix, the processing codes and the response codes are configuration — so a new endpoint is a profile rather than a release.
7.2 · Functional specification
| Module | Specification |
|---|---|
| Protocol engine | ISO 8583-1:1987 with a data-driven packaging profile: field map, message-type matrix, processing codes and response codes are configuration, not code. Binary primary and secondary bitmaps, ASCII field bodies, and a two-byte binary length header on the TCP stream. |
| Message types | Authorisation and pre-authorisation (0100/0110), financial (0200/0210), advice (0220/0230), reversal (0400/0410), core-banking-side reversal (0420/0430) and network management (0800/0810) for sign-on, sign-off, echo and key exchange. |
| Processing codes | Purchase, purchase with cashback (cashback portion carried in the additional-amounts field), refund within the agreed window with the original reference, balance inquiry, card and token authentication, and settlement batch. Legacy codes are normalised at the edge of the switch. |
| Session management | Persistent TCP sessions with an active and a standby connection per endpoint, primary and DR ports, echo heartbeat every 60 seconds, three retries and automatic failover. |
| Pre-auth lifecycle | Authorised, incremented, completed or released states with expiry handling, matched through the original-data and replacement-amount fields. |
| Duplicate detection | Replay window keyed on message type, primary account number, processing code, amount, trace number, retrieval reference and terminal; a replay returns the stored response rather than a second authorisation. |
| Reversal engine | A financial-response timeout triggers an automatic reversal carrying the original data elements, retried three times and then queued with an alarm; a reversal with no original is answered with the agreed decline code. |
| HSM security services | PIN translation from the terminal's DUKPT base derivation key to the scheme working key and between working keys, PIN verification, MAC generation and verification on every inter-switch message, EMV cryptogram services and data-block encryption — delivered by a domain-separated HSM service whose acquiring command set is isolated from issuing and ATM commands. |
| Risk & fraud monitoring | Real-time rules per institution, merchant and terminal: velocity, high value, geography, rapid repeats, MCC restrictions and card-type restrictions; risk scoring with decline or alert actions. |
| AML screening hook | Screening call-outs on acquiring authorisation and settlement flows to the institution's AML system, with alert routing and case references. |
| Clearing, settlement & chargebacks | Clearing file generation and ingestion, settlement position calculation per merchant, institution and currency, settlement reports, and the retrieval, chargeback, representment and write-off case workflow. |
Sessions
Sign-on, then an echo every sixty seconds. A standby connection is held open beside the active one, across primary and DR ports. Three retries, then failover — without anyone being paged to notice first.
The link comes up and is announced. Key exchange runs on the same message pair.
A heartbeat on the active connection. Silence is a signal, not an absence of one.
The second connection is already open. Failover is a switch of traffic, not a reconnect.
Primary and DR ports per endpoint, so a site failure is a route change.
Reversals & duplicates
A financial response that does not arrive within the timer is not an unknown. It is a reversal.
A frozen screen and a second tap must not become a second authorisation.
Pre-authorisation
Hotels, fuel and rental live here. Each state transition is matched through the original-data and replacement-amount fields, so a completion for a lower amount releases the difference rather than leaving it held.
The hold is placed. The original data elements become the key for everything that follows.
A further amount is added to the existing hold rather than raising a second, unrelated authorisation.
Captured at the final amount through the replacement-amount field; the unused portion of the hold is released.
An explicit release, or expiry handling when nothing completes the hold within the window.
Risk, fraud and AML
Rule sets are named in the merchant suite, assigned to merchants and terminals, and enforced here at authorisation time — scoped by institution so one acquirer's rule never fires on another's traffic.
Velocity, high value, geography, rapid repeats, MCC restrictions and card-type restrictions, per institution, merchant and terminal.
Risk scoring with a configured action — decline the transaction, or approve it and raise an alert for review.
Call-outs on acquiring authorisation and settlement flows to the institution's AML system, with alert routing and case references.
Next step
Your scheme endpoint, your CBS interface and your terminal mix are enough for us to come back with an ISO 8583 packaging profile, a sizing note and a certification schedule.