Payment Gateway Integrations
Money moves through The Academix in two ways — a student buying a course, and an institute paying for its own Academix plan. Both are backed by real gateways wired into the backend: Razorpay and Stripe.
Course Purchase Checkout — Razorpay
When a student buys a course through an institute’s storefront, the backend creates a Razorpay payment link scoped to that course, institute, and buyer — the student pays through Razorpay’s own hosted checkout rather than a form built into The Academix. Razorpay sends the buyer an SMS and email confirmation once the link is generated, and the order is recorded against the institute and course before payment is even confirmed.
This is a one-time payment per course, not a recurring per-course charge — there is no per-course subscription billing for students today.
Recurring & Subscription Billing
Recurring billing isn’t limited to a single flow. Razorpay’s Subscriptions API is wired in directly — the backend requests a subscription, gets back a subscription ID that the checkout page bills against, and a dedicated webhook (signature-verified, and de-duplicated by event ID) confirms each billing cycle. Stripe runs an equivalent recurring flow through Checkout Sessions in subscription mode, with prorated amounts when a plan is upgraded mid-cycle, coupon codes, and tax rates applied automatically to the invoice.
This recurring machinery bills an institute for its own Academix plan — priced by student count and billed monthly or yearly — rather than billing a student for a course subscription. Course purchases, described above, stay one-time payments.
Currency
Both gateways are built to bill in more than one currency, not hard-coded to a single one.
Razorpay
Course payment links accept a currency parameter and default to INR when none is set. The subscription flow prices plans using a currency looked up against the institute's country.
Stripe
Checkout sessions build their line-item price from the currency code stored against the institute's plan, converting the amount before the session is created.
That’s currency-level flexibility in the payment code, not a claim about specific supported countries, local payment methods, or regulatory coverage beyond what each gateway itself provides.
Webhooks, Verification & Receipts
Payments aren’t marked complete on the strength of a redirect alone. Razorpay posts to a signed webhook endpoint — verified against its signature header — before an order’s status flips to paid, and a separate callback-verification endpoint checks payment status directly. Stripe’s webhook does the equivalent job for subscription events: it verifies the Stripe signature, then retrieves the relevant subscription, payment intent, or invoice before updating the institute’s billing record.
Once a course payment clears, a PDF receipt — itemized as a course purchase, with the buyer’s details attached — is generated automatically and available for download.
Ready To See The Payment Flow In Action?
Book a demo and we'll walk through course checkout, subscription billing, and receipts end to end.
Book a demo