Package earnings

A package pays you session by session, not at purchase. How the split is calculated, when each slice is released, and what a discount does to every future one.

View as .md

This is the most misread thing on the mentor side, so it is worth stating before anything else:

Why#

The buyer has paid for sessions they have not had yet. Until a session happens, it is owed rather than earned - and if the package expires unused, that was never your money to have been paid.

Releasing per redemption is what makes a package safe to sell without either side carrying the whole risk.

How the split is calculated#

At purchase, your net for the package is divided between the sessions in it, in proportion to what each child service sells for on its own.

A package containing one ₹2,000 call and one ₹3,000 mock interview splits 40/60, not 50/50. The mock interview is the bigger share because it is the bigger service.

That split is frozen onto the buyer's entitlement at purchase. Changing your prices afterwards does not re-cut a package already sold.

What a discount does#

This is where money is quietly lost.

The escrow is calculated from the discounted price. So a code does not reduce the first session - it reduces every redemption for the entire life of that package.

  1. A ₹10,000 package sells for ₹8,000 with a 20% code.
  2. Your net is taken from ₹8,000.
  3. That net is split across the sessions and frozen.
  4. Every redemption - this week or in eleven months - releases the smaller slice.

The service editor shows the split twice for exactly this reason: once at your list price, and again at the discounted price. If those two tables differ, the second is what you will be paid. It is rendered twice rather than explained in a sentence because otherwise you would be doing proportional arithmetic on your own money.

After a slice is released#

Each released slice then travels the normal payout stages - the dispute window, clearing, transfer. See when you get paid.

So there are two waits stacked on a package: waiting for the buyer to redeem, and then the ordinary wait on that redemption.

If a package expires unredeemed#

Sessions the buyer never used are not released to you. The validity you chose is a real commitment in both directions - you held capacity for that period, and they had that long to use it.

Cancelling a redeemed session#

Cancelled 6 hours or more before the start, the credit returns to the package and the slice goes back to being unreleased. Inside 6 hours, the credit is spent. Rescheduling and cancelling covers why the boundary is there.

Was this page helpful?

Last checked against the product on . Behaviour changes are listed in the changelog.