com.sec.android.app.billing Copy

Shown as "Samsung Checkout", this is Samsung's payment component on Galaxy devices. Samsung's own support material describes Samsung Billing as the behind-the-scenes payment service used by the Galaxy Store and Galaxy Themes apps, and Samsung offers developers a matching Samsung In-App Purchase service for apps distributed through Galaxy Store. In our sample it is not user-facing and is signed with a Samsung key that signs this package alone rather than the device framework, which fits a discrete payment app rather than a platform component. Its permissions match a checkout flow: INTERNET, GET_ACCOUNTS_PRIVILEGED, CAMERA, NFC, REQUEST_INSTALL_PACKAGES and INSTALL_SELF_UPDATES. Version note: no change of role across Android releases could be sourced for this package. The target SDK range recorded on the site runs from 34 to 36, so the builds observed are recent rather than a frozen factory version, and the INSTALL_SELF_UPDATES permission indicates it can update itself independently of a firmware release. For Android Enterprise, EMM and kiosk use it has no role in enrolment, provisioning or policy. Its only function is taking payment for Samsung's own consumer content, so on a corporate-owned or kiosk device it is generally unwanted. Note that Galaxy Store is the usual control point here: Samsung's Knox Service Plugin exposes a "Show Galaxy Store application" setting, and hiding the store is the documented way to close off that purchase route. Turning off Checkout itself will stop purchases in Galaxy Store and Galaxy Themes, which is normally the intent, but it is a Samsung app that other Samsung apps call into, so test on a single device before rolling it out.

• Phone or tablet cannot make purchases through Samsung Billing - Samsung Support →
• Samsung In-App Purchase - Samsung Developers →
• Application management policies - Knox Service Plugin, Samsung Knox Documentation →
• Package provenance for com.sec.android.app.billing - Android System App Database →

• Signed by the device maker's own signing key (Samsung), so it is an OEM preinstall, and that single certificate is consistent across all 21 device profiles. This attribution is tentative - the certificate has only been seen on Samsung so far (1 package, 33 observations).
• Its largest observed manifest declares 40 permissions: 6 runtime (user-granted), 5 signature or system-level, 13 install-time and 16 vendor or uncatalogued.
• Reported as an updated system app on 21 of 21 profiles - a newer build is installed over the one in the system image there.