School finance infrastructure

Every payment.
Accounted for.

Bank gateways call Fee Syncer dev to validate student accounts and report completed payments. Confirmed payment data then moves to the school system through its agent.

Explore integration See the payment flow

Multi-school isolation Agent-backed delivery Operational monitoring

Live transaction rail Connected
Student referenceADM-02418
Bill validationAccepted
Payment channelM-Pesa
ReconciliationKES 24,500
Incoming gateway event recorded for school delivery
One operational path

From parent intent to reconciled school balance.

The platform handles the moments where payment systems and school records must agree.

Validate before payment

Confirm the admission reference and outstanding balance before a gateway authorises a transaction.

Record on arrival

Capture gateway notifications as they land, preserving the identifiers needed for reconciliation.

Keep balances current

Refresh student and fee snapshots through each school’s agent-backed connection.

Isolate every school

Run multiple institutions from one control plane while keeping each school’s records in its own schema.

Protect credentials

Encrypt school API credentials and scope agent access to the school that issued each key.

Operate with context

Monitor incoming callbacks, queues, agents, and school sync jobs from one focused workspace.

Designed for every side of the integration

One connection point. Clear value for every team.

Explore the integration

For schools

Reduce manual reconciliation and keep fee balances available to payment channels.

  • Isolated school data
  • Current student references
  • Visible payment status

For banks and gateways

Integrate with stable validation, notification, and transaction-query endpoints.

  • Versioned endpoints
  • Predictable JSON contracts
  • School-specific callback URLs

For integration teams

Operate the full path with health checks, queues, agent metrics, and diagnostics.

  • Central operations view
  • Failure visibility
  • Controlled school onboarding
Inbound integrations

Banks configured to call Fee-Syncer

Live and planned bank callback integrations

Live KCB Bank
99.9%
Uptime SLA
24/7
Monitoring
Every 5 min
Balance sync
Every 6 hrs
Student sync
Planning an integration?

Map your payment flow with our onboarding team.

Share your school system and gateway requirements. We will identify the endpoints, credentials, and rollout steps involved.

Explore the flow
Payment sequence

A traceable path, not a black box.

Each handoff has a clear purpose and a durable record for finance teams and integration operators.

Data isolation and credential security

Each school's student, balance, and payment records are stored in a dedicated PostgreSQL schema, keeping tenant data separated within the shared database. School API credentials are encrypted at rest. Bank gateways call school-specific Fee-Syncer endpoints, and incoming requests are rate-limited and scoped to the resolved school.

01

Parent identifies the account

The admission number links the payment intent to a student ledger.

02

Gateway requests bill validation

The bank gateway calls Fee-Syncer, which checks the latest school data and returns the amount due.

03

Bank completes the payment

The payer confirms and the payment channel processes the transaction.

04

Bank sends the notification

The gateway calls Fee-Syncer with the completed transaction and its bank reference.

05

School system receives the payment

The school agent collects the confirmed payment from Fee-Syncer and records it locally.

06

School balance is refreshed

The agent returns the updated fee balance from the school system.

A controlled rollout

Move from discovery to live callbacks with clear checkpoints.

The onboarding path separates configuration, testing, and production promotion so each institution can validate the integration before going live.

Review the rollout
01

Discover

Confirm the school fee system, gateway contract, callback domains, and operational contacts.

02

Configure

Create the school environment, API credentials, domains, and agent enrollment.

03

Test

Exercise bill validation, payment notification, school delivery, and balance refresh.

04

Go live

Promote the school, activate production endpoints, and monitor the first transactions.

School network

Onboarded institutions

Schools connected to the payment operations desk.

3 active

Kambui Girls Secondary

Connected 2 months ago
Active

Koelel

Connected 2 months ago
Active

Utumishi

Connected 2 months ago
Active
Common questions

The details teams ask before integrating.

Need an answer specific to your environment?

Explore the API flow

The bank or payment gateway is configured with school-specific Fee-Syncer URLs for bill validation, payment notification, and transaction queries.

The school agent collects confirmed payment work from Fee-Syncer and records it through the school-side fee system.

Yes. Each school has its own lifecycle, credentials, domains, agent access, and PostgreSQL schema.

Yes. Schools progress through development and testing before promotion to live, allowing endpoints and agent delivery to be verified first.

The operations desk surfaces sync activity, queues, agent health, payment records, balance freshness, and integration diagnostics.
Integration desk

Turn your payment flow into a working integration.

Tell us which school system and payment channel you need to connect. We will help map the next step.

Explore integration View gateway sample