MealVersity Delivery Partner Finance, Earnings, COD & Settlement Policy

Entity: MealVersity Technologies Private Limited
CIN: U62099WB2025PTC284465
Effective Date: 1 August 2026
Last Updated: 1 August 2026
Registered Office: 59 Uttar Sithi Road, Barasat, Kazipara, North 24 Parganas – 700125, West Bengal, India
Contact: business@mealversity.com | +91 8900099783

1. Financial Principles

  1. Every earning, deduction or adjustment must have a delivery, settlement or incident reference.
  2. The Rider should see the expected ordinary payout before accepting a delivery, where operationally possible.
  3. A confirmed delivery’s payout terms cannot be reduced retrospectively without a valid correction or verified incident.
  4. MealVersity will not make an unexplained deduction.
  5. The same loss, fine or adjustment must not be deducted twice.
  6. A performance score alone will not create an automatic financial penalty.
  7. The Rider may dispute an incorrect earning, COD entry, fine or adjustment.

2. Rider Earnings

Rider earnings may include:

Only earnings applicable to a particular delivery will be included.

3. Expected Payout

A delivery opportunity should show, where available:

The final payout may change only because of:

4. Standard Completed-Delivery Payout

For a successfully completed delivery, Rider earnings may be calculated as:

Base delivery payout
+ Eligible distance payout
+ Eligible waiting payout
+ Rider’s surge share
+ Applicable incentive or bonus
+ Approved reimbursement
+ Approved positive adjustment
− Valid fine
− COD or wallet adjustment
− Applicable statutory deduction
= Net Rider earning

The applicable rates must be available in the Rider App or zone-specific Finance Schedule.

5. Base Delivery Payout

  1. The base payout is the minimum delivery earning applicable to an accepted and successfully completed order.
  2. The amount may vary by: Service zone; Vehicle type; Delivery type; Distance band; Time; Demand; and Applicable campaign.
  3. The applicable base payout should be shown before acceptance.
  4. MealVersity must not reduce the base payout after completion without an auditable reason.

6. Distance Payout

  1. Distance may be calculated using MealVersity’s approved mapping or routing system.
  2. The Finance Schedule must state: Included distance; Per-kilometre rate; Maximum eligible distance; Rounding method; and Whether pickup and customer legs are both included.
  3. GPS or route manipulation is prohibited.
  4. A genuine route diversion caused by closure, safety or traffic may be reviewed.
  5. A materially incorrect distance may be disputed through Rider Support.

7. Surge and Peak-Time Earnings

  1. MealVersity may offer additional payout during high demand, difficult weather or selected time periods.
  2. The offer should show: Surge amount or Rider share; Eligible zone; Eligible period; Completion requirement; and Applicable cap.
  3. A confirmed surge benefit must not be removed after successful completion unless the delivery was fraudulent or otherwise ineligible.
  4. Customer surge fees and Rider surge payouts may be different amounts and must be recorded separately.

8. Waiting-Time Payout

Waiting payout may be available for verified waiting at:

A waiting payout applies only when:

  1. Arrival was recorded at the correct location.
  2. The required waiting threshold was completed.
  3. The Rider remained reasonably available.
  4. The delay was not caused by the Rider.
  5. The applicable zone rule provides a waiting payout.

The Finance Schedule must state the free waiting period, per-minute or fixed payout, and maximum cap.

The mandatory 10-minute customer waiting period does not automatically create additional payout unless the applicable Finance Schedule provides it.

9. Return-to-Restaurant Payout

When support approves return to the Restaurant, Rider earnings may include:

Return payout requires:

A false return claim is not eligible for payout.

10. Customer Refusal Finance

Customer refusal must be verified before finalising Rider earnings.

Approved return to Restaurant

The Rider may receive:

Original eligible Rider payout
+ Approved return payout
− Valid Rider fine
= Final Rider payout

Prepaid order closed without return

Where the Rider completed the required delivery attempt and support closes a prepaid order without return, the Rider may retain the eligible completed-delivery payout according to the approved resolution.

Unpaid COD order closed without return

An uncollected COD order is not customer revenue. Rider payout will follow the approved refusal resolution and may be zero where no eligible delivery or return payout is authorised.

The final result must be visible in the delivery finance record.

11. Rider Incentives

Incentives may be based on:

Each incentive must state:

MealVersity must not change completed incentive conditions retrospectively.

12. Customer Tips

Where customer tipping is supported:

  1. The approved tip will belong to the Rider.
  2. MealVersity will not deduct commission from the tip.
  3. The tip should appear separately from delivery payout.
  4. Any payment-provider or statutory treatment must be disclosed.
  5. The Rider must not demand or pressure a customer for a tip.

13. Cash on Delivery Collection

  1. COD money is collected on behalf of the authorised party and does not belong to the Rider.
  2. The Rider must collect only the amount displayed in the app.
  3. COD may be collected through: Cash; Authorised Rider QR; MealVersity QR; or Another approved method.
  4. The Rider must not use an unauthorised personal QR or bank account.
  5. COD payment must be verified before the order is marked delivered.
  6. Every collection must show: Delivery ID; Amount; Collection method; Collection time; Payment reference, where applicable; and Deposit or reconciliation status.

14. COD Cash Reconciliation

Collected COD cash may be reconciled through:

The Rider must follow the stated deposit deadline.

MealVersity must provide:

15. COD QR Payment

  1. The Rider must use only the QR generated or approved for the delivery.
  2. A screenshot or customer statement alone does not establish successful payment.
  3. The payment must be verified through the authorised payment system.
  4. The Rider must not mark QR payment received while its status remains pending.
  5. Duplicate or excess QR payment must be reported immediately.
  6. An authorised QR payment will not be treated as cash held by the Rider.

16. Rider Wallet

The Rider App may maintain a wallet or ledger showing:

Wallet entries must be append-only or otherwise fully auditable.

The Rider should be able to view the source and reason for every entry.

17. COD Access and Wallet Restrictions

MealVersity may restrict new COD assignments where:

The Rider must be shown:

Prepaid delivery access should not be unnecessarily restricted because of a disputed COD amount.

18. Rider Settlement

  1. MealVersity will transfer eligible Rider earnings to the approved bank account according to the payout cycle displayed in the Rider App.
  2. Each payout should have a settlement reference.
  3. The Rider should be able to view: Pending earnings; Upcoming payout; Completed payout; Failed payout; COD adjustment; Fine; Incentive; Tax deduction; Other adjustment; and Final paid amount.
  4. An amount below a disclosed minimum-payout threshold may be carried forward.
  5. Undisputed earned payouts must not be withheld without contractual or legal grounds.

19. Rider Settlement Statement

Every Rider statement should show:

20. Failed or Delayed Payout

Payout may be delayed when:

MealVersity should show the reason and required corrective action.

Only the reasonably disputed amount should be held unless a broader hold is legally justified.

21. Bank Account Changes

A bank-account change may require:

MealVersity may apply a reasonable security hold after a verified bank-account change.

The Rider must be notified about the hold and release condition.

22. Valid Fine Requirements

A Rider fine may be applied only when:

  1. The applicable rule was disclosed.
  2. A specific incident occurred.
  3. Evidence supports Rider responsibility.
  4. The amount is proportionate.
  5. The amount does not exceed the disclosed cap.
  6. The same loss is not recovered twice.
  7. The Rider receives the reason and incident reference.
  8. The Rider can appeal.

A pending investigation should appear as pending and not as a completed fine.

23. Tracking-Related Fines

A tracking-related fine may be considered for verified:

A fine must not apply for:

Tracking fines must have category-specific amounts and a total per-delivery cap in the Finance Schedule.

24. Delivery Abandonment Fine

A fine or loss recovery may apply where the Rider:

No fine will apply for a verified accident, breakdown, emergency, unsafe condition or support-approved reassignment.

25. COD Shortage or Misappropriation

Where COD cash is not deposited:

  1. The amount collected may be recorded as Rider COD liability.
  2. The amount may be adjusted against Rider earnings according to the disclosed reconciliation rule.
  3. The Rider must receive a transaction-level statement.
  4. A genuine mismatch must remain disputable.
  5. Confirmed theft or deliberate misappropriation may result in suspension, termination and legal recovery.
  6. MealVersity must not recover more than the verified outstanding amount plus a separately lawful and disclosed charge.

26. Food Damage or Tampering

A Rider may be financially responsible where evidence establishes that the Rider:

Liability should be limited to the verified loss caused by the Rider.

The Rider will not be responsible for an item missing inside an intact sealed package unless other evidence establishes responsibility.

27. False Status or Evidence

A fine may apply for verified:

Serious fraud may result in termination in addition to financial correction.

28. Late Delivery

A Rider will not be fined solely because an order was delivered late.

MealVersity must consider:

A fine may apply only where avoidable delay resulted from verified Rider misconduct, such as an unauthorised extended stop or deliberate route manipulation.

29. Customer or Restaurant Complaint

A complaint does not automatically create a fine.

Before imposing financial liability, MealVersity should review:

Unverified complaints must not appear as confirmed Rider financial liability.

30. Fine Schedule

The final amount for each category must be published in the Rider App or zone Finance Schedule.

| Incident | Financial treatment | | --- | --- | | Genuine offer rejection | No fine | | Valid customer refusal | No automatic Rider fine | | Customer unavailable after 10-minute wait and three attempts | No automatic Rider fine | | Restaurant delay | No Rider fine | | Platform or payment failure | No Rider fine | | Verified delivery abandonment | Disclosed capped fine or verified loss | | Verified location disabled during active delivery | Disclosed category fine | | Verified deliberate network disconnection | Disclosed category fine | | Verified heartbeat manipulation | Disclosed category fine | | Verified location spoofing | Disclosed capped fine and account review | | False delivered status | Verified loss plus disclosed capped fine | | COD shortage | Verified outstanding amount | | COD misappropriation | Verified outstanding amount and applicable legal action | | Food tampering or theft | Verified loss and account action | | False refusal or return evidence | Disclosed capped fine and account review | | Duplicate deduction | Prohibited |

31. Fine Caps

  1. Each tracking category must have a disclosed maximum.
  2. The total tracking fine for one delivery must have a disclosed per-case cap.
  3. A financial deduction cannot exceed the verified Rider earning or stated cap unless it represents: Unreturned COD cash; Theft; Fraud; Court-ordered recovery; or Another separately established legal liability.
  4. Any outstanding amount carried forward must remain visible and disputable.

32. Manual Adjustments

A manual credit or debit may be created only for:

Every adjustment must show:

An unexplained manual debit is prohibited.

33. Reimbursements

MealVersity may approve reimbursement for:

The Rider may be required to provide a receipt or other reasonable evidence.

MealVersity is not required to reimburse an unauthorised personal expense.

34. Taxes and Statutory Deductions

MealVersity may apply legally required:

Each deduction must be separately displayed.

MealVersity should provide available tax statements or certificates required by law.

The final tax and social-security treatment must be approved by qualified Indian legal and tax advisers.

35. Financial Holds

A temporary financial hold may apply because of:

The Rider must be shown:

MealVersity must release undisputed funds when the reason for the hold ends.

36. Finance Disputes

A Rider may dispute:

A financial dispute should be raised within 7 calendar days after the entry or settlement becomes available.

MealVersity must:

  1. Issue a ticket number.
  2. Review transaction records.
  3. Consider Rider evidence.
  4. Provide a reasoned decision.
  5. Reverse a verified error.
  6. Pay or credit an approved correction.

A clear calculation error or duplicate deduction may be corrected after seven days where appropriate.

37. Finance Support

Rider Finance Email: [Finance Email]

Rider Support Number: [Phone Number]

Support Hours: [Support Hours]

Finance Escalation Officer: [Full Name]

Designation: [Designation]

Email: [Escalation Email]

Postal Address: [Full Address]

Before publication, MealVersity must complete the zone-specific payout rates, settlement cycle, waiting rates, tracking-fine amounts, per-delivery fine cap, COD deposit deadline and minimum-payout threshold.

MealVersity Technologies Private Limited · CIN: U62099WB2025PTC284465