Cards get lost. Phones get banned. Cash gets stolen. On a campus where the same people come back every day, only one credential fits.
Every payment credential answers a single question: how do we know it's you?
On an open network (the street, an e-commerce checkout, a petrol pump), that question has to scale to a stranger. The credential has to be something you carry, because the merchant has no prior relationship with you. A card, a phone, a biometric tokenised into a network.
The closed loop is different
Inside a school, a campus, a members' club, or a corporate cafeteria, the institution already knows who you are before you walk up to the counter. You are a student, an employee, a member. The institution has already enrolled you, assigned you a role, and issued you a policy.
In that context, the payment credential question collapses into a much simpler one: which of our already-enrolled people is standing in front of this camera?
That is a 1:N match inside a small, well-defined set. It is a problem face recognition solves with embarrassing accuracy and sub-second latency.
What this unlocks
Once the credential is the face itself, a lot of downstream problems evaporate.
You cannot forget your face at home. You cannot lose it at the playground. You cannot pass it to a friend at lunch break. It does not need charging. It cannot be demagnetised. It does not need to be replaced at the start of the academic year.
All of this is trivially true, and therefore easy to dismiss. But anyone who has managed a canteen or a tuck shop at scale will tell you that the boring failures (forgotten cards, lost PINs, kids sharing passes, end-of-day cash that doesn't tally) are what actually dominate operations. Removing them is not incremental. It is a different category of product.
What it doesn't unlock
Face payments do not replace the global payment rails. Money still has to get into the system from somewhere, and still has to leave the system for vendors to get paid. That part remains ordinary: a regulated payment gateway, the institution's own bank account, the usual KYC and settlement rhythm.
Enfacial is the layer on top of that, not a replacement for it. We are not a payment aggregator. We don't hold funds. We operate the closed loop: the part where the face is enough.
The only interesting question
The only question that matters is whether the institution and the people it serves actually trust this enough to use it daily. That is a privacy question, not a technology question. We have a view on how to earn that trust; we'll write about it separately.