NuPay connects to the bank by API, so every deposit and payment arrives in the school’s books on its own, matched to the right student and invoice. The money stays in the school’s account. NuPay only reads it.
ZB BankConnected by API
Live
NuPay is integrated with ZB Bank by API. A school that banks there sees every account it runs in one place, updated without anyone downloading a statement.
ZB BankLive bank feed · SDC, tuition and other school accounts
Connected
More banks are being added. Bank with someone else?
Deposits, transfers and mobile-money settlements are read from the feed and matched to the student and invoice they belong to.
Payments leaving the account are allocated to the right expense account and department.
USD and ZWG accounts sit side by side, each reconciled on its own.
The connection carries information about transactions. It does not carry money.
The school authorises NuPay to read the accounts it chooses.
Each deposit and payment comes through with its date, amount and reference.
References, amounts and names are matched to students and invoices. Expenses are categorised.
The ledger, the student balance and the parent portal change together.
NuPay is not a wallet and not a holding account. Parents pay, the bank settles into the school’s own account, and NuPay reads the transaction to keep the books right.
A school that can see its bank account inside its accounting system has little reason to move it. NuPay invites banks to connect, so the schools you serve get live feeds, automatic matching and clean books on top of the account they already hold with you.
Fees settle directly into the school’s account at your bank. NuPay never takes custody of the money.
When the bank feed drives the school’s daily bookkeeping, the account becomes part of how the school runs.
Bursars stop asking for statements and proof-of-payment checks, because the transactions are already in front of them.
Connected banks are named in NuPay and on this page, where schools look when deciding where to bank.
We work to your API and your security standards, not the other way round.
A live feed depends on your bank. Until yours is connected, NuPay still does the rest of the work.
Fees paid through the payment gateway are matched to the student and invoice automatically, whichever bank the school uses.
Bank deposits, cash and swipe payments are captured against the student, and the books stay complete.
We’ll approach them. The more schools ask, the sooner a bank connects.
NuPay is integrated with ZB Bank by API for live bank feeds. More banks are being added, and availability depends on your financial institution.
No. Money settles directly into the school’s own bank account. NuPay reads the transaction so it can match it and keep the books.
The transactions on the accounts the school has authorised: date, amount, reference and narration. That is what it needs to match a payment to a student and invoice.
Yes. Online payments through the payment gateway are still matched automatically, and bank deposits can be recorded in NuPay. Tell us who you bank with and we will approach them.
Get in touch and we will set up a conversation with your digital or corporate banking team. We scope the integration against your API and security standards, test it, pilot it with one school, then open it to every school that banks with you.
Fees settle and stay in accounts at your bank, the school’s daily bookkeeping runs on your feed, and your bank is named as connected wherever schools use NuPay.
Online payments run through a separate integration with the payment gateway. Both lead to the same place: the money in the school’s bank, and the payment matched in NuPay.
Schools: see your bank feed matched live. Banks: talk to us about connecting.