Registration Payments & Receipts

How money moves when a learner pays to register, where receipts come from, and how to handle refunds.

Where the money goes

LecturePanda never holds your registration revenue. Funds move directly from the registrant's card to your own payment processor, and from there to your bank account.

The flow looks like this:

1. Registrant enters their card → your payment processor. The processor (Stripe, Neon Pay, Authorize.Net, Elavon, and others) charges the card.
2. Your processor → your bank account, on whatever payout schedule you've configured with that processor.
3. Your processor → LecturePanda. We receive a confirmation that the charge succeeded for the correct amount.
4. LecturePanda → registrant. On that confirmation, the learner is granted access to the course.

Our only role is being told the payment succeeded so we can open up the course.

"When will the money hit our account?"

That's set by your payment processor's payout schedule, not by LecturePanda. Check your processor's dashboard and bank settings — we have no visibility into their deposit timing.

Every organization connects its own processor. See Payment Processors for the supported list and setup, and Payments for how pricing rules determine what each registrant is charged.

Receipts

How registrants get a receipt

Two ways:

1. Attached to the registration confirmation email, sent immediately after they register.
2. From their LecturePanda account. If the learner has an account, they can sign in and download the receipt any time.

When a registrant says they never got their receipt, point them to the second option first — it's faster than re-sending anything.

Turning receipts on

Receipts are attached automatically when the receipt option is enabled in your course settings and the registrant paid for the course. Enable it early in your course setup so every registrant gets one from the start.

Your organization logo must be set

The receipt PDF pulls in your organization's logo when it generates. If no logo image is loaded on your account, receipts can fail to build — registrants see an error, a file that won't open, or no receipt at all. If several people report receipt problems at once, check your logo in Organization Settings → Company Info first.

What a receipt can and can't say

The receipt PDF carries your organization's logo and the business details from Organization Settings → Company Info, and that's the extent of what you control. There's no free-text block, so it can't carry a save-the-date, a promo message, or anything else you'd want to cross-sell with — and LecturePanda doesn't send texts at all.

That's a marketing-tool job rather than a receipt job, and there are three ways to do it properly:

• Marketing Tools — registrants opt in during registration, their address flows into Mailchimp or Constant Contact, and you send the promotion from there. Cleanest option for most organizations.
• Zapier — push registration data into whatever marketing or texting platform you already run and trigger the message from that side.
• Ask for a phone number as a registration question, then export the registrant list and use the numbers in your own texting tool. Manual, but needs no integration.

Receipts for past registrations

Turning receipts on covers every registration from that point forward, so it's worth enabling early in your setup. For transactions taken before then, your payment processor can produce a receipt for any historical charge from its own dashboard.

Refunds

Because you hold the merchant relationship, refunds are issued in your processor — the money moves the same way it came in. There are two steps, one for the money and one for access:

1. Refund the payment in your processor's dashboard. Find the transaction and issue the refund there.
2. Inactivate the registration in LecturePanda, if the person should no longer have access. Open the course's Registrants list, find them, and inactivate.

Keeping these separate is deliberate: it lets you refund someone while leaving their access in place — a goodwill refund for a learner who still wants to finish — or close access without touching a payment. Do both when you want the two fully in sync.

Some processors — TouchNet, for example — put a refund button right on the registrant's profile in LecturePanda, so you can handle the whole thing without leaving the page.

Your processor's own dashboard is a separate login

Card and settlement detail lives with your processor, and access to it comes from them, not from us — LecturePanda can't issue credentials for your Stripe, Elavon or Authorize.Net portal. Registration data, prices paid, and the Payment History reconciliation report all stay on the LecturePanda side.

What checkout looks like

The registration flow is the same whichever processor you use — price, optional discount code, pay — but the payment step itself may be served by the processor rather than by LecturePanda.

Stripe, Square and AffiniPay draw their card fields directly into the page. Elavon (Converge) opens the processor's own payment window over it, and TouchNet and BluePay embed the processor's page inside yours. All three of those look different from the rest of your course, and that's expected — card details go straight to the processor and never touch LecturePanda.

If you're switching processors, warn whoever handles registration questions that checkout will look different — it's the change learners notice, and it prompts "is this legitimate?" emails on the first day.