hlr-20-strong-user-authentication-for-electroni

Enforce EUDI strong user authentication requirements for electronic payment transactions.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-20-strong-user-authentication-for-electroni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hlr-20-strong-user-authentication-for-electroni
Source: https://github.com/sourcelabbg/eudi-knowledge/tree/main/.ai/skills/hlr-20-strong-user-authentication-for-electroni
Command: npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-20-strong-user-authentication-for-electroni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need for robust user authentication in electronic payments within the EUDI framework, ensuring secure and compliant transactions.

Core Features & Use Cases

  • EUDI High-Level Requirements: Implements normative SHALL/SHOULD/MAY requirements for strong user authentication in electronic payments as defined in ARF Annex 2.
  • Transaction Data Processing: Enables Wallet Units to process transactional data for SUA attestations, including rendering, signing, and logging.
  • Use Case: When a user needs to authorize a payment using their EUDI Wallet, this Skill ensures the Wallet Unit correctly handles the transaction data and cryptographic processes required for Strong User Authentication (SUA) as per PSD2 regulations.

Quick Start

Use the hlr-20-strong-user-authentication-for-electroni skill to ensure compliance with EUDI requirements for electronic payment authentication.

Frequently Asked Questions about hlr-20-strong-user-authentication-for-electroni

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement strong user authentication for electronic payments in an EUDI Wallet?

Strong user authentication for electronic payments is implemented by enforcing EUDI high-level requirements from ARF Annex 2, ensuring Wallet Units correctly process transactional data, device binding signatures, and SUA attestations for PSD2 compliance.

What are the EUDI requirements for processing transaction data during payment authorization?

EUDI requirements mandate that Wallet Units process transaction data for SUA attestations by handling data rendering, device binding signatures, and logging according to normative SHALL/SHOULD/MAY specifications defined in ARF Annex 2.

How does a Wallet Unit validate SUA attestations against technical specifications?

A Wallet Unit validates SUA attestations by checking transactional data and cryptographic processes against attestation rulebooks and technical specifications like TS12 to ensure compliance with EUDI strong user authentication standards.

Do I need to follow PSD2 regulations for EUDI wallet payment authentication?

PSD2 regulations apply to EUDI wallet payment authentication, requiring Wallet Units to execute Strong User Authentication (SUA) processes that correctly handle transaction data and cryptographic signatures for compliant electronic payments.

What is the difference between SHALL, SHOULD, and MAY specifications in EUDI strong authentication?

SHALL, SHOULD, and MAY specifications in EUDI strong authentication dictate varying levels of obligation for Wallet Units, governing how transactional data is rendered, signed, and logged for SUA attestations under ARF Annex 2.