Home / L3 Certification & Testing / Urovo

Build and Certify on Urovo Terminals

POS payment applications for Urovo's Android terminals — built, integrated against the OS build the fleet actually runs, and certified in-house on UL Brand Test Tool and FIME toolsets. One team, start to submission.

Platform Notes

OS Fragmentation Across the Range

Urovo's smart POS range has shipped on several different Android versions across its models and generations. That matters for certification: SDK behaviour, permission handling and background-service reliability can all shift between OS versions, so confirming the exact Android build a given fleet is running is one of the first things we check when scoping a campaign — a P2-generation unit and a newer model can't be assumed to behave identically just because both run Android.

Urovo's hardware also carries PBOC certification — China's domestic card scheme — alongside the EMV marks most of our clients need. Our default L3 campaigns cover Visa, Mastercard and Amex; PBOC is scoped in separately if a specific deployment calls for it, rather than assumed.

We build POS payment applications for Urovo 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 Urovo Project

Terminals Covered

Urovo i9000

Platform

Android-based OSOS build verified per fleet

Schemes We Certify

VisaMastercardAmex

Available on Request

PBOC (China domestic)

Certified In

South Africa

Before Certification

The Application Comes First

Certification tests an application that already exists. On Urovo hardware, getting to that point is its own body of work.

Payment App Development

We build the POS payment application for Urovo terminals, not only test one that already exists.

SDK Integration

SDK behaviour, permission handling and background-service reliability all shift between Android versions, so integration is done against the OS build the fleet actually runs.

OS Build Verification

Urovo's range has shipped on several Android versions. Confirming the exact build for a given fleet happens before development scope is set, not after.

Certification Process

OS Build Confirmed Before Scope Is Set

Scope

Urovo model, Android build, 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 OS-version-specific 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 OS or app update.

FAQ

Urovo Development & Certification, Explained

What Android version do Urovo terminals run?

It depends on the model and generation — Urovo's smart POS range has shipped on several Android versions over time. We confirm the exact OS build for a given fleet during scoping, since it affects which SDK behaviours and permission handling apply during certification.

Do you certify Urovo terminals for schemes beyond Visa, Mastercard and Amex?

Our standard L3 campaigns cover Visa, Mastercard and Amex. Urovo's hardware also carries PBOC certification — China's domestic scheme — which is relevant if a deployment needs it, but it sits outside our default scope unless the project calls for it.

Do you integrate against the Urovo SDK, or only work with an application that is already built?

Either. We integrate the payment application against the terminal SDK as part of building it, and we also take on applications written elsewhere that need certification. Because SDK behaviour shifts between Android versions, confirming the exact OS build a fleet runs is part of that work in both cases.

Do you also build the payment application, or only certify it?

Both. We build POS payment applications for Urovo terminals and run L3 certification in-house, so a defect found during testing goes back to the same team that can fix it — not a different vendor.

Also Supporting

Other Terminal Platforms

SunmiKozenFeitianView All Platforms →