# Online School Fee Payment: From the Payment Link to the Receipt

Source: https://wakp.net/en/online-school-fee-payment/
Last reviewed: 2026-11-15

> Online school fee payment lets a guardian settle what is owed from a phone without visiting the treasury, after which the amount reaches the school and the entry is recorded automatically. In wakp a staff member creates a secure payment link, or the guardian pays from the portal, through a payment gateway on the school's own merchant account, and one receipt is created and posted to the ledger. Gateways work with accounts the school opens itself, and schools that prefer bank transfers get a proof workflow a reviewer approves.

Online school fee payment means a guardian settles what is owed from their phone, and the amount is recorded in the student's account with a receipt without a staff member handling cash. It is part of the wakp [school management system](/en/): it is not separate from a student's charges and instalments, nor from the school's treasuries and ledger. This page explains how a payment starts, how the system checks it, where the money goes and what a school needs in order to switch it on.

## The problem: why fee collection drags

Cash collection alone wears out the school and the guardian:

- The guardian has to come in during treasury hours.
- A late instalment is only chased by scattered phone calls.
- A bank transfer arrives and the accountant cannot tell which student it belongs to.
- A receipt is written by hand after collection, so balances lag.
- A payment notification repeats and the amount is recorded twice.
- An amount paid on the gateway does not match what reached the school.

## How online payment works in wakp, step by step

### 1. Setting up the school's payment account

The school opens a merchant account in its own name with the provider it chooses, then enters its details in the **payment gateways** screen. wakp supports **Fawaterak** for schools in Egypt and **Tap** for Saudi Arabia and the Gulf, alongside a **manual proof** type for transfers. Each account holds:

- The provider's keys, stored encrypted and never sent back to the browser once saved.
- A **test** or **live** environment, and a **test connection** button.
- The allowed payment methods.
- The treasury the money lands in.
- Who bears the gateway commission: the school or the guardian.

Because the account is in the school's name, guardians' money goes to the school directly and wakp does not hold its customers' funds. Without a merchant account at a real provider no live payments can be collected: wakp connects the system to the gateway but does not open the account on the school's behalf.

### 2. The secure payment link

From a student's fees screen, a staff member creates a **payment link** for the student's enrolment. The full link is shown once only and just its hash is stored; the staff member copies it and sends it through whichever channel the school uses. The system records who it was sent to and who created it. The link has a default validity of 14 days and can be revoked at any time. An expired or revoked link, or one that belongs to another school, returns a page-not-found, and requests to the page are rate limited.

### 3. The public payment page

The guardian opens the link on the school's site with no account and no password, and sees:

- The school name, the student name and the year.
- The items owed, with each item's due date and what remains, and the total owed.
- The student's credit balance, if any.

The guardian picks specific items or an amount that does not exceed what is owed, optionally enters a name, email and phone, and is then sent to the provider's page to complete the payment. Partial payment is possible, and the system does not accept an amount above what is owed. If the school has no active payment account, the amounts owed show without a pay button.

### 4. Verifying the payment

It is not enough that the provider says the payment went through. When the gateway's notification (webhook) arrives, the system:

1. Stores the raw notification for review.
2. Verifies its **signature**, and rejects and logs it if it is not valid.
3. Asks the provider directly for the payment's **status** and matches the **amount and currency** before accepting it.
4. Prevents duplicates with a lock, so a payment has one receipt however often the notification repeats.
5. If the amount, currency or status disagree with what the provider reports, the payment becomes **needs review** and reviewers are notified; nothing is accepted.

Beyond notifications, the system also reconciles pending payments with the provider periodically (every fifteen minutes) and with a wider daily sweep, so a payment is not left hanging because its notification never arrived.

### 5. The automatic receipt and posting

When the payment succeeds, **one receipt** is created automatically with an "online" source and the payment reference, and the amount is allocated to the items the guardian chose or to the oldest due items first. If the items changed between starting the payment and its arrival, the money that arrived is not refused: items no longer owed are trimmed and the rest becomes a credit balance for the student. The amount enters the **treasury** set on the gateway account and is posted to the general ledger together with the gateway commission.

**[Book a demo meeting](https://my.wakp.net/book?utm_content=article)**

## Proof of bank transfer

For schools that take transfers instead of a gateway, wakp provides a **manual proof** workflow:

1. The guardian opens the payment link and lands on a proof upload page instead of a gateway page.
2. They pick the method from bank transfer, InstaPay, wallet, cheque or cash, upload a photo or PDF of the receipt and may add a note.
3. The proof becomes "awaiting review", and a second proof is not accepted while the first is undecided.
4. A reviewer examines the proof in the **manual payment proofs** screen, opens the attachment and either **confirms** it, at which point the payment is recorded and the receipts and entries are created like any other payment, or **rejects it with a written reason**, which the guardian is told and no amount is recorded.

Every decision is written to the audit log with the reviewer and the time.

## Capabilities at a glance

| Function | What wakp offers |
| --- | --- |
| Payment gateways | Fawaterak (Egypt) and Tap (Saudi Arabia and the Gulf) on a merchant account in the school's name |
| Payment link | An encrypted token shown once, 14 days by default, revocable |
| Payment page | No sign-in: items owed, full or partial payment |
| Guardian portal | Invoices, balance, receipts and online payment from the portal |
| Verification | Notification signature, then a match of amount and currency with the provider |
| Duplicate protection | One receipt per payment |
| Special cases | Needs review, and periodic reconciliation of pending payments |
| Receipt | Automatic with an online source, any surplus becomes credit |
| Commission | Borne by the school or the guardian and posted to the ledger |
| Transfer proof | Upload then confirm or reject with a reason |
| Payment monitoring | A payments screen with tabs: pending, succeeded, failed or expired, all |

## Integration with other modules

- **Student accounts:** charges, instalments, discounts, receipts and the statement live in [student accounts and fees software](/en/student-accounts-software/), and online payment is a way to settle them.
- **School finance:** treasuries, daily collection and expenses live in [school finance and treasuries](/en/school-finance-management-system/), and the gateway has a dedicated treasury the money lands in.
- **General ledger:** the receipt and the gateway commission are posted to the [general ledger software](/en/school-general-ledger-software/) with no manual entry.
- **Parent app:** the guardian pays from the portal in the [school and parent app](/en/school-and-parent-app/), through the same path.
- **Dashboard:** collection results show in the [school management dashboard](/en/school-management-dashboard/).

For more: [school management system features](/en/school-management-system-features/).

## Payment states: what do they mean?

| State | Meaning |
| --- | --- |
| Pending | The payment started and is not yet settled |
| Succeeded | The system verified the payment and created the receipt |
| Needs review | The notification is valid but the amount, currency or status disagrees with the provider, so a person decides |
| Failed, cancelled or expired | The payment did not complete and no amount is recorded |
| Refunded or partially refunded | All or part of the amount was returned |

Only the "succeeded" state is allowed to settle a charge: nothing else changes a student's account.

## Security in this cycle

- Gateway keys are encrypted in the database with a separate key and are not sent to the browser.
- The payment link token is not stored as text, only its hash.
- Each school sees only its own payments, and a link token is resolved inside the current school only.
- No payment is accepted on a notification alone: signature first, then a query for the amount.
- Every sensitive action (creating a link, revoking it, confirming or rejecting a proof) is in the audit log.

## Online payment versus traditional collection

| Aspect | Traditionally | With wakp |
| --- | --- | --- |
| Paying | A visit to the treasury | A link or portal from a phone |
| The receipt | Written by hand | Created automatically, once |
| Bank transfer | Asked about after it arrives | An uploaded proof and a recorded review decision |
| Accounting entry | Keyed in manually | Automatic posting with the commission |
| Partial payment | Tracked by hand | Items or an amount chosen, the rest stays owed |
| Duplicates and errors | Risk of a double entry | A lock prevents two receipts for one payment |

## What wakp does not do

- It does not open a merchant account for the school or handle its money: each school opens its own with the provider.
- It does not charge a guardian's account automatically without the guardian starting the payment.
- It does not set the commission the provider charges: it records what the school agrees with it.
- Online payment works only for a school with an active payment account; without one, collection stays at the treasury as before.
- Payment starts on the school's oldest active account, so it is best to keep one active account for online collection.

## Implementation checklist

1. Open a merchant account in the school's name with a provider suited to your country.
2. Enter the account details in payment gateways and test the connection in the test environment.
3. Choose the receiving treasury and who bears the commission.
4. Decide who creates links and who reviews proofs and payments that need review.
5. Try a small payment, then check the receipt, the entry and the treasury.
6. Switch the account to live and tell guardians how to pay.

## An example: an instalment from link to receipt

1. A student's instalment falls due, and a staff member creates the payment link from the fees screen and sends it to the guardian.
2. The guardian opens the link on a phone, sees the instalment and what remains, and decides to pay it in full.
3. They are sent to the gateway page and the payment completes.
4. The gateway notification arrives, and the system verifies the signature and the amount and accepts the payment.
5. The receipt appears in the student's account, the treasury, the general ledger and the guardian portal.
6. If the notification repeated five times, there would still be one receipt.

## How wakp helps

wakp turns payment from a staff task into a connected path: a link, then a payment, then verification, then a receipt, then an entry, with no manual middle step. Because the gateway runs on the school's own account, the money goes straight to the school, and the school keeps the ability to review and audit every step.

## Who it is for

Private, national and international schools in Egypt and Saudi Arabia that want faster collection with less reliance on visiting the treasury, and that have or can open a merchant account with a payment provider in their country. Requirements for invoices and electronic receipts differ between the two countries and follow each official body's instructions, so check what applies to your school before switching on.

## Common mistakes in online payment

- **Going live before testing the connection:** try the test environment first.
- **Sending a link to the wrong guardian:** the link is the key to the page, so send it only to the right person and revoke it if you slip.
- **Not setting the receiving treasury:** set it so the money lands in the right one.
- **Ignoring payments that need review:** review them quickly before they confuse the guardian.
- **Accepting transfers without an uploaded proof:** the proof is what ties a transfer to a student and an instalment.

## A suggested online collection routine

1. At the start of the day, review payments that need review and transfer proofs awaiting a decision.
2. Create payment links for due instalments and send each to its owner.
3. The accountant follows the successful payments and their receipts.
4. At the end of the day, review the daily collection.
5. Revoke links that are no longer needed.

**[Book a demo meeting](https://my.wakp.net/book?utm_content=article)**

### What is online school fee payment?

It is the guardian paying fees and instalments over the internet, from a payment link or the portal, instead of visiting the school. The amount is recorded in the student's account with a receipt, so nobody has to key it in by hand.

### Which payment gateways does wakp support?

wakp supports Fawaterak for schools in Egypt and Tap for Saudi Arabia and the Gulf, plus a manual proof workflow for bank transfers. Each gateway works with a merchant account the school opens in its own name with the provider and whose keys it enters in the system, so wakp does not hold guardians' money.

### Does the guardian need an account to pay?

No. The payment link opens the payment page without signing in; the link the school sent is enough. A guardian who has an account can also pay from the portal.

### What happens if the gateway's notification arrives more than once?

Only one receipt is created per payment however often the notification repeats. The system verifies the notification's signature and then asks the gateway for the payment's status and amount before accepting it.

### How do I receive bank-transfer payments?

The school sets up an account of the manual proof type. The guardian uploads a photo or file of the receipt and picks the payment method, and a reviewer confirms or rejects it with a reason. Nothing is recorded as paid before confirmation.
