1. Scope
This Payment Policy applies to Users and Partners of MARRYMANTRA SERVICES PRIVATE LIMITED. Users select a payment schedule during booking. Partners accept applicable payment policies during KYC (Step A6) and when collecting advances.
2. Token and advance
Token: default ₹5,000 (config key booking.token_amount), typically prepended by the payment engine.
Advance: default 20% of booking total (booking.advance_percentage), platform-locked as part of confirmation.
Paying token/advance helps confirm intent and enables vendor locking / assignment workflows as described in the Terms of Service.
3. Payment schedule policies
Available policy templates include: Standard, Milestone, 50-50, Minimal, and Pay-as-you-Go. Leftover phases after token and advance sum to 100% of (total − token − advance).
Phase timing examples: Within 3 days; Before event (−15 days); Midpoint; Event day; After completion (+2 days). Exact schedule is shown in-app before you confirm.
Multi-day events may use SPLIT_EVENT_DAYS allocation where enabled.
4. What is collected via gateway today
Razorpay (or mock provider in non-production) currently collects TOKEN and ADVANCE phases online. MID, EVENT_DAY, and FINAL phases may display in the schedule and be collected later via product updates, payment links, or City Manager offline marking.
Ledger kinds may include TOKEN, ADVANCE, PROGRAM (onboarding fees), and WALLET_* movements.
5. Razorpay and merchant of record
Online payments are processed by Razorpay. Card/UPI data is handled by Razorpay under its terms. MarryMantra records order/payment identifiers and amounts for reconciliation.
Unless otherwise stated on a receipt, Platform collects token/advance as marketplace facilitator; partner service portions are settled under Partner Payout Terms.
6. Partner onboarding fees
Partners may pay UPFRONT, YEARLY, or follow PAY_AS_GROW economics. Fee amounts are shown before payment in the Partner App. Failed onboarding payments may block KYC completion.
If KYC is rejected after payment, refund handling is case-by-case via support (gateway fees may be deducted).
7. Offline / City Manager marking
Authorised City Managers may mark advance paid for operational cases (e.g., cash collected through franchise office). Such marks are binding for booking status and commission triggers when recorded in the system.
8. Invoices and GST
Where GST invoices are generated, buyer/seller snapshots (names, addresses, GSTIN) are stored. Users and Partners should provide accurate tax details.
9. Failed payments and chargebacks
Failed Razorpay attempts do not confirm a booking phase. Successful capture (webhook payment.captured) confirms payment. Chargebacks or payment disputes may pause fulfilment and trigger clawbacks of related commissions/rewards.
10. Not escrow
Funds are not held in a statutory escrow account for Users or Partners unless a separate escrow product is explicitly offered in writing.
11. Refunds
Refund eligibility follows the cancellations section of the User Terms of Service. Approved refunds are returned via the original payment method or wallet credit where Razorpay/banking constraints require.
12. Changes
Token amount, advance percentage, and schedule templates are admin-configurable. The schedule shown at confirmation binds that booking. Policy document updates publish at /payment-policy.
Contact: support@marrymantra.in.