We’re excited to introduce a highly requested feature—Web Transaction Syncing with IAPHUB! This new functionality allows you to sync transactions from your web-based payment system to IAPHUB, ensuring a seamless and unified purchase experience across all platforms.

Why This Matters​

Until now, IAPHUB has been the go-to solution for managing in-app purchases on the iOS and Android mobile platforms. However, many developers also offer web-based subscriptions or one-time purchases. With our new Web Transaction Sync feature, you can now:

• Track and manage web purchases alongside mobile transactions.
• Ensure your users get a consistent purchase experience across platforms.
• Maintain accurate billing and subscription records in one place.

How It Works​

Syncing your web transactions with IAPHUB is straightforward. Simply follow our step-by-step guide to integrate your payment provider and send transactions to IAPHUB:

📖 Read the full setup guide here

Get Started Today!​

We can’t wait for you to try out this feature and streamline your purchase management across platforms. Head over to our documentation and start syncing your web transactions today!

Got questions or feedback? You can reach out to our support.

Happy coding! 🚀

We're excited to introduce a new property for products in IAPHUB: alias!

The alias property is a unique, human-readable identifier designed to help you distinguish your products more easily. This is particularly useful when dealing with products that have different product IDs on Android and iOS. To simplify product management, we recommend using the same alias value for the corresponding iOS and Android product IDs whenever possible.

Availability​

The new alias property is available in the latest versions of our SDKs:

• [email protected]
• [email protected]
• [email protected]
• [email protected]

How to Use the Alias Property​

To take advantage of this new feature, simply set the alias for your products in the IAPHUB dashboard. Once configured, the alias will be included in the product data returned by the SDK.

This update makes it easier to manage cross-platform products and maintain consistency across different platforms.

We hope this new feature helps streamline your product management. As always, feel free to reach out if you have any questions or feedback!

If you’re an app developer or someone managing in-app purchases, you may have recently seen a warning about the SHA-1 intermediate certificate used for signing App Store receipts expiring on January 24, 2025. Apple’s notice has caused some concern, especially for those who rely on on-device receipt validation. But don’t worry—if you’re using IAPHUB to manage your in-app purchases, you’re already covered.

What’s Happening with the SHA-1 Intermediate Certificate?​

The SHA-1 intermediate certificate used by Apple for signing App Store receipts will expire on January 24, 2025. This has prompted many developers to assess whether their app's receipt validation process will continue to work seamlessly after this date. The key concern is that if you're still using the SHA-1 certificate for on-device receipt validation, your app might face issues when the certificate expires.

This is an important change, but there’s no need to panic if you're using IAPHUB. IAPHUB validates all receipts on the server-side by using the official Apple API, which means you’re always using the most up-to-date certificates and validation processes.

Why You Don’t Need to Worry with IAPHUB​

At IAPHUB, we understand the complexities of receipt validation. We handle the technicalities for you, so you don’t have to. IAPHUB performs receipt validation on the server using Apple's official APIs, ensuring that your receipts are always validated correctly and securely.

When Apple switches to the new SHA-256 intermediate certificate, our server-side validation will seamlessly support the update, ensuring uninterrupted validation for your users. You can rest assured that IAPHUB has already taken care of the necessary adjustments.

No Action Needed on Your Part​

For IAPHUB users, this update doesn’t require any changes to your app or your implementation. Unlike on-device validation, which may require updates to support SHA-256, our server-side receipt validation automatically handles these updates. You can continue to rely on IAPHUB to ensure your app’s in-app purchase validation process remains flawless, regardless of Apple's changes.

What About Developers Who Aren’t Using IAPHUB?​

If you're not using IAPHUB, you may need to review your receipt validation process. Apple’s move to SHA-256 will require updates to ensure your app continues validating receipts properly after January 24, 2025. Developers who use on-device validation will need to ensure their app can handle the new intermediate certificate to prevent potential issues.

Conclusion​

If you're using IAPHUB, you can rest easy knowing that the upcoming expiration of the SHA-1 intermediate certificate won’t affect your app. Our server-side receipt validation seamlessly supports the transition to SHA-256, so there’s nothing you need to do. IAPHUB ensures your in-app purchase validation process remains uninterrupted, allowing you to focus on growing your app rather than worrying about certificate changes.

Ready to future-proof your in-app purchase system and eliminate receipt validation concerns? Sign up for IAPHUB today and experience seamless, hassle-free validation!

We're happy to introduce two new features for your IAPHUB products!

Available now on:

• [email protected]
• [email protected],
• [email protected]
• [email protected]

Product Localized Title and Description​

You can now define the title and description of your products directly from the IAPHUB dashboard in all the languages your app supports.

To do this, start by editing your products on the IAPHUB dashboard and setting the title and description in each supported language.

Then, simply provide the language ISO code to the lang property in the start method of the IAPHUB SDK, and the localizedTitle and localizedDescription properties of your products will be loaded from IAPHUB instead of coming from Google or Apple (the default behavior).

If you need to update the user language, you can use the setLang method.

Product Metadata​

You can now define metadata for your products on the IAPHUB dashboard.

Metadata is structured information represented as key/value pairs, where each key is a string corresponding to a specific attribute of the product (such as 'credits' or 'category'), and each value is also a string that provides the relevant details (such as '100' or 'premium').

To do this, start by editing your products on the IAPHUB dashboard and setting the metadata properties of each product.

After doing so, the product metadata will be returned by the IAPHUB SDK along with all the other properties of the product.

With these new features, managing your products has never been easier. We hope you enjoy the enhanced flexibility and customization options!

We've added two new filters for your stores when using the smart listing feature.

You can now add a Start Date and an End Date, which allow you to define the earliest and latest dates for when a store's availability begins and ends.

These two additional filters can be useful if you're planning a temporary promotion.

Exciting news: IAPHUB has rolled out full support for StoreKit V2 on iOS 15 and above! 🚀📱

As you may know, IAPHUB uses Apple's StoreKit SDK under the hood to process your in-app purchases. While the previous version, StoreKit SDK (V1), has served its purpose, it also encountered several issues that Apple sought to address with the release of StoreKit V2.

And let me tell you, a lot has changed! Normally, upgrading your codebase to StoreKit V2 would be quite the undertaking. However, since you're leveraging IAPHUB, we've handled all the heavy lifting for you, ensuring a seamless transition without any noticeable differences on your end!

One of the standout features of StoreKit V2 is that Apple now returns the price and currency of a transaction when validating a purchase using their server API (you might not have been aware, but this wasn't the case before). This means no more reliance on client-side data, resulting in more accurate and transparent in-app purchases than ever before. Moreover, it's expected to be faster and more reliable, providing a smoother experience for both you and your users.

And rest assured, even if some of your users haven't made the leap to iOS 15 yet, IAPHUB has got you covered. We seamlessly transition to StoreKit V1 for iOS versions below 15, ensuring uninterrupted functionality for all users.

Before you begin, don't forget to configure the App Store Server API.
Update the IAPHUB SDK to the latest version, then simply set enableStorekitV2 to true when initializing the IAPHUB SDK using the start method. IAPHUB will automatically use StoreKit V2 if it's available.

Also, make sure to test a few transactions in the sandbox before rolling out your app update with StoreKit V2. Proper testing before publishing a change is always a good idea 🙂. Happy coding!

If you're using IAPHUB webhooks, a new major version (v2) is available.

This new version introduces the new transfer webhook.

The transfer webhook will be triggered when an active subscription (or non-consumable) is transferred to a different user ID.

This can occur when a user restores their purchases or replaces an active subscription using a different user ID, but only if the User transfer option on the IAPHUB dashboard is enabled, which is the default setting.

Our goal is to make things easier compared to the previous system (v1), which relied solely on the user_id_update webhook.

We recommend updating to the new version as soon as possible. Let's recapitulate the differences between the v1 and the v2:

Before (v1)​

The user_id_update webhook is triggered in the following scenarios:

• When a user restores an active subscription (or non-consumable) using a different user ID.
• When an active subscription is replaced using a different user ID.
• When an anonymous user (not logged in) with purchases logs in.
• When the user ID of a user with purchases is updated via the API.

Now (v2)​

The user_id_update webhook is triggered when user ID 1 becomes user ID 2.

It can happen in the following scenarios:

• When an anonymous user (not logged in) with purchases logs in.
• When the user ID of a user with purchases is updated via the API.

The transfer webhook is triggered when a subscription (or non-consumable) is transferred from user ID 1 to user ID 2.

It can happen in the following scenarios:

• When a user restores an active subscription (or non-consumable) using a different user ID.
• When an active subscription is replaced using a different user ID.

How to upgrade?​

Once your server can handle the transfer webhook properly, you can update the webhooks version from the Settings page of the IAPHUB dashboard.

Click on the Webhooks section, update the Webhook version input to version 2, and click on the Save button.

If any issue happens, you can still rollback to version 1.

A new property (subscriptionCancellationDate) is now available through the API & webhooks. It is the date IAPHUB detects a subscription auto-renewing has been cancelled.

You can find more information on the documentation.

Exciting news for Flutter developers! The IAPHUB SDK for Flutter is now available, providing an easy and user-friendly solution for in-app billing implementation for your iOS/Android apps.

Say goodbye to the frustration of understanding the StoreKit framework and the Google Billing Library, and the time and effort required to develop a server for managing subscriptions, processing receipts, and handling edge cases. With the IAPHUB SDK, you can effortlessly implement in-app billing without having to reinvent the wheel.

Implementing IAPHUB in your Flutter app has never been easier. Simply follow our comprehensive guide that will take you step by step through the process.

IAPHUB is thrilled to announce that we are now available on Adalo!

We understand that one of the biggest challenges facing app developers is figuring out how to monetize their creations. That's why we're dedicated to making in-app purchases as easy and accessible as possible.

With our new components on Adalo, we're confident that thousands of people who may not have coding experience will now be able to develop their own mobile apps and monetize them. Adalo is a powerful platform that allows anyone to create professional, polished mobile apps without needing to write any code. With IAPHUB integrated into Adalo, users can now easily add in-app purchases to their apps, making it simple to generate revenue from their creations.

Adalo users will finally be able to unlock a whole new realm of monetization options by being able to sell subscriptions or consumables within their apps. For example, with IAPHUB integration, Adalo users can now easily create paywalled content that is only available to users with a subscription. This opens up a whole new world of possibilities for app creators looking to generate revenue from their creations, whether it be through recurring subscription fees or one-time consumable purchases. The sky truly is the limit with the added capabilities that IAPHUB brings to Adalo.

We're excited to see what kinds of amazing apps people will create using our components on Adalo. Whether you're a seasoned developer or a complete beginner, we believe that our tools will help you take your app to the next level.

Get started now by taking a look at the comprehensive guide we've prepared for you.