RiskPulseRequest Demo

Solution · Merchant Fraud

The merchant that looked fine at onboarding.

Transaction laundering, bust-out merchants, collusive refunds and chargeback abuse. The signal is almost never in one transaction. It is in the portfolio, over weeks, across merchants that are not supposed to be related.

Abstract composition of a merchant portfolio being tested
PortfolioBehaviourFinding

The work

What the file
actually takes.

A merchant case is a worked example of the problem: every individual transaction is defensible, the population is enormous, and the finding has to hold up against a merchant who will dispute it and a scheme that will move to the next acquirer.

01

Trigger

A monitoring rule, a chargeback threshold, an acquirer enquiry or a referral opens the file — and the scope is set.

02

Baseline

The merchant's own history and its peer set are established, so the deviation is measured against something rather than a fixed threshold.

03

Behaviour

Refund and chargeback patterns, volume shifts, ticket-size drift, and processing that does not match the stated business are tested.

04

Relationships

Ownership, settlement accounts, bank details and addresses are mapped across the portfolio to surface merchants that are not supposed to be linked.

05

Findings

The determination, the evidence behind each finding, and the actions your policy mandates — hold, terminate, refer or report.

Processing, merchant and chargeback data from the institution's own systems is tested, mapped and scored by RiskPulse, then presented to an investigator who adjudicates the fileYOUR SYSTEMSProcessing dataMerchant recordsChargeback dataOnboarding fileRISKPULSEBehaviour testedRefund and chargeback patterns, volume shifts, ticket-size driftOwnership mappedSettlement accounts, bank details and addresses across related merchantsScored on your policyMerchant, transaction, control, collusion and documentation riskINVESTIGATORAdjudicates the fileCase recordFindings, evidence,recommended actionNothing is held or terminated on the platform's authority — the file is adjudicated by a person.

Where the agents run

Plan. Examine. Report.

The same three agents run this case type as run every other. What differs is the policy behind them — the plan template, the dimensions scored, the tools available, and the report that comes out.

The link the portfolio was hiding.

One merchant rarely looks wrong enough to act on. Five merchants sharing a settlement account, a director and the same chargeback curve do. RiskPulse tests each merchant against its own history and its peers, then maps the relationships across the book — so what reaches an investigator is the cluster and the evidence for it, not the single merchant that happened to trip a threshold.

  • Peer and self baselines — deviation measured against the merchant's own history and comparable merchants, not a fixed threshold
  • Relationship mapping — ownership, settlement accounts, bank details and addresses linked across the portfolio
  • Stated business tested — what the merchant said it sells at onboarding against what it actually processes
  • Referral pack — findings ranked by severity with the mandated actions stated
RiskPulseSearch casesCASE-4471 · Merchant reviewPortfolio cluster · four linked merchantsTERMINATION PROPOSEDPending adjudicationFINDINGEVIDENCESTATUSRefund rate above peer set for nine weeksProcessing dataREVIEWSettlement account shared with three merchantsMerchant recordsOPENProcessing does not match stated businessOnboarding fileEVIDENCEDDirector common to the linked merchantsRegistry recordCONFIRMED
RiskPulse · Case record

Policy for this case type

Configured,
not hardcoded.

Nothing on this page is fixed in the product. Every element below is a policy setting you define, which is why the same platform runs this case type and the others.

Domain
Merchant and acquiring risk — with its own matter types, from transaction laundering to collusive refunds and bust-out activity.
Risk dimensions
Merchant, transaction, control, collusion and documentation risk — the weights, the composite bands and the override rules are yours.
Plan template
Matter type drives which behaviours are tested, the peer set used, and how far across the portfolio the relationship map reaches.
Report template
Your merchant review format, including the findings ranking and the actions your policy mandates.

How configuration works

Controls

Defensible
after the fact.

The same governance and quality controls apply to this case type as to every other — because an examiner does not lower the standard for the harder files.

Governance

Full reasoning chain

Every conclusion carries its reasoning and a citation to the source document, with agent actions and human overrides recorded in sequence.

Quality control

Sampling built in

A sampling methodology sits behind this case type, so your quality team can assess a representative sample rather than reviewing at random.

Quality assurance

Independent assessment

A separate set of agents assesses case quality end to end against your methodology — a second opinion on the work.

See it on your own file

Bring a real case.
We’ll show you the workflow.

Pick a real file or a closed case and see how RiskPulse plans it, evidences it, and writes it up under your policy.

Request Demo