Join our Newsletter — 33% off our NHI Course
Home› FAQ› Authentication, Authorisation & Trust› What is the difference between customer due diligence…
Authentication, Authorisation & Trust

What is the difference between customer due diligence and strong customer authentication here?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 30, 2026 Domain: Authentication, Authorisation & Trust

Customer due diligence proves who the customer is and what attributes they possess, while strong customer authentication proves the user is present and authorised for the transaction. EUDI Wallets may support both, but the controls, evidence, and liability questions are different. Teams should not assume one control automatically satisfies the other.

How the controls differ in purpose

customer due diligence is about establishing the customer relationship itself: who the customer is, what risk attributes apply, and whether that relationship can be opened or continued under policy and regulation. strong customer authentication is about proving that the person initiating a specific transaction is present and authorised at that moment. The two controls can overlap in a journey, but they answer different questions.

That distinction matters operationally because one control is evidence about identity and risk profile, while the other is evidence about transaction-time control. CDD supports onboarding, ongoing review, and regulatory screening decisions. SCA supports payment or transaction execution decisions, especially where the business must demonstrate that the transaction was deliberately authorised and, in many regimes, bound to the specific transaction details.

For the customer relationship side, teams usually need identity proofing, screening, and periodic refresh of customer attributes. The Identity Proofing and KYC Guide is the natural reference point when the question is about verifying who the customer is and what assurance evidence supports that judgement. For the transaction side, the PSD2/PSD3 Strong Customer Authentication Guide focuses on the controls, exemptions, and evidence around transaction authorisation.

Why one control does not satisfy the other

CDD and SCA are often confused because both deal with customer trust, but they fail differently. A customer can be fully due-diligenced and still have a weak or bypassable transaction authentication flow. Likewise, a strong transaction authentication event does not prove the customer was properly identified, screened, or risk-rated at onboarding. Treating them as interchangeable creates gaps in both compliance and fraud defence.

In practical terms, CDD answers whether the business knows enough about the customer to accept the relationship and manage ongoing obligations. SCA answers whether the business can rely on a strong, current transaction-time assertion that the user authorised this action. Those are different evidence standards, and the liability consequences can differ when a dispute, fraud claim, or regulatory review follows.

That is why the same wallet or digital identity mechanism may contribute to both, but only if it produces the right type of evidence for each control. An EUDI Wallet may help carry verified identity attributes and support user authentication, yet the implementing system still has to separate onboarding evidence from authorisation evidence. The FATF Recommendations are the clearest external baseline for CDD expectations, while the NIST SP 800-63 Digital Identity Guidelines help frame assurance, authenticators, and transaction-related identity proofing.

What to check when both show up in the same flow

When customer onboarding and transaction authentication are part of the same product journey, the most common failure is evidence confusion. Teams record a successful login or wallet presentation and then assume the customer is fully due-diligenced, or they collect onboarding documents and assume later transactions are strongly authenticated. Both assumptions are unsafe.

  • Confirm which step is proving identity attributes, and which step is proving transaction authorisation.
  • Check whether the evidence retained for CDD is sufficient for audit, screening, and lifecycle review.
  • Check whether the SCA method resists replay, relay, and account takeover in the actual transaction channel.
  • Verify whether liability and dispute handling are documented separately for onboarding evidence and transaction evidence.

The best external cross-check for the customer due diligence side is the EBA AML/CFT Guidance, which anchors the regulatory treatment of customer checks in the EU context. If the implementation is in a banking or payment setting, SCA design should be assessed against the transaction controls in the relevant payment rule set, not against onboarding policy alone.

Risk and Threat Considerations

The main risk is control substitution, where an organisation believes one control closes the gap left by the other. That can lead to weak onboarding, weak transaction security, or both, especially when wallets, federation, or delegated flows make the control boundary less obvious.

Failure mechanism: A customer is either over-trusted after onboarding because transaction checks are too light, or a transaction is treated as safe because onboarding was completed, even though the live auth event is weak or stolen.

Impact: The result can be account takeover, unauthorised payments, failed disputes, regulatory findings, or an inability to prove which control was actually satisfied when the event occurred.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-63, NIST SP 800-53 Rev 5 and OWASP ASVS set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-63AAL — Authenticator Assurance LevelSCA depends on transaction-time authentication assurance and authenticators.
Recommendation — Map the transaction flow to the required assurance level and authenticator strength.
NIST SP 800-53 Rev 5IA-8 — Identification and Authentication (Non-Organizational Users)Customer due diligence and customer identity assurance concern external user identity proofing.
IA-5 — Authenticator ManagementSCA relies on managing authenticators, lifecycle, and resistance to compromise.
IA-12 — Identity ProofingCDD and onboarding evidence map to identity proofing and verification.
Recommendation — Use non-organizational user identity controls to verify external customer identity evidence. Manage authenticators so transaction authentication remains strong across its lifecycle. Apply identity proofing controls to validate customer attributes before account opening.
OWASP ASVSV6 — AuthenticationSCA is an authentication requirement, especially for user-present authorisation.
V10 — OAuth and OIDCWallet-based or federated flows often use token-based authentication and assertions.
Recommendation — Verify the authentication design resists takeover and satisfies the required assurance. Review federation and token flows so the authorisation step cannot be forged or replayed.

Practitioner Guidance

What to verify: Separate your evidence model into two buckets, customer-identity evidence for CDD and transaction-authorisation evidence for SCA. If the same event is being reused for both, treat that as a design flaw until you can show distinct assurance, logging, and retention.

Decision rule: If a control proves who the customer is, do not present it as proof of transaction authorisation. If a control proves transaction authorisation, do not treat it as sufficient onboarding or screening evidence.

Practitioner takeaway: Good implementations make the control boundary explicit in product flows, audit trails, and liability handling, because the hardest failures here come from assuming one strong control can stand in for the other.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org