Why this matters
We get a lot of questions during implementation about how spending limits and card controls actually work behind the scenes — especially from IT and digital banking teams who want to understand what talks to what before they sign off. This guide answers the most common ones in plain language.
How Nuuvia connects to your systems
Nuuvia always needs two things to work: a way to verify who's logging in, and a way to read and update account/card information. Depending on your digital banking provider, card processor, and core, those two jobs can be handled by the same system or by two different ones.
Pattern A — one system does both. Your digital banking provider handles sign-in and is the source of your banking data (accounts, balances, transactions). Card controls depend on whether that provider's platform has built out a card-controls capability yet — some have, some haven't.
Pattern B — sign-in and banking data are split. Your digital banking provider handles sign-in only. Once a member is authenticated, Nuuvia connects directly to your core processor for everything else — accounts, balances, transfers, and card controls.
What this means for you: if your institution's card controls aren't available through Nuuvia yet, it's almost always because of Pattern A — the digital banking provider's API doesn't yet expose card data, not because of anything on Nuuvia's side or your core. In Pattern B setups, card controls work end-to-end because we connect straight to the core, where that data actually lives.
Where is the spending limit actually stored?
Two places, and it's worth understanding the difference:
Your core is the system of record. When a parent sets a spending limit in the Nuuvia app, we write that value directly to the card record in your core, in real time.
Nuuvia also keeps a local copy so the app can show the parent their current settings instantly, without a delay waiting on the core. Think of it as a cache, not a second source of truth.
One thing to know: if a limit is ever changed directly in your core system (outside of Nuuvia — for example, by a staff member), Nuuvia's local copy won't reflect that until the next time we read it. If your team wants those two values to always match in real time, that's a conversation worth having during implementation.
How does the daily spending limit actually work?
Parents set one daily spending limit in the app. Behind the scenes, most cores enforce limits by category (ATM withdrawals, in-person purchases, signature purchases, bill pay, etc.) rather than as a single number. So when a parent sets their limit, Nuuvia applies that same amount across the relevant categories at once, so the limit is consistent no matter how the card is used.
Parents typically choose from a set of pre-approved amounts (which your institution defines, often by age group) rather than typing in a custom number — this keeps the options aligned with your institution's youth account policies.
Can a parent change the card status (lock/unlock) too?
Spending limits and card status (active, locked, etc.) aren't quite the same under the hood:
Spending limits are read/write — a parent's change goes to the core immediately.
Card status is currently read-only in the app — parents can see the card's status, but can't lock or unlock it from Nuuvia itself.
If lock/unlock is something your institution wants for youth cards, flag it during implementation so we can confirm whether it's available for your specific core/provider combination.
Does this data update automatically, or does someone have to refresh it?
Everything is read in real time, on demand — at login, when the account dashboard loads, and whenever a card control action is taken. There's no batch job or overnight sync. The one exception is the spending limit display itself, which (as noted above) shows Nuuvia's stored value rather than re-checking the core every time the screen loads.
Why can't we get card controls today?
The most common reason is that your digital banking provider's published API simply doesn't include a "card controls" capability yet — this is a gap across the industry, not specific to Nuuvia or any one FI. Providers are actively working to close this gap, and once an integration is available, we can generally add support without disrupting anything else you already have live.
If your institution is on a core/provider combination that supports direct connectivity (Pattern B above), card controls are typically fully available today.
Questions?
If you have questions specific to your institution's setup — which pattern applies to you, whether card status controls are on your roadmap, or anything else — reach out to your Nuuvia implementation contact and we'll walk through your specific architecture.