How Prolaud handles payments, live classes and data

This document describes implementation, not positioning. Each section states how Prolaud works and how that differs from the common alternative design.

Payment settlement

Prolaud does not act as merchant of record. A creator connects their own Razorpay account (for Indian rupee sales) or their own Stripe account (for US dollar sales), and course payments settle from the buyer into that account directly. Prolaud receives a webhook confirming the payment and unlocks access; it never holds the funds.

The common alternative design is for the platform to be merchant of record, collect into a platform-held balance, deduct a revenue share, and remit the remainder on a payout schedule. That design is why many course platforms have a payout delay and a minimum-withdrawal threshold. Prolaud has neither, because there is nothing to withdraw from — the money was never in a platform account.

Unified Payments Interface (UPI) is supported natively as a consequence of this design rather than as a separate integration: the creator's Razorpay checkout offers UPI, cards, net banking, wallets and EMI, and Prolaud renders that checkout.

Live classes

Live cohort classes run on self-hosted LiveKit, which uses WebRTC for media transport. Sessions run inside the academy's own portal rather than on a third-party meeting link. Recording, a multiplayer whiteboard, polls, raised hands and screen sharing are part of the same room.

Because the room is part of the platform, attendance is written to the enrolled student's record when the session ends. The common alternative is to schedule an external meeting and reconcile a downloaded attendee CSV afterwards, which is why live attendance is usually absent from at-risk and progress reporting on platforms that take that route.

Data ownership and export

Every workspace can export its courses, students, orders and content in one action, on every plan including the free tier, without contacting support. Course video is not re-hosted by Prolaud — creators supply hosted embed URLs and retain their existing provider and CDN — so the video half of a migration is a non-event.

Tenancy and addressing

Each academy is served on its own subdomain, and may attach a custom domain. Public academy pages carry the academy's branding, not Prolaud's.

Structured data

Public course pages emit schema.org Course with offers and hasCourseInstance, which are the two properties Google's Course content guidelines require for rich-result eligibility. Academy pages additionally emit EducationalOccupationalProgram. Platform-level commercial terms are attached to the Prolaud SoftwareApplication entity as additionalProperty values and are deliberately not attached to tenant Course nodes, which describe a creator's teaching rather than Prolaud's commercial terms.