Recommended Free Tools
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Bureau announced a $30 million Series B on December 18, 2024, led by Sorenson Capital, with PayPal Ventures and five other investors participating. The company says it will use the funding to expand its products, research and development, and international reach. Despite the headline focus on deepfakes and payment fraud, Bureau is not just a deepfake detector: it sells a broader platform for identity checks and fraud-risk decisions across customer onboarding and later transactions.
What happened in Bureau’s $30 million funding round?
Bureau said Sorenson Capital led its Series B. Participants were PayPal Ventures, Commerce Ventures, GMO Venture Partners, Village Global, Quona Capital, and XYZ Ventures. The company’s announcement and contemporaneous coverage date the news to December 18, 2024. SecurityWeek’s report lists the investors and says the company planned to direct the money toward product development and expansion; Bureau’s funding announcement describes investment in product, research and development, and international growth.
SecurityWeek reported that Bureau had raised more than $50 million since its 2020 launch. For context, TechCrunch reported in July 2023 that the company had reached $20.5 million in total funding after expanding its Series A to $16.5 million. That earlier coverage also noted Bureau’s acquisition of identity-verification startup inVOID and a strategic partnership with GMO Payment Gateway. These totals are reported figures, not independently audited funding accounts. TechCrunch’s 2023 report provides the earlier financing context.
The round’s date can be confusing: Bureau’s current funding page displays June 1, 2025, while SecurityWeek and the syndicated announcement date the financing to December 18, 2024. The contemporaneous date is the appropriate date for the announcement. The syndicated release is dated December 18, 2024.
#1 Best Overall
- Ideal for government, military, healthcare or banking. Portable design with power and scan LED indicators
- Fast 825kbps read speed with multi-protocol support** ISO7816 implementation-Class A, B and C (5V, 3V, 1. 8V) card
- EMV2000 Level 1 approved and supports 3V & 5V cardsCAC compatible for use with CAC card software
- Supports PIV cardsTAA compliant
- CAC Middleware is not included** Software driver may be needed to achieve maximum speed. Actual speed may be dependent on system environments
The public materials cited here do not state the round’s valuation, whether it included secondary sales or debt, Bureau’s revenue, customer count, or the share of revenue from each product line.
Bureau is a risk-decisioning platform, not only a deepfake detector
Bureau’s core proposition is to bring identity verification, device and behavioral intelligence, compliance checks, and transaction-risk signals into a common decisioning layer. A customer can use such a platform to assess risk at onboarding and, depending on its configuration, during later account activity or payments. That is different from buying a tool whose sole job is to classify an image or video as authentic or manipulated.
Bureau describes use cases that include identity and business verification, liveness checks, document-fraud detection, account-takeover prevention, fraud-ring and money-mule detection, KYC and AML screening, sanctions and watchlist checks, transaction monitoring, and credit-risk decisioning. Its website presents the broader product scope, while its onboarding page covers identity checks and deepfake-related claims.
Four different checks that are easy to conflate
- Liveness: asks whether a live person is present during a verification interaction.
- Deepfake detection: looks for signs that visual, audio, or identity material has been manipulated or synthetically generated.
- Identity verification: checks whether a person’s claimed identity matches documents, databases, or other evidence.
- Risk decisioning: combines these and other signals—such as device, behavior, network links, and transaction context—to inform what a business should do.
Passing one check does not settle the others. A live person can use stolen or synthetic identity information; a document may appear genuine while the device or account history is suspicious. Conversely, a legitimate customer can look unusual because of a shared device, a VPN, travel, poor lighting, or an older phone. Liveness by itself is not a complete defense against identity or payment fraud.
How deepfakes connect to payment fraud
Manipulated video, audio, documents, and identity evidence can help a fraudster impersonate another person or make a fraudulent application look credible. If an account is opened or recovered using deceptive evidence, the attacker may then seek to take it over, link payment instruments, recruit or exploit a mule, or make unauthorized transactions. Deepfakes are therefore one possible entry point in a wider fraud chain, not a synonym for every kind of payment fraud.
Some scams do not involve a fake identity or manipulated media at all. In an authorized payment scam, a real customer may be persuaded to approve a transfer. Deepfake screening at onboarding cannot alone prevent that outcome; transaction context, beneficiary history, behavior, and timely intervention also matter.
The U.S. Government Accountability Office has warned that deepfakes can exploit people’s tendency to believe what they see, while noting that complete estimates of fraudulently induced payment scams are unavailable. The GAO report provides that context. Separately, the FBI’s 2025 Internet Crime Report recorded 22,364 complaints involving AI-related fraud or scams and reported losses of $893,346,472. Those are reported complaints and losses, not a measure of all fraud worldwide or of Bureau’s addressable market. The report describes AI-assisted investment scams and voice spoofing or possible voice deepfakes in employment scams. The FBI report details the figures and examples.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What Bureau says its technology combines
Signals across devices, behavior, and networks
Bureau says it analyzes device fingerprints, user behavior, network relationships, and transaction information to identify patterns associated with spoofed or emulated devices, bots, repeated account creation, account takeover, fraud rings, mule accounts, and promotion abuse. The rationale is that a single document check may miss links between an applicant and other suspicious accounts, devices, or payment activity.
Rank #3
An identity knowledge graph
At the time of its Series B announcement, Bureau said its proprietary identity knowledge graph contained more than half a billion identities and behavioral patterns. The company describes the graph as connecting identity, device, behavioral, financial, and partner data to generate risk intelligence. Its current homepage separately advertises more than one billion verified identities. Those are company-reported figures published in different places, and the materials do not establish that they use the same definition or measurement date; they should not be read as a directly comparable growth series.
Decisions and workflow integration
The distinction between detection and decisioning matters to a buyer. A vendor can return signals or a risk assessment, while a bank, merchant, or payment provider sets thresholds and decides whether to approve, reject, challenge, or review an activity. The public descriptions do not establish that Bureau itself executes or blocks every payment. Buyers should confirm which actions the service can take, how it connects to existing fraud and compliance systems, what evidence it returns to investigators, and how quickly a decision is delivered.
Privacy claims need operational detail
Bureau says it shares decisions rather than raw consumer data and uses tokenized identities in its privacy architecture. Tokenization is a design claim, not a complete account of data protection. A prospective customer still needs to understand what information Bureau receives, how long it is retained, whether it is used to train models, how deletion and access requests work, how cross-customer signals are separated, and which cross-border transfer rules apply. Explainability and consumer recourse also matter when a risk score affects access to a financial product.
What the public performance claims do—and do not—show
Bureau’s onboarding page advertises a 70% reduction in manual reviews, an 80% drop in account-takeover cases, 10–25% higher catch rates, and an eightfold reduction in session hijacks. It also claims coverage across more than 195 countries and more than 2,000 document types, as well as onboarding in under 10 seconds. These are Bureau’s marketing claims, not independently established results in the public materials cited here. The page does not provide a detailed methodology, customer-level baselines, sample sizes, time periods, or definitions for the performance figures. Bureau’s onboarding page contains the claims.
The sources reviewed do not provide independent benchmark results, published false-positive and false-negative rates, or a controlled comparison with competing systems. They also do not detail performance by attack type, country, document, skin tone, lighting, device, or network quality. Without those details, a buyer cannot infer how a marketing percentage would translate to its own customer population or fraud mix.
The same caution applies to the $486 billion annual global fraud-loss figure cited in Bureau’s funding announcement. It is a company-cited market statistic, not a Bureau-specific loss measurement; the announcement alone does not establish a common methodology for treating it as a definitive worldwide total.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why investors may see an opportunity—and what funding cannot prove
Fraud teams often manage separate systems for onboarding, identity checks, device signals, AML screening, and payment monitoring. A platform that joins signals across a customer’s lifecycle may reduce integration work and make it easier to spot activity that looks innocuous in isolation but suspicious in combination. That is the strategic case behind Bureau’s broader platform pitch.
Free tools Windows power users keep installed
One-click scans. No signup required.
Consolidation has trade-offs. A single vendor can become a point of operational dependence, make migration harder, and reduce the flexibility to choose a specialist for each task. It can also make it more difficult to isolate which signal or model drove an outcome. Financing from Sorenson Capital, PayPal Ventures, and the other participants indicates investor backing for the company; it is not independent evidence that the product outperforms alternatives or reduces customer losses.
International expansion adds further complexity. Bureau says it supports onboarding in more than 195 countries, but document formats, data availability, fraud patterns, privacy rules, and acceptable verification practices vary by jurisdiction. Broad coverage claims do not by themselves show that accuracy or fairness is consistent in every market.
How a financial business should evaluate Bureau
A demo should lead to evidence and a controlled deployment plan, not just a feature walkthrough. Ask the vendor and internal stakeholders to define what a successful result means for the specific use case.
- Detection quality: Request false-positive and false-negative rates by attack class, plus test results for deepfakes, synthetic identities, document fraud, and liveness under poor lighting or limited bandwidth.
- Coverage: Establish whether the deployment covers onboarding only or also authentication, account recovery, payment authorization, ongoing monitoring, AML screening, and the channels the business uses.
- Integration: Confirm API and SDK availability, web and mobile support, decision latency, webhooks, case-management connections, sandbox quality, and the ability to tune rules by geography or product.
- Operations and auditability: Check for reason codes, audit logs, manual-review workflows, threshold controls, investigator evidence, and a way to override or appeal decisions.
- Privacy and governance: Ask about data minimization, retention, subprocessors, cross-border transfers, customer consent responsibilities, access and deletion requests, security audits, and model governance.
- Commercial fit: Clarify minimum commitments, whether pricing is per verification, decision, account, or transaction, implementation and support costs, and whether individual modules can be purchased. Bureau does not publish pricing in the reviewed materials; its onboarding page directs prospective buyers to request a demo.
For any claimed improvement, ask for the attack classes included, the definition of “catch rate” or “account-takeover case,” the evaluation period and baseline, the population tested, and whether results were prospective or retrospective. A pilot should measure fraud outcomes alongside customer abandonment, manual-review workload, and the rate at which legitimate customers are incorrectly challenged.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
