Feedzai: fraud decisioning, digital trust, AML and data orchestration

Digital Trust can enrich an existing risk engine or operate with Feedzai’s engine. Its current product page describes monitoring from initial interaction through logout and the ability to terminate high-risk sessions. That makes the monitored session and permitted response part of the design, alongside the later payment decision.[3]

Orchestration accepts upstream APIs, bulk files and streams. Teams can transform inputs using a SQL- and Python-ready canvas, expose the workflow through a REST endpoint, or deliver bulk results through Snowflake table shares and AWS S3. The product includes logging, monitoring and alerts. Its configuration gateway supports version-control integration and access controls, so data-source changes can be managed as part of the application’s release process.[5]

Digital Trust’s Marketplace documentation specifies JavaScript for web banking and an SDK for mobile apps. It describes API connections to external transaction-monitoring, SIEM and fraud-management systems.[8]

The 12 February 2026 Neterium partnership added transaction-screening capabilities to Feedzai Watchlist Screening. The announcement describes Neterium’s screening infrastructure embedded in the Feedzai offering, with API integration, list updates, matching explanations and links to its transaction-fraud and AML applications. Neterium is the screening technology partner in this arrangement; the purchased solution should identify which customer and transaction checks are included.[7]

Transaction Fraud also describes ingestion from databases, transaction systems and third-party tools, use of custom rules or external scoring, and import/export of machine-learning models. This gives a team several integration choices: supply additional data to a Feedzai decision, consume its score in an existing engine, or connect model development to the operational workflow.[2]

Feedzai’s direct purchasing page requests a quote across account opening, takeover prevention, AML, KYC, transaction fraud and screening. The scope therefore needs to identify the products and customer journeys being purchased.[10]

The Feedzai SA Digital Trust listing on AWS Marketplace publishes these U.S.-dollar prices for a 36-month contract. Each tier includes implementation for web and mobile channels.[8]

These are the named listing’s contract prices, not annual charges. Its public table does not define the overage unit’s measurement period. Additional infrastructure costs may apply, and entitlements expire at the contract end unless renewed or replaced.[8]

The separate Feedzai Spain IQ Score listing requests a private offer. It advertises a 60-day evaluation, extended to 90 days when the customer shares fraud labels. That is a published evaluation route for IQ Score, not a general trial entitlement for the RiskOps suite. The commercial order should specify the evaluation’s data and conversion terms.[9]

RiskOps exposes customer profiling, no-code multivariable rules, self-service model deployment, backtesting and challenger testing. A practical rollout can use these controls to compare a proposed strategy with the current one before making it responsible for live decisions. The team must define the decision owner, investigation queue and route from a risk result to the permitted action.[1]

AML implementation has a different feedback cycle from immediate payment blocking. Feedzai describes an alert-prioritisation model that learns from prior alert labels, case investigations and SARs. Rules produce candidate alerts and the model orders them for review. The implementation therefore needs consistent outcome labels and a way to feed completed investigations back into the strategy, as well as customer/account data and selected scenarios.[4]

For IQ Score, the 9 June 2026 release describes pretrained models without a requirement for the joining bank to supply years of historical data. It says a faster-payments use case can start with as few as 15 fields. That is a stated starting point for that use case; the integration still has to map the required fields and decide how its score affects an institution’s existing payment workflow.[6]

The support portal’s June 2026 instructions provide company SSO or corporate-email registration. A user who has already emailed support can complete access through password recovery. Ticket visibility depends on the organisation’s access settings. The request page asks for a reproducible description and relevant logs or screenshots; it directs customers with critical degradation or disruption to the incident hotline in their support arrangements.[12][13]

The Marketplace-linked v.2025 EULA specifies English-language support around the clock. Urgent and high-priority incidents require telephone reporting. Its cloud SLA leaves availability and scoring-response commitments to the order; it applies to production in Feedzai’s cloud. Target resolution times are described as estimates.[11]

The current privacy policy, effective 18 September 2026, distinguishes Feedzai’s roles by product. It describes the company as controller for its own activities, product administration involving customer employees, and end-user processing for the data consortium. For other services supplied to business customers, it describes Feedzai as processor acting under customer instructions and agreements. The applicable role therefore needs to be tied to the particular service and data flow.[14]

The Marketplace-linked EULA retains the customer’s ownership of End-User Data. Clause 3.2 nevertheless permits service-related processing, including use in services for other customers without identifying the End-User as the data source. That wording concerns the source institution; it should not be paraphrased as a blanket promise that personal data is never processed. Personal data is subject to the attached processing agreement. The EULA makes End-User Data available for download during the agreement and for 30 days after it ends. Service rights end on termination apart from that export right; the attached DPA calls for export, or an export request, before expiry.[11]

Feedzai’s AML product supplies reporting software, including a SAR Manager that maps a common template into country-specific formats. Its stated functions include generating and electronically filing SARs, STRs and related reports. Selecting the applicable reporting workflow and configuring the institution’s review and filing process are part of implementation.[4]

The group’s May 2026 statement identifies its parent as the Portuguese Feedzai – Consultadoria e Inovação Tecnológica, S.A. The formal entity list includes Feedzai, Inc., regional companies in Australia, Hong Kong, Spain, Singapore, the United Kingdom and Malta, and DemystData entities. These are group companies; the seller and contracting entity should be taken from the relevant offer.[15][14]

The acquired product family includes Revelock, whose acquisition Feedzai announced on 4 August 2021, bringing behavioural biometric technology into its offering. On 22 April 2025, Feedzai announced that it had acquired Demyst, including the Zonic orchestration platform and related integration technology.[16][17]

Operator

Feedzai – Consultadoria e Inovação Tecnológica, S.A.

Service scope

Financial-crime software spanning transaction fraud, digital-session monitoring, AML investigations, screening, network risk scoring and onboarding data orchestration.

Customer types

Banks; Fintech companies; Payment service providers; Merchant acquirers; Payment networks

Delivery

SaaS; API; On premises

Pricing publication

Public and quoted pricing

Platforms

RiskOps Platform; RiskOps Studio; Transaction Fraud; Digital Trust; AML Transaction Monitoring; Feedzai Orchestration; Feedzai IQ Score; Farol

Integrations

REST APIs; SQL and Python workflows; Snowflake data shares; AWS S3; Web JavaScript and mobile SDK; Neterium screening integration; AWS Marketplace

Pricing scope

Direct purchasing and IQ Score use quotes. The cited Feedzai SA AWS Digital Trust listing publishes 36-month active-user tiers with listed overages and web/mobile implementation.

Implementation

Map customer, session and payment data; configure decision and investigation workflows, test strategy changes and establish feedback from investigation outcomes. Integration scope differs by product.

Support

Customer portal, support email and incident hotline; published EULA provides English-language support around the clock, with cloud service commitments specified by the order.

Permissions and regulatory scope

Fraud, AML and regulatory-reporting software. Data-processing roles differ by product: the current notice distinguishes the data-consortium controller role from processor services delivered under customer agreements.

Provider metadata checked 20 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 9Source 7Source 8Source 10Source 11Source 12Source 13Source 14Source 15Source 16Source 17Source 19

Novobanco supplies a dated example of phased expansion. Feedzai’s 6 March 2026 release says the first 2023 project used Digital Trust and Transaction Fraud for online and mobile banking. A 2025 agreement extended transaction-fraud coverage and brought in its AML suite. The release identifies Neterium-powered screening as an introduced capability and reports improvements in alert quality and investigation work. It separately places event-based customer reviews and additional fraud and Digital Trust modules in the next phases. This distinguishes the implemented stages from the continuing transformation programme.[18]

Farol, launched on 24 September 2026, adds an agent within RiskOps Studio. Feedzai describes rule-performance analysis, investigation summaries, product questions and SAR drafting as its initial skills, with information kept in the institution’s environment. The release quotes SEB’s fraud-prevention business owner describing data retrieval, insight generation and rule suggestions through one interface. This is an attributed customer account of the workflow; the release does not supply a full implementation duration or contract scope for SEB.[19]