Accept crypto payments at your flight school

Why flight school tuition is the hardest money a private school collects

A flight school looks like an education business, but it bills like an airline crossed with a fuel depot. The product is not a seat in a classroom; it is an aircraft, an instructor and a block of sky, dispatched hour by hour, with a meter running in tenths.

Three structural facts shape every payment the school ever receives.

First, the ticket size. A private pilot certificate costs more than most cars its students drive; a full professional programme — zero to commercial licence with instrument and multi-engine ratings — is priced like a house deposit. No other private school hands an invoice that large to a twenty-two-year-old, and almost no family pays it in one piece. So the money arrives in tranches: an enrolment deposit, a payment per phase, top-ups per block of hours.

Second, the prepaid hour account. Most schools bill flying against a balance: the student funds an account, and every Hobbs hour, sim session and landing fee burns it down. When the balance reaches zero, dispatch stops releasing aircraft — not out of malice, but because flying a student on credit is how schools go under. That single rule wires the payment system directly into the flying schedule: a late payment is measured in grounded days.

Third, the cadets are increasingly not from here. Airlines are hiring pilots faster than domestic pipelines produce them — Boeing's Pilot and Technician Outlook projects demand for hundreds of thousands of new pilots over the next two decades, much of it outside North America and Europe. Cadets train where the fleet, the weather and the examiners are, and pay from where their families bank. The largest payments in the business are international by default.

Four revenue lines that behave nothing alike

Programme tranches and hour blocks. The business. Large, scheduled, usually cross-border, and always attached to a deadline that is not administrative: the start of the next training phase, the sim slot booked for Thursday, the checkride window.

One-offs. The enrolment deposit that holds a place in an intake. Examiner and checkride fees. Theory exam fees. A headset, charts and a kneeboard from the shop. A discovery flight sold to a walk-in on a Saturday. An hour-building block sold to a visiting licence-holder.

Recurring. Ground-school memberships, simulator club dues, aircraft-rental club memberships for licensed renters — modest monthly amounts billed indefinitely, often to people who travel.

Payouts. Freelance instructors paid per flight hour, contract examiners, the maintenance shop, and the recruitment agents abroad who send the school its next intake and invoice a commission per enrolled cadet. A long list of small, frequent, individually-transferred payments — many of them international too.

What a late wire costs when the aircraft is on the ramp

The grounded cadet. The tranche was sent Monday from another continent. It routes through correspondent banks, lands Thursday — or the following Monday — and arrives a few dozen dollars short after deductions, so the account shows unfunded and dispatch holds the booking. Meanwhile the cadet is paying for accommodation, the visa has an end date, the instructor was rostered, and the aircraft flew for nobody. Weather already cancels a real share of training slots; the banking system should not cancel more.

The invoice that arrives short. Intermediary fees come off international transfers in transit, so a tuition invoice paid in full lands incomplete. Now admissions writes to a family that already paid, asking for the difference — the single most corrosive email in the relationship, repeated every phase.

The card ceiling. Cards fail on this vertical in both directions. Interchange on a five-figure tranche is roughly an instructor's month, so most schools cap what they will take by card — which pushes the serious money back to wires, banking hours and the problems above. And the card payments the school does take are the most reversible ones.

Disputes against training already delivered. An enrolment deposit disputed after a visa refusal. A washed-out student disputing a phase as "not as described". A parent who does not recognise the school's billing name disputing a tranche from another country. Card scheme dispute rights run for a window measured in months, as set out in the Visa Core Rules — and your evidence is a training folder and a dispatch log, read by someone who has never seen either. Acquirers know the profile, which is why advance-payment tuition tends to attract conservative terms, reserves, or a polite refusal.

The cadet whose money cannot leave. Some of your strongest applicants live behind capital controls, transfer quotas and official exchange rates nobody transacts at. Their families have the money; the banking system will not move it, or moves it at a punitive rate with paperwork per transfer. Many of those families already hold dollar-denominated stablecoins precisely because of this — and today the school has no invoice they can point that balance at.

The payout stack. On the last Friday of the month the school owes a freelance instructor for 41.7 Hobbs hours, an examiner for three checkrides, the recruitment agency in another country its commission for two cadets, and the avionics contractor for a job. Each one is a separate transfer with its own fee, cut-off and reference-typing exercise.

Why cards, wires and remittance apps each break on flight training

None of these rails is badly built. Each one assumes something a flight school violates.

Wires assume the deadline is administrative. A wire has a cut-off, a value date and a chain of intermediaries, and that is fine when the money is due "this month". A flight school's deadline is an aircraft slot on Thursday at 08:00. The rail measures time in banking days; the school measures it in grounded days.

Cards assume a deliverable and a local payer. The dispute framework was built around goods with tracking numbers, and the economics were built around domestic retail tickets. A cross-border, card-not-present, five-figure advance payment for a service delivered over months is the exact opposite of that design — which is why it is expensive where it is possible and refused where it is not.

Remittance apps assume a person, not an invoice. They pay out to a relative in local currency, with no field your training-management software can match to a student ID and a phase. Some families use them anyway, and your admissions office spends the morning working out who paid what.

All of them assume the payer's country lets money out easily. For a real share of the world's aspiring pilots it does not, at any price that makes sense. We wrote the general version in getting paid from abroad without a bank account — flight training is that article with a Hobbs meter attached. It is also the same structural problem we described for language schools, with one difference: here the money keeps crossing the border every few weeks, phase after phase, for a year or more.

How Payzum lets a flight school accept crypto payments — tranche, top-up and checkride

Payzum is a non-custodial, crypto-only payment processor. Both halves matter here.

Non-custodial means the money never sits in a Payzum balance. A tranche goes from the family's wallet straight to wallets your school controls. There is no processor float, no settlement batch, no rolling reserve priced against an "advance-payment tuition" risk profile, and nothing for a third party to hold while your fuel supplier, your insurer and your instructors are paid on fixed dates. The settlement is the payment.

Crypto-only means the rail is on-chain and the payment is final once confirmed — roughly 0.4 seconds on Solana, around two seconds on Base and Polygon. A family nine time zones away can fund an hour block at 23:00 their time and the account is credited before the morning briefing. And because you can auto-convert everything to USDC or USDT, "crypto" does not have to mean price movement; see USDT vs USDC for payments for how the two differ.

The instruments, mapped to how a school actually bills

• Invoices with an expiry, a student reference and overpayment detection — tranches and hour blocks. The flagship for this vertical. Every invoice carries the student ID, the programme phase or block, and an expiry set to the date that matters: the start of the next flight phase, not the end of the month. The payment arrives whole — no intermediary deductions — and reconciles itself to the student's account instead of landing as an unlabelled transfer. Overpayment detection catches the parent who rounds up or pays two blocks at once.
• No-code payment links. For the enrolment deposit that holds a seat in the March intake, the examiner and checkride fees, a theory exam resit, a 25-hour hour-building block sold to a visiting pilot, or a discovery flight gift voucher — sent by email or WhatsApp to a payer who is usually in another country, and closed the same hour.
• Hosted checkout. Behind the "book a discovery flight" or "buy sim time" button on your website, so a Saturday booking pays for itself without anyone at the front desk.
• Recurring subscriptions. Ground-school memberships, simulator club dues and renter-club memberships charged monthly with nothing behind them that can expire or be reissued — the failure mode we covered in crypto subscriptions without chargebacks.
• POS with a fresh QR per sale and PIN cashiers. At the front desk for headsets, charts, kneeboards, exam fees paid in person and walk-in discovery flights. Any phone is the terminal; each dispatcher or desk staffer signs in with their own PIN and you get per-cashier analytics. Mechanics in turning a phone into a crypto POS.
• CSV mass payouts and EVM stablecoin payouts. One file on Friday for freelance instructors paid per Hobbs hour, contract examiners, the maintenance contractor and the recruitment agents abroad — on Polygon, Arbitrum, Optimism, Base, BNB Chain or Avalanche, plus BTC/LTC/DOGE batches. The format is walked through in bulk crypto payments by CSV.
• REST API with signed webhooks. Your scheduling and dispatch software learns the moment a top-up confirms: the hour account is credited, tomorrow's booking is released, and nobody at the desk re-keys anything on a Sunday night.

What actually happens after the debrief

The instructor logs 1.3 hours and the account dips below the dispatch threshold. The system sends the top-up invoice with the student reference attached. The cadet forwards it to their family — or pays it themselves from the stablecoin balance the family already funds — and it confirms in seconds. The signed webhook credits the account, the 08:00 slot stays released, and the money is in the school's wallet: not in a processor's account, not in a batch that settles Tuesday, not in transit between correspondents.

The change is not primarily about speed. It is that the flying schedule stops depending on the banking calendar — grounded days over payments go to zero, and the school stops being an unwilling creditor between wire and value date.

Honest scope: finality cuts both ways

On-chain finality removes chargebacks. It also removes your ability to reverse a payment made in error, and it removes the student's ability to pull money back from a prepaid account by disputing a card charge. That is the same property seen from three sides, and a school should understand it before switching anything on.

In practice: refunds of unused hours become payments you initiate, from your wallet, under the refund schedule written in your training contract. That is more control than a card rail gives you — and more responsibility, because the contract is now the whole agreement. Where your jurisdiction regulates prepaid tuition — refund rules, surety bonds, escrow requirements for advance payments — those obligations attach to your school, not to the rail, and they do not change because the money arrived in USDC.

What this rail does not do

Payzum is a payment rail. It is not your training approval or certification, your national security-vetting process for foreign students, your students' visas, your airworthiness programme, your insurance, your examiner's independence or your tax engine. Nothing about how a cadet pays changes a single requirement of any of them — and no payment rail makes a washed-out student succeed or an abandoned course un-abandoned. What it removes is the far larger category: payments that were fully intended, and were late, short, blocked or reversed by the instrument.

Volatility is a setting, not a risk

The objection every owner raises first: "my costs are avgas, insurance and salaries — I cannot hold something that moves." You do not have to. Accept whatever the payer holds and auto-convert to a dollar-denominated stablecoin — USDC or USDT — so what lands in your wallet is a dollar amount against a dollar-priced programme. The chain is the transport; the stablecoin is the unit of account.

How it works, step by step

1. Connect your wallets. Create the Payzum account and point it at wallets your school already controls — many operators use one per base or per fleet so reporting stays clean. Turn on auto-convert to USDC or USDT and enable 2FA. Nothing sits with Payzum at any point.
2. Template your invoices. Student ID, programme phase or hour block, amount, and an expiry aligned to the training calendar — the phase start date or the sim-slot booking window, with overpayment detection on.
3. Create links for deposits and fees. Enrolment deposit, checkride and examiner fees, theory exams, hour-building blocks, discovery flights — each one a link you can drop into an email or a WhatsApp thread with a family abroad.
4. Put subscriptions behind the clubs. Ground school, sim club, renter club — monthly plans that end when someone cancels them, not when a bank reissues plastic.
5. Put a PIN cashier on the front desk. Fresh QR per sale for the shop and walk-ins, one PIN per staff member, per-cashier analytics across bases.
6. Connect your scheduling software. REST API and signed webhooks, so a confirmed payment credits the hour account and releases the booking through your own system automatically.
7. Run the payouts from one file. Freelance instructors, examiners, maintenance and overseas agent commissions in a single CSV — verifying any changed payee details out of band before you send it. Same rail, opposite direction.

Use cases at a flight school

Five situations that happen at every academy with an international intake, and what each looks like on this rail.

• The cadet from a capital-controlled country. Her family in Buenos Aires has the full programme funded — in a currency their banks will not send abroad at any usable rate. They already hold USDC for exactly this reason. Each phase, they pay the invoice from that balance in minutes; it arrives whole, referenced to her student ID, and she never misses a slot waiting on a transfer that legally could not leave.
• The tranche that used to ground a week. Phase 3 starts Monday. Under the old rail, the wire sent the previous Tuesday cleared Thursday — or the following Tuesday — and dispatch held the bookings. Now the invoice expires Sunday night, the payment confirms in seconds whenever it is made, the webhook credits the account, and Monday's 08:00 departs with the student on board.
• The checkride fee at 22:00. The examiner confirms for tomorrow; the fee is due before the ride. The school sends a payment link; the cadet's father pays it from another continent before going to bed; the confirmation is in the school's wallet before the aircraft is preflighted.
• The hour-builder from abroad. A licensed pilot flies in for a 25-hour block in your cheap, sunny fleet. He is exactly the customer whose foreign card trips every fraud rule you have. A payment link settles the block before he arrives; top-ups mid-stay settle on a QR at the desk; nothing about his bank's country matters.
• Saturday at the desk, Friday's payout run. Two discovery flights and a headset sold on QRs under the dispatcher's PIN — no card terminal, no cash tin. Then one CSV on Friday: the freelance CFI's 41.7 hours, the examiner's three rides, the agency in Bogotá's commission — settled the same day, with payee details verified out of band beforehand.

Payzum vs wires and cards for a flight school

Common objections, answered

"Our students don't hold crypto."

Most domestic ones do not, and this is not for them. It is for the slice of your roster that is already painful: the cadet whose family pays from a capital-controlled country, the parent nine time zones away, the hour-builder whose foreign card always declines, and the agent abroad waiting on a commission. Run it alongside the rails you already accept. Your local students will never notice, and you should not ask them to change anything.

"We already take wires. They work."

They clear — eventually, short, during banking hours, with a reference typed by hand. The question is not whether the money arrives; it is how many grounded days, re-asked balances and manual matches each arrival costs, multiplied by every phase of every international cadet on your roster. If your intake is entirely domestic, wires are fine. If it is not, you are running your flying schedule on a rail with a value date.

"Is prepaid tuition safe sitting in crypto?"

The funds do not sit with Payzum at all — that is the point of non-custodial. Payments land in wallets your school controls, protected by your own key management, with 2FA, signed webhooks and a full audit log on the account. Auto-convert means what you hold is a dollar-denominated stablecoin, not a volatile asset. Where local rules require prepaid tuition to be bonded or held a certain way, those rules apply to you the same as with any rail — ask your adviser, not your processor.

"What about our accountant and our regulator?"

Tuition collected in USDC is tuition revenue, recorded on the day it is received at that day's value, against the student and the phase — the same as any other receipt, and easier to reconcile because the reference travels with the payment. Your training approvals, your student contracts, your refund schedule and your tax treatment are unchanged. Confirm the details for your jurisdiction with your own advisers; we are a payment rail, not your compliance department.