Payments Policy

Version: 2026-02-20

Last updated: 2026-02-20

This policy explains how lesson payments are authorized, charged, and recorded on DarsKhana.

1. Payment method requirements

  • Students must maintain at least one valid payment method for paid bookings.
  • A payment method that is linked to active/future bookings or scheduled charges cannot be removed until those links are resolved.
  • To remove a linked method: add a replacement method, set it as default, then update/cancel affected bookings as needed.

2. Charge timing and booking lifecycle

  • No immediate charge is taken at booking hold/creation stage.
  • Charges are scheduled only after tutor confirmation for paid non-trial bookings.
  • The standard charge attempt is scheduled for approximately 24 hour(s) before lesson start.
  • If tutor confirmation or reschedule confirmation happens inside that window, charge processing may be queued immediately.
  • If payment has not completed by the lesson close window, platform workers may auto-cancel the booking as unpaid under operational policy.
  • Free-trial and zero-value bookings do not create payable scheduled charges.

3. Failed payment handling

  • If a charge fails, DarsKhana may retry or request payment-method updates.
  • Retry behavior may include immediate retry, delayed retry, and infrastructure-safe retry depending on failure type.
  • Persistent payment failure can lead to booking disruption, cancellation, classroom access blocking, or account restrictions where necessary.
  • Users are notified of payment failure and required next steps by email/in-app messages where configured.

4. Invoices and receipts

  • Each successful payment may generate an invoice/receipt reference and downloadable record.
  • Invoice and payment metadata are retained for accounting, support, and compliance.

5. Refunds and reversals

  • Refund eligibility is governed by the Cancellation & Refund Policy.
  • Approved refunds are returned to the original payment method where possible.
  • When refunds affect tutor earnings/payouts, platform wallet and ledger adjustments may be applied.
  • For incomplete lesson outcomes, refund/cancellation handling may execute automatically under platform rules.

6. Payouts to tutors

  • DarsKhana currently supports two payout methods for tutors: Stripe Connect and MoneyGram.
  • Stripe Connect payouts: tutors with a connected Stripe payout account can request payout of available balance. Processing speed depends on Stripe account status, verification state, banking rails, and country-level payout schedules.
  • MoneyGram payouts: tutors using MoneyGram submit payout requests that are processed through platform/admin remittance workflow. Processing is not instant and depends on remittance batch timing, recipient details validation, and compliance checks.
  • Tutor balances become available based on settlement windows and may remain pending during dispute/risk review windows or while payment outcomes are still being finalized.
  • Payouts may be delayed, adjusted, or held where there is an open dispute, suspected fraud/risk event, charge reversal, refund impact, sanctions/compliance check, or missing payout verification data.
  • Payout availability and timing can differ by provider, corridor, country, banking calendar, and regulatory requirements.

7. Payment security

  • Payment flows use integrated provider infrastructure (e.g., Stripe) for secure method handling.
  • DarsKhana stores operational payment metadata and tokenized references, not full card PAN/CVV values.

8. Support for payment issues

For payment failures, invoice mismatches, or charge disputes, contact Admin@darskhana.com and include booking ID, invoice reference, and date/time.

Operational note: classroom access for non-admin users is generally blocked when a booking is unpaid, and lesson windows typically close 3 minute(s) after scheduled end unless changed in platform settings.

Related policies: Terms | Cancellation & Refunds | Privacy | Security | Safeguarding