By Equifax

Equifax Payments Fraud on Kount 360

Device and transaction evidence, payment-risk scoring and configurable business policies for card-not-present interactions.

The offering

What Equifax Payments Fraud on Kount 360 does

Payments Fraud on Kount 360 evaluates payment interactions using device and network evidence such as device ID, IP address and location. It returns a risk score and applies the business’s configured accept, block or challenge policy. Equifax’s gambling-operator sheet names payment fraud, Omniscore, device collection, Orders API and customisable policies for deposit and withdrawal risk.

Define which transaction stages are assessed and where the response is enforced. Link the evidence to player and payment records, review exception cases and test rule changes against representative traffic. Agree the signals, optional models and analyst access in the package. Fraud assessment and policy handling do not themselves authorise a card transaction, move funds or settle a player withdrawal.

Who should explore it?

Operator payment-risk teams using device and transaction evidence for controlled fraud decisions.

  • Assess a card-not-present deposit before the configured payment step
  • Review transaction risk evidence and adjust a fraud policy

Documented capabilities

  • Device/IP/location risk inputs
  • Payment-risk score
  • Customisable accept/block/challenge policies
  • Dashboard, analytics and shared API schema

Reported in the linked public sources. We have not independently tested these capabilities.

Product details

Fraud role
Assess card-not-present payment interactions and apply the business’s configured policy.Source
Risk inputs
Device ID, IP address, location and transaction interaction evidence; gambling material also names device collection and Orders API.Source
Policy output
Risk score with configured accept, block or challenge response; payment authorisation and funds movement remain separately controlled.Source
Platform interfaces
Kount 360 shared API schema, policy engine, dashboard and analytics; scope the contracted Payments Fraud functions.Source
Gambling scope
Official gambling-operator material names Payments Fraud, Omniscore and policies for deposits/withdrawals; agree the actual assessed transaction flows.Source

Delivery & commercial details

Delivery & integration
Kount 360 shared API/platform environment; gambling material describes device collection and Orders API. Map risk results and policy responses to the operator’s payment workflow.Source
Pricing
Request a quote for evaluated events, signals/models, platform access, implementation and support. No numerical price was established in the reviewed product material.

Confirm market availability, rights, service levels and contractual terms for your implementation. API availability alone does not establish a named integration.

Buyer questions, answered

Is Payments Fraud a payment processor?

Its documented job is risk assessment and policy response for payment interactions. The payment provider and operator still control authorisation, funds movement and settlement.

Source
Who chooses whether to accept or challenge an interaction?

The product page states that business policies determine accept, block or challenge after the risk score is generated. Agree policy configuration, enforcement and analyst exceptions.

Source