Why one profile can be verified across portals

Verification in KiddyCash isn’t tied to a portal — it’s tied to a person. That distinction matters more than it might seem at first.

When you complete identity verification as a parent on the app, that same verified status follows you into the business portal if you’re running a school canteen in Westlands, and into the school portal if you’re also a teacher or administrator. You don’t re-verify. You don’t upload your national ID twice. The system already knows who you are.

This works because KiddyCash built verification around a single identity layer — your profile — rather than around each product surface separately. Understanding why that design choice was made helps you get more out of the platform.

The shared identity model

Every KiddyCash user has one profile. That profile is the source of truth for your identity across the app, business, and school portals. When you go through KYC (Know Your Customer), you’re verifying that profile — not a session, not a role, not a portal-specific account.

This means:

  • A parent verified on the consumer app carries that status into any business they create or are invited to manage.
  • A school administrator who completes KYC once doesn’t need to restart the process if they also manage a family wallet.
  • Businesses going through KYB (Know Your Business) still rely on the underlying KYC of their individual representatives.

The practical result is that trust is portable. If you’ve already proven who you are, KiddyCash doesn’t ask you to prove it again just because you switched contexts.

Where verification lives on your profile

You can see your current verification status, review what documents were submitted, and understand what’s still pending directly at your KYC profile page. This is the single place where your identity state is managed — regardless of which portal you primarily use.

If you haven’t completed verification yet or need to update your documents, submitting KYC from your profile walks through the exact steps. The process accepts national IDs, passports, and other government-issued documents widely used across Kenya and the broader East African region.

Why this matters in practice

Consider a merchant in Nairobi running a tuck shop that’s linked to a nearby primary school through KiddyCash. They’re operating across two portals — business and school — and potentially also using the app to manage their own children’s allowances in KES. Without a shared identity layer, they’d face redundant verification at every level.

The unified model also has compliance implications. KiddyCash operates in environments where financial regulations require confirmed identities before certain actions — issuing transaction codes, enabling wallet withdrawals, or integrating with payment rails like M-Pesa. A single verified profile means those compliance checks only need to happen once. The verification state then propagates wherever it’s relevant.

This approach is increasingly common in platforms designed for layered financial access, and KiddyCash has extended it to cover its specific mix of family finance, school payments, and business tools. You can read more about how this has evolved in What’s new in verification in KiddyCash and get deeper context in A closer look at verification in KiddyCash.

A note on role-based access

Verification unlocks access — but roles still control what you can do. Being verified doesn’t make you an admin on a school portal you haven’t been invited to. The identity layer and the permissions layer are separate. Verification answers “who are you?” — portal roles answer “what can you do here?”