Skip to main content
NewChargeback Protection + Fee Intelligence for high-volume merchants. Get a savings analysis and a review of your dispute handling.See how it works
Details

Chargeback Protection + Fee Optimization

See how it works: high-volume merchants get automated dispute evidence, interchange optimization, and real-time savings visibility.

See how it works
Fee Check

Payment processing for online course providers and bootcamps

Payment processing for online course providers has to cover three jobs: a learner paying at checkout before course access opens, tuition collected in scheduled installments, and an employer paying an invoice for several seats. RapidCents handles them with Hosted Checkout, Recurring Payments, Payment Links and Invoicing, and your representative shows you how payment results reach your LMS.

Online course team reviewing tuition installments in the RapidCents dashboard beside a card terminal
An online course team checks checkout sales, tuition installments and seat invoices in the Merchant Dashboard.
  • PCI DSS Level 1
  • SOC 2 Type II
  • All major cards: Visa, Mastercard, Amex, Discover, UnionPay, Diners Club & PIN Debit
  • Interchange-plus available
  • Specialist onboarding support

How online course providers get paid

Online course providers and other edtech businesses get paid in six ways: learners pay in full at checkout, spread tuition over a payment plan, or put down a bootcamp seat deposit; subscribers renew memberships; employers settle seat invoices; and parents or sponsors pay for someone else. Each job has its own payer, trigger and failure point, and each needs a reference that ties the money to a learner, cohort or invoice.

  • Paying in full at checkout

    A learner buys a course or bundle on your sales page and pays the full price in Hosted Checkout, redirected or embedded in the page. An approved payment is what opens the course. If a card is declined, a checkout is abandoned or a coupon is applied in the course platform, the order simply waits. Finance gets one transaction carrying the order reference and learner email.

  • Spreading tuition over a payment plan

    Learners who cannot pay for a certificate or diploma course up front choose a payment plan: a first installment at checkout, then the balance on set dates from a card they authorized. What goes wrong is a declined installment partway through the course. Each installment reaches finance as its own transaction linked to the plan and the learner.

  • Bootcamp seat deposits and tuition installments

    A bootcamp student, or the parent or employer paying, puts down a deposit to hold a seat in a cohort, then pays tuition on dates tied to the cohort calendar. When an admissions advisor takes the deposit by phone, Virtual Terminal records it with an audit log. If a student withdraws or defers to a later cohort, the schedule changes with them. Finance sees the deposit and each installment under the cohort code.

  • Renewing a course membership

    Online course recurring payments cover memberships to a course library, community or coaching program, renewed monthly or yearly on a card the subscriber saved at sign-up. Recurring Payments sends a notification before each charge and uses Account Updater for reissued cards. If a subscriber cancels or a card expires, the renewal stops or updates. Finance sees one renewal transaction per subscriber per period.

  • Invoicing employers for training seats

    Corporate training invoice payments come from an employer's learning and development or accounts payable team buying seats for staff. You send a RapidCents invoice with a payment link, and the company pays by card, or by bank payment where enabled, against its purchase order. If seats are swapped, approval runs late or the company part-pays, the invoice shows it. Finance tracks each invoice from draft to paid.

  • Collecting from a parent or sponsor

    When someone other than the learner pays, such as a parent funding a teen's coding course or a sponsor covering a learner's fees, send that payer a payment link by email or SMS. The payer's name may differ from the learner's, and that is expected. Finance still files the payment under the learner's reference, and the receipt goes to whoever paid.

How do course tuition payment plans work?

Course tuition payment plans let a learner start after the first payment and pay the rest on a fixed schedule, charged to a card they authorized at checkout. With RapidCents, the learner picks the plan on your course page, pays the first installment in Hosted Checkout, and Recurring Payments runs the rest with automated retries. The plan is a collection schedule you set, not a loan to the learner.

  • How a payment plan runs

    The learner sees each amount and date on your course page before paying the first installment in Hosted Checkout, and the course opens once that payment is approved. Recurring Payments then charges the saved card on each scheduled date and sends a notification beforehand. Every charge produces a receipt for the learner and a Merchant Dashboard entry carrying the plan reference.

  • Terms and authorization to set up first

    Write plan terms the learner accepts before paying: number of payments, amounts, dates, what happens after a failed payment, and how to cancel. That acceptance is the authorization that lets RapidCents store the card as a token and charge it later, so keep it with the learner's record. If you add a fee for paying over time, ask your own advisor whether consumer credit rules apply.

  • When an installment declines

    Recurring Payments retries a declined installment automatically, and Account Updater can refresh card details after a bank reissues a card. If the retries fail, send a payment link for the missed amount so the learner can pay with another card. Whether the course stays open meanwhile is your rule, applied in your course platform; the payment record shows which installment is outstanding.

  • A $900 certificate course in three payments

    Say a provider sells a $900 project management certificate as one payment or three monthly payments of $300. A learner picks the plan, pays $300 at checkout and starts the first module. The second charge declines, a later automatic retry succeeds, and the third payment closes the plan. Finance sees three settled transactions under one plan reference, so the learner's balance is easy to check.

LMS payment gateway integration: enroll only after payment succeeds

An LMS payment gateway integration should create an enrollment only when a payment is approved and remove access when that payment is refunded. With RapidCents, your site sends the learner to Hosted Checkout or charges through the Payment Gateway API, a webhook reports the result, and your enrollment logic grants access on success. RapidCents processes the payment; your learning management system keeps the enrollment, progress and learner record.

  • Payment first, enrollment second

    The learner picks a course and goes to Hosted Checkout with your order reference attached. When the card is approved, a RapidCents webhook notifies your enrollment service, which asks the LMS to enroll the learner. The learner lands on a confirmation page, and the payment record carries the same order reference the LMS stores, so support can trace any enrollment back to its payment.

  • What your developer builds

    RapidCents integrates with many major platforms through APPIE and RapidBridge, and the right option depends on your LMS vendor and version. Where your developer builds the link, the Payment Gateway REST API covers authorize, capture, void, refund and tokenize, and webhooks report each result. Your developer writes the step that turns an approved payment into an enrollment and makes sure a repeated notification never enrolls a learner twice. If your LMS is software you sell to other schools, ask about Embedded Payments and Platform Payments.

  • Declines, refunds and disputes

    A declined card never reaches the LMS, so no enrollment is created and the learner can try another card on the same checkout page. A refund or a lost dispute should send the reverse instruction and remove access. Low-priced courses attract card testing, so use Fraud Prevention and 3D Secure where applicable. Dispute alerts, evidence and deadlines sit in the RapidCents dispute tools, while course activity logs stay in the LMS.

  • A self-paced course sale

    Say a learner buys a self-paced SQL course on a learning site your team runs. The site creates a pending order and sends the learner to Hosted Checkout. The card is approved, the webhook arrives with the order reference, and the course appears in the learner's account. Another learner's card declines; no enrollment is created, and the pending order expires under the site's own rules.

RapidCents products for online course providers

Hosted Checkout takes the first payment before access opens, Recurring Payments runs tuition plans and memberships, Payment Links reach the parent or sponsor who pays, and Invoicing bills employers for training seats. Each one carries your learner or invoice reference into RapidCents reporting.

Bootcamp installment billing: deposits, missed payments and withdrawals

Bootcamp installment billing takes a seat deposit when the enrollment agreement is signed, collects tuition on fixed dates through the program, pauses access when an installment stays unpaid, and refunds part of the schedule when a student withdraws. RapidCents covers the payment side with Contracts & eSignatures and Recurring Payments; your school sets the grace period, access rules and refund policy.

  • Enrollment agreement and seat deposit

    Send the enrollment agreement through Contracts & eSignatures, capture the student's signature and take the seat deposit in the same flow. The agreement should set out the tuition, installment dates, authorization to charge the stored card, cancellation terms and refund policy. When a parent or employer pays, the authorization has to come from that payer, and the agreement should name who receives the receipts.

  • Pausing access after a missed installment

    When an installment declines and the automatic retries fail, the payment record shows the failed attempt. Your team, or the LMS through a webhook, then follows the agreement: a grace period, a payment link for the missed amount, and a pause on course access if the balance stays unpaid. Once the student pays, access comes back the same way it was paused.

  • Refunding part of the schedule

    When a student withdraws mid-program, your written refund policy, or a licensing body's rules if your program is licensed, decides the amount owed. Refund the settled installments, or the part of one, that the policy returns, against the original transactions, then cancel the installments not yet charged. Each refund is recorded against the payment it reverses, so the ledger shows what was kept and what went back.

  • A bootcamp withdrawal in week five

    Say a 16-week coding bootcamp takes a $1,000 seat deposit at signing and four monthly installments of $2,500 from the first day of class. A student withdraws in week five, after two installments. Under the school's written policy, it keeps the deposit and first installment, refunds the second in full and cancels the last two before they run. Finance sees one refund linked to the second installment.

Compare fees using your real course payment mix

Compare processing fees using your own mix of checkout sales, installments, renewals and seat invoices, because that mix decides what you pay. RapidCents prices on interchange-plus: card-network interchange passes through at cost, your RapidCents markup is set out in your Fee Schedule, and fees for equipment or services apply if you use them. The agreement runs month to month, with no fixed term.

  • Online and stored-card payments

    Nearly every course payment is card-not-present: Hosted Checkout, payment links, invoices and stored-card installments. Online and keyed transactions usually carry higher interchange than tapped or inserted cards, so compare quotes on card-not-present volume rather than in-person examples. Sales at a live workshop or campus open day, taken on a terminal or with Tap to Pay, fall on the in-person side.

  • Who pays, and with which card

    A learner paying tuition with a premium rewards card, a subscriber on a debit card and an employer paying a seat invoice by corporate card each trigger different interchange. Commercial cards generally cost more than consumer debit, and cards issued in other countries can add cross-border network charges. Bank payments for large invoices are priced separately, so look at how your Fee Schedule lists them.

  • Installments, renewals and a worked mix

    Splitting tuition into installments turns one sale into several transactions, so any per-transaction charge repeats, and small monthly renewals feel fixed costs more than large tuition payments do. Picture a provider with a membership, a certificate on a three-payment plan and two corporate cohorts a year: three cost profiles. Comparing quotes on that mix, not one average ticket, shows where interchange and markup land.

  • What to bring to Fee Check

    Bring two or three recent processing statements, your split between checkout sales, installments, renewals and invoice payments, the average ticket for each, any corporate or international card share you know, and your refund and chargeback counts. Fee Check reads an uploaded statement and shows interchange separately from markup. List course platform fees on their own line so quotes compare like with like.

Using RapidCents alongside Thinkific, Teachable and your LMS

Your setup depends on which system takes the payment: hosted course platforms such as Thinkific, Teachable and LearnWorlds run their own checkout, while Moodle and Canvas LMS sites usually take payment through plugins or a separate registration system. RapidCents integrates with many major platforms through APPIE and RapidBridge, and your representative explains the option for your edition and country. Payment Links, Invoicing or the Payment Gateway API can also work beside the platform.

  • Thinkific

    Thinkific sites sell courses and bundles through Thinkific's own checkout, using the payment options Thinkific offers in its settings. Thinkific payment processor compatibility depends on your plan and country; your RapidCents representative will walk you through the right option. Sales outside the checkout, such as seat invoices, run through RapidCents Invoicing, with learners enrolled in Thinkific afterward.

  • Teachable

    Teachable runs one-time purchases, payment plans and subscriptions inside its own checkout, so the plan logic and the access rules live there. Check with Teachable which processors your plan and country allow, then talk to your RapidCents representative about the route that fits. Moving plans out of Teachable means your team takes over schedules and access changes, so weigh that when you plan the move.

  • LearnWorlds

    LearnWorlds combines course pages, checkout and learner access, with payment options configured in each school's settings. Your RapidCents representative will show you which payment route fits your LearnWorlds plan and country. If you take some payments outside LearnWorlds, use the learner email or order number as the shared reference so RapidCents reports and LearnWorlds records match.

  • Moodle

    Moodle, the open-source LMS, takes payment through enrollment and payment plugins installed on your site, so the setup depends on your Moodle version, the plugins you run and who maintains them. A developer or Moodle partner can connect your enrollment flow to the RapidCents Payment Gateway API and webhooks, so a course opens only after an approved payment. Your representative explains the options.

  • Canvas LMS

    Canvas LMS is mainly where courses, assignments and grades live; paid registration usually runs in a separate storefront or registration system in front of it. Tell your RapidCents representative which system takes the payment and they will show you how to connect it. Where that is not an option, send Payment Links or invoices for program fees and seat purchases, then enroll learners in Canvas LMS through your usual process.

Payment options for online course providers selling internationally

Payment options follow the country of your merchant account. RapidCents serves merchants in Canada and the United States, and the card brands, bank-payment methods and settlement currency on your account follow that country. Because learners enroll from anywhere, plan for cards issued in other countries, and your representative walks you through the options before you open a course to a new region.

  • Learners paying from other countries

    Your RapidCents representative can set up International Payments for learners who pay with cards issued in other countries. Those cards can carry different interchange and network charges, and some issuers decline unfamiliar cross-border payments, so watch decline reasons in the Merchant Dashboard and use 3D Secure where applicable as your audience grows abroad.

  • Bank payments and settlement currency

    Bank-payment options and the settlement currency come from the country of your merchant account, not from where the learner lives. Price courses in a currency your account supports, or ask your representative how other currencies are handled, before you publish prices for learners in other regions.

Switching processors with tuition plans still running

Once your account is approved, you can switch processors mid-term if you inventory every active plan and stored card first, test the new flow, and keep the old account open until its plans and refunds run out. Stored cards do not move on their own: a token transfer needs both providers to agree, and otherwise learners enter a card again with a new authorization. Reconcile each RapidCents deposit using the learner, cohort or invoice reference.

  • Inventory what is still in flight

    List every active payment plan with its remaining installments and next charge date, every membership renewal, every open corporate invoice, every refund promised but not yet issued, and every open dispute. Mark which plans started on the old processor: their stored cards, authorizations and history live there, and refunds on those payments go back through the account that took them.

  • Move stored cards with fresh authorization

    Ask both providers whether a token transfer is possible; it happens only when both agree. If not, each learner on a plan enters a card with RapidCents and gives a new authorization before their next installment, for example by paying that installment through a payment link. Learners who do not respond go on a follow-up list before their old schedule ends.

  • Test the full course flow first

    Before moving live sales, run a checkout sale that opens a course, a declined card that does not, a first plan installment, a partial refund on a bootcamp payment and an invoice paid by link. Check that each result reaches your course platform or LMS with the right reference, then move one product or cohort at a time while the old account winds down.

  • Reconcile deposits to the ledger

    Each settlement deposit groups many learner payments, so match it with the RapidCents settlement report rather than with course platform order totals. Carry the same order, cohort or invoice reference in RapidCents, your LMS and your books. RapidCents connects settled transactions, fees and refunds to QuickBooks Online and Xero, and SAP and NetSuite import settlement files. When tuition counts as revenue is your accountant's call.

Payment questions from online course providers

What is the best payment processor for online course providers?

The best payment processor for an online course provider is the one that handles your sales channels and workflows at a total cost you can verify; no single processor is best for every school. Compare checkout before access, course tuition payment plans, bootcamp installment billing, memberships and seat invoices, then platform compatibility, dispute handling and how deposits reconcile. Ask each provider, RapidCents included, for a written, itemized quote based on your own statements.

How much does credit card processing cost for online course providers?

Credit card processing for online course providers costs interchange, plus the processor's markup, plus any equipment or service fees, and the total depends on your card mix and channels. With RapidCents interchange-plus pricing, interchange passes through at cost and your markup is set out in your Fee Schedule. Online payments, premium rewards cards, corporate cards and cards issued in other countries generally cost more than tapped consumer debit. Upload a recent statement to Fee Check to see how your course payments split between interchange and markup.

Can Thinkific use a different payment processor?

It depends on your Thinkific plan and country: Thinkific's checkout uses the payment options Thinkific offers in its settings, so start with those settings and Thinkific's documentation. RapidCents integrates with many major platforms through APPIE and RapidBridge, and your RapidCents representative will walk you through the option for your plan and country. Payments outside the checkout, such as employer seat invoices or bootcamp deposits, run through RapidCents, and you enroll those learners in Thinkific yourself.

How can online course providers switch processors without losing payment history?

Keep your old processor account open while you move, download its transaction history, and list every stored card, active plan, open invoice and pending refund before the switch. Refunds on old payments go back through the account that took them, and stored-card tokens move only if both providers agree to a transfer; otherwise learners re-enter a card with a new authorization. Enrollment history stays in your course platform or LMS either way.

Which payment options are available to online course providers in Canada and the United States?

It depends on the country of your merchant account. RapidCents serves merchants in Canada and the United States: card payments through Hosted Checkout, Payment Links and Invoicing are the common core, while bank-payment methods and the settlement currency differ by country. Learners elsewhere can usually pay by card, subject to their card issuer. Your RapidCents representative lists the methods on your account so your course pages show the right options.

How can we collect tuition in installments?

Offer a payment plan on your course page, take the first installment in Hosted Checkout, and let Recurring Payments charge the saved card on the remaining dates. Before the first charge, the learner accepts terms covering the number of payments, amounts, dates, failed-payment handling and cancellation. Each installment settles as its own transaction with the plan reference, so finance can see every learner's balance. RapidCents collects the schedule you set; it does not lend money to the learner.

How can we enroll a student only after payment succeeds?

Make the approved payment the trigger for enrollment. Send the student to Hosted Checkout or charge through the Payment Gateway API, and let a RapidCents webhook tell your enrollment system when the payment is approved; only then does your LMS create the enrollment. A declined card creates nothing, and a refund should remove access. Your developer builds the webhook step, and your representative walks you through the options for your LMS and version.

How can we invoice a company for several course seats?

Send the company one RapidCents invoice with a line for each course or cohort, the number of seats and its purchase order number, plus a payment link. The company pays by card, or by bank payment where enabled, and the invoice shows as paid. Enroll the named learners once payment arrives, or earlier if your terms allow; seat swaps change the roster in your LMS, not the invoice.

How can we pause course access after a failed installment?

Pause access in your LMS or course platform when an installment stays unpaid after retries; RapidCents reports the payment result, and your platform controls access. Recurring Payments retries the declined charge automatically. If it still fails, send a payment link for the missed amount and apply the grace period in the learner's plan terms. A webhook can trigger the pause if your developer connects it; otherwise staff check failed payments in the Merchant Dashboard. Restore access once the learner pays.

How can we refund part of a bootcamp payment schedule?

Refund the installments your refund policy returns against their original transactions, then cancel the installments that have not run yet. Work out the amount from the written policy in the enrollment agreement, or from a licensing body's formula if one applies. Card refunds go back to the card that paid and are recorded against the payment they reverse, so reconciliation stays clear. Adjust course access in your LMS as a separate step.

What MCC is used for online course providers?

MCC 8299, schools and educational services not elsewhere classified, is commonly associated with online course providers, bootcamps and training companies. RapidCents sets the merchant category from what your business actually sells, so a company earning mainly from software licenses or digital downloads may be categorized differently. Describe your courses, memberships and corporate training accurately when you apply.

Industries with similar payment workflows

Software & SaaS, Digital Products, Downloadable Software, Gaming and E-commerce share the building blocks course providers rely on: checkout before access or delivery, stored-card renewals with retries, refunds that must also revoke access, and reports that tie each payment to an account or order.

See all industries

Take the next step

See what your course payments really cost

Upload a recent processing statement to Fee Check to see interchange separated from markup across your checkout sales, tuition installments, memberships and seat invoices. Then talk to your RapidCents representative about how payments reach your course platform or LMS.

Review my course payment costsOpen a Merchant Account
  • No obligation
  • Payment specialists, not a call centre
  • Secure statement upload