All insights

Workflows and the decisions API for regulated banks

Nov 19, 2026

APIs should expose decisions and status — not force banks to rebuild the ops console elsewhere.

Workflows with intent

Routing, dual control, and escalation only help when they match how the bank already works. Over-engineered BPM theatre slows analysts and creates shadow processes in spreadsheets.

Start with the few handoffs that actually fail today. Automate those. Leave ceremony out.

Decisions API

External systems need clean ways to submit context, receive decisions, and read case status. That is how an AML workspace sits beside core banking and onboarding stacks without becoming a dead end.

A useful API surface includes authentication, tenancy, idempotency, and clear status semantics — not only “create alert.”

What to expose carefully

  • Decision outcomes and reasons
  • Case status and ownership
  • Screening match state
  • Score snapshots with factor lineage where policy allows

What not to expose casually: raw investigative notes that were never meant for downstream automation without review.

Multi-tenant reality

Banks and groups often need separation by entity or brand. Tenancy and permissions are product requirements, not afterthoughts. API clients inherit those boundaries; ignoring them creates compliance debt.

Fatcon’s API posture

Fatcon exposes workflows and decisions so institutions can integrate without rebuilding the ops console elsewhere. The console remains the place people investigate. The API remains the place systems coordinate.