Build and Certify on Kozen Terminals
POS payment applications for Kozen P3, P5 and P10 — built, integrated against the shared EMV SDK library, and certified in-house on UL Brand Test Tool and FIME toolsets. One team, start to submission.
One SDK, Three Hardware Revisions
Kozen's P3, P5 and P10 all run on Android and share a common EMV SDK library across the range, which is a genuine advantage for a fleet that spans multiple models — but it also means the SDK behaving consistently is not the same thing as the hardware behaving identically. Screen size, hardware revision and OS build can differ enough between models that we verify the specific unit and SDK version in play before treating one model's test result as representative of another.
Kozen's device-level certifications go beyond the three schemes we typically test against — the hardware itself carries broader marks including D-PAS and Mastercard TQM. Our L3 campaigns are scoped to whichever schemes a given deployment actually needs, rather than testing everything the hardware is theoretically capable of.
We build POS payment applications for Kozen terminals as well as certifying them, so a defect found mid-campaign goes back to the same team that can fix it.
Talk About Your Kozen ProjectTerminals Covered
Platform
Schemes
Certified In
The Application Comes First
Certification tests an application that already exists. Across the Kozen range, getting to that point is its own body of work.
Payment App Development
We build the POS payment application for Kozen terminals, not only test one that already exists.
Shared SDK Integration
P3, P5 and P10 share a common EMV SDK library, so integration work carries across the range rather than restarting for each model.
Per-Model Verification
Screen size, hardware revision and OS build still differ between models, so the specific unit and SDK version in play are verified rather than assumed.
Consistent Process Across the Range
Scope
Which Kozen model, hardware revision, SDK version, scheme and target certification level defined up front.
Execute
UL BTT and FIME test plans run in-house across contact, contactless, fallback and PIN scenarios.
Analyze
Field 55 deep dives and TVR/TSI interpretation on every failed case.
Fix & Retest
If the application is ours — or handed to us — the same team fixes and reruns in the same cycle.
Hand Off
Evidence packaged for your acquirer to submit to the scheme, with regression packs ready for the next model or SDK update.