

Keep your card checkout as the default, and add one route that does not run through a bank. Cards will serve most of your students. The ones they fail are usually students in a country where an issuer, a processor or a compliance rule sits in the way, and retrying the card does not move any of those.
For those students the working answer is a payment they make from their own wallet: a stablecoin transfer, priced in dollars, that lands in minutes and asks nobody's bank for permission. A stablecoin is a token pegged to a currency — one USDT is meant to be worth one dollar, and in practice it stays close.
That is the whole answer. The rest of this is the detail you need to run it: why a foreign card declines, what course payment processing actually costs you, what changes when a programme is paid in three instalments, and how you give money back halfway through a course when the payment cannot be reversed.
You will rarely be told the real reason. Decline codes are written to be vague on purpose, so that a fraudster cannot use them as feedback. But the causes sit in four places, and it helps to know which one you are looking at.
The first cause you cannot fix. The middle two you can improve a little by tidying the checkout — clearer descriptor, local currency shown, fewer fields, a retry that does not lose the cart. That work is worth doing before you conclude the rails are broken, and it is a separate craft: what actually moves payment conversion is mostly small things done in order.
But if the same country keeps failing for every student, stop optimising. You are looking at cause one or cause two, and the answer is a second route, not a better form.

Card pricing across the industry has the same shape wherever you look, and it is worth seeing all four layers, because sellers usually budget for the first one only.
There is one more layer people discover late: when you refund a card sale, the processing fee from the original payment generally stays with the processor. Refund a 500-dollar course in full and you are out the fee as well as the course.
Crypto payments have their own cost stack — a gateway percentage plus a network fee that depends on which chain the transfer used — and it is worth knowing how crypto payment fees are actually built before you compare the two on a spreadsheet. The honest comparison is not "cheaper"; it is that the crypto stack does not grow when a student is far away.
Here is the mechanism, plainly. You send the student an amount to pay and an address to pay it to. They open the wallet app they already use, send that amount, and a minute or two later the payment is confirmed on the network and shows up as settled on your side. No issuer approves it. No acquirer holds it. No currency is converted on the way.
Two choices sit inside that. The first is which stablecoin you price in, and the differences that matter there are practical rather than technical: which one your students already hold, which networks it runs on, how easily it turns back into bank money at your end — choosing between the main stablecoins works through the trade-offs.
The second is the network. Take USDT: the same token exists on several blockchains, and a transfer sent on one your checkout does not accept simply does not arrive.
What each chain charges moves about, and not in the order the old rules of thumb suggest. On Ethereum a USDT transfer costs cents while the network is quiet and climbs into dollars when it is busy. On TRON the sender burns a set amount of TRX every time — a few dollars at today's TRX price — unless their wallet has TRX staked to cover transfers, in which case it costs close to nothing.
Settle which chains you accept before your first invoice, because that choice decides what your students pay to pay you: the differences between the USDT standards lays them out side by side.

Now the limit, because this route has a real one. Your student needs a wallet with money already in it, plus a small amount of the network's own coin to pay the transfer fee: a wallet holding only USDT cannot send USDT on TRON, Ethereum or BNB Chain. That second part catches people out constantly, and it is worth reading why a payment fails when the gas coin is missing before you talk a student through their first transfer.
Someone who has never touched crypto will not do all of that to buy your course this evening. This is a second route for the people cards fail, not a replacement for the people cards serve.
Adding it is not a rebuild. A hosted checkout window over your existing page, a payment link sent by email, or an API call from your own backend — the four ways to add crypto to a site differ mostly in how much of your own code is involved. If you are weighing whether the whole thing is worth it, the numbers to ask any provider for are in what a crypto gateway really costs.
Ask every provider the same four questions: what they take per payment, what happens to the money between arrival and your bank, how much building you have to do before the first payment, and whether your student needs an account with them. The answers vary more than the marketing pages suggest.
For a course seller specifically, three of CryptumPay's answers are worth naming. Payment links first: you create an invoice in the console and send the link anywhere — a welcome email, a DM, a message to a cohort — with no checkout to build and no code to write. That matters when your storefront is really a landing page and a spreadsheet, and it is the same billing pattern as invoicing by link or QR code.
On price, CryptumPay charges 1% per successful payment, down to 0.5% at higher volumes, and the fee can be passed on to the customer instead of absorbed. And whatever coin a student pays with, CryptumPay converts it to USDT as soon as it arrives, so your balance is not sitting in something that can move 8% while you sleep.
This is where a school differs most from someone selling a template. Courses get sold as payment plans, and a wallet payment has no card on file behind it: every transfer needs the payer to confirm it, so nothing can be charged silently on the first of the month.
So an instalment plan becomes a schedule of invoices instead of a standing charge. In practice that means:
The same problem in a subscription business has a fuller answer — how renewals work when there is no card on file covers the reminder timing and the grace period, and a monthly membership is closer to that than to a cohort.

A crypto payment has no chargeback. Nobody can reach into your balance and take money back, which removes the dispute fee and the fraud loss — and also removes the mechanism a student would normally use if they feel wronged. You get the upside only if you replace it with something visible.
Three things to have in place before your first cohort:
The practical difference is speed and finality. A card refund takes business days to appear on a statement and can still be followed by a dispute. A stablecoin refund is a transfer you send, done in minutes, and it is over.
A balance in USDT is not yet money in your bank account, and the step that turns it into one is its own decision: an exchange, a licensed off-ramp, a business account that supports it. The route affects your fees and your paperwork — converting a crypto balance back to bank money is where most of the friction in this model actually lives.
Some of it may never need converting. If your school pays tutors, editors or designers in other countries, you are already sitting on a currency they can receive without a correspondent bank in the middle — paying contractors in stablecoins is the same rails pointed outward, and it removes a wire fee at both ends.
Being paid in USDT does not move a sale out of the tax system it was already in. It changes the instrument, not the transaction.
One concrete example, so this is not abstract. If your school is based in one EU country and sells to private consumers in other EU countries, VAT on electronically supplied services follows the buyer — but only once those cross-border sales pass EUR 10,000 in a calendar year. Under that line you charge VAT at home; over it, the tax belongs to each country your students live in, and the Union One Stop Shop lets you declare all of them in a single return instead of registering in each one. That describes the EU rules as they stand on 10 September 2026.
Whether your particular programme counts as an electronically supplied service, how you record a payment received in USDT, and what any of this looks like outside the EU are questions for an accountant in your own jurisdiction. This article is not legal or tax advice.
Cards are your main road and a stablecoin route is your bypass. You build the bypass because a specific set of students keeps hitting a wall you do not control, and because a course sold internationally accumulates cross-border markups, conversion spreads and dispute fees that a wallet transfer simply does not have.
Start small: add one payment link for the students who write to say their card failed. If a handful of them pay you within a week, you have your answer about whether to put it on the checkout page.
The payment confirming and the lesson unlocking are two different events, and you want them wired together rather than done by hand at midnight. The mechanics of releasing a file, a key or a login the moment money arrives are covered in the guide to delivering digital products after payment.
Almost always one of three things: they sent on a network your checkout does not watch, the amount arrived short because their exchange took a withdrawal fee, or the invoice had already expired. Each has a specific fix, and the common causes of failed crypto payments walks through them in order.
Yes, and for a lot of cohort-based schools that is the natural place for it, since the conversation and the checkout end up in the same window. The options — links, bots, and Telegram's own payment mechanics — are laid out in how to take crypto payments in Telegram.
Receiving business is not the same as receiving anonymous money, and providers screen incoming funds for a reason. What the checks look for, what gets held and what you are expected to do yourself is in AML, KYC and wallet screening for crypto payments.
Price in the currency you think in and let the checkout do the conversion at payment time. Quoting a course in a volatile coin means your price changes overnight and your refund policy becomes unanswerable; quoting in dollars and settling in USDT keeps both stable.
Create an account and connect the checkout yourself, or talk to sales and we will plan the integration with you.