Terminal platforms we have shipped on
IngenicoPAXSunmiNexgoKozenMiuraDspreadFeitianUrovoBBPOS+ more
What We Build
The Full Transaction Lifecycle, on Real Hardware
From sleek Android smart terminals to traditional Linux devices, we develop applications that handle every transaction type your acquiring business needs — engineered to port cleanly across your terminal estate.
- EMV contact & contactless (NFC)Chip, tap, magstripe fallback and QR acceptance flows
- Complete transaction setPurchase, refund, void, reversal, pre-auth, completion, tip adjust, settlement
- Security & key managementPIN entry, DUKPT and master/session key schemes
- Terminal managementRemote updates, parameter downloads, RKI and estate management
- Value-added servicesDCC, loyalty, digital receipts and merchant apps alongside payments
- Estate-wide reportingPairs with our payment platforms practice for fleet-wide visibility
txn — authorization
MTI : 0100 PAN : ************4242 AMOUNT : 000000012500 STAN : 003741 ENTRY MODE : 071 — Contactless EMV FIELD 55 : 9F26 08 A1B2C3D4… ───────────────────────── RESPONSE : 00 — APPROVED ✓
Why Deazitech
Why Acquirers and PSPs Choose Us
10+ Vendor Platforms
We've already shipped on the hardware you're targeting — no SDK learning curve on your bill.
Switch-Ready by Design
Our apps are built with the host integration in mind — see our switch integration service for the other half.
Certification Built In
L3 testing with UL BTT and FIME tools is part of our delivery, not a hand-off — see L3 certification.
FAQ
Payment Applications, Explained
Do you build the application on the terminal, or connect an existing POS to a terminal?
Both. A terminal payment application runs on the device itself and handles the card, the EMV kernel and the host connection. A semi-integrated integration keeps your existing POS in charge of the sale and has it drive a terminal whose certified application handles the card. The second route usually keeps card data out of your POS and relies on the processor's existing certification rather than a new one, so tell us which you need and we'll scope that one.
Which terminal platforms have you shipped payment applications on?
Ingenico, PAX, Sunmi, Nexgo, Kozen, Miura, Dspread, Feitian, Urovo and BBPOS, across Android smart terminals and Linux devices. If your terminal isn't on that list, send us the model and its SDK documentation and we'll tell you plainly whether it is new ground for us.
Do you develop the EMV kernel as well?
No. We integrate the terminal vendor's certified Level 2 kernel through its SDK and build the payment application on top of it. EMV L2 kernel development and L1 or L2 certification are outside what we do; Level 3 certification of the finished application is in scope.
Is L3 certification part of the project or a separate engagement?
It is part of delivery. We run L3 testing in-house with UL Brand Test Tool and FIME tools, so the team that wrote the application also takes it through certification. L3 is certified per card scheme against your acquirer's host, so we need both named at the start.
Can an application built for one terminal be moved to another vendor's device?
Largely, yes. Transaction logic, host messaging and receipt handling carry over. The vendor SDK layer, kernel configuration and device-specific parts such as printing and PIN entry are redone for each platform, and a new terminal model generally needs its own L3 campaign.
Related Reading