Sardine
Agentic fraud and AML platform
Sardine’s current platform spans fraud prevention, device and behavioral signals, KYC, KYB, AML monitoring, case management, and agent-assisted operations. Its published agent set includes business due diligence, screening, graph analysis, and SAR generation. It is a broader-suite candidate even though the original list places it only under fraud.
Our assessment
Add it to the cross-domain evaluation set. Confirm the exact depth of underwriting and filing.
Best fit and limitations
A serious broader-suite candidate for fintech and payment risk teams that need device intelligence, onboarding, and ongoing fraud/AML operations connected.
- Do not assume all identity or business data is proprietary or included.
- Credit underwriting workflows are documented. Merchant reserves, settlement execution, and network exposure controls still need separate proof.
- A SAR generation agent does not prove automated submission in every jurisdiction.
Tools 7
Device and behaviorEarly fraud detection+
- Device, emulator, bot, and behavioral risk signals
- Context from onboarding through payment activity
Fraud and transaction riskPayment controls+
- Real-time fraud and transaction monitoring
- Combine customer, device, and outcome context
KYC onboardingIdentity orchestration+
- Risk-adaptive verification and step-up checks
- Use as a workflow layer or alongside existing vendors
Global KYBBusiness due diligence+
- Business verification and beneficial ownership context
- Configurable policies and business research agents
Credit UnderwritingCredit decision workflows+
- Consumer, business, and seller-financing policies
- Combine bureau, cash-flow, identity, and fraud data; test decisions in shadow mode
AML operations + AI agentsInvestigations and reporting+
- Screening, cases, and transaction monitoring
- OSINT, graph, sanctions, PEP, and SAR agent roles
Merchant risk monitoringMerchant onboarding and portfolio signals+
- Combine KYB, website, acquiring, device, and behavior context
- Monitor dispute volumes, authorization changes, and merchant behavior
- Review emerging merchant risk separately from individual payment risk
AI capabilities
Predictive fraud + specialized risk agents
Sardine lists agents for rule help, data analysis, due diligence, screening, transaction review, and SAR generation. Each has a different evidence and approval requirement.
What to validate
Test each selected agent separately. Require source-linked findings, permission limits, escalation on uncertainty, and approval before high-impact actions.
Implementation
Integration checklist
- Join SDK signals, customer records, businesses, and payment events.
- Test latency, session availability, case creation, and downstream payment actions.
- Clarify direct versus orchestrated data providers and export rights.
Commercial scope
Quote required. Separate device/behavior events, fraud scoring, verification data, AML, cases, agents, and reporting.
Questions for the demo
- Which functions remain with partners, and what are their extra costs?
- What incremental fraud capture comes from device and consortium signals?
- Can every AI-generated finding be traced back to source evidence?
Engineering
- Inputs
- Business records for US KYB verification · Bureau, cash-flow, identity, and fraud inputs for configured credit policies · KYB, website presence, acquiring data, and device/behavior signals
- Outputs
- Business verification using registry, EIN/TIN, sanctions, and address signals · Credit policy decisions and shadow-mode evaluation · Merchant onboarding context and continuing portfolio-risk findings
- Webhooks
- The public KYB guide documents asynchronous /businesses processing with webhook updates.
- Decision timing
- No measured latency or contracted response time verified.
- Deployment
- Deployment options not verified.
- Dependencies
- Confirm credentials, data licenses, event identifiers, and environment access.
Verified details 9
- Inputs
Business records for US KYB verification
Source Checked 2026-09-18 - Outputs
Business verification using registry, EIN/TIN, sanctions, and address signals
Source Checked 2026-09-18 - Webhooks
The public KYB guide documents asynchronous /businesses processing with webhook updates.
Source Checked 2026-09-18 - Country scope
United States
Source Checked 2026-09-18 - Connected provider
Middesk
Source Checked 2026-09-18 - Inputs
Bureau, cash-flow, identity, and fraud inputs for configured credit policies
Source Checked 2026-09-17 - Outputs
Credit policy decisions and shadow-mode evaluation
Source Checked 2026-09-17 - Inputs
KYB, website presence, acquiring data, and device/behavior signals
Source Checked 2026-09-18 - Outputs
Merchant onboarding context and continuing portfolio-risk findings
Source Checked 2026-09-18
Illustrative contract
An example for your internal adapter. This is not a vendor endpoint, request, or response.
{
"contract": "internal-risk-review/v1",
"vendorId": "sardine",
"internalCorrelationId": "example-001",
"vendorRecordId": null,
"control": "Early fraud detection",
"evidence": [],
"status": "pending",
"decision": "review",
"requiresHumanReview": true
}Integration limits
- Illustrative internal integration contract. This is not a vendor request, response, endpoint, or SDK example.
- Empty country, deployment, or provider lists mean not verified in this review. A documented country refers to the specific product noted in its source, not universal platform coverage.
- Detailed API references, SDKs, and integration guides require login. Risk API authentication, exact payloads, retries, and idempotency remain unverified. Separate Sardine payment-checkout docs do not establish risk-platform contracts.
- Country and provider entries concern US business verification only. The page mixes planned and live report descriptions; no broader UBO release status or global KYB coverage is inferred.
- Baseline product scope, not a vendor API schema. Lending decisions do not establish merchant reserves or settlement execution.
- This product description does not publish a reserve or settlement-control API.
Sources 5
Source review dates are shown above. Product claims come from public sources. Fit, limits, and evaluation questions are our analysis. This is not a hands-on performance test. Methodology · Changelog
