01
One bad row stops everyone.
A wrong account number, a closed account, a new joiner who isn't set up yet — and the whole run bounces. Everybody waits, and finance spends the day on the phone.
Payroll infrastructure · Egypt
Payroll that pays you back.
Every business in Egypt runs payroll. Almost none get anything back from it. Payramid turns each monthly run into a permanent, verifiable record. Payramid turns each monthly run into a permanent, verifiable record — so one bad row never stops everyone else, employees see every payment they have ever received, and the history you build actually counts for something.
01Approved
02Permanently recorded
03Visible to the employee
PAYRAMID · PILOT PROGRAMME
SALARY, SETTLED.
The problem
Payroll is the most reliable thing your business does. And the least useful.
Every month, on time, without fail — and at the end of it you have a bank confirmation, a spreadsheet, and nothing anyone outside your company can check.
02
The record lives in someone's inbox.
Payslips in one folder, transfer confirmations in another, corrections agreed over WhatsApp. When someone asks what was actually paid in March, answering it is an afternoon's work.
03
Your best track record counts for nothing.
Two years of paying eighty people on time is the clearest evidence your business is sound. It just isn't evidence anyone will accept, because nothing stops the numbers being edited after the fact.
What Payramid does
Run payroll the way you already do. Get back something you never had.
You upload the same spreadsheet. Everything after that is different.
Preview before you commit
Every row on screen before anything is submitted — who is paid, how much, and anything that doesn't look right. No surprises discovered afterwards.
One bad row, held alone
A payment that can't go through is set aside on its own. The rest of the run continues on schedule. Nobody else waits.
Employees see everything
Each person gets their own view of their salary and every payment they have ever received — in an account that belongs to them, not to their employer.
A record nobody can rewrite
Approvals, rejections and corrections are added to a permanent history. Nothing is ever quietly edited — including by us.
What an employee sees
Example
Mariam H.
Monthly salary
18,400
March 2026
18,400Received
February 2026
18,400Received
January 2026
17,900Received
Every payment, kept in one place
The same history is there whether or not the person still works for you.
March payroll · 250 payments
Example
Mariam H.
18,400Recorded
Youssef A.
12,750Recorded
Nour E.
21,000
Held
Karim S.
9,600Recorded
Salma R.
15,250Recorded
249 of 250 completed · 1 awaiting review
EGP 4.18M
An illustration of how a run behaves — not a customer record.
The difference
One bad row shouldn't cost everyone their payday.
Payroll goes out as a single batch of hundreds of payments. In most systems, if one row is bad, the whole batch fails and nobody gets paid that day. Here, that one payment is held back — and every other payment in the run still goes through.
- Only the affected payment stops. The rest of the run completes on schedule, untouched.
- Somebody has to look at it. An administrator approves or rejects the held payment — and rejecting it requires a written reason.
- The review joins the record too. Who decided, when, and why is kept permanently — so the decision itself can be checked later.
Who it's for
Built for everyone who touches payroll.
Four defined roles. Everyone gets a view built for what they actually do — and nothing beyond it. No informal tiers, no shared logins.
Employees
Their salary, their history, their account.
- Every payment they have ever received, in one place
- An account they hold themselves — the keys are never ours
- No paperwork to chase when they need proof of income
- Nothing to install, and nothing to lose if a phone is replaced
HR & finance
Run the month without holding your breath.
- Upload the spreadsheet you already use
- Every row previewed before anything is submitted
- Track the run and report on it afterwards
- Budget controls and reporting scoped to your own organisation
Administrators
Oversight that leaves a trail.
- Review held payments and record the decision
- Work across every organisation on the platform
- New administrator accounts need a second person's sign-off
- Suspend an organisation and its portal closes immediately
The longer game
Your payroll history is an asset. Today it evaporates.
A lender deciding whether to finance your business wants to know one thing: does money reliably go out on time? You already have that answer — twelve, twenty-four, thirty-six months of it. What you don't have is a version anyone will trust, because a record your own company can edit isn't evidence.
Payramid builds that record as a by-product of doing payroll. Automate payroll now; use the verified history to help eligible businesses reach regulated financing later.
A year of payroll is a year of record. You add nothing to it by hand — every month you pay people, the history gets one month longer.
01
Built by doing
You fill in nothing extra. The record is simply what running payroll already produces.
02
Portable by design
The history describes your business, not our software. It is yours to show to whoever needs it.
03
Checkable by outsiders
The whole point is that someone who has no reason to trust you can still verify it.
Financing is a stated direction, not a service Payramid offers today. Any lending would sit with licensed partners, not with us.
Why now
Egypt first — on purpose.
A large base of small employers
Most employers in the country are small and mid-sized businesses, running payroll by hand, month after month, with no system underneath it.
A national push away from cash
Moving payments out of cash is national policy — and payroll is one of the largest recurring cash flows a business has.
A regulator that publishes a path
There is a published fintech sandbox, which means an emerging model has somewhere to be tested rather than merely argued about.
Where we actually are
We'd rather you hear this from us.
Most companies at this stage leave this section out. We think the businesses we want to work with would rather know exactly what is being offered.
Live today
The platform runs. Payroll runs are uploaded, previewed, approved and permanently recorded. Employees have accounts and can see their own payment history. This is working software, not a mockup.
Not yet
We do not move the money. Payramid records that a payment was approved and owed; the transfer itself still happens on your existing rail. Moving money requires a payment licence, and our route to it is a licensed partner rather than becoming a payment institution ourselves.
In a pilot
Nobody's salary depends on us. We run alongside your existing process for two payroll cycles, on real data. You keep paying people exactly the way you do now. At the end you have a verified record of those cycles, and we have proof the model holds.
Get involved
We're looking for a small number of pilot organisations.
Two or three businesses between 30 and 150 employees, and one licensed payment partner. If either sounds like you, this form is the whole application.
- It runs alongside what you do now. Your current payroll process does not change during the pilot.
- Two cycles is enough for you to tell whether this is genuinely useful, and short enough to walk away from.
- At the end you have a verified record of those two cycles, whether or not you continue.
- We will tell you what Payramid cannot do before you commit to anything — the section above is the short version.