Schools, academies, multi-academy trusts, colleges and universities can have surprisingly complex payment requirements.
Payments might include:
- school meals;
- trips and activities;
- clubs and wraparound care;
- tuition or course fees;
- international student payments;
- accommodation;
- events and ticketing;
- donations and fundraising;
- uniform or equipment;
- online shop purchases;
- telephone payments;
- payment links;
- recurring payments; and
- face-to-face card payments.
A small school may only need a straightforward way for parents to pay online.
A university or multi-academy trust may need multiple merchant accounts, online and face-to-face payments, integrations with existing software, central reporting, different settlement accounts and a formal procurement process.
The right payment setup therefore depends on the organisation rather than simply choosing the cheapest card-processing rate.
How do schools and education providers take payments?
Education providers can use several different payment channels.
Online payments
Parents, students and other customers may pay through a website, parent portal, student portal, hosted payment page or payment link.
Online card payments normally require a payment gateway or payment service provider capable of securely passing the transaction for processing.
Face-to-face payments
Card terminals may still be required for:
- reception desks;
- school offices;
- campus facilities;
- events;
- cafés;
- shops;
- sports facilities; and
- other in-person payments.
Payment links
A payment link can be useful where the institution needs to request a specific payment without asking the parent or student to navigate through a full ecommerce checkout.
Telephone payments
Some institutions still need to accept card payments over the telephone, particularly for larger or more complex payments.
Recurring payments
Recurring card payments or Direct Debit can be relevant for regular charges such as childcare, memberships, instalment arrangements or certain tuition-payment plans.
Start with the payment requirement, not the provider
A school may already use a parent-payment platform, accounting system or management system.
A university may have separate systems for tuition, accommodation, events and campus services.
A trust may want all schools to use a common payments framework while retaining individual reporting and settlement.
Understanding those requirements first makes it much easier to identify which payment providers should actually be considered.
Dedicated school payment platforms vs separate payment providers
Some education organisations use specialist school-payment platforms that combine parent-facing payment functionality with other school-management features.
Others use a separate payment gateway, merchant account or PSP that connects with existing software.
Neither approach is automatically better.
A dedicated education platform may provide functionality such as:
- parent accounts;
- meal payments;
- trip payments;
- permissions;
- school communications;
- balances; and
- education-specific reporting.
A separate payment setup may offer more flexibility where the organisation needs:
- different acquiring arrangements;
- several payment gateways;
- specific integrations;
- multiple legal entities;
- multiple merchant IDs;
- international acquiring;
- multi-currency payments;
- centralised procurement; or
- more control over commercial terms.
The important question is how well the payment setup fits the organisation's wider systems and operating model.
Payments for multi-academy trusts
Multi-academy trusts can introduce additional payment complexity because several schools may sit within one wider organisation.
A trust reviewing payments should establish whether it wants:
- one central provider across every academy;
- separate merchant IDs for each school;
- central or individual settlement accounts;
- trust-level reporting;
- school-level reporting;
- standardised terminals;
- common online-payment journeys;
- shared integrations;
- central contract management; and
- the ability to add further schools later.
A provider that works well for one standalone school may not necessarily have the reporting, account structure or commercial model required across a larger trust.
Payments for colleges and universities
Colleges and universities can have a broader mix of payment channels than most schools.
These can include:
- tuition fees;
- international student payments;
- accommodation;
- application or administration charges;
- short courses;
- conferences and events;
- campus retail;
- catering;
- sports facilities;
- donations;
- research or commercial services; and
- other departmental income.
The payments estate may therefore involve several merchant IDs, gateways, terminals and software systems.
For larger institutions, reducing the number of disconnected payment arrangements and improving reporting can be just as important as negotiating transaction rates.
Reviewing payment providers for a school, trust, college or university?
Tell us how payments are currently collected, which systems need to connect and what you want to improve.
Merchant Advice Service can help you understand the payment requirement before identifying providers that may be suitable.
Review your payment requirements
When should an education payment project become a tender?
Not every school needs to run a formal payment-provider tender.
For a straightforward merchant account or card-terminal requirement, a structured comparison of suitable providers may be enough, subject to the organisation's own procurement rules.
However, a more formal procurement or RFP can become useful where the payment requirement includes:
- a multi-academy trust or multiple campuses;
- significant annual payment volume;
- several merchant IDs or legal entities;
- online and face-to-face acquiring;
- international payments;
- multiple currencies;
- software or ERP integrations;
- complex reporting;
- central reconciliation;
- migration from several existing providers;
- large numbers of payment terminals;
- defined service-level requirements;
- longer-term contracts; or
- formal public-sector procurement requirements.
The tender should then look beyond transaction rates.
Our guide to running a payment provider RFP or tender explains how to build the requirement, shortlist providers and compare proposals on a consistent basis.
A payment tender should cover more than price
For a larger education organisation, a low headline transaction rate is only one part of the decision.
A useful tender can also compare:
- gateway and acquiring architecture;
- implementation;
- integrations;
- merchant-ID structure;
- settlement;
- reporting;
- reconciliation;
- payment terminals;
- refund processes;
- fraud controls;
- international payments;
- support and service levels;
- contract length;
- exit arrangements; and
- total cost.
A provider that is cheapest on one transaction type may not represent the best overall fit across the complete education payment environment.
Procurement rules for schools and academy trusts
Schools and academy trusts also need to consider their procurement obligations when buying payment services.
Department for Education guidance says schools should follow their own procurement rules and use the appropriate buying route for the value and nature of the purchase.
Those routes can include:
- using an appropriate framework agreement;
- obtaining competitive quotations;
- advertising a contract and inviting bids; or
- running a procurement process compliant with the Procurement Act 2023 where required.
Payment-provider selection therefore needs to fit both the organisation's payment requirements and its procurement obligations.
Schools and trusts should use current Department for Education guidance and take appropriate procurement or legal advice where necessary.
What should go into a school payment specification?
Before approaching providers, the organisation should document what the payment service actually needs to do.
A useful specification might include:
- number of schools or campuses;
- legal entities;
- existing providers;
- annual processing volume;
- transaction volumes;
- average transaction values;
- online payments;
- face-to-face payments;
- telephone payments;
- payment links;
- recurring payments;
- Direct Debit;
- international payments;
- currencies;
- required integrations;
- reporting;
- reconciliation;
- refund requirements;
- settlement accounts;
- implementation timescale;
- support requirements; and
- contract and exit requirements.
This is the same principle we use with commercial payment tenders: define the requirement before asking providers to price it.
Payment gateway integration for schools and universities
A payment gateway should not be selected in isolation if it needs to connect with existing education or finance software.
The organisation may need payments to integrate with:
- school-management software;
- parent-payment platforms;
- student-information systems;
- finance systems;
- ERP software;
- accounting platforms;
- booking systems;
- accommodation systems;
- ecommerce platforms; or
- custom internal software.
The integration should ideally connect the original payment request with the successful payment, refund and settlement information.
Organisations with more complex software requirements can also read our guide to integrated payments .
Reporting and reconciliation
Education payment systems can generate large numbers of relatively small transactions across several departments or schools.
Reporting therefore matters.
Finance teams may need to identify:
- which school received the payment;
- which student or parent made it;
- what the payment related to;
- which department owns the income;
- which payment method was used;
- the transaction fee;
- whether a refund has been issued;
- which settlement batch contains the payment; and
- which bank account received the funds.
A provider comparison should therefore consider whether reporting reduces administration rather than simply whether payments can be accepted.
See our guide to payment reconciliation for more complex payment environments.
International student payments
Universities, colleges, boarding schools and other education providers may receive payments from overseas students or families.
This can introduce additional considerations such as:
- international cards;
- multi-currency checkout;
- foreign-exchange costs;
- international acquiring;
- local payment methods;
- bank transfers;
- Open Banking or account-to-account payments where available;
- fraud controls; and
- international refund handling.
A provider that works well for domestic parent payments may not necessarily provide the strongest international-payment setup.
Card terminals across schools and campuses
Education providers may also need several types of card terminal.
That might include:
- countertop terminals at reception;
- portable terminals for events;
- mobile terminals;
- integrated EPOS terminals;
- campus retail terminals; and
- temporary devices for events or activities.
For a large trust or university, the terminal estate should be included in the wider provider review rather than contracted separately without considering the overall payment strategy.
Refunds and cancellations
Education providers can have significant refund requirements.
Examples include:
- cancelled trips;
- withdrawn courses;
- event cancellations;
- accommodation changes;
- duplicate payments;
- overpayments; and
- payments made against the wrong student account.
The provider should support a controlled refund process and make it easy for the finance team to link refunds back to the original transaction.
Merchant category codes for education
Payment providers use Merchant Category Codes, or MCCs, to classify businesses according to the type of goods or services they provide.
Common education-related categories include:
- MCC 8211 – Elementary and Secondary Schools;
- MCC 8220 – Colleges and Universities;
- MCC 8241 – Correspondence Schools; and
- other education or childcare classifications depending on the organisation.
The provider should classify the institution according to its actual activity rather than selecting an MCC solely because it appears broadly education-related.
What should education providers compare?
Total payment cost
Compare the complete pricing structure rather than a single advertised card rate.
Online payment capability
Can the provider support the organisation's websites, portals, hosted checkout and payment links?
Card terminals
Does the provider have suitable devices and estate-management capability?
Integrations
Can payment data connect with the education and finance systems already in use?
Merchant structure
Can the provider support several schools, legal entities, merchant IDs and settlement accounts where required?
Reporting
Can finance teams obtain both central and institution-level reporting?
Reconciliation
Can transactions be matched back to students, parents, invoices, events or other payment references?
International payments
Does the provider support the countries, currencies and payment methods required?
Settlement
When are funds paid and can settlement be directed correctly across the organisation?
Support
What happens when a payment system used across several schools or campuses stops working?
Contract and procurement
Do the contract terms fit the institution's procurement process, implementation requirements and future exit arrangements?
Planning a school, trust or university payment review?
A straightforward requirement may only need a provider comparison. A larger multi-site or integrated environment may justify a structured payment-provider tender.
Merchant Advice Service can help you understand the requirement first, then identify providers that may be suitable.
Review your payment setup Read the payment tender guide
How Merchant Advice Service helps education providers
Merchant Advice Service helps businesses and organisations understand their payment requirements before identifying payment providers that may be suitable.
For schools, trusts, colleges and universities, that can include:
- merchant accounts;
- payment gateways;
- online payments;
- card terminals;
- payment links;
- recurring payments;
- multiple merchant IDs;
- multi-site requirements;
- international payments;
- software integration;
- reporting;
- reconciliation;
- settlement;
- provider comparison; and
- payment-provider RFP or tender requirements.
Larger organisations planning a structured provider review should also read our Payment Provider RFP & Tender Guide .
Editorial & Commercial Disclosure
This guide provides general information about payment processing for schools, academies, multi-academy trusts, colleges and universities.
Payment requirements, procurement rules and provider arrangements can vary significantly between education organisations.
Schools and trusts should follow their own procurement policies and current Department for Education guidance and obtain procurement or legal advice where required.
Merchant Advice Service does not provide procurement legal advice and does not determine whether an organisation is required to use a particular tender or procurement procedure.
MAS is an independent payments information and provider-matching service. MAS may receive a referral fee or commission from some payment providers where an organisation proceeds following an introduction. Commercial relationships do not determine the factual information or provider-selection principles contained within this guide.
Payment providers determine their own pricing, eligibility, technical functionality and contractual terms.
Information is provided for general guidance and should not be treated as legal, procurement, regulatory or financial advice.