Migration Guides
Transitioning to a new billing system shouldn't be a headache. Whether you are moving from a competitor or upgrading from an older Aptoide solution, these guides provide a clear mapping of methods, listeners, and logic to get you up and running on the new Aptoide Billing SDK as quickly as possible.
The new SDK is designed with a modern architecture that provides high parity with industry standards, making the switch intuitive for most Android developers.
- Native Bottom-Sheet Checkout — Users buy inside your app, with no Wallet install required, for higher payment conversion.
- Fraud-reduction UI — Blocks false mid-flow cancellations.
- 16 KB page-size support — Required for newer Android device compatibility.
Choose Your Migration Path
Find your current setup in the table below to see the recommended target SDK, the estimated effort, and a direct link to the relevant guide or documentation.
| Current Setup | Recommended Target | Effort | What's Involved | Guide |
|---|---|---|---|---|
Aptoide Billing SDK (com.aptoide:android-aptoide-billing) below 1.2.0 | Aptoide Billing SDK 1.+ (com.aptoide:android-aptoide-billing) | ~5 min | Drop-in dependency version bump — no API changes required. | Release Notes |
AppCoins SDK (io.catappult:android-appcoins-billing) above 0.7.3.0 and below 0.10 | AppCoins SDK 0.10.+ (io.catappult:android-appcoins-billing) | ~5 min | Drop-in dependency version bump — no API changes required. | Release Notes |
Google Play Billing SDK (com.android.billingclient:billing) | Aptoide Billing SDK 1.+ (com.aptoide:android-aptoide-billing) | ~10 min (with AI prompt) | Map BillingClient listeners and swap Google-specific dependencies for Aptoide equivalents. Near 1:1 API parity. | Migration Guide · AI Prompt |
Legacy AppCoins SDK (io.catappult:android-appcoins-billing) below 0.7.3.0 | AppCoins SDK 0.10.+ (io.catappult:android-appcoins-billing) or Aptoide Billing SDK 1.+ (com.aptoide:android-aptoide-billing) | ~30 min | Move off legacy flows to a callback-driven native implementation and the newer Aptoide Connect backend APIs. | Migration Guide |
| One-Step Payment (OSP) | Aptoide Billing SDK 1.+ (com.aptoide:android-aptoide-billing) | ~1 hour | Replace URL-launched web payments with the native SDK client connected directly to the Aptoide Wallet. | Migration Guide |
Note: The AppCoins SDK (
io.catappult:android-appcoins-billing) is the maintained legacy line, while the Aptoide Billing SDK (com.aptoide:android-aptoide-billing) is the modern, recommended SDK for new and long-term integrations. If you have the time, migrating to Aptoide Billing SDK1.+is the best long-term choice.
Available Migration Paths
Depending on your current implementation, choose the guide that matches your starting point:
Migration from Google Play Billing
For developers that have previously integrated Google's Billing SDK, the Aptoide Billing SDK follows a very similar pattern to Google Play's Billing SDK and this guide will help you migrate flawlessly.
- Key focus: Mapping
BillingClientlisteners and replacing Google-specific dependencies with Aptoide equivalents.
Migration from Legacy AppCoins SDK
For developers using the older AppCoins integration. This migration focuses on moving away from the legacy SDK flows toward a more robust, callback-driven native implementation.
- Key focus: Security improvements, easier integration, improved features and transition to newer Aptoide Connect backend APIs.
Migration from OSP Integration
If you previously used the One-Step Payment (OSP) web-based flow, this guide helps you wrap those interactions into a native Android experience.
- Key focus: Replacing manually launched payments using URLs with the high-performance native SDK.
General Migration Tips
- Dual Integration: You can maintain your existing Billing SDK alongside the Aptoide SDK by using a simple flavor or "Provider" pattern in your code.
- Check our Aptoide Diceroll SDK example for more insights on how to accomplish this.
- Test in Sandbox: Always use the Sandbox Environment to verify your migration before pushing to the production track.