Topic starter
06/06/2026 1:39 am
TL;DR: Retail authentication now has to follow customers across mobile apps, kiosks, loyalty systems, and connected devices, with 73% of consumers shopping across several channels during the buying journey, according to Descope. Static login pages no longer match omnichannel retail journeys, where device trust, risk signals, and cross-channel session continuity determine both conversion and account security.
Editorial analysis by NHI Mgmt Group, based on content published by Descope: “The Power of Descope Flows: Omnichannel Retail Auth”.
By the numbers:
- 73% of consumers shop across several channels during their buying journey.
Key questions
Q: How should retailers design authentication for customers moving between mobile apps and kiosks?
A: Retailers should design authentication as a continuous identity journey, not a single login event.
Q: Why does shared-device retail authentication create higher fraud risk?
A: Shared devices compress the boundary between a customer session and an untrusted terminal.
Q: What are the signs that retail authentication is too static for omnichannel journeys?
A: The warning signs are repeated logins across channels, frequent friction on kiosks or smart devices, inconsistent step-up behaviour, and session handoffs that fail when the customer switches from one device to another.
Practitioner guidance
- Map retail journeys by device and channel Inventory where customers start, pause, and resume sessions across web, mobile, kiosks, loyalty flows, and connected devices, then define where identity must persist versus re-verify.
- Use second-device approval for shared endpoints Route kiosk and other shared-device authentication through a trusted mobile approval step so credentials are never typed on public or keyboard-limited hardware.
- Apply step-up rules to high-risk retail actions Require stronger verification for checkout, payment updates, reward redemptions, or unfamiliar device activity, while keeping low-risk browsing paths low friction.
Bottom line: Retail authentication now has to follow the customer across channels, devices, and shared endpoints rather than stop at a single login.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 2 days ago by NHI Mgmt Group
06/06/2026 2:53 am
Retail authentication is becoming a session-orchestration problem, not a login problem: The old assumption was that identity proof happens once at the start of a browser session. That assumption breaks when customers move across mobile, kiosk, loyalty, and connected-device touchpoints inside one shopping journey. The implication is that identity teams have to govern continuity across channels, not just authenticate entry.
A few things that frame the scale:
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: Should identity teams prioritise conversion or stronger verification in retail journeys?
A: They should not treat it as an either-or choice. The better approach is to reserve stronger verification for higher-risk contexts such as unfamiliar devices, payment changes, or reward redemption, while keeping trusted paths friction-light. That balance protects revenue without normalising excessive prompts that push customers out of the journey.
👉 Read our full editorial: Omnichannel retail authentication is shifting beyond single-session login
This post was modified 2 days ago by NHI Mgmt Group