Who Sardine is
Sardine is a fraud and compliance platform built to fight financial crime. It combines device intelligence and behaviour biometrics with machine learning models and a no-code rule editor, and covers onboarding, payment fraud, card issuing fraud, account takeover, scams and AML transaction monitoring.
Banks, fintechs, marketplaces and merchants use it, and its Sonar consortium network connects fraud signals across fintech, banking and commerce. That focus on money movement is why it is one of the fraud engines our Fraud & risk module connects to.
What it does in your platform
Fraud & risk
Scores sign-ups, logins, card payments and transfers with Sardine's device and behaviour signals and its consortium models. What it sees in a session, such as a remote-access tool or a customer being coached through a payment, joins your own rules in one decision.
How the connection works
Sardine's Risk SDK runs in your web and mobile apps and collects device and behaviour signals during each session. The module calls Sardine's API at each risky moment and gets a risk score back; later updates arrive by webhook.
A session starts
Sardine's SDK runs in the app, noting the device, the network and how the customer types, pauses and moves between screens.
A transfer is requested
The customer enters a new payee and an amount. The module sends the transfer to Sardine together with that session.
Sardine scores it
Its models weigh the device, the behaviour, the payee and consortium data, and the rules you set in Sardine turn that into a score, in real time.
The module decides
Long pauses, pasted details and a remote-access tool point to a coached payment. The module merges Sardine's score with your own rules and holds the transfer, asks for a second factor or blocks it.
Your team reviews
The held transfer lands in the case queue in the backoffice, with Sardine's signals next to the customer's history. Later updates from Sardine arrive by webhook.
Next to other providers
The module can call Sardine in parallel with another engine, such as SEON or Sift, or with Fingerprint's device intelligence, and merge their signals into one decision. If Sardine is slow to answer, the decision falls back to your own rules within a set timeout.
Your rules and the case queue belong to the module, not to Sardine. Adding Sardine, or replacing it later, does not change your apps, and past decisions stay in your records.
When Sardine fits best
A strong fit when
- You move money fast: instant transfers, card payments or crypto withdrawals.
- Scams in which customers are talked into paying are one of your main risks.
- You want fraud signals and AML transaction monitoring from one provider.
Also worth a look
- SEON or Sift, when you want a different mix of data and models next to Sardine or instead of it.
- Fingerprint, when what you need most is a stable identifier for each device.
How we get you live
The contract
We help you get your Sardine account and contract in place, set up for your products and markets.
The rules
We set up the rules with you in Sardine, new ones in shadow mode first, and the matching thresholds in the module: what is held, what is challenged, what is blocked.
The keys
Sardine's API credentials go into your platform's secrets and nowhere else, and the apps never hold them.
A full test run
The whole flow runs in Sardine's sandbox, from a new session to a held transfer in the case queue, before your first real customer.
