The ConsoleMint publishing partner program

Updated 23 July 2026 · ConsoleMint Team

What is a publishing partner?

A publishing partner holds a Google Play developer account in good standing and lets ConsoleMint publish apps through it. ConsoleMint writes the apps, submits them, updates them, keeps them policy-compliant and monetizes them with in-app advertising. The partner contributes distribution — the account — and shares in the ad revenue those apps generate.

The asset being monetized is the app, not the account. The account is simply the channel through which a real, maintained product reaches users, which is why the arrangement is priced against install scale rather than against the existence of an account.

Who qualifies as a publishing partner?

Anyone holding a Google Play developer account in good standing: no active policy strikes, no suspension history, and a verified developer identity. Both established or organization accounts and newer personal accounts qualify — they are simply placed on different payout structures, because they reach install scale at different speeds.

• Established / organization accounts — registered before November 2023, or registered as an organization rather than an individual. These reach install scale faster, so they are paid per app.
• Newer personal accounts — individual accounts registered more recently. These build scale more gradually, so they run on a staged structure that starts with a fixed monthly payout.
• Not eligible — accounts under suspension, accounts with unresolved policy strikes, and accounts the applicant does not actually own. Every account is checked before anything is published.

Full criteria are on the eligibility page.

How do established and newer accounts differ on payouts?

Established and organization accounts carry per-app terms because their apps typically reach install scale sooner, so revenue arrives sooner. Newer personal accounts run a staged schedule that begins with a fixed monthly amount during ramp-up and converts to a revenue share as installs land. Neither structure is better in the abstract.

Stages 2 to 4 are performance-driven and reviewed roughly every 45 days against real install and revenue data — they are not fixed sums. Only the ramp-up stage is fixed. Across the book, annual outcomes range from ₹3–7 lakh, driven by account age, app count and install volume. The mechanics are explained in full on how ad revenue share works.

What access do you grant, exactly?

Access is granted inside Google Play Console under Users and permissions, by inviting a separate ConsoleMint Google account and assigning it the Developer role, scoped to the apps we publish. You never share your Google password, your two-factor authentication stays intact, and account ownership never moves. Removing that user takes two clicks.

Play Console’s multi-user permission system exists so that studios, agencies and contractors can operate an account alongside its owner. Using it is the intended path, not a workaround. See is it safe and is it legal.

What does ConsoleMint do, and what do you do?

ConsoleMint does all of the technical and commercial work. The partner does an onboarding step at the start, and then nothing operational — no builds, no releases, no user support, no policy correspondence, no advertising setup.

How many apps go on your account?

A maximum of 10 apps. The cap is deliberate: it keeps the account’s publishing pattern within what Google expects from a normal developer, keeps every app properly maintained rather than shipped and abandoned, and avoids the high-volume churn pattern that attracts policy scrutiny. It protects the asset the partnership depends on.

How does the partnership grow over time?

Through two levers. Apps already live on the account keep accumulating installs, so the revenue share keeps rising with no action from either side. Beyond that, ConsoleMint either publishes additional apps to the account up to the 10-app ceiling, or transfers existing apps across to it, so total revenue compounds rather than plateauing.

Once the arrangement has converted out of ramp-up, the payout tracks what the apps actually earn. The 10-app cap bounds how many surfaces can earn at once; it does not bound how much any of them can earn.

How long does review and onboarding take?

Review takes 24–48 hours. You send your developer account details, we check age, type and standing, and we come back with the payout structure your account qualifies for. Nothing is granted and nothing is published until you accept, and there is no obligation to continue after review.

1. Submit your account for review. Send the account details through the submission form so we can check age, type and standing.
2. Receive your payout structure. Within 24–48 hours you get the terms your account qualifies for — per app, or the staged ramp-up schedule — with the payout dates.
3. Grant Developer-role access. If you accept, invite our Google account under Users and permissions and assign the Developer role. No password changes hands.
4. We publish and maintain. Apps are built, submitted, updated and monetized by ConsoleMint, up to the 10-app ceiling.
5. You are paid monthly. Between the 1st and 5th, by UPI or bank transfer, with an earnings statement each cycle.

How and when are you paid?

Between the 1st and 5th of each month, by UPI or direct bank transfer in INR, with an earnings statement for the cycle. During ramp-up the amount is fixed regardless of what the apps have earned. After conversion it is a share of actual ad revenue, stepped up on a performance review roughly every 45 days.

How do you end the partnership?

By revoking access in Play Console, which takes two clicks. The agreement asks for 30 days notice so the live apps can be transitioned cleanly rather than stranded mid-release, but the technical control never leaves you — there is no mechanism by which ConsoleMint could retain access to an account whose owner has removed it.

Who you are partnering with