SEON: fraud decisions, identity verification and AML operations

SEON supplies a connected fraud and compliance platform for digital customer journeys. For a brokerage, the relevant control points are account opening, repeated logins, funding and withdrawals: the same customer or device can be assessed as activity changes. Its financial-services offering combines early risk signals with formal identity checks and ongoing monitoring, so a suspicious registration can be investigated before the firm completes a more costly verification flow.[1]

The Scoring Engine returns APPROVE, REVIEW or DECLINE using rules, lists and risk signals. Default rules can be switched on or off; custom rules can change scores, decisions and list membership. AI Insights produces a separate 0–100 probability score that can be incorporated into rules. These distinctions matter operationally: changing a threshold, setting a list exception and accepting a machine-learning suggestion are different changes to the decision process.[7]

Integration combines server requests with client-side collection where needed. JavaScript, iOS and Android components gather device/session signals; the server sends the appropriate data for analysis. Requests use X-API-KEY. The documented default rate is two requests per second for trial accounts and 20 after trial, measured per licence key; higher requirements go through support. Client timeout settings should allow 500–1,000 milliseconds beyond the configured SEON timeout.[3]

A webhook endpoint must answer the validation ping with HTTP 200. SEON permits ten endpoints and retains delivery-attempt logs for 30 days. The published retry delays double from one minute through 256 minutes. These records let an operations team distinguish an underlying risk event from repeated delivery attempts.[10]

The price page prints a dollar sign without a currency code. SEON’s billing FAQ says invoice currency follows the billing agreement, and requests to change EUR/USD billing should reach its finance team before the next invoice.[16]

Separately signed agreements prevail. Default fees are prepaid, tax-exclusive, due 30 days from invoice; late interest is 1.5% monthly or the lower legal maximum. Fixed terms renew equally with 5% uplift unless 60 days’ notice is given. Indefinite online orders allow immediate cancellation and require 30 days’ price-change notice.[17]

Workflows let the implementation team separate journeys by customer segment, jurisdiction or event. A route can start with low-friction checks, request documents only when a condition warrants it, and retain the results of each step for investigation. Analysts inspect the full run rather than only its final state. Configuration still determines which information the backend must supply and which checks the user actually completes.[8]

The sandbox has its own database, rules and settings. Its transactions and labels do not alter production. That separation supports integration work and rule tuning before a live change, while its shared consumption allowance remains relevant to the commercial plan.[18]

Managed Risk Services adds a senior fraud consultant, daily alert review and rule adjustments, weekly trend analysis and monthly performance reporting. It is an ongoing operational service alongside technical support, with training and tailored risk settings. Its scope is especially relevant where a broker wants help maintaining rules after the initial integration.[22]

Standard-term response goals: one hour/S1, same business day/S2 and next business day/S3. Measured from complete incident information, within Monday 02:00–Friday 22:00 UTC, excluding holidays. Monthly uptime is 99.5% web/99.9% API, excluding scheduled maintenance; credit requests are due within 30 days of the event.[17]

The Premium page separately advertises 24/7 support access; the response clocks above describe the standard contractual schedule.[12]

AML search results identify potential matches, not a conclusive identity or eligibility determination. SEON’s AML notice assigns interpretation and final verification to the customer and prohibits solely automated significant decisions based on those results. SEON acts as controller when building its public-source AML database; that role differs from processing customer verification data on instructions.[24]

The linked IDV notice and later DPA publish different defaults; confirm the configured period.[17][26]

The October 2026 Device Intelligence notice lists Ireland as the default storage region, with Northern Virginia, Singapore and Jakarta options. It separately allows processing elsewhere by group companies and providers, so storage selection does not mean that every processing activity stays in that location.[25]

SEON’s current-linked security whitepaper describes AES-256 at rest, TLS 1.2 or higher in transit and logically separated customer data in shared infrastructure. It describes an independently provisioned AWS account as a negotiated option, plus multifactor access and quarterly access reviews. ISO 27001 and SOC 2 Type2 are vendor-disclosed assurance credentials; the whitepaper is not the underlying audit report.[27]

SEON Technologies dates its founding to 2017. Its current leadership page names Tamás Kádár as chief executive and Bence Jendruszák as chief operating officer, and places the identity-verification launch in January 2026. The company lists offices across Austin, London, Budapest and Asia-Pacific, reflecting a customer base wider than financial services alone.[28]

The group includes SEON Technologies Kft. in Hungary and SEON Technologies US Inc. in Delaware.[25]

The September 2025 financing announcement reported USD 80 million of Series C funding led by Sixth Street Growth, with IVP, Creandum, Firebolt and Hearst among participating investors. Complytron is an acquired AML business incorporated into SEON’s screening offering; it should be treated as part of this provider’s history rather than a separate current platform purchase.[29][30]

Operator

SEON Technologies Kft.; contracting entity depends on the order

Service scope

Fraud signals and decisions, identity verification, AML screening, transaction monitoring and case operations.

Customer types

Financial institutions; Fintech and payment businesses; Digital platforms

Delivery

SaaS; API; Managed service

Pricing publication

Public and quoted pricing

Platforms

Fraud API; Workflows; Identity Verification; AML Compliance; Case Management; SEON MCP

Pricing scope

Public Starter price; Premium is quoted. API, monitoring and sandbox consumption have distinct billing rules.

Implementation

Backend APIs, device SDKs and visual verification workflows.

Support

Plan-dependent technical support, documentation and optional specialist fraud services.

Permissions and regulatory scope

Risk and identity software. The customer assesses AML matches and remains responsible for consequential decisions.

Provider metadata checked 21 Oct 2026Source 28Source 17Source 1Source 22Source 12Source 9Source 24Source 30Source 8

The AI disclaimer distinguishes customer-specific models trained within that customer’s account from cross-customer models built with sanitized, aggregated or anonymized information that identifies neither customers nor individuals. It says customer data is not used to train third-party AI models. Customers remain responsible for the oversight and configuration of their decision processes.[34]

Erase API v2 requires product domains plus at least one identifier filter or date range. The published domains cover fraud, AML screening and AML case management. Optional start/end dates must be supplied together, cannot be future dates and may span no more than seven days. With dates but no identifier filters, all transactions in the interval are selected. Processing is asynchronous, with a request ID for status checks and logged outcomes; there is no dry run. Erasing a transaction also removes its underlying session record, so other transactions sharing that session lose their device/session data, including in exports.[35]

After termination, export remains available for at least 30 days. Deletion or anonymization follows within 30 days after that window, subject to return instructions and legal retention.[17]