Join our Newsletter — 33% off our NHI Course

Merchant risk council membership: what it means for identity teams

 

(@nhi-mgmt-group)
Member Moderator
Joined: 1 year ago
Posts: 21730
Topic starter  

TL;DR: Merchant fraud is increasingly blending identity verification, account takeover, synthetic identity, and payment abuse into one control problem, according to SumSub. That convergence makes lifecycle governance, fraud signals, and customer trust management inseparable for practitioners.

Editorial analysis by NHI Mgmt Group, based on content published by SumSub: “Sumsub Joins Merchant Risk Council to Advance Fraud Prevention and Digital Trust”.

Key questions

Q: What breaks when identity verification, authentication, and fraud controls are managed in separate systems?

A: Separate systems usually create duplicated data, inconsistent decisions, and weak context sharing.

Q: When should teams prioritise identity verification over downstream fraud review?

A: Teams should prioritise stronger identity verification when account creation, seller onboarding, or payout access creates immediate loss potential.

Q: How should security teams measure whether trust controls are actually working?

A: Security teams should measure trust controls through a small set of operational indicators that show scope, compliance, lifecycle performance, and anomaly trends.

Practitioner guidance

  • Align verification with lifecycle governance Define when an account moves from trusted to monitored to restricted, and tie those states to fraud telemetry rather than initial KYC or onboarding checks alone.
  • Correlate fraud and identity signals Join account creation, login behaviour, payout changes, device signals, and payment outcomes so fake accounts and mule activity are visible in one risk view.
  • Separate customer trust from compliance completion Avoid treating completed verification as a permanent trust outcome, because fraud patterns can emerge after the original identity check has passed.

Bottom line: Merchant fraud is increasingly a lifecycle governance problem, not just a payment or onboarding problem.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 day ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 5 months ago
Posts: 21566
 

Identity verification is becoming a fraud governance control, not a compliance step. In marketplace and e-commerce environments, verification now helps determine whether an account should be trusted for transaction activity, seller onboarding, or payout access. That moves it into the same governance conversation as access review and privilege management. Practitioners should treat verification outcomes as a policy input, not a formality.

A few things that frame the scale:

  • 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface, according to Ultimate Guide to NHIs.
  • 79% of organisations have experienced secrets leaks, with 77% of these incidents resulting in tangible damage.

A question worth separating out:

Q: How can fraud, payments, and IAM teams work from the same control model?

A: They should share a common view of identity risk across enrolment, authentication, recovery, and monetisation. That means fraud signals must influence identity decisions, and identity assurance must shape payment trust. The goal is one operating model that sees the same user or seller across all high-risk steps.

👉 Read our full editorial: Merchant risk and identity verification are converging in fraud control



   
ReplyQuote
(@mr-nhi)
Member Moderator
Joined: 5 months ago
Posts: 21566
 

Merchant fraud and identity verification now form one governance surface. The article reflects a broader market reality: identity assurance no longer ends at onboarding, because fraud actors exploit the gap between verified identity and trusted behaviour. That collapse matters for merchant risk teams, IAM leads, and fraud operations alike. Practitioners should stop designing controls around a single verification event and instead govern trust as a lifecycle property.

A few things that frame the scale:

A question worth separating out:

Q: What should merchants do when verified accounts start behaving like fraud risk?

A: They should move from verification status to behavioural review, then restrict or suspend privileges that create financial exposure. Verified identity does not equal safe behaviour, so the response should focus on limiting payout access, order abuse, and account misuse before the case is closed.

👉 Read our full editorial: Merchant risk and identity verification are converging in fraud control


This post was modified 1 day ago by NHI Mgmt Group

   
ReplyQuote
Share:

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.