Google Play Billing vs Kenshi/core

Google Play Billing lets developers sell digital products and content in Android apps through one-time purchases or subscriptions. It is for digital items; developers selling physical goods or services are directed to the Google Pay SDK. One-time products may be consumable for repeat purchases or non-consumable for a lasting benefit, and can grant permanent access or a particular non-renewable use. Subscriptions grant defined benefits for a set period and support base plans, offers, prepaid plans, and add-on entitlements. The Play Billing Library connects an Android app with Google Play Services to retrieve localized offerings and launch purchase flows. Google recommends a secure backend using the Play Developer API for purchase verification and subscription management. That API can check purchase status and modify or cancel recurring purchases. Cloud Pub/Sub delivers notifications about changes to Google Play-managed subscriptions. Purchases that are not acknowledged within three days are automatically refunded. Google says service fees vary by developer and transaction; its overview says 97% of developers distribute apps and use Google Play at no charge, and 99% of developers subject to a service fee are eligible for a fee of 15% or less through available programs. The listed plan is free.

Kenshi/core is a paid, cross-platform anti-cheat and anti-tamper platform protecting software from hardware through the application layer. It lists 27 detection modules across hardware, kernel, runtime and binary layers, plus 32 anti-tamper protections including runtime hardening and code protection. Events from those layers are correlated on one timeline. The developer SDK supports Unreal, Unity, Source and custom C++, while operator integrations include Slack, Discord, PagerDuty and Datadog. Kenshi says it can operate alongside EAC, BattlEye, in-house anti-cheat systems and EDR tools such as CrowdStrike, Sentinel and Defender. Typical engagements include a scoping workshop, SDK integration and live launch support; integrations typically take 4 to 6 weeks. Licensing may be per title or studio, usually beginning with a scoped pilot for one title. Kenshi lists Linux and Windows, uses TLS 1.3 in transit and AES-256 at rest, and defaults processing and storage to UK and EU regions. Pricing is on request.