Anti-fraud rules and KYC

2.1

The score and its reasons

Screening looks at signals and nothing else:

• the amount against the merchant’s usual;
• the payer’s country against the card’s, and blocked countries;
• the number and the sum of attempts in a day;
• a payer seen for the first time, the hour, the kind of business and the instrument;
• the threshold for mandatory reporting.

It records a score with its reasons; a rule of the unit may then block the payment, hold it for a person or route it elsewhere. The facts of screening carry no payer’s name or address: in the demo a payer is a pseudonymous handle.

2.2

A person decides on a held payment

A held payment is released or blocked by a compliance officer; the decision is a fact with the role, the reason and the time, recorded where the automatic verdicts are. Nothing in the engine decides for the reviewer, and nothing that touches money or a person’s standing is left to an agent.

2.3

Alerts across payments

One payment is screened; a pattern is watched. Amounts at a reporting threshold, several payments just below it, bursts, geography, funds that do not match an invoice, a match on a sanctions list — each opens an alert with its evidence, assigned to a person and moved through investigation, escalation and report, with every note kept.

2.4

Onboarding a merchant

A provider that holds its merchants’ money takes each one on through a case: documents, a check of the company and its beneficial owners, a sanctions check, an assessment of risk, and a decision by a person — approved, sent back for more, or rejected.