Billing software touches two things you can't afford to get wrong: money and personal data. Here's how OrdaBill protects both — plainly, without the sales brochure.
Where your money sits
OrdaBill is not a bank and never holds customer funds itself. Payments are processed by licensed gateways (Paystack today), which handle collection, PCI compliance for card data, and settlement to your configured bank account. OrdaBill's ledger records every payment with both legs — the tenant share and the platform fee — so you can reconcile each shilling against what the gateway actually settles.
How payment notifications are trusted
A payment is only marked paid when the gateway's webhook notification passes signature verification. Forged or tampered notifications are rejected outright. Replayed notifications are detected and don't double-count. If the gateway says nothing, the invoice stays unpaid — the system fails closed, never open.
How accounts are protected
- Server-side sessions — logins are tracked in Redis-backed sessions with idle expiry, not guessable client-side tokens.
- Role enforcement — administrative user management is restricted to super administrators, with guardrails against locking the platform out.
- Tenant isolation — every invoice, subscription and customer record is checked against the tenant or customer asking for it. One tenant cannot read another's data.
- CSRF protection — state-changing requests require a per-session token, so a malicious site can't act on a logged-in user's behalf.
- HTTPS — production deployments run behind TLS, so credentials never travel in the clear.
What you should do on your side
- Use strong, unique passwords, and change them if you suspect a breach.
- Keep Paystack API keys out of shared documents; rotate them if they leak.
- Review your admin user list regularly and deactivate people who leave.
More on how the money flows: Paystack payments and settlement.