For ISVs delivering payments, ordering, table-side, or vertical-specific software to North American merchants, the platform choice in 2026 comes down to a simple question. Do you spend six months negotiating SDK access and certification with a closed POS vendor, or do you ship a working integration on SUNMI Android in weeks?

The SUNMI Android POS SDK sits on top of standard Android, exposes the hardware your app needs through a clean Java/Kotlin API, and clears the most common ISV concerns: printer, scanner, EMV payment, MDM, and semi-integrated payment modes. Rosper is the official SUNMI distributor for North America, and we work with ISV partners weekly on integration scoping, dev hardware, and production rollout.

This guide covers what the SUNMI Android POS SDK actually exposes, how the four payment integration modes compare, and the practical timeline an ISV team should plan for going from sandbox to a production rollout across a US or Canadian merchant base.

What the SUNMI Android POS SDK gives you

The SUNMI Android POS SDK is a layered stack. At the bottom is standard Android (10, 11, or 13 depending on the device generation). On top of that, SUNMI exposes hardware APIs as Android services, called through AIDL or higher-level Java/Kotlin wrappers.

The most relevant SDKs for ISV teams are:

• Inner Printer SDK — controls the 58 mm or 80 mm built-in thermal printer with text, image, QR, and barcode primitives.
• Scanner SDK — wraps the 1D and 2D scanner on devices that have one. On devices without a scanner, a Bluetooth or USB scanner can be paired through standard Android.
• NFC and Card SDK — handles MIFARE, NFC, and magnetic stripe reads where the hardware supports it.
• Payment SDK — exposes EMV chip and contactless transaction flows on payment-rated devices, with PCI PTS 6x certification.
• Sub-display SDK — drives the customer-facing screen on devices with a second display, such as the D3 Mini, T3 family, or CPad Pay.
• Cash drawer kick — fires the drawer trigger on devices that support it.
• System SDK — exposes hardware identifiers, network info, status LEDs, and device management hooks.

Higher-level developer tools include:

• Inner Printer Service — a system service that allows multiple apps to share the printer without conflict.
• Semi-integrated payment SDK — handles the four common ISV payment integration modes.
• AIDL emulator binaries — useful for early-stage testing on a workstation without a physical device.

You request access to the SUNMI Android POS SDK and sample code through the SUNMI developer portal. Rosper helps US and Canadian ISV partners cut down portal turnaround by routing the request through our channel relationship. The CPad family is the most common dev hardware for ISV teams building sub-display experiences.

The four semi-integrated payment SDK modes

Most ISV teams approach SUNMI for the payment integration story. Here is the practical breakdown of the four modes the semi-integrated payment SDK supports.

Mode 1: Semi-integrated with a third-party processor

Your app sends a transaction request to a payment app on the same SUNMI device, the payment app handles EMV, contactless, and the processor connection, and returns a result. You stay out of PCI scope on the card data side.

Best for: ISVs who do not want to take on PCI DSS and processor certification themselves, and merchants who want flexibility on processor choice.

Mode 2: Full-integrated with your own payment kernel

Your app handles the payment flow end to end using the EMV kernel on the device. You take on PCI DSS scope and processor certification, but you get full control of the UX and tip prompts.

Best for: ISVs with existing payment infrastructure who want a single-app experience.

Mode 3: Cloud-based payment with a server-side processor

Your app generates the transaction on the cloud side, sends a payment instruction down to the device, the device prompts for card or tap, and the result is reconciled server-side.

Best for: omnichannel ISVs running online and in-person under one payment platform.

Mode 4: SoftPOS with no external reader

On supported devices, the SoftPOS path turns the SUNMI Android device into a PCI-listed tap-to-pay endpoint without an external reader. The SUNMI SoftPOS path runs on devices certified for tap on Android (TOA).

Best for: handheld and mobile-first deployments where carrying a separate reader is friction.

For a deeper breakdown of the four modes and how to choose between them, see our semi-integrated payment SDK guide.

Dev hardware: what to order before you write code

Before your team writes a line of integration code, get the right dev hardware in front of them. The cheapest mistake an ISV team makes is building against an emulator and discovering the production device behaves differently.

For most ISV integration projects in 2026, the recommended dev kit is:

• One SUNMI V3 Mix or D3 Mini as the primary form factor for testing printer, scanner, sub-display, and NFC flows.
• One SUNMI K2 Mini or K2 kiosk if the integration includes self-order or self-checkout flows.
• One SUNMI P3 Mix or V2s for payment-specific integration testing, including EMV and Interac Flash.
• One handheld (L2s Pro or P3 family) if the use case includes shop-floor or warehouse scanning.

Rosper ships dev hardware to ISV partners from US and Canadian warehouses, typically inside 2 to 7 business days. We also pre-configure devices with MDM enrollment and the right Android version before they leave the warehouse so the engineering team is not burning time on initial provisioning.

A practical SDK integration timeline

Here is a realistic timeline for an ISV team integrating the SUNMI Android POS SDK into an existing Android POS or order-management app. Adjust based on your team size and prior Android experience.

Week 1: Environment and printer

• Set up SUNMI dev portal access.
• Order dev hardware through Rosper.
• Wire up the Inner Printer SDK to your existing receipt rendering logic.
• Validate text, image, QR code, and barcode print on the target form factor.

Week 2: Scanner, NFC, and sub-display

• Integrate the Scanner SDK for 1D and 2D barcode flows.
• Wire up the sub-display SDK for the customer-facing screen if your form factor has one.
• Add NFC tag reads for loyalty or membership card flows.

Week 3 to 4: Payment integration

• Choose the semi-integrated mode that matches your business model.
• Implement the request/response flow against the payment app or kernel.
• Run sandbox transactions against the chosen processor.
• Validate EMV chip, contactless, and tap-to-pay paths.

Week 5: MDM and lifecycle

• Enroll a test fleet in the SUNMI Partner Portal MDM.
• Validate kiosk mode lockdown if the deployment includes self-order.
• Test over-the-air updates and policy push.
• Wire up your own remote-config or feature-flag system to coexist with SUNMI MDM.

Week 6: Pre-production and certification

• Run a small pilot in a real merchant environment.
• Validate edge cases: low paper, printer head jam, network drops, NFC tag conflicts.
• Complete any processor certification steps required for the payment mode you chose.
• Sign off on the production build.

For experienced Android teams with a prior payment integration, the end-to-end timeline can compress to 3 or 4 weeks. For teams new to payment integration, 6 to 10 weeks is more realistic.

Production rollout: from sandbox to fleet

Once the integration is signed off, the production rollout shifts from engineering to logistics. The pieces that matter at this stage are:

• Hardware staging at the warehouse. Each device should leave the warehouse with the right Android version, MDM enrollment, your app, and any pre-configured settings. Rosper does this from US and Canadian warehouses for ISV partners.
• MDM tenant configuration in the SUNMI Partner Portal, including kiosk mode rules, network policies, and OTA update schedules. The MDM is free for SUNMI hardware deployments.
• Provisioning flow for merchants to self-enroll or accept devices at the door without engineering involvement.
• Warranty path for in-the-field hardware. SUNMI’s official 3 year warranty on Gen 2 and Gen 3 hardware covers the device. Rosper assists with warranty claims and coordinates RMA paperwork in-region.

For the Canadian side of a rollout, the Canadian restaurant POS terminal guide covers the device-level recommendations that pair with ISV-built software on top.

ISV partner economics with Rosper

The Rosper ISV partner program is built around three things ISV teams ask for: dev hardware fast, predictable volume pricing, and a fulfillment path that scales without surprise.

Typical economics look like this:

• Dev hardware at a discounted partner rate, with most kits shipping in 2 to 7 business days from US or Canadian warehouses.
• Volume pricing tiers that kick in at meaningful merchant counts, not at unreachable thresholds.
• MDM enrollment included, with no per-device license fee.
• Pre-staging of fleet hardware before it ships, including your app, MDM tenant, and any merchant-specific config.
• Warranty coordination inside North America, with no cross-border RMA paperwork for Canadian deployments.

For deeper US-side considerations, our SUNMI MDM Partner Portal guide walks through MDM setup for US fleets and pairs naturally with the SDK side of the integration.

Common ISV SDK questions

Does the SUNMI Android POS SDK require a paid license?

No. The SUNMI POS SDK is free to use on SUNMI hardware. There is no per-device license fee for the printer, scanner, sub-display, or basic system SDKs. The MDM through the SUNMI Partner Portal is also included with the hardware.

What does it actually take to get a SUNMI dev account?

You apply through the SUNMI developer portal. Approval typically takes a few business days. ISV partners working with Rosper can have their dev account request fast-tracked through our channel relationship, which usually cuts the wait by half.

Can I emulate the SUNMI hardware on a workstation?

Partially. SUNMI provides AIDL emulator binaries useful for early-stage integration testing. However, the printer, scanner, EMV kernel, and NFC stack behave differently on real hardware, and processor certification has to be done on a production form factor.

How does the SUNMI semi-integrated payment SDK compare to PAX, Ingenico, or Verifone SDKs?

The SUNMI semi-integrated SDK uses a similar pattern to PAX BroadPOS and Ingenico ECR integrations: the ISV app sends an intent or AIDL call to the payment app on the device, the payment app handles the EMV and processor flow, and a result is returned. The major difference is that SUNMI runs on standard Android and the payment app is a normal Android APK, which makes the ISV side significantly easier to develop and debug.

What if my software depends on a payment processor that is not in SUNMI’s reference list?

SUNMI Android is open enough that any processor SDK with an Android library can be integrated. Rosper has helped ISV partners integrate with Moneris, Global Payments, Chase Merchant Services, Worldpay, Elavon, and a long list of regional Canadian and US processors. If you have a specific processor in mind, ask us before you start.

Can a smaller ISV team realistically integrate the SUNMI SDK?

Yes. The Android POS SDK is engineered to be readable by a one to three person Android team. Most integrations we have seen are scoped at one senior Android engineer for 4 to 8 weeks, with a second engineer covering processor certification in parallel.

Where does the warranty sit when an ISV ships SUNMI hardware to a merchant?

The SUNMI 3 year warranty on Gen 2 and Gen 3 hardware sits with SUNMI as the manufacturer. Rosper, as the official North American distributor, assists ISV partners and their merchants with warranty claims and coordinates the RMA paperwork. The ISV does not need to carry warranty exposure itself.

Get started on the the SDK

Rosper supports ISV teams across the full integration lifecycle, from dev hardware to production rollout, with US and Canadian warehouses, MDM pre-staging, and in-region warranty coordination. The shortest path from a software idea to a deployed Android POS fleet in 2026 runs through the SUNMI’s POS SDK and a distributor that handles the logistics so your engineering team stays focused on the integration. To scope an ISV integration, request a dev kit, or get a volume quote for a production rollout, request a quote with your form-factor target, payment processor, and merchant count plan.