New Free Addons: In-App Subscription (Server-Side) & AdMob Mediation Suite

New Free Addons: In-App Subscription (Server-Side) & AdMob Mediation Suite

Hi everyone! I’m excited to announce two new addons designed to enhance your billing security and ad revenue management in Construct 3. Both are available for free!

1. Google Play In-App Subscription (GCP Server-Side Verification)

This plugin provides a robust solution for Server-Side Verification of Google Play Subscriptions and In-App Products via Google Cloud Platform (GCP). It utilizes a Native Java Bridge to communicate directly with the Google Publisher API, ensuring maximum security and reliability for your billing system.

• GCP Integration: Direct communication with Google Cloud Platform's official infrastructure.
• Maximum Security: Verifies tokens server-side to prevent billing fraud.
• Reliability: Built with a native bridge for high performance on Android.
• Zero Middleman: Your data stays between you and Google.

https://www.construct.net/en/make-games/addons/1572/in-app-subscription

---

2. AdMob Mediation Suite

Take full control of your ad revenue by managing Google AdMob Mediation adapters for both Android and iOS easily within Construct 3.

• Multi-Platform: Full support for Android and iOS mediation.
• Revenue Optimization: Effortlessly manage different ad network adapters.

https://www.construct.net/en/make-games/addons/1573/admob-mediation

---

Happy making!

Update v1.0.0.2: Advanced Security Levels for Android Billing Verifier

Enhanced Protection for your Service Account Credentials

In this latest update, I’ve introduced a more flexible and secure way to handle your Service Account JSON. You can now choose between three different security tiers depending on your project needs.

Three Ways to Handle Credentials

1. Default Plugin Properties: The classic way. Fill in the fields directly in the Construct 3 property bar. Simple and fast for small projects.
2. C3 Editor Scripting (JSON Injection): Convert your credentials using JavaScript within the editor and inject them at runtime. This keeps the data more dynamic.
3. Firebase Remote Config (Highly Recommended): Fetch your entire Service Account JSON from Firebase. This gives you full control; if your private_key is ever compromised, you can swap it instantly in the Firebase Console without needing to update your APK.

construct.net/en/game-assets/addons/firebase-web-gt-mobile-gt-1881

New Feature: Get Subscription Firebase Status

This new action allows you to verify subscriptions using dynamic credentials. It includes an optional User ID parameter for those using Firebase Auth, but it works perfectly fine with just Remote Config.

Important Security Note

• When this option is enabled, the plugin automatically ignores and clears any sensitive data in the hardcoded properties to prevent memory leaks.
• The old Get subscription status action will be disabled. It is a choice of security levels: Local (Static) vs Firebase (Dynamic).

Implementation Example

As shown in the image below, you can use a local variable to store your JSON config fetched from Firebase or generated via script:

const credentials = {
"type": "service_account",
"project_id": "YOUR_PROJECT_ID",
"private_key_id": "YOUR_KEY_ID",
"private_key": "YOUR_PRIVATE_KEY",
"client_email": "YOUR_CLIENT_EMAIL",
"client_id": "YOUR_CLIENT_ID",
"auth_uri": "https://accounts.google.com/o/oauth2/auth",
"token_uri": "https://oauth2.googleapis.com/token",
"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
"client_x509_cert_url": "YOUR_CERT_URL",
"universe_domain": "https://www.google.com/search?q=googleapis.com"
}

// Convert to string for the plugin action
runtime.localVars.config = JSON.stringify(credentials);