The payment reality of online education
A course platform or training provider loses students in two ways that look unrelated but aren't. A renewal that fails to authorize silently lapses an enrolment — the student didn't cancel, the payment just didn't clear, and by the time anyone notices, the student has moved on to a competitor or simply stopped logging in. In markets with low card penetration, some students can't pay at all, because checkout only accepts a method they don't hold.
Refunds add a second layer of friction specific to education: cooling-off periods, partial refunds for cohorts that start late or drop a module, and proration when a student upgrades mid-term. Handled manually, each of those is a support ticket that pulls someone off other work; handled on the payment platform, they're a transaction that settles like any other.
A failed renewal and a genuine cancellation look identical on most dashboards. We show you which one it actually was.
How CyberPay helps
Four capabilities, built around where education platforms actually lose enrolment: a failed renewal, a missing local method, or a refund handled by hand. Each is aimed at a specific point where enrolment quietly leaks, rather than a generic list of payment features.
Recurring tuition routed for authorization
Each renewal routed to the acquirer that performs best for it, so a subscription lapses because a student chose to leave, not because a charge failed for reasons unrelated to their intent.
Bank transfers and local methods where cards are rare
The methods a market actually uses added alongside cards, so enrolment isn't gated by card ownership in markets where students bank differently.
Refunds and proration
Cooling-off refunds, partial refunds and mid-term proration handled on the same platform used to collect, not as a manual reconciliation exercise for a support team.
Instalment-style collection
Where a market supports it, tuition can be collected across scheduled instalments rather than a single upfront charge that puts off price-sensitive students.
Methods and markets
Tuition and course fees clear differently depending on whether a market defaults to cards or bank rails:
- Cards, Apple Pay and Google Pay — for markets where card payment is the norm.
- Local bank transfer and Open Banking — in Europe and other markets where students pay directly from a bank account.
- Local eWallets — where a market's students rely on a wallet over a card.
- Refunds and proration — cooling-off periods and mid-term changes handled on the same platform.
CyberPay covers 73 markets across 6 regions — see the full coverage map.
Enrolment, renewal and refund all settle through the same reconciliation, regardless of the method or market a payment used, so the finance team isn't matching three systems against each other.
Integration
A course platform can collect tuition through the Hosted Cashier for the fastest path to launch, or the Direct API to keep enrolment on its own checkout. Recurring tuition, refunds and proration run on the same integration, with Query-Transactions for reconciliation. Test renewal logic against the sandbox before going live.
Use cases
Three ways education platforms use CyberPay to keep enrolment open across markets and keep renewals from lapsing silently before anyone notices. Each maps to a different shape of education business, but all three share the same underlying routing and reconciliation.
A course platform selling globally
A platform selling self-paced courses to students across dozens of countries adds the local methods each market needs, so a student in a market with low card penetration can still enrol, and renewals route for the highest chance of authorization month after month.
A university or training provider taking international tuition
An institution billing international students in multiple currencies collects tuition without asking every student to hold the same payment method, and reconciles fee payments from every market on one platform rather than one per region.
A cohort programme with instalments
A bootcamp or cohort-based programme collects tuition across scheduled instalments rather than one upfront charge, with each instalment routed for authorization and proration handled if a student changes plans mid-cohort.
Frequently asked questions
How does recurring billing work?
Renewals are routed to the acquirer best placed to authorize them, and failed renewals are visible immediately rather than surfacing as a support ticket weeks later. Renewal routing is applied automatically, so there's nothing to configure per student.
What about students in markets with low card penetration?
Local bank transfer, Open Banking and eWallets are added per market, so enrolment isn't limited to students who hold a card.
How are refunds and cooling-off periods handled?
Refunds, partial refunds and mid-term proration are issued on the same platform used to collect, reconciled alongside the original payment. Cooling-off periods are set to match the regulations of the markets you enrol students from.
What currencies can you bill in?
Tuition can be billed and settled across the currencies used in your served markets — see the full coverage map.
What happens when a renewal fails?
A failed renewal is visible in reconciliation immediately, rather than only showing up once a student has already disengaged and stopped logging in.
Ready to open enrolment everywhere?
One integration for recurring tuition, local payment methods and clean refunds, across every market your students are in.