Author: Aneta Ciurkot

How Banks Can Use NEC to Strengthen Identity Across the Customer Lifecycle 

Posted by Aneta Ciurkot on Posted in Digital ID, Enterprise, Finance Tagged

Banks tend to see the value of digital identity most clearly at the points where trust is being tested: account opening, authentication, recovery, payments, and employee access. In each of those areas, stronger identity can help reduce fraud, improve consistency, and give customers and institutions more confidence in the interaction. 

These are the areas where NEC helps financial institutions apply digital identity and biometrics in practical ways. The goal is to give banks a stronger and more consistent way to verify identity, reduce fraud, and support trust across the customer and workforce lifecycle.  

Onboarding and KYC 

The first place banks feel the limits of weaker identity is at onboarding. Account opening has to be fast enough to support digital growth, but strong enough to stand up to fraud, impersonation, and compliance requirements. 

NEC can help banks strengthen digital onboarding and KYC through identity verification that captures and validates an identity credential, then verifies a live selfie with liveness detection and a one-to-one biometric match against the photo on the ID credential. In practical terms, that helps the bank confirm that the document is valid, that the person is real and present, and that they are the rightful holder of the identity being presented.  

Authentication, Account Protection, and Recovery 

Once the account is opened, the identity challenge shifts. Banks need to protect existing accounts against misuse, confirm identity during ongoing access, and restore access when credentials are compromised or an interaction requires stronger proof. 

NEC can help banks carry identity assurance forward after onboarding through ongoing biometric confirmation. That gives the institution a stronger way to confirm that the same trusted person is returning, rather than relying only on passwords, OTPs, or knowledge-based checks. It is especially relevant in account recovery, where the bank needs to re-establish confidence quickly and securely without forcing the customer into a branch visit or a manual process. The platform overview identifies account recovery and step-up verification in financial services as a direct use case.  

Step-Up Identity for Higher-Risk Actions

Not every interaction calls for the same level of assurance. A routine login may require one approach. A large transfer, a new payee, unusual account activity, or a sensitive profile change may require something stronger. 

This is where banks can use NEC to apply biometric verification as a step-up control for higher-risk actions. A customer can be asked to complete a live biometric verification event when the bank needs greater certainty that the person behind the action is the legitimate account holder.

Payments, Wallets, and Channel Continuity 

Banks also need identity to work consistently across apps, payments, wallets, and in-person service environments. A customer may open an account in one channel, authenticate in another, approve a payment somewhere else, and interact with bank staff in a different setting. If identity is handled differently in each place, gaps start to appear. 

NEC can help banks connect those experiences more effectively. The retail banking and payments architecture you shared brings together wallets and apps, POS components, customer identity and access management, bank and payment systems, and an identity resolution platform. That gives banks a stronger way to support payment approval, face-based payment experiences, and more consistent identity assurance across channels.  

Consent-Based Fraud Investigation and Linked-Identity Analysis 

Banks can also use NEC to support fraud investigations through consent-based biometric matching. When a customer provides identity information as part of account opening and verification, that data can later be used, within the bank’s policies and applicable legal framework, to investigate suspected fraud. If a suspicious account is identified, investigators can use the associated image to compare against other enrolled records and datasets to see whether the same person may be linked to multiple accounts using different details. This is not surveillance. It is a defined fraud investigation use case based on customer-provided data and a legitimate banking purpose. The value for fraud teams is the ability to connect related identities and spot patterns that might otherwise remain hidden. 

Where NEC Can Help First 

For most banks, the best place to start is with the use cases where identity has the clearest business impact: onboarding and KYC, account protection and recovery, higher-risk approvals, payments, and workforce access. Those are the moments where stronger identity can improve security, reduce operational strain, and create a more dependable experience for customers and employees alike. 

To see how this applies in practice, explore NEC’s use cases for banking and financial services, or speak with our team about how we’re helping banks address these use cases as part of a broader identity strategy rather than as disconnected projects.

The Biometrics Debate in Banking Has Changed

Posted by Aneta Ciurkot on Posted in Biometrics, Finance Tagged

Banks are operating under a different identity standard than they were even a few years ago. Customers are more familiar with biometrics, more aware of account takeover and impersonation risks, and less likely to believe that passwords and one-time passcodes are enough on their own. They expect stronger protection, especially when the interaction carries financial risk. They also expect identity checks to feel measured, appropriate, and well handled.

That shift matters because many banks are still relying on identity models built for an earlier digital environment. Passwords, passcodes, and fragmented verification steps still have a role, but they are no longer a strong enough foundation for trust on their own. Not when customers are opening accounts remotely, restoring access after suspicious activity, approving significant transactions, or moving across channels where certainty has to hold together.

The Old Identity Model Is Starting To Show Its Limits

The debate around biometrics in banking has changed because the problem has changed. Identity is no longer confined to login. It now stretches across onboarding, ongoing access, account recovery, transaction approval, and exception handling. In those moments, the bank is not simply granting access. It is deciding how confidently it knows who it is dealing with.

That is why biometric identity is becoming more important. Not as a standalone feature, and not as a replacement for every other control, but as part of a stronger model for confirming the person behind the interaction.

Customers Are Bringing A Different Set Of Expectations

Customers are asking for identity processes that match the seriousness of the interaction. A routine access event may call for one level of assurance. A high-value transaction, an account recovery request, or unusual account activity may call for something stronger. The expectation is not complexity for its own sake, but a confidence that the bank is applying the right level of identity assurance at the right moment.

That is one reason older methods no longer feel sufficient on their own. The issue is not that passwords or one-time passcodes have disappeared from banking. It is that they no longer represent a convincing standard by themselves for the moments where trust is genuinely being tested.

What A Stronger Identity Model Looks Like In Practice

A better identity model gives banks a way to carry trust forward. It connects the assurance established at onboarding to later interactions, rather than forcing the institution to rebuild confidence from scratch each time risk rises or something goes wrong. That continuity matters in practice. It can strengthen onboarding, support more reliable account recovery, improve transaction approval, and create a more consistent identity posture across channels.

This is where NEC’s banking identity approach becomes relevant. NEC Digital ID and NEC Identity Cloud are built around the idea that trust in financial services is not a one-time event. It has to be established at the start of the relationship, maintained over time, and applied consistently across the moments that matter most. For banks, that means support for remote identity verification, ongoing biometric authentication, and stronger continuity between onboarding, access, recovery, and higher-risk customer actions.

Stronger Identity Also Has To Stand Up To Scrutiny

Customers want stronger protection, but they also want to know that information is being handled with care. Regulators and internal stakeholders want to know that systems are proportionate, explainable, and aligned with responsible data practices.

To see how this applies in practice, explore NEC’s biometrics use cases for banking and financial services, or speak with our team about how we work with leading financial institutions on digital trust, responsible biometrics, and stronger identity across the customer lifecycle.

Why Biometrics Are Becoming Part of the Bank’s Trust Architecture

Posted by Aneta Ciurkot on Posted in Biometrics, Digital ID, Finance Tagged

For years, identity sat quietly behind the scenes in banking. It appeared at account opening, at login, and occasionally during a recovery process, but it was rarely treated as a strategic layer in its own right. That is changing. In 2026, identity is becoming part of the bank’s trust architecture: not a single control, but a framework for how institutions establish confidence, manage risk, and sustain digital relationships over time. Accenture’s Top Banking Trends 2026 points to an industry being reshaped by agentic AI, digital assets, and new competitive conditions, while Deloitte’s 2026 outlook describes a more demanding environment for governance, resilience, and regulatory oversight.

Identity Has Moved Out Of The Background

The old model treated identity as a sequence of isolated checkpoints. One process handled onboarding, another handled authentication, another dealt with call-center verification, and still another sat inside workforce access or approval flows. That approach is increasingly out of step with how banks operate now. Digital relationships are continuous, channels are interconnected, and assurance has to hold together across far more moments than it once did.

That is why identity now belongs in a larger institutional conversation. It sits close to fraud strategy, operational resilience, AI governance, and customer confidence. J.P. Morgan’s latest annual report letters make that plain. Jamie Dimon writes that misuse of customer data is likely to grow worse with AI and agentic commerce, while Jennifer Piepszak emphasizes that AI must be connected to well-governed data and safeguards that protect clients, firms, and the financial system. 

Why The Operating Model Matters More Than The Feature Set

Once identity is understood as trust infrastructure, the questions become more serious. Banks are asking whether the institution has a coherent way to establish trust at the start of a relationship, maintain it across later interactions, and support trusted reuse of identity when appropriate.

NEC Identity Cloud points to a useful way of understanding the identity challenge in banking. Trust is not created once and left behind. It begins at onboarding, has to be sustained through later interactions, and increasingly needs to support how verified identity is used across a wider set of services and decisions. That is closer to how banks actually experience the issue: not as a single checkpoint, but as an ongoing responsibility.

That matters because the quality of trust is often tested long after the first verification event. A bank may know who a customer is at account opening, but the more important question is whether that assurance can still be relied on during account recovery, transaction approval, or an unusual event. When the answer is yes, identity becomes a steadier part of the operating model. When the answer is no, the institution ends up trying to recreate certainty under pressure.

[Learn more about NEC Identity Cloud >]

Trust Is Now A Governance Question As Well As A Security One

This is what makes the biometric conversation more consequential than it was even a few years ago. The issue is no longer limited to performance measures such as speed, accuracy, or fraud reduction. Those remain important, but the larger question is whether identity systems are being used in ways that are proportionate, understandable, and properly governed.

NEC approaches digital trust through a public commitment to privacy and responsible AI. For financial institutions, that is significant because trust is not defined only by technical strength. It is also shaped by whether systems can be clearly explained, responsibly overseen, and applied in ways that reflect the sensitivity of identity in banking.

In banking, this makes biometrics part of a broader conversation about institutional trust: how it is created, how it holds up over time, and how it is governed as risk and customer expectations continue to evolve.

Explore NEC’s biometrics use cases in banking and financial services, or connect with our team to discuss how leading institutions are approaching digital trust, stronger identity, and secure customer experiences.

Why a Foundational Trust Layer Matters for Financial Services in 2026

Posted by Aneta Ciurkot on Posted in Biometrics, Digital ID, Finance

Customers engaging with financial institutions today are not simply looking for convenience. They expect their digital interactions to be secure, private, and resilient by default. High-profile fraud, data breaches, and payment scams have made consumers more informed about risk, and their expectations have shifted accordingly. Security and privacy are moving from implicit assumptions to explicit criteria by which institutions are judged.

At the same time, U.S. financial institutions are operating in an environment where account takeover, identity fraud, payment fraud, and credential compromise are persistent and measurable realities. Regulators continue to raise expectations around controls and auditability, while internal teams are tasked with modernizing legacy systems without introducing new points of failure.

Against this backdrop, digital identity has taken on a different role within financial institutions. It is no longer treated as a peripheral security function. It has become a foundational layer that supports how risk is managed, transactions are authorized, and trust is maintained across digital channels.

Identity as a Financial Risk Control

Data from U.S. regulators and industry reporting consistently shows that identity-driven fraud represents a material portion of financial losses across banking and payments. Identity theft, account takeover, and social engineering attacks remain among the most common methods used to compromise accounts and initiate unauthorized transactions.

Many of the mechanisms still widely used to establish identity—static passwords, knowledge-based questions, and one-time passcodes, were not designed for this operating environment. They are costly to manage, vulnerable to compromise, and increasingly misaligned with both threat realities and customer expectations.

As a result, identity is no longer confined to the login process. It plays a direct role in:

  • Customer onboarding and verification
  • Transaction and payment authorization
  • Fraud detection and investigation
  • Regulatory compliance, auditability, and control validation

Why Institutions Are Re-Architecting Identity

Leading financial institutions are responding by treating identity as shared infrastructure rather than a collection of isolated tools. This shift reflects a broader recognition that identity assurance must be consistent across channels, products, and transaction types.

An upgraded identity foundation must:

  • Establish high confidence in who is transacting, not just who is accessing a system
  • Support privacy-aware verification methods appropriate for regulated environments
  • Scale across digital banking, payments, and internal platforms
  • Integrate with core banking, payments, and risk systems
  • Align with U.S. regulatory, data residency, and resiliency requirements

NEC Digital ID: Built for Financial-Grade Trust

NEC Digital ID is designed to support this infrastructure-level role. Rather than focusing on a single authentication method, NEC Digital ID provides a comprehensive identity capability that supports authentication, identity verification, and transaction protection across digital financial services. This breadth allows institutions to apply appropriate levels of assurance based on transaction risk, channel, and regulatory context.

NEC Digital ID supports cloud, on-premises, and hybrid deployment models, enabling institutions to align identity architecture with regulatory obligations, internal risk frameworks, and existing technology investments.

Security and compliance are embedded into the design. Advanced biometric verification, multi-factor authentication, and adaptive risk controls help financial institutions address account takeover, unauthorized transactions, and fraud while supporting AML, KYC, and privacy requirements.

NEC’s experience delivering large-scale, mission-critical identity systems across government, defense, and highly regulated commercial environments in the United States informs this approach.

For additional perspective on how digital identity supports secure financial services in the U.S. market see:

Digital ID for Venues: The Identity Layer You Can Trust (and Explain) 

Posted by Aneta Ciurkot on Posted in Biometrics, Digital ID, Hospitality Tagged , ,

If you build or run technology for a stadium or arena, you already know the truth: identity is everywhere, even when no one wants to think about it. 

It shows up at the gate. In premium areas. At staff entrances. In vendor access. In loyalty. In age-restricted purchases. In incident response. And the more digital your venue becomes, the more those touchpoints depend on something a person has (a QR code, a phone, a credential) instead of who a person is. 

That’s why we’re seeing a clear shift: venues are thinking beyond single checkpoints and toward the full in-stadium experience where fans aren’t repeatedly asked to pull out a phone or re-confirm who they are at every moment that matters.

At NEC, we built Digital ID and Identity Cloud Service (ICS) to support this at venue scale – securely, responsibly, and in a way you can clearly explain to stakeholders and fans.  

Why this matters now: the old tools don’t answer the right question 

Traditional venue security and access tools: turnstiles, bag checks, metal detectors can help manage risk, but they don’t reliably answer the question venues increasingly need to answer: 

“Is this person the right person for this access?” 

Even modern digital tools can fall short. Tickets can be shared. Accounts can be taken over. Credentials can be passed around. And every extra check you add to compensate becomes another point of delay and another operational strain. 

Facial biometrics change the model: instead of repeatedly asking guests to present something, we can confirm identity through presence—securely, quickly, and with controls that respect choice and privacy.  

What venues and fans actually get from Digital ID 

This only works when the value proposition is real for both sides. 

For fans, the “job” is simple: get into the venue and move through key moments without repeated device dependence. Once a fan chooses to enroll, identity confirmation can happen without repeatedly presenting a phone, code, or physical credential—making interactions feel faster and more natural. 

For clubs and venue operators, the job is operational: increase identity assurance across multiple touchpoints—entry, staff zones, VIP, vendor access—without forcing a full rebuild of infrastructure. We designed our approach to integrate into existing environments via APIs and SDKs and scale across use cases rather than staying locked to a single lane or single checkpoint.  

The security question: “What exactly are you storing—and what aren’t you?” 

This is where most Digital ID conversations succeed or fail. So we address it directly. 

Our venue-focused approach is designed around privacy-by-design principles and strong controls, including: 

  • Encrypted biometric templates (not stored photos). 
    At NEC, our Digital ID technology converts a face scan into an encrypted biometric template (a mathematical representation of facial features). In this model, we do not store photos, and these templates cannot be reverse-engineered.  
  • Liveness detection. 
    We use liveness detection to help confirm the person is physically present—so it’s not a photo, video, or mask. 
  • Proven accuracy (independently benchmarked). 
    NEC’s face recognition technology has consistently ranked at the top in NIST’s face recognition benchmark testing.  
  • Cloud-native orchestration with Identity Cloud Service (ICS). 
    ICS is our identity verification service designed to deploy quickly and scale—supporting 1:1 verification, 1:N search, and optional liveness and presentation attack detection capability, with secure tenant onboarding and administration.  

What a responsible rollout looks like

If we want fans to adopt Digital ID in a stadium environment, the bar is higher than “it works.” It has to be explainable, governed, and predictable at scale.

That’s why we see three non-negotiables in successful deployments:

  1. Choice is visible and real
    Digital ID must be opt-in, with a clear alternative. Adoption grows when fans understand what they’re signing up for and how to unenroll. 
  2. Purpose is limited and systems stay separated
    A responsible design minimizes data and prevents “one giant database” thinking. Ticketing, payments, and security/watchlist workflows should remain distinct systems with clear governance and documented purpose.
  3. Performance holds up in the real world
    Venue conditions are not lab conditions. Hats, sunglasses, rain, low light, face paint—these are normal. That’s why real-world testing across conditions (and demographics), plus tuned thresholds and fallback processes, are part of doing this responsibly. 

Under that model, Digital ID becomes what venues actually need right now: an identity layer that can support multiple moments across the venue journey, not by adding more steps, but by reducing how often we ask fans to prove who they are. 

And when we design it with privacy and security as the foundation, using encrypted biometric templates and controls that are built for trust, Digital ID can scale in a way that’s good for fans and operationally sound for venues.