Build and Certify on Sunmi Terminals
POS payment applications for Sunmi P2, P2 SE, P2 Lite SE and P3 Mix — built, integrated against Sunmi's payment SDK, and certified in-house on UL Brand Test Tool and FIME toolsets. One team, start to submission.
Building and Certifying on an Android Payment Terminal
Sunmi's smart POS range runs its own Android-based OS, and the payment application talks to Sunmi's payment service through Android's bindService/AIDL mechanism rather than a proprietary embedded API. That puts standard Android packaging, permissions and service-lifecycle behaviour inside the certification surface, alongside the EMV test cases themselves — a different failure mode than an embedded terminal running a closed firmware stack.
Sunmi has also revised the EMV kernel across the P2 series over its lifetime — the active kernel version is readable through the SDK, and confirming which kernel a given fleet is running is one of the first things we check when scoping a campaign, since it changes which test cases and defect patterns are relevant.
We build POS payment applications for Sunmi 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 Sunmi ProjectTerminals Covered
Platform
Schemes
Certified In
The Application Comes First
Certification tests an application that already exists. On Sunmi hardware, getting to that point is its own body of work.
Payment App Development
We build the POS payment application itself for Sunmi's smart POS range — not only test one that already exists.
SDK Integration
Binding to Sunmi's payment service through Android's bindService/AIDL interface, and handling the service-lifecycle behaviour that comes with it.
EMV Kernel Handling
Sunmi has revised the EMV kernel across the P2 series. The active version is readable through the SDK, and confirming it early changes which test cases and defect patterns apply.
The Same Process, Every Sunmi Model
Scope
Which Sunmi model, current EMV kernel 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, with Android service-binding behaviour checked alongside EMV logic.
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 kernel update.