Skip to content
Fraud and risk

Decisioning inside the payment path

Fraud controls arrive on a platform already clearing, where customers notice every false decline. We add decisioning to live inbound and outbound rails.

Shadow first

A new engine scores before it decides

Both directions

Inbound and outbound rails

Auditable

Every decision kept with its reasons

What we build

Capabilities in fraud and risk decisioning

Fraud and risk decisioning

Sardine and Featurespace wired into inbound and outbound rails, with ThreatMetrix device signals as an input and a decision returned inside the payment's own window.

Onboarding, KYC and KYB

Identity verification with GBG IDscan, Jumio or Onfido, and KYC and KYB screening with ComplyAdvantage or greenID, run as one onboarding flow with every outcome recorded against the customer it concerns.

Limits and controls

Limits, velocity rules and card controls held in one place and applied the same way on every rail.

Rollout without a maintenance window

Shadow scoring first, then a staged switchover, so a new engine is proven on live traffic before it can decline anyone.

Fraud engines
Sardine, integrated twice

At Shaype, between 2018 and 2023, Sardine replaced Featurespace for transaction monitoring and fraud decisioning; the team our managing director led as its Head of Engineering ran the cutover. At an APRA regulated bank it is going in now, as a Sofitect engagement, on inbound and outbound account to account rails: shadow scoring first, then a staged switchover, with no maintenance window. Whichever engine you run, the work is the same: a decision returned inside the payment's own window and kept with its reasons.

  • Transaction monitoring and fraud decisioning · Shaype, 2018 to 2023
  • Fraud and risk decisioning on live rails · an APRA regulated bank, in delivery
  • Featurespace before it, so the cutover between engines has been run once · Shaype, 2018 to 2023
Integrations

Integration surfaces we know from the inside

  • Sardinetransaction monitoring and fraud decisioning · Shaype, 2018 to 2023
  • Sardinefraud and risk decisioning · an APRA regulated bank, in delivery
  • Featurespacefraud decisioning, later replaced by Sardine · Shaype, 2018 to 2023
  • ThreatMetrixdevice identification and fraud prevention · Shaype, 2018 to 2023
  • GBG IDscan and Jumioidentity verification · Shaype, 2018 to 2023
  • Onfidoidentity verification · Shaype, 2018 to 2023, and FixDay
  • ComplyAdvantage and greenIDKYC and KYB · Shaype, 2018 to 2023

Entries marked Shaype, 2018 to 2023 were built while Marius Telespan was Shaype's Head of Engineering. They are his track record, not Sofitect engagements. The APRA regulated bank and FixDay are Sofitect engagements.

Where this applies

In the UK and EU

Since October 2024 a UK receiving PSP carries half the cost of reimbursing authorised push payment fraud, so inbound decisioning is a cost line, not a nice to have. Confirmation of Payee, 3D Secure step up, velocity limits and card controls are the decisions that sit inside the payment window, and the engine we build is where they are made. Onboarding is identity, KYC and sanctions screening against the OFSI and EU lists as one flow, every result kept.

How we work

The delivery path

In delivery. Inbound and outbound rails. The new engine. 01 Map the money paths: Every rail in both directions; a platform already clearing. 02 Run in shadow: The new engine scores live traffic without acting on it; its decisions are compared with what actually happened. 03 Switch over in stages: Rail by rail and cohort by cohort; a rollback that does not need a deployment.Inbound and outbound railsThe new engine01Map the money pathsEvery rail in both directionsa platform already clearing02Run in shadowThe new engine scoreslive traffic without acting on itits decisions are comparedwith what actually happened03Switch over in stagesRail by railand cohort by cohorta rollback that does notneed a deployment
Added without a maintenance window: shadow scoring first, then a staged switchover.
01

Map the money paths

Every rail in both directions, and the point on each where a decision can sit without missing its deadline.

02

Run in shadow

The new engine scores live traffic without acting on it, and its decisions are compared with what actually happened.

03

Switch over in stages

Rail by rail and cohort by cohort, with a rollback that does not need a deployment.

04

Keep the evidence

Every decision stored with its inputs and reasons, readable by an analyst and an auditor alike.

Proof
Undisclosed client

An APRA regulated Australian bank we do not name, holding ADI, AFSL and ACL authorisations: broadly, a prudentially regulated deposit taker with financial services and consumer credit permissions. The current engagement is Sardine fraud and risk decisioning on its inbound and outbound rails.

  • Sardine fraud and risk decisioning on inbound and outbound account to account rails
  • In delivery
  • Added without a maintenance window: shadow scoring first, then a staged switchover
SardinePythonTypeScriptAWS serverlessTerraform / CDK

Bring us your fraud and risk decisioning problem

Ninety minutes with the engineers who would do the work, on one problem you name: a fraud or risk decision, an onboarding or KYC check, a new fraud engine cutover with no false declines.