MealVersity Restaurant Partner Finance & 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

---

Introduction

This Policy explains how MealVersity Technologies Private Limited ("MealVersity") manages Restaurant Partner prices, earnings, payments, settlements, platform margins, refunds, fines and other financial adjustments.

It forms part of the MealVersity Restaurant Partner Terms and Conditions.

1. No Commission from Restaurant

1. MealVersity does not deduct sales commission from the Restaurant's approved base item or add-on price.
2. The Restaurant determines or approves the amount it expects to receive for each item and add-on.
3. MealVersity may add a separate platform margin to determine the customer-facing selling price.
4. MealVersity's platform margin will not reduce the Restaurant's approved payout.
5. A change in platform margin will apply only to future orders.
6. Financial terms for a confirmed order cannot be changed retrospectively.
7. If any dashboard or historical record uses the word "commission", it refers to MealVersity's separately added platform margin and not a deduction from Restaurant earnings.

2. Customer-Facing Price

The standard item-price calculation is:

Restaurant-approved base price

+ MealVersity platform margin

= Customer-facing item price

Applicable packaging, delivery, handling, platform, small-order, surge and tax amounts may be added separately at checkout.

The customer must see the final payable amount before confirming the order.

3. Platform Margin

1. Platform margin is MealVersity's revenue for providing technology, customer acquisition, order processing, support and related services.

Platform margin may vary according to:

• Item or add-on;
• Category;
• Restaurant;
• Service zone;
• Promotion;
• Customer-facing pricing rules; and
• Operational cost.

1. Platform margin is added above the Restaurant-approved base price.
2. Platform margin must not appear as a Restaurant deduction.
3. MealVersity bears any reversal of its platform margin when the corresponding customer amount is refunded.
4. The Restaurant must not be made liable for MealVersity's platform-margin portion unless a separate amount was caused by verified Restaurant misconduct and is legally recoverable.

4. Restaurant Earnings

Restaurant earnings may include:

• Approved food-item base price;
• Approved add-on base price;
• Eligible packaging revenue;
• MealVersity-funded promotional reimbursement;
• Approved preparation or return payout;
• Approved positive adjustments; and
• Other Restaurant amounts stated in the order record.

5. Restaurant Settlement Formula

The net Restaurant settlement will be:

Restaurant base item revenue

+ Restaurant base add-on revenue

+ Eligible packaging revenue

+ MealVersity-funded promotional reimbursement

+ Approved positive adjustments

− Restaurant-funded discount or gift cost

− Verified Restaurant refund liability

− Valid cancellation fine

− Valid return charge

− Applicable statutory deductions

− Approved negative adjustments

= Net Restaurant Settlement

No MealVersity sales commission will be deducted.

6. Packaging Charges

1. The approved per-order packaging charge will be payable to the Restaurant.
2. The Restaurant must provide suitable packaging for every charged order.
3. The packaging charge must be reasonable and disclosed to the customer.
4. MealVersity will not deduct sales commission from packaging revenue.

A packaging refund or deduction may apply where:

• Packaging was not provided;
• Packaging was materially inadequate;
• Leakage or damage resulted from verified packaging failure; or
• A valid order was cancelled before packaging was used.

1. Packaging liability will be limited to the verified affected amount.

7. Delivery and Customer Fees

Unless otherwise expressly agreed, the following are not Restaurant earnings:

• Customer delivery charge;
• MealVersity platform fee;
• Handling fee;
• Small-order fee;
• MealVersity's share of surge fee;
• Customer's previous pending charges; and
• Other customer fees collected for another party.

Free-delivery promotions will not reduce Restaurant payout unless the Restaurant previously agreed to fund part of that promotion.

8. Offers, Discounts and Cart Gifts

Every promotion must identify its funding source.

Restaurant-funded promotion

Only the Restaurant's agreed contribution will be deducted from its payout.

MealVersity-funded promotion

The Restaurant's approved payout will not be reduced.

Jointly funded promotion

Each party's agreed contribution will be recorded separately.

For every promotion, the Restaurant should be able to see:

• Base price;
• Customer discount;
• Restaurant contribution;
• MealVersity contribution;
• Gift or add-on cost;
• Customer-facing price; and
• Final Restaurant payout.

A confirmed funding share cannot be changed retrospectively.

9. Online Payment

1. Online customer payments will be processed through MealVersity's authorised payment provider.

Restaurant earnings will be recognised only after:

• Payment verification;
• Successful order creation; and
• Restaurant acceptance.

1. Payment-gateway references will be retained for reconciliation.
2. If payment is captured but no order is created, the customer payment will be reconciled and will not be treated as Restaurant revenue.
3. The Restaurant must not request customers to make unauthorised direct payments.
4. Payment-provider charges will not be deducted from Restaurant earnings unless expressly agreed in writing.

10. Cash on Delivery

1. COD payments may be collected through authorised cash or QR methods.
2. COD collected by a delivery partner is not treated as cash directly received by the Restaurant.

MealVersity will reconcile:

• COD amount due;
• Amount collected;
• Collection method;
• Rider deposit or remittance; and
• Restaurant payout.

1. An unpaid COD order will not be recorded as successfully collected customer revenue.
2. Restaurant payout for a refused COD order will depend on the verified resolution.
3. The Restaurant must not request unauthorised cash from a customer or delivery partner.

11. Settlement

1. MealVersity will transfer eligible Restaurant earnings to the approved bank account according to the settlement cycle displayed in the Partner App or Commercial Schedule.
2. Each settlement must have a unique reference.

The Partner App should separately show:

• Unsettled earnings;
• Upcoming settlement;
• Completed settlement;
• Failed settlement;
• Refund deductions;
• Fines;
• Return charges;
• Adjustments; and
• Final payable amount.

1. Amounts below the disclosed minimum-settlement threshold may be carried forward.
2. MealVersity will not withhold undisputed earnings without contractual or legal grounds.

12. Settlement Statement

Every settlement statement should contain:

• Settlement ID;
• Settlement period;
• Included orders;
• Restaurant base sales;
• Add-on revenue;
• Packaging revenue;
• Restaurant-funded promotions;
• MealVersity-funded promotion reimbursement;
• Refund liability;
• Cancellation fines;
• Return charges;
• Taxes and statutory deductions;
• Manual credits or debits;
• Net settlement; and
• Bank-transfer reference.

MealVersity's platform margin must not appear as a Restaurant deduction.

13. Failed or Delayed Settlement

Settlement may be delayed when:

• Bank details are incorrect;
• Bank verification is pending;
• The bank rejects the transfer;
• Required tax or compliance information is missing;
• FSSAI or another mandatory document has expired;
• A legally required hold applies;
• A genuine financial dispute is under review;
• Fraud investigation is active; or
• A banking or payment-system failure occurs.

The Partner should be shown the reason and required corrective action.

14. Bank Account Changes

1. A bank-account change requires verification of the authorised Partner.

MealVersity may require:

• Mobile or email OTP;
• Cancelled cheque;
• Bank statement;
• Account-holder verification; and
• Administrative approval.

1. MealVersity may apply a reasonable security hold after a bank change.
2. The Restaurant must be informed about the hold and expected release condition.
3. Bank details will not be changed solely through an unverified call or message.

15. Customer Cancellation Before Preparation

If the customer validly cancels before preparation starts:

• The Restaurant will not receive food revenue for that order;
• No Restaurant cancellation fine will apply;
• No platform margin will be deducted from the Restaurant;
• Any premature deduction will be reversed; and
• The cancellation will not be recorded as Restaurant fault.

The Restaurant must stop preparation after receiving the cancellation notice.

16. Cancellation After Preparation Starts

If cancellation is requested after preparation begins, MealVersity may review:

• Preparation status;
• Preparation timestamp;
• Reason for cancellation;
• Restaurant conduct;
• Platform or rider delay;
• Customer conduct; and
• Available evidence.

An eligible preparation payout may be provided only where the applicable business rule permits it.

No preparation payout will be due where cancellation resulted from Restaurant fault.

17. Restaurant Cancellation Fine

The default fine for an unjustified Restaurant cancellation is:

₹50 per verified incident

A different amount may apply only if it is configured, disclosed in advance and accepted through the Restaurant's applicable Commercial Schedule.

The fine may apply where the Restaurant:

• Accepts an order despite unavailable items;
• Cancels without a genuine operational reason;
• Remains online while knowingly unable to fulfil orders;
• Provides a false cancellation reason;
• Accepts and repeatedly cancels orders; or
• Cancels because of an undisclosed Restaurant-side pricing error.

The fine will not apply where cancellation was caused by:

• Customer request;
• Payment failure;
• MealVersity platform failure;
• Delivery-partner failure;
• Verified equipment emergency;
• Serious food-safety concern;
• Government restriction;
• Natural disaster or force majeure; or
• Another event outside the Restaurant's reasonable control.

Every fine must show its order ID, reason, evidence status, amount and appeal option.

18. Missing-Item Charge

If a Restaurant is verified to have omitted an item:

1. Restaurant liability will normally be limited to the approved Restaurant base value of the missing item.
2. MealVersity will bear the reversal of its related platform-margin portion.
3. A packaging or delivery amount may be allocated separately only where the omission affected the complete order and the allocation is justified.
4. The same missing item must not be deducted twice.
5. The Restaurant must be allowed to submit packing or handover evidence.

19. Wrong-Item Charge

Where the Restaurant is verified to have supplied the wrong item:

• The Restaurant may bear the affected item's approved base value;
• Full-order liability may apply only when the wrong item materially affects the entire order;
• MealVersity's platform-margin portion will not be deducted as Restaurant commission;
• Redelivery cost may be allocated only where disclosed and reasonably caused by Restaurant fault; and
• The Restaurant may dispute the decision with evidence.

20. Food-Quality and Safety Charges

Verified Restaurant liability may arise from:

• Stale or unsafe food;
• Foreign object;
• Contamination;
• Incorrect dietary classification;
• Material quality failure;
• Materially short quantity;
• Food not matching its description; or
• Serious packaging failure.

Liability may include:

• Affected Restaurant base item value;
• Full Restaurant base order value where the entire order is affected;
• Reasonable and documented redelivery or investigation costs where contractually permitted; and
• Other actual liability imposed by applicable law.

There will be no automatic uncapped food-safety fine. Serious incidents may instead result in investigation, suspension, termination or action required by law.

21. Refund Liability Rules

1. Refund liability will follow verified responsibility.

Liability may be allocated among:

• Restaurant;
• Delivery partner;
• MealVersity;
• Customer; or
• Multiple responsible parties.

1. Restaurant liability must not exceed the verified Restaurant-related amount.
2. Item-level problems should ordinarily create item-level liability.
3. The same refund must not be deducted twice.
4. A pending complaint must not appear as a final deduction.
5. An unverified complaint must not be recorded as confirmed Restaurant fault.

The Restaurant should see:

• Order ID;
• Complaint reason;
• Affected item;
• Evidence status;
• Customer refund amount;
• Restaurant liability;
• MealVersity liability;
• Rider liability;
• Decision status; and
• Appeal route.

22. No Restaurant Liability Cases

The Restaurant should not bear a refund or charge caused solely by:

• Delivery-partner delay or misconduct;
• MealVersity platform failure;
• Payment-provider failure;
• Wrong delivery address caused by the platform;
• Customer fraud;
• Customer refusal without Restaurant fault;
• Customer unavailability;
• Unverified complaint;
• Duplicate customer claim; or
• MealVersity-funded promotion.

23. Refused-Order Finance

A customer refusal must be verified before financial responsibility is assigned.

MealVersity may consider:

• Whether the correct order was prepared;
• Food and packaging condition;
• Restaurant preparation records;
• Rider pickup and delivery evidence;
• Customer contact attempts;
• Payment status; and
• Final support decision.

The resolution may include:

• Return to Restaurant;
• Close without return;
• Restaurant payout;
• Rider payout;
• Customer refund;
• Customer charge;
• Return charge; or
• MealVersity-absorbed loss.

The Restaurant will not automatically be charged merely because the customer refused delivery.

24. Return-to-Restaurant Charge

A Restaurant return charge may apply only when:

• It was disclosed in advance;
• The Commercial Schedule permits it;
• A return actually occurred;
• The amount is proportionate;
• The reason is recorded;
• Operational evidence supports it; and
• It does not duplicate another charge.

The Restaurant must confirm whether the returned order was:

• Received;
• Complete;
• Incomplete;
• Damaged;
• Tampered with; or
• Not received.

A disputed return charge must remain pending until reviewed.

25. Fine and Charge Schedule

| Financial event | Restaurant financial treatment | | --- | --- | | MealVersity sales commission | No deduction | | MealVersity platform margin | Added separately to customer price | | Unjustified Restaurant cancellation | ₹50 per verified incident by default | | Valid customer cancellation before preparation | No Restaurant fine | | Missing item caused by Restaurant | Verified Restaurant base value of affected item | | Wrong item caused by Restaurant | Verified affected Restaurant base value | | Materially short quantity | Proportionate verified Restaurant base value | | Packaging failure | Verified affected amount | | Restaurant-funded discount/gift | Agreed Restaurant contribution | | MealVersity-funded promotion | No Restaurant deduction | | Rider/platform delivery failure | No Restaurant liability | | Return charge | Only disclosed and verified amount | | Duplicate deduction | Prohibited | | Unverified complaint | No final Restaurant deduction | | Serious food-safety violation | Actual verified liability and applicable legal/contractual action |

26. Manual Financial Adjustments

A manual credit or debit may be created only for:

• Calculation correction;
• Duplicate-deduction reversal;
• Settlement correction;
• Refund correction;
• Promotion correction;
• Tax correction;
• Approved compensation; or
• Dispute resolution.

Every adjustment must show:

• Reference number;
• Credit or debit;
• Amount;
• Reason;
• Date;
• Authorised decision; and
• Related order or settlement.

An unexplained manual debit is prohibited.

27. Taxes and Statutory Deductions

MealVersity may apply taxes or withholding required by law, including applicable:

• GST on MealVersity-provided services;
• TDS;
• TCS; or
• Other statutory deductions.

Statutory deductions must be shown separately.

The Restaurant remains responsible for its own registration, invoicing, reporting and tax obligations.

Product requirement: the final tax structure must be approved by a qualified Indian tax professional before this Policy is relied upon operationally.

28. Financial Holds

MealVersity may hold a disputed amount where:

• A refund or chargeback is pending;
• A bank-account change is under verification;
• Fraud investigation is active;
• A legal authority requires a hold;
• A genuine settlement dispute exists; or
• The Commercial Schedule permits an identified reserve.

The Restaurant must be shown:

• Amount held;
• Reason;
• Hold date;
• Expected review or release condition; and
• Appeal route.

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

29. Finance Disputes

The Restaurant may dispute:

• Missing settlement;
• Incorrect Restaurant payout;
• Platform margin shown as a deduction;
• Duplicate deduction;
• Incorrect refund liability;
• Incorrect cancellation fine;
• Incorrect promotional contribution;
• Incorrect return charge;
• Tax discrepancy;
• Manual debit; or
• Bank-transfer failure.

A dispute should be raised within 7 calendar days after the settlement statement becomes available.

MealVersity must:

1. Issue a ticket number.
2. Review transaction records.
3. Provide a reasoned decision.
4. Reverse any verified error.
5. Credit the correction through the next or a separate settlement.

Clear calculation errors and duplicate deductions may be corrected even after seven days.

30. Finance Support

Finance Support Email: business@mealversity.com

Partner Support Number: +91 8900099783

Support Hours: 24 hours a day, 7 days a week

Finance Escalation Officer: Tarik Anowar

Designation: Founder & CEO

Email: business@mealversity.com

Postal Address: 59 Uttar Sithi Road, Barasat, Kazipara, North 24 Parganas – 700125, West Bengal, India

Product requirement: the final settlement cycle, statutory tax treatment, return-charge amount and any zone-specific financial rule must be completed and approved before publication.

— End of Finance, Payment, Margin, Fine and Charges Policy —