Summary: This article orients teammates to what Nuuvia is, how families access it, and how the core product areas work. Use it as a baseline reference when onboarding a new team member or when a client asks "what is Nuuvia, at a high level."
What is Nuuvia
Nuuvia is a youth banking experience that financial institutions (credit unions and banks) offer to their members as a co-branded or white-labeled add-on to their existing digital banking platform. Rather than giving a minor a standalone adult-style debit app, Nuuvia gives parents and children a shared, guided experience layered on top of the FI's own online and mobile banking — so the FI keeps the deposit relationship, the card program, and the household connection.
Nuuvia is not a stand-alone consumer app with its own signup. Families only reach it through their bank or credit union's branded digital banking platform.
How families access it
The parent logs into their FI's existing online or mobile banking.
From there, they single sign-on (SSO) into Nuuvia — no separate Nuuvia login is created.
The parent completes registration, which sets up their own parent profile and adds one or more child accounts to the household.
Each child gets their own child-facing view, separate from the parent's view but linked to the same household.
Because everything happens inside the FI's branded environment, all activity, approvals, and card controls are handled inside the bank or credit union's own platform — not a separate Nuuvia-branded site.
The core product areas
Nuuvia's baseline navigation has four tabs: Spend, Save, Give, Earn.
For financial institutions that have adopted the Enhanced Learning / BizKids module, the nav changes: Give is removed from the top-level nav (it moves into the overflow/kabob menu) and a Learn tab takes its place. Give functionality isn't removed from the product — just relocated — and Learn becomes the home for financial-education content (including what used to be "Training Videos" under Save).
"Borrow" is not a tab. It shows up in some client-facing marketing/onboarding copy as a friendly label for the kid loans feature, which lives inside Earn — not as its own nav item.
Tab | Present for | What it covers |
Spend | All clients | Card enablement, transaction activity, balances, card controls (where configured) |
Save | All clients | Budgeting, savings goals, progress tracking, financial education (unless a Learn tab is present) |
Give | All clients (top-level nav, unless Learn is enabled — then moves to the overflow menu) | Charitable giving |
Earn | All clients | Chores/tasks, one-time money requests, kid loans ("Borrow" in some marketing copy), allowance |
Learn | Clients on the BizKids/Enhanced Learning module | Financial literacy curriculum (BizKids core, optional "It's a Money Thing" content) |
Every one of these areas follows the same core permission pattern:
The child initiates or completes. They complete a task, request money, ask for a loan, or submit something for review.
The parent approves or configures. Nothing involving money moves without a parent taking an action — approving a task, approving a request, or setting up the rule in advance (like an automated allowance).
This "child proposes, parent approves" pattern is consistent across Earn specifically, and is a good mental model for the platform as a whole, since Nuuvia is COPPA-covered and money movement always requires a parent-side gate somewhere in the flow.
What a first-time setup typically looks like
Parent completes registration through the FI's platform and adds their child (or children) to the household.
Parent sets initial configuration — for example, an allowance schedule, a savings goal, or card controls for a child's Spend tab (availability of specific controls depends on the FI's core/digital banking integration).
Child logs into their own view and can explore Save (or Learn) content, submit a savings goal, or request money for a completed task.
Parent reviews pending items — task completions, money requests — and approves or declines them.
Ongoing use is mostly asynchronous: kids propose/complete, parents review and approve, and both sides can see balances and progress in real time.
Notes / things to double check when helping a client
Confirm whether a client is on the BizKids/Enhanced Learning module before describing the nav. If they are, expect Learn in the top nav and Give under the overflow menu. If they're not, expect the standard four-tab layout.
Not every FI has every feature enabled. Availability of specific controls (like card limits) depends on the FI's digital banking and core banking integration — don't assume a feature is live for a given client without checking their configuration.
Terminology varies by client copy, but the underlying pillars and the child-proposes/parent-approves pattern are consistent across all Nuuvia implementations.