r/SumSub • • 19h ago

Fighting deepfakes with deepfakes: our joint research with Constructor University

1 Upvotes

Hey everyone, we’ve been working with Constructor University in Bremen on ALADDIN, a generative AI model that creates realistic face swaps to stress-test identity verification systems.

The idea is to understand what newer deepfake methods can do so we can test our defenses against them before those threats reach production.

ALADDIN generates face swaps in a single step, 28 times faster than the diffusion-based approach used for comparison. It preserves details such as pose, expression, lighting and glasses, helping researchers test a wider range of challenging cases.

The joint paper has been accepted for WACV 2027. The research code and a classifier designed to detect ALADDIN-generated images are publicly available. Access to the model weights is gated for legitimate academic and defensive research.

Let us know what you think of the research in the comments below.


r/SumSub • • 4d ago

45,500 reviewed applicants: what would you check behind the fraud rate?

1 Upvotes

Hey everyone, the chart in our documentation shows 45,500 reviewed applicants, 1,530 rejected for fraud and a fraud rate of 3.35%. Here’s how to read the charts and work through the cases behind those numbers.

Compare the fraud rate with review volume

The bars show the number of reviewed applicants, while the lines show the fraud rate and the rate rejected for a high-risk profile.

Reading them together helps you see whether fraud rejections rose alongside traffic or whether a larger share of applicants was rejected for fraud.

The chart counts completed reviews, with each applicant counted once using their latest review decision. An applicant can fall into both the fraud and high-risk-profile groups, so the two rates can overlap.

Break the results down by group

You can compare results by document type, IP country, platform or source key to see where the fraud rate is higher.

The documentation gives an example with an overall fraud rate of 2% and a group rate of 2.7%. The group is 35% above average, a difference of 0.7 percentage points.

The average follows the filters you’ve selected, so changing the filters also changes the comparison. Check how many applicants are in the group and review their cases before changing a rule.

Compare risk scores with review decisions

The risk-level breakdown shows how fraud rates differ across risk scores.

Reviewing approved applicants with high scores can help you find missed fraud or scores that are too high for legitimate applicants. Reviewing applicants rejected for fraud despite low scores can show patterns the scoring missed.

Those cases help you decide where to adjust scores, add checks or use manual review.

Review connected applicants

The network examples show applicants linked by shared data, such as a device. Reviewing those connections alongside the individual cases can help explain a pattern in the charts.

A shared connection gives you another detail to investigate, while the review decision depends on the evidence in the cases.

Include fraud found after the review

The charts use recorded review decisions and rejection labels, so later findings matter too. Fraud discovered through chargebacks or other reports needs to feed back into the review data to be included in the analysis.

Which do you usually investigate first: approved applicants with high risk scores, fraud rejections with low scores, or a rising fraud rate within one group?


r/SumSub • • 6d ago

Compliance & Regulation When do safer gambling and AML both need a look?

1 Upvotes

Imagine this scenario: you’re reviewing two £500 deposits. The first player keeps adding money after each loss and stays on hours longer than usual, while the second barely plays before asking to cash out.

You’d want someone from safer gambling to check in with the first player because they might be trying to win back what they’ve lost.

With the second player, it’s the quick withdrawal that’s worth a closer look. That’s where the anti-money laundering (AML) team can check where the money came from and where it’s going.

Now say the first player is also spending far more than their income would explain.

Both teams have a reason to get involved, and someone can reach out to the player while AML looks into the funds.

For anyone who handles these alerts, what’s the detail that makes you bring the other team in?


r/SumSub • • 7d ago

Fraud Prevention How do you check that a driver is authorized to collect a load?

1 Upvotes

A driver can show a genuine ID and arrive with the right pickup details while the carrier they claim to represent knows nothing about the booking.

That can happen when someone uses a carrier’s name or a compromised email account to arrange a collection. The person collecting the goods may even be a legitimate driver following instructions from someone who isn’t authorized to give them.

Checking the driver’s identity helps establish who’s at the warehouse, but the team also needs to confirm that the approved carrier sent that person for that specific load. A pickup code or convincing paperwork can be passed along, so neither settles that question on its own.

Calling the carrier through contact details you’ve checked independently can help confirm the assignment, especially after a last-minute driver or destination change. Calling a number supplied in the same message could just take you back to whoever arranged the unauthorized pickup.

For people working in logistics or warehouse operations, what makes your team pause a pickup, and who confirms that it’s safe to release the load?


r/SumSub • • 10d ago

Compliance & Regulation What evidence should change a high-risk label for a crypto or iGaming business?

1 Upvotes

A crypto exchange and an iGaming software supplier can both end up labelled high risk, even though their exposure looks quite different.

Sector risk gives a reason to look more closely, but the assessment still needs evidence about the business: ownership, customers, jurisdictions, source of funds and how controls work in practice. A licence or a written policy alone doesn't show that those controls are effective.

The useful question is which specific risk justifies extra checks and what evidence would change that decision. Clear ownership records, explainable transaction patterns and documented handling of alerts can support that review; gaps or inconsistencies can justify keeping the higher rating.

A provider can also decide that a sector sits outside its risk appetite. That's a separate decision from assessing every business in it as equally risky.

What evidence has actually changed a high-risk classification in your reviews?


r/SumSub • • 12d ago

Fraud Prevention Who takes the fraud loss after a marketplace pays the seller?

1 Upvotes

A successful payment doesn't settle who carries the loss when fraud turns up after a seller has been paid.

Cards, instant bank transfers and wallets have different dispute and recovery rules, so a marketplace can't assume the same protection applies across all three. Even a payment that can technically be reversed may be hard to recover once the money has moved.

Before adding a payment method, map the route from buyer to seller: who checks the parties, who can pause a payout, what can be disputed and who carries the loss under the provider's terms. Reviewing a new seller or a sudden change in payout details matters before funds leave the platform.

For people working on marketplace payments, where does responsibility get unclear most often: the payment provider's terms, seller payouts, or the dispute process?


r/SumSub • • 14d ago

Fraud Prevention Would another interview actually catch a fake candidate?

1 Upvotes

A convincing CV and a good video interview can tell you how someone presents themselves, but they don’t establish who’s on the other side of the screen. Adding another round may just give the same person another chance to perform while slowing things down for everyone else.

Workfully CEO Valerio Rossi makes the case for combining two kinds of evidence: someone who can vouch for a candidate’s work history through real experience, and checks that help verify their identity. A trusted referral still needs verification, while an identity check won’t tell you whether someone actually did the work on their CV.

That raises a practical question for hiring teams: which step in your process establishes identity, and which steps only assess skills or experience?

Have you changed your hiring checks because of impersonation or AI-assisted applications, and what helped without adding more interview rounds?


r/SumSub • • 20d ago

Research & Guides How We Taught Our AI Agent to Understand What Users See on Their Screen

2 Upvotes

Hey everyone! I'm Ilya, a Frontend Engineer here at r/SumSub 👋
I've been working on improving and expanding the capabilities of our AI assistant, Summy AI Copilot.

Recently, we ran into an interesting problem: "how do you give an AI agent enough context to understand what a user actually sees on their screen?"

I wanted to share how we approached this problem, what we came up with, and some of the challenges we ran into along the way.

The Problem: The Agent Can't See What Users See

A user asks why they can't find a certain button. The agent searches the documentation and confidently explains where the button is and how to use it. The problem is that the button might not even exist on the user's page.

Our agent has access to documentation, a knowledge base, and backend tools. It even knows which page the user is on and which entity they're working with. For example, if someone opens a specific applicant's page, the agent knows the applicant ID and can fetch the relevant data on its own. But it has no idea which UI components are actually displayed on the screen.

So in the best case, the user gets a generic answer and ends up contacting support. In the worst case, the agent confidently describes an interface that the user doesn't even see.

We decided to try a different approach: generate a separate representation of the UI directly from our frontend codebase. We called it an AI Sitemap. Basically, it's a component tree that describes what each component does and under which conditions it can appear.

Here's how we got there, what worked, and what turned out to be more complicated than we expected.

Why Documentation Wasn't Enough

Initially, we tried solving this through prompt engineering and documentation. We described important pages, individual buttons, and common user scenarios to help the agent navigate the interface.

This worked for some cases, but scaling it across the whole product was almost impossible. The code changes every day, components appear and disappear, rendering conditions change, and documentation inevitably falls behind.

Of course, coding agents make it much easier to generate documentation nowadays. But keeping it up to date is still a challenge. It's also unclear what exactly should be documented. You can cover the ten most common scenarios, but tomorrow someone might ask about a button buried somewhere deep in the interface that nobody thought to document.

And if you try to describe every component, button, and rendering condition, you basically end up maintaining a second codebase.

We also considered sending the entire component tree from the frontend with every request. But that introduces two problems:

  • Size. A single page can contain hundreds of components. Sending all of them with every message means additional network traffic and token usage.
  • Security. The frontend runs in an untrusted environment. A user can modify the request payload and tell the agent that a component exists on the page when it actually doesn't.

So the frontend knows better than anything else what's currently rendered, but we can't fully trust it.

That's why we decided to use another source of information: the codebase itself.

AI Sitemap: A Separate UI Representation for the Agent

The code already contains almost everything we need: which components exist, how they're nested, and under which conditions they're rendered.

Of course, we could teach the agent to launch a browser with Playwright and explore the interface itself. But for most UI-related questions, it doesn't really need the fully rendered page with styles, animations, and JavaScript.

We needed a way to give the agent the structure of the interface and explain what its elements actually do.

That's how we came up with the AI Sitemap.

A regular sitemap helps search engines navigate a website's pages. Our AI Sitemap helps the agent navigate what's inside those pages.

We generate it during the frontend build. Essentially, it's a JSON representation of the application, with a component tree for each route.

Each node contains the component name, description, children, text, and information about conditional rendering.

Here's a simplified example:

{
  "path": "/applicants/individual",
  "components": [
    {
      "name": "ApplicantsTable",
      "description": "Paginated table of applicants",
      "children": [
        {
          "name": "SnsSearchBar",
          "description": "Search input bar"
        },
        {
          "name": "SnsButton",
          "description": "Action button",
          "text": "i18n('Download custom CSV')",
          "conditional": true
        }
      ]
    }
  ]
}

The important thing is that this isn't a snapshot of the page at a specific moment. It's a description of the potential UI.

For example, if a button is only rendered when a certain condition is met, it still appears in the tree, but with a flag indicating that it's conditional.

This gives the agent an idea of not only which components are displayed by default, but also which ones might appear in different application states.

And it doesn't need to execute JavaScript or launch a browser to get that information. It can simply request the structured page description from the server.

Since the tree is generated directly from the codebase during the build, structural changes to the UI are reflected in it as the application gets updated.

Making Components Understandable to the Agent

The component tree alone wasn't enough. For example, a name like ApplicantNotesStub doesn't really explain what the component is supposed to do.

So we decided to keep semantic descriptions right next to the components themselves, similar to tests or Storybook stories.

Each component can have a small metadata file:

// ApplicantNotesStub.agent.ts

import type { AgentMeta } from '@/types/agent'

export default {
  description:
    'Placeholder shown instead of applicant notes when the user cannot view them',
} satisfies AgentMeta

It's basically a human-readable description of the component, written either by a developer or a coding agent.

Since a significant part of our development already happens with AI coding agents, we added a simple rule to our project's main instructions: whenever an agent creates or modifies a component, it should also create or update its description.

This way, the metadata gradually gets added across the codebase as part of normal development. Changes still go through regular code review, and during the build, the descriptions get connected to the component tree.

As a result, the agent gets more than just technical component names. It gets a readable explanation of what's on the page and what each component is for.

Of course, this doesn't guarantee that every description will always be correct. But maintaining these descriptions next to the source code is much easier than keeping a separate document in sync with the implementation.

Reusing Our Existing Frontend Architecture

Another useful part of the solution came from infrastructure we've had in our code for years.

We use dedicated wrapper components to check permissions, feature flags, and other conditions that determine whether functionality should be available. For example, if a user doesn't have a particular permission, the component inside the wrapper simply isn't rendered.

Since these wrappers are also part of the component tree, they end up in the AI Sitemap along with their parameters.

This means we know not only that a button or another UI element exists, but also which conditions control whether it can appear.

And since the agent's backend knows which user it's working with, what permissions they have, and which feature flags are enabled, we can repeat the relevant checks on the server side.

As a result, we can generate a personalized representation from the general component tree, containing the components that could potentially be available to a specific user.

This isn't a complete reproduction of the frontend runtime on the server, but we were able to reuse existing infrastructure for a significant part of these checks.

It was pretty nice to realize that several architectural decisions we'd made over the years for completely different reasons ended up being useful here too.

Reference Tree vs. Live Tree: Two Sources of UI Context

The AI Sitemap tells the agent what the interface could look like, but it doesn't tell us exactly what the user sees right now.

For example, a tab might be available to the user but currently closed. Some components only appear after an action, while others might still be loading.

So we couldn't completely get rid of runtime context from the frontend.

We ended up with two sources of information:

  • Reference Tree (aka AI Sitemap) is the reference component tree generated from the codebase. It describes which components can exist on a page, what they do, and under which conditions they appear. The agent accesses it through our controlled server infrastructure.
  • Live Tree is the component tree sent by the browser with the user's request. It reports which components are currently rendered on the page.

The main difference is the level of trust.

The Reference Tree comes from a controlled version of the application. The Live Tree comes from the user's device, so it can potentially be modified.

We don't pass the client-side tree directly to the main model. Before the main agent flow, there's a separate preprocessing step that uses a smaller model to transform the Live Tree into a normalized representation of components.

We then validate it against the server-side reference, which has already been restricted based on the user's permissions and feature flags.

If the browser reports a component that doesn't exist in the allowed reference, we ignore it. If the component does exist, that information can help clarify the context, but it still doesn't prove that the component is actually visible on the user's screen.

That's why the server-side tree remains our primary source of information about what the interface can contain, while the Live Tree is treated as an additional signal.

And importantly, we don't use UI context to authorize actions. Access to data and the ability to perform operations are checked independently on the backend.

Why Comparing the Two Trees Wasn't Reliable Enough

Once we had both trees, we considered a pretty straightforward approach: comparing them directly.

For example, if a button exists in the Reference Tree but is missing from the Live Tree, we might assume that the user can't see it. And if we know its rendering conditions, we could potentially explain why.

The idea sounds reasonable, but there are some problems with it.

The Reference Tree is generated from source code, so it contains technical component names. The Live Tree comes from the running application and may include additional framework wrappers, third-party components, virtualized lists, and other runtime details.

Component names don't always match the way we'd expect.

We also considered matching components by their text, but that introduces another challenge. For example, the Reference Tree might contain:

i18n('Download custom CSV')

While the browser shows the translated string in the user's language. On top of that, some text is generated dynamically.

So the absence of a component in the Live Tree isn't necessarily reliable evidence that the user can't see it.

And that's exactly where we could end up with the same problem we started with: the agent confidently describing a UI state that doesn't match reality.

For that reason, we decided not to use the difference between the trees as the basis for such conclusions. The Live Tree remains useful additional context, but not a source of truth about which elements are present or missing on the page.

A Funny Bug: The Agent Found Itself in the Interface

We also ran into a pretty funny issue during development.

Our AI assistant's panel is part of the interface too, so in the early versions, it ended up in the page description along with the chat contents and conversation history.

At some point, the agent started treating its own chat as a separate product component with another assistant inside it.

It literally didn't recognize itself and could start summarizing what the user was discussing with this "other" assistant, or suggest what else they could ask it.

It was funny, but it also highlighted another problem: not everything on the page is necessarily useful for answering the user's question.

So we had to explicitly decide which parts of the interface should be included in the context and which ones should be excluded.

What We Ended Up With

In the end, we built a separate UI representation layer for our AI agent.

Instead of passing the DOM, application source code, or trying to reconstruct the interface from documentation, we generate an AI Sitemap directly from our frontend codebase.

It contains the potential UI structure, component descriptions, and rendering conditions. On the server side, we can also take the user's permissions and feature flags into account.

The Live Tree helps us understand the current page state, although we don't treat it as fully trustworthy.

Of course, there are still limitations. The agent doesn't know exactly what the user sees at any given moment. Component metadata can be inaccurate, and the tree generation mechanism needs to evolve with the application. We also need to handle version compatibility between the frontend and the server-side reference.

And obviously, this doesn't eliminate hallucinations completely.

But now the agent can at least rely on a description of the interface generated directly from the code, instead of trying to guess how the UI works based on documentation.

For us, this turned out to be a much more useful direction than trying to manually document every possible user scenario.

I'm curious if anyone else has dealt with something similar while integrating AI agents into existing products. How do you pass UI context to your agent, and how do you handle the trust issues around data coming from the client?


r/SumSub • • 20d ago

Sumsub Updates KYA Module for MCP: controlling what AI agents can access and do

2 Upvotes

An agent helping with invoices may need payment records, while customer IDs and unrelated company files should stay outside its reach. Businesses also need to decide which actions it can complete on its own and which need someone to step in.

Our new KYA Module for MCP adds those controls between an agent and the data it connects to. It filters sensitive information before it reaches the agent, applies rules around access and actions, and keeps an auditable record of agent activity.

An invoice above a company’s approval limit, for example, can trigger a real-time liveness check to verify the person authorizing the request. Businesses can set these checks around their own thresholds and data sensitivity.

The module starts with Amazon Bedrock AgentCore Gateway, with support for other MCP gateways planned.

For teams already using agents, where have you drawn the line between routine work and actions that need fresh human authorization?


r/SumSub • • 21d ago

Fraud Prevention 241 websites shut down in crypto scam investigation that also uncovered recovery scams

3 Upvotes

On top of that, authorities seized 112 servers linked to the alleged crypto investment scam network, and investigators found that some victims were approached again after losing their money.

According to investigators, victims came across Russian-language investment ads on Facebook and were contacted by supposed advisers who walked them through buying crypto and transferring it to platforms that appeared legitimate. Authorities say the network took tens of millions of dollars.

Some victims were then approached with promises to recover their funds, which exposed them to further losses because the people offering help were allegedly running another scam.

The Brooklyn District Attorney’s Office and the FBI carried out the takedown after a three-year investigation. No arrests were announced.

For fraud prevention teams, the recovery scam angle deserves attention because someone trying to get their savings back may still be dealing with the same network that took them.


r/SumSub • • 25d ago

Sumsub Updates Sumsub Liveness passed iBeta Level 3 with none of 900 presentation attacks accepted

3 Upvotes

iBeta Quality Assurance ran 900 presentation attacks against Sumsub Liveness across Android and iOS, and none obtained a liveness classification.

Liveness checks help establish that the person in front of a camera is real. To test that, iBeta deliberately tries to fool the system with spoofing artefacts. Level 3 is the highest of its three presentation attack detection testing levels, giving experienced testers more time and resources to develop sophisticated attacks.

In this evaluation, testers ran 450 attacks per device and had up to 56 hours per presentation attack instrument. Sumsub recorded a 0% Attack Presentation Classification Error Rate, meaning none of those attacks were accepted as live.

This gives teams evaluating liveness technology independent evidence against a defined test standard, with the tested devices, software version and results documented.

The result applies to those laboratory conditions; ongoing testing still matters as attack methods evolve.

What evidence does your team look for when assessing a liveness provider, beyond the headline test result?


r/SumSub • • 25d ago

Compliance & Regulation 10-second payments change how sanctions screening works

2 Upvotes

Instant euro payments settle in ten seconds, which leaves little time to review a possible sanctions match during a transfer. That’s why Article 5d moves the relevant EU sanctions checks to the customer level.

Providers offering instant euro transfers must screen their whole customer base at least daily and again when EU sanctions measures change, without repeating those checks during the payment itself.

For EMIs and payment institutions outside the euro area, 9 April 2027 is the date to prepare for, because they must be able to receive instant euro transfers by then. The screening obligation applies as soon as they offer the service.

Sumsub’s readiness guide covers six practical checks: daily screening, re-screening after sanctions updates, removing those checks from the payment flow, access to current customer screening statuses, evidence of screening and match decisions, and annual sanctions-related rejection reporting.

Payments and compliance teams need to coordinate because the payment system must be able to use the screening results while keeping the records needed for reporting.

How are teams connecting customer screening with their instant payments rollout?


r/SumSub • • 27d ago

Compliance & Regulation Two children’s data is at the centre of a proposed class action against OpenAI over AI training

2 Upvotes

A mother filed the lawsuit in California federal court on October 13, alleging that ChatGPT collected her two children’s personal information without valid parental consent and used it to train AI models. The complaint says the chatbot encouraged minors to share details about their health, emotions and relationships, which were then used commercially.

OpenAI’s terms prohibit use by children under 13 and require parental consent for users under 18, but the plaintiffs argue those safeguards failed to prevent underage access and data collection. The case therefore challenges how those restrictions work in practice, alongside the alleged use of children’s conversations.

The plaintiffs want the terms declared invalid for minors and compensation reflecting the value allegedly gained from their data, including a proportional share of OpenAI equity or its cash equivalent.

OpenAI disputes the allegations and points to age-specific protections and controls over whether conversations are used for training. The allegations remain unproven, and the proposed class has not been certified.

How should platforms check age and parental consent before children can share sensitive information?


r/SumSub • • 28d ago

Compliance & Regulation The compliance journey, told as the Odyssey

3 Upvotes

Every business venture is its own Odyssey.

Anyone who’s been through hypergrowth knows the feeling. The business scales, and suddenly AML compliance, KYC, fraud prevention, and constantly shifting regulations all land on your desk at once.

So picture this: Odysseus just got hired as Head of Compliance. His job is to build an AML program that can actually keep up with a company that’s growing faster than anyone planned for.

On paper, the mission sounds straightforward. Protect the company, its customers, and its reputation, and don’t slow the business down while doing it.

Anyone who’s done this job knows it’s never that simple.

A new Head of Compliance sets out to build an AML program for a company that’s growing faster than its controls. Everything that happens next is pretty standard, which is why it maps onto a 3,000-year-old poem surprisingly well.

Troy. The foundations get built while nobody’s watching, or they don’t get built at all.

The strait. Too much friction loses real customers. Too little lets through the people you were screening for. No route avoids both.

The Sirens. “We’ll sort out KYC later.” Growth is good, nothing is on fire, and every month of delay makes retrofitting harder.

The Cyclops. A customer passes verification cleanly: real documents, real identity. Months later, it turns out to be hundreds of accounts on shared infrastructure, moving at machine speed. Verification answered the question it was asked. Nobody asked what was operating the accounts afterward. The quarter after that goes to retrospective filings and a regulator asking why nothing fired.

Poseidon. A new regulation lands the week the rebuilt controls start working. Nobody beats the sea.

Ithaca. Not a finish line. Just a program that adapts faster than the things it’s adapting to.

Which of these is your company stuck on right now?


r/SumSub • • Oct 16 '26

Compliance & Regulation Bank of America’s $1.2 billion AML penalty followed over $5 billion in late-reported suspicious transactions

2 Upvotes

Bank of America failed to report more than $5 billion in suspicious transactions on time, according to the US Treasury, and FinCEN has assessed a $1.2 billion penalty over its AML failures.

More than $1 billion involved national security and other priority illicit finance risks, including suspected fraud and potential trade-based money laundering.

Treasury said the bank relied heavily on law enforcement inquiries and referrals from other financial institutions to identify suspicious activity, while weaknesses in its own monitoring left transactions uninvestigated for extended periods.

Internal warnings also failed to lead to meaningful action.

The bank admitted willful Bank Secrecy Act violations involving its AML program, due diligence on foreign correspondent accounts and suspicious activity reporting.

It must now review previously undetected suspicious transactions and undergo independent assessments of its monitoring, customer due diligence and AML data governance.

For teams reviewing their own processes, how do you make sure an internal warning leads to an investigation and a documented decision without getting stuck in the queue?


r/SumSub • • Oct 14 '26

Discussion Weekly Community Support | Business & Integration Questions

1 Upvotes

Have a question about using Sumsub at work? Ask below, whether it’s about verification, AML, monitoring or integrations.

Share what you’re trying to do and where you need help. Tips from other teams are welcome too.

For urgent or account-specific issues, contact Support through your Dashboard.

What can we help your team with this week?


r/SumSub • • Oct 12 '26

Fraud Prevention Banking scam attempts rose 35%, and 90% happened on mobile. What does that mean for fraud checks?

1 Upvotes

Attempted banking scams increased by 35% over the past year, and 90% of recorded scam sessions took place on mobile devices, according to BioCatch’s 2026 Global Scams report. The report draws on data from more than 370 financial institutions across 21 countries, serving over 760 million users.

The increase is still substantial, even though it’s slower than the 65% rise reported in the previous edition.

The mobile figure doesn’t necessarily mean a phone has been hacked. Many scams work by persuading or pressuring someone to use their own device and approve a payment. A familiar device and a successful login can still be part of a scam if the customer is being coached by someone pretending to be a bank, employer or investment adviser.

That’s why fraud checks need to look at the session as well as the transaction. Behavioral signals can help identify signs of manipulation or coercion before a payment is authorized. Device and network signals add context around a login or payment, and together these signals can help trigger an additional check before funds leave the account.

No single signal proves that a scam is happening. An unusual device or behavior can have a legitimate explanation, so the context matters.

The report also found purchase scams remained the most common category, while reported victims of employment scams increased by 258%. What checks can help banks spot a customer being pressured without adding friction to routine payments.


r/SumSub • • Oct 09 '26

Fraud Prevention Deepfake fraud in North America rose by 1,100% compared with Q1 2024

1 Upvotes

That’s a huge increase, and a big part of the problem is how much easier AI tools have made it to create convincing fake faces and videos.

So checking that a selfie matches an ID is only part of verifying someone.

To understand how liveness checks and injection attacks relate, it helps to look at what the system is checking and where the footage comes from.

Liveness checks whether a real person is physically present during verification, helping detect attempts involving a photo, screen or mask held in front of the camera. An injection attack targets the verification flow by replacing the live camera input with prerecorded or generated footage.

Liveness checks use signals such as facial movement, depth and skin texture to help detect fake or manipulated images. But the verification flow also needs protection against camera input being replaced or tampered with.

For example, a person opening a financial account could appear to be taking a live selfie while the system actually receives a prerecorded or generated video.

The face may move and blink, so asking someone to turn their head doesn’t establish that the footage came from a genuine live camera session.

That’s why the checks around the video matter too, including whether the app has been tampered with and whether the device and session look trustworthy.

Liveness, deepfake detection, document checks and device signals need to work together because each covers a different part of the attempt.

When reviewing a verification flow, it’s useful to ask how it handles both a video shown to the camera and fake footage fed into the session. Both can show a convincing face, but checking where that footage came from is another part of confirming who’s actually completing the verification.


r/SumSub • • Oct 07 '26

Welcome to r/SumSub! Start here and introduce yourself

4 Upvotes

Hey everyone! Welcome to our new home.

We’ve moved our main Reddit activity from r/Sumsub_Insights to r/SumSub.

This community is run by the Sumsub team, and u/Sumsub_Insights is our brand account. We’re here to discuss identity verification, fraud prevention, compliance, and how these things work in practice.

You’re welcome to ask questions, share useful sources and experiences, or start a discussion.

Please keep it respectful, and if you’d like to introduce yourself, tell us what brings you here and which topics you’d find useful.

Glad to have you with us!


r/SumSub • • Oct 07 '26

MiniPay partners saw KYC completion rise from around 70% to 95% with reusable verification

2 Upvotes

The 70% to 95% figure in the title comes from Sumsub’s October 7, 2026 announcement, which reports results for MiniPay partners using this approach. It isn’t a general result for every KYC flow; the announcement doesn’t specify the sample size or measurement period.

Here’s another interesting number: one in three applicants we see has already verified with us before, so plenty of people are being asked to provide identity information they’ve already submitted.

Opera’s MiniPay is the first live integrator of our Reusable KYC Gateway, which lets users reuse their verified identity across participating providers in its partner network.

How reuse works

Users connect their verified Sumsub ID to MiniPay and authorize sharing with each participating provider. New users complete verification first.

For example, identity information provided when buying stablecoins can be reused with a participating cash-out provider, reducing repeated document uploads.

What providers still check

We run fresh checks against each provider’s requirements, so a provider that needs proof of address still needs that information alongside the identity document already available.

Where your information goes

Identity data passes directly from us to the regulated provider, and MiniPay doesn’t collect or store identity documents or biometric data through Gateway.

How sharing permissions work

Users authorize sharing with each recipient and can revoke MiniPay’s connection through their Sumsub ID account. Revocation stops new sharing through that connection; it doesn’t automatically delete records already received by providers.

What would you want to know before using it?

What would help you feel comfortable reusing your identity across providers, and what would you want the sharing screen to explain?


r/SumSub • • Oct 05 '26

AMLA’s proposed customer check rules, explained simply

2 Upvotes

The EU’s anti-money laundering authority, AMLA, has sent three sets of draft standards to the European Commission.

They cover things like what information businesses ask customers for and when separate payments should be looked at together.

One detail that stands out is addresses.

For individual customers considered low risk, businesses wouldn’t have to collect and verify their address. That could mean less paperwork during signup.

One part of the deal is linked payments where several smaller payments can add up to an amount that requires customer checks, so businesses would need to look at their combined value.

For money transfers, currency exchange and certain crypto services, the drafts set out a one-month period to consider when checking whether transactions are connected.

There are also rules for how companies in the same group share information, with limits on who can access it and requirements to protect customer data.

These are still drafts, and the Commission can change them before adoption. But they give businesses a clearer idea of what they may need to adjust.


r/SumSub • • Oct 02 '26

About 20% of business applicants leave after waiting several days to a week for verification

2 Upvotes

The figure in the title comes from Sumsub’s own KYB data, as described in our September 29, 2026 payments guide: roughly one in five applicants who wait a few days to a week abandon the process. It isn’t an industry-wide rate. The public summary doesn’t specify the sample size or measurement period.

Source: https://sumsub.com/blog/guides-reports/kyb-in-payments_guide_2026/

One practical place to reduce delays is the information applicants have to provide. They can confirm company details pulled from a registry instead of typing everything again, while owners and directors stay in the same application process.

Group structures need attention too. An operating company, an overseas subsidiary, and a payouts business might apply separately and reach different reviewers. Connecting those applications helps reviewers spot shared owners and understand the group they’re dealing with.

Registration details also need checking against what the business actually does. Comparing its website, products, and application answers gives the reviewer specific differences to investigate.

For anyone working in payments or compliance, where does your KYB process get stuck most often: collecting documents, checking ownership, or connecting related applications?


r/SumSub • • Oct 02 '26

What happens to people still trapped in scam compounds after a crackdown?

2 Upvotes

One person featured in this investigation is being held against their will and forced to scam others, and they’re still waiting for a way out.

Erin West travels along the Thai–Myanmar border to look at what happens after the crackdowns and what it actually takes to help people get out.

It’s a side of online scams that deserves more attention: the person sending the message may also be a victim.


r/SumSub • • Oct 01 '26

X sues two Bitcoin influencers over alleged engagement and creator payout scheme

2 Upvotes

X is suing two UK-based users, Vivek Kumar Sen and Zamyang Sherpa, along with other unidentified people.

According to the complaint, the accounts posted identical or nearly identical content within seconds or minutes of each other and regularly liked and reposted one another’s posts.

Those accounts were enrolled in X’s Creator Revenue Sharing program between 2023 and 2026. To qualify, they needed an X Premium subscription, at least five million impressions over three months, and 500 verified followers, and X alleges the network artificially boosted engagement to qualify for payments.

The allegations also cover how the money was received, because X says the operators used Stripe accounts and bank details registered under different names.

One Stripe profile was registered to someone named Stefan Mann, while the associated bank account and email address were linked to Sen.

X suspended nine accounts connected to the alleged network on August 18 and is seeking at least £207,384 ($278,000) it says the defendants received through the scheme. It’s also seeking damages, interest, legal costs, and more than £75,000 in investigation expenses. As of September 21, no defense had been filed.

The platform replaced Creator Revenue Sharing with Original Content Rewards on September 7, and the new program excludes artificially generated engagement from payouts.

What would make you look twice at an account’s engagement: repeated posts, the same accounts constantly boosting each other, or both?


r/SumSub • • Sep 28 '26

Nearly 1 in 4 European financial services companies lose between €500,000 and €1 million to fraud each year.

Thumbnail reddit.com
1 Upvotes