What We Deliver
Fluent in ISO 8583 — and Every Dialect of It
Every switch speaks its own version of the standard, and many speak something entirely proprietary. We've integrated enough of them to know where the surprises hide: in the bitmaps, the key ceremonies and the reversal logic. We often deliver this alongside the POS application on the terminal end, so one team owns both sides of the connection.
- ISO 8583 messaging (1987 / 1993)Bitmap parsing, message packagers and field-level validation
- Proprietary protocols from specImplemented directly from the switch's message specification
- SecurityKey exchange, PIN translation, MAC generation and verification
- ResilienceStand-in, store-and-forward, timeouts and automatic reversals
- Back officeReconciliation, settlement, cutover and dispute support data
- Host simulatorsSo development and regression testing never wait on a test host
iso8583 — field map
DE 002 PAN DE 003 Processing Code DE 004 Amount, Transaction DE 011 STAN DE 022 POS Entry Mode DE 035 Track 2 Data DE 039 Response Code DE 052 PIN Block DE 055 EMV / ICC Data DE 064 MAC
Why Deazitech
Integrations That Survive Production
From-Spec Implementation
Hand us the switch's message specification and we'll implement it precisely — no guessing, no "mostly compatible".
Security Done Right
Key ceremonies, PIN blocks and MACs handled with the discipline acquiring banks expect — and auditors verify.
Faster Certification
Clean integrations sail through L3. Pair this service with our L3 testing for a single accountable path to production.
FAQ
Switch Integration, Explained
Which versions of ISO 8583 do you work with?
ISO 8583:1987 and 1993, along with the dialects individual switches build on top of them. Where a switch uses a fully proprietary protocol, we implement it directly from that switch's message specification.
What do you need from us to start, and can work begin before the test host is ready?
The switch's message specification, its key management requirements and, when available, test host access. Work does not have to wait for the host: we build a host simulator from the specification so development and regression testing can run before and between test windows.
How do you handle timeouts and lost responses?
Every request has a defined timeout, and when a response does not arrive the application sends an automatic reversal so a cardholder is not charged for a transaction the terminal never completed. Stand-in and store-and-forward are implemented where the switch's rules allow them.
Do I need an ISO 8583 integration to take card payments in my POS?
Not always. If your POS drives a payment terminal through a processor's semi-integrated interface, the terminal's certified application talks to the host and your POS never builds an ISO 8583 message. A direct host integration is needed when you run your own payment application on the terminal, or when your acquirer or switch requires a direct connection.
Do you build the terminal application as well as the host integration?
Yes, and we often deliver both together, so one team owns the terminal end and the host end of the same connection. It also gives L3 certification a single accountable team, since an issue on either side goes to the same engineers.
Related Reading