A fraud decision is part of a payment service
Feedzai describes a platform spanning fraud, scams, identity and financial-crime operations, with banks, fintechs, payment providers and acquirers among its intended users. Its public materials describe models, rules and case workflows rather than a single interchangeable fraud score. These are vendor product descriptions, not independent evidence that every implementation reduces losses or improves acceptance. [1]
The business objective depends on the workflow. An issuer may need to distinguish a genuine purchase from account misuse; an acquirer may need to manage merchant exposure; an investigation team may need better context after a suspicious event. A faster or more accurate score creates value only when the surrounding service reaches an appropriate outcome.
Wio Bank gives the product names an operating context
Feedzai’s undated Wio Bank case, reviewed September 29, 2026, names Digital Trust and Transaction Fraud for Banking as the solutions used by the Abu Dhabi-based bank. It includes commentary from Wio’s Head of Fraud Risk, Jo Jeyaseelan. The inspected page establishes a vendor-hosted customer account but supplies no comparable fraud-loss or series. It should not be turned into a quantified return-on-investment claim. [5]
Analysis: combining information about a digital session with a payment event may help a bank decide when to intervene. The operating result depends on what follows the score: a hold, additional authentication, an investigation or a customer conversation. For an authorized scam, a customer’s confirmation may still be consistent with deception; the intervention needs to match the threat.
Jack Henry is a distribution route, not another bank customer
Jack Henry’s own product-context page identifies its collaboration with Feedzai behind Financial Crimes Defender. Separately, Jack Henry’s February 23, 2026 release says SELCO Community Credit Union is using Defender to bring fraud and BSA/AML work into a shared environment. Together these sources document a route through a banking-technology provider to an institution. They do not establish a direct SELCO–Feedzai contract or that SELCO uses every standalone Feedzai module. [6][7]
In that release, Stephanie Ziegler, SELCO’s Director of Financial Investigations, says Defender provides “a clearer view of our fraud and compliance universe.” This is attributed customer commentary about operating visibility; the release does not provide an independently controlled measurement of losses prevented. [7]
Buying through a platform changes the diligence map
Analysis: a bank evaluating an embedded service needs to know which party supports the interface, supplies model updates, investigates incidents and maintains the audit record. A technology-provider relationship can simplify integration while creating an additional dependency. The bank should understand the route by which an error in an upstream signal becomes visible and correctable in its case system.
Scroll horizontally to see all columns.
| Question | Evidence to obtain | Interpretation |
|---|---|---|
| What was deployed? | Named modules, covered payment rails, live date and traffic share | A platform selection is not proof of every feature being active. |
| What improved? | Comparable fraud dollars, , investigation hours and mature outcomes | Visibility and efficiency gains do not automatically equal loss prevention. |
| Who can change a decision? | Version records, approval authority, rollback and exception logs | A model update and a bank policy change have different owners. |
| What survives an outage? | Fallback behavior, delayed-event replay and reconciliation results | A fast normal path does not establish resilience. |
Actual ML versus marketing
Machine learning can rank risk, detect nonlinear interactions and adapt models more efficiently than static rules. It cannot independently determine legal liability, customer intent or the proper friction threshold. Feedzai public case studies report outcomes such as a 37% improvement in detection for one customer and alert-backlog reduction for another; these are vendor-selected claims. They do not disclose enough common baseline, loss maturation, cost or independent replication to generalize.
Evidence gates
Scroll horizontally to see all columns.
| Gate | Minimum evidence | Why it matters |
|---|---|---|
| Baseline | Current model, fraud rate, approval and review policy | A lift percentage needs a denominator |
| Labels | Fraud, scam, first-party, dispute and recovery definitions | Different labels imply different controls |
| Performance | Recall, precision, , dollars saved and friction | AUC alone does not establish operating value |
| Maturity | Observation window and aged losses by cohort | Early results can miss delayed |
| Governance | Reason codes, versions, overrides, fairness and monitoring | Challenge, audit and controlled change |
| Resilience | Latency, capacity, fallbacks, replay and incident response | Real-time rails leave little recovery time |
| Economics | License, integration, review cost and prevented loss | Adoption does not establish positive ROI |
Measure completed legitimate activity
Analysis: evaluate detection alongside legitimate payment completion, step-up success, retries and repeat customer contacts. A declined payment that succeeds on the second attempt may count as both a decline and an eventual sale. Report at the appropriate customer or purchase level as well as the individual transaction level to avoid inflating either failure or recovery.
A low rate can still create substantial friction at high payment volumes. Conversely, fewer alerts may simply shift unresolved exposure to a later dispute queue. Segment by rail, channel and customer tenure, and compare outcomes at a stated intervention level. These are proposed evaluation measures, not Feedzai performance claims.
The economic result extends beyond fraud dollars
Illustrative analysis: preventing an additional $100,000 of net fraud loss while adding $30,000 of review expense and $20,000 of measurable lost contribution produces $50,000 before licensing, integration and other costs. Use net losses after recoveries consistently; do not count the same prevention benefit in both fraud and savings.
Implementation also needs reliable events, labels and response behavior during outages. The named Wio Bank and Jack Henry examples in this profile help show distribution and operating context, but neither a customer reference nor a partner announcement supplies a transferable return estimate for another provider.
What would demonstrate useful performance
The strongest evidence combines incremental fraud reduction, reliable transaction service and lower total resolution effort in the actual deployment. Preserve the difference between vendor-reported customer cases, controlled comparisons and observed production results.
For payments and financial-service readers, Feedzai’s relevance is the connection between detection and execution. The deciding question is whether legitimate activity becomes safer and easier after the full cost of intervention.
Sources
- Feedzai RiskOpsSourceBack to text: ↑
- Vendor case study: detection improvementSource
- Vendor case study: modernizationSource
- Feedzai ML overviewSource
- Feedzai: Wio Bank customer story; undated page reviewed September 29, 2026SourceBack to text: ↑
- Jack Henry: Feedzai collaboration behind Financial Crimes Defender; undated page reviewed September 29, 2026SourceBack to text: ↑
- Jack Henry: SELCO Community Credit Union deployment; February 23, 2026; vendor/customer announcementSourceBack to text: ↑1↑2↑3