
A Japan-based manufacturer of Android payment terminals was preparing its next device generation. Each terminal had to pass EMV Level 2, meet PCI PTS and SRED rules for manual card number entry and the secure keypad, and still give retailers scanning, printing and sales on one screen. Certification came first.
Dev Station took on the embedded C++, the Android app, the AWS back end and the firmware update pipeline as one cross-functional squad. One decision shaped the rest. Card data may exist only inside the secure CPU, and the Android app never receives it.
Five constraints shaped the brief, and each one came from the certification process or from the cost of running terminals in the field.
1. Card entry under certification rules: The terminals had to reach EMV Level 2 and meet PCI PTS and SRED requirements for manual PAN entry and the secure keypad. There was no way around the audit.
2. Separate tools, separate experiences: Barcode and QR scanning, remote printing and the retail app lived as different Android utilities. The manufacturer wanted one app with one flow across the device range.
3. A small PCI scope: Every system that touches card data enlarges the audit. The brief asked for the smallest scope that could work, and for cloud operations an auditor can trace from end to end.
4. Fewer field visits for firmware: A field service visit costs money. The manufacturer wanted reliable firmware-over-the-air (FOTA) updates, with signed bundles and rollouts that can be undone.
5. Speed without shortcuts: Time to market mattered. So did certification and device hardening, and the plan had to protect both.
Talk to the engineers, not a sales team
Thirty minutes on your current system and the integration constraints. No sales pitch.






