Integrations

Connect Sparsu to the data that makes every decision better.

Each integration contributes a specific piece of information to the decision and the defense. None is required to get started.

Case intake

EMAIL

Chargeback notifications read and turned into cases.
FTP

Periodic files from card networks and acquirers processed in batch.
FILES

Spreadsheets and historical exports — the starting point of the analysis.
MANUAL

Direct entry through the interface for one-off volumes.
API

Real-time case creation from your own systems.

What each connection adds to the decision and the defense of a case like CB-1042.

Data sources by purpose
Data source	What it contains	What it supports
Payment and transaction	Amounts, authorization, installments and card data.	Anchors the case to the right transaction and supports proof of purchase authentication.
Order	Products, dates, amounts and order status.	Ties the disputed charge to something concrete that was sold.
Delivery	Tracking, delivery confirmation and recipient.	The decisive evidence in "item not received" — as in 13.1.
Customer	Account history, previous purchases and support contacts.	Shows a legitimate relationship and reveals friendly fraud.
Authentication	Login, device and transaction authentication.	Supports whether the person who bought is the one disputing — or not.
Dispute submission	Acquirer, sub-acquirer and card network flows.	Enables automatic submission and result import where supported.

APIs

Cases, decisions, evidence, documents and results — with webhooks for every state change. Programmatic access for agents is also available via MCP.

// Event · webhook

{

"event": "case.outcome_received",

"case": "CB-1042",

"outcome": "recovered",

"recovered_amount": 4820.00,

"currency": "BRL",

"received_at": "2026-08-02T09:14:00Z"

}

// Illustrative example

The initial analysis uses only your historical data. Connections come in when they make sense.