Unclear.ai: Transaction Intelligence, engineered by Paying.co

Every transaction begins unclear. The job isn't to guess faster — it's to understand, and to be able to say why.

Unclear.ai is Paying.co's Transaction Intelligence platform, built for ISOs, ISVs, processors, and acquirers who need more than a fraud score. It synthesizes every payment signal into one explainable decision, turning transactional noise into operational clarity — on your own data, in language a reviewer and an auditor can both follow.

🎯 The problem with most fraud tools

Most fraud tools hand you a number and ask you to trust it. Unclear hands you the number and the reasoning, every time. A risk score is only useful if you can defend it — so instead of an opaque probability, Unclear returns plain-language factors: "card seen across three merchants in two minutes," not a black box.

🔍 Five scoring engines, one explained verdict

Each engine examines a different dimension of risk. Their signals combine into one score, with each engine's contribution shown, so you always know which lens drove the call.

01 — Rules — Your own logic, authored as editable data. The conditions you already know matter for your portfolio.

02 — Decline signal — Normalizes raw processor decline codes into a fraud taxonomy, so an issuer's "do not honor" carries real weight.

03 — Graph / rings — Links transactions that share a card, email, or device across merchants — the fingerprint of organized fraud.

04 — Merchant baseline — Learns what normal looks like per merchant, then flags the transactions that break the pattern.

05 — Denylist floor — Known-bad entities set a minimum band. An analyst's confirmed-fraud label becomes tomorrow's automatic catch.

All five combine in the aggregator into one score, one band, one explanation — with an optional ML signal layered in when available.

⚙ Reshape scoring without code

Weights, thresholds, rules, and denylists are editable data, not engineering tickets. Tune Unclear to your portfolio and risk appetite, then change your mind tomorrow — no deploy required.

📊 Traceable after the fact

Every run records the model and ruleset versions that produced it. Re-run later and you get the same verdict. The audit trail is built in, not bolted on — critical when a score needs to hold up in front of a regulator or an auditor.

💬 Ask Unclear — query your portfolio in plain language

Every scored run is queryable. Ask what you'd ask an analyst:

"Which merchants drove high-risk exposure this week?"

Unclear answers from your own data — for example, surfacing that three merchants account for the majority of high-band exposure across recent runs, led by a card-testing ring spanning multiple merchants, with the top contributing factors named. Every answer cites the runs and factors behind it — never an unexplained summary.

📥 Three ways in, no migration project

Unclear reads the transaction exports you already produce.

Portal upload — Drag a CSV or XLSX export into the portal. Columns map to Unclear's canonical fields automatically.

HTTP API — POST a batch to the same endpoint the portal uses. Scoped API keys for machines; scored, explained results come straight back.

Watched folder — Have a processor or job drop files into a watched folder on a schedule. Unclear picks them up, scores them, and files the run, fully hands-off.

A row is just a transaction — amount, card BIN, decline code, merchant, timestamp — the fields your exports already carry. Full card numbers are truncated and emails hashed on the way in, so nothing sensitive is stored.

🔄 From file to verdict in four steps

1. Ingest — Upload via API, portal, or scheduled drop folder. Columns map to a canonical model automatically.
2. Enrich — Each row gets BIN reference data and a normalized decline class. No full card numbers stored.
3. Score — Five engines run, producing a score, a band, and the factors behind them, plus ring analysis across the batch.
4. Review — Triage in the portal, export to CSV/XLSX, and watch the portfolio trend build run over run.

👥 Built for the people who answer for the numbers

Risk & Fraud Manager — A ranked queue instead of a raw file, with high-risk transactions surfaced alongside the factors behind them. Ring analysis links one bad actor across merchants, cards, and devices. Every verdict is reproducible enough to hold up in an audit.

Payments & Finance Lead — Approvals, declines, and chargebacks explained — what changed and why. Recoverable revenue quantified per issue, with portfolio trend visible run over run, no dashboard-building required.

ISV & Platform Engineer — One API drops explained risk scoring into your product without owning a fraud stack. Tenant-isolated reports you can surface to your own merchants. Stays out of PCI and money-transmission scope entirely.

🔒 An analysis engine, not a processor — deliberately narrow

Unclear scores and explains. It never touches money, and that design choice keeps it out of the heavy regulation that would otherwise apply.

✓ No money movement — out of money-transmission regulation by design
✓ No full PANs — card numbers truncated and emails hashed on ingest, out of cardholder-data scope
✓ Tenant-isolated — every report is scoped to its owner; a run you don't own simply doesn't exist
✓ SSO & API keys — analysts sign in with your identity provider, machines use scoped keys

🔌 API-first, built to drop into your stack

The same API powers the portal, your integrations, and the drop-folder watcher.

One API, three channels — push files over HTTP, let analysts upload in the portal, or have a processor drop them in a watched folder. Same pipeline, same verdicts.

Reports are the conduit — immutable, per-run, tenant-scoped reports: summary, flagged, rings, declines, and a rolling portfolio trend.

Yours to configure — scoring profiles, rulesets, and denylists are first-class API objects. Calibrate per tenant, reproduce any run on demand.

🌐 Speaks the processors you already speak

Unclear plugs into the processors and decline taxonomies you already use — TSYS, Fiserv, Worldpay, Elavon, Global Payments, and the major card networks: Visa, Mastercard, Amex, Discover.

Why Paying.co built this

Unclear.ai carries the same engineering discipline behind every Paying.co product: 131+ EMV Level 3 certifications, decades of payment processor integration experience, and a security-first approach to handling transaction data. It's risk intelligence built by people who understand the rails it runs on — explainable by design, narrow in scope by choice, and ready to plug into a stack that already exists.

unclear.ai is rolling out to payments teams now, with scoped trials available on your own files.

🔗 unclear.ai
🔗 Book a demo
🔗 paying.co

PayingCo #UnclearAI #FraudDetection #TransactionIntelligence #RiskManagement #Fintech #PaymentProcessing #FraudPrevention #EMV #PaymentSecurity #ArtificialIntelligence #MachineLearning #ISV #ISO #PaymentTechnology