The control layer above your financial systems.
Unde connects to core banking, payment infrastructure, KYC providers and AML systems, links their data in a Financial Operations Graph, reasons over it with rules, models and language models, and acts through controlled, auditable workflows.
Platform architecture
Read from your systems · act through them
Interfaces
How teams and systems use the platform
- Operations Copilot
- Investigation workspace
- Dashboards
- REST and event APIs
- Arabic · English
Control
Who can do what, and the record of what was done
- Workflow engine
- Case management
- Human approvals
- Role based access
- Audit log
Intelligence
Rules, models and language models in one decision record
- Rule engine
- Machine learning models
- Anomaly detection
- Graph analytics
- LLM reasoning
Financial Operations Graph
Entities and relationships across every connected system
- Entity resolution
- Relationship model
- Temporal history
- Operational events
Integration
Secure, event driven ingestion
- Connectors
- Event streaming
- Change data capture
- Batch and SFTP
- Webhooks
Your systems
Unchanged. Unde reads from them and acts through them.
- Core banking
- Payment gateways
- KYC providers
- AML systems
- CRM
- Ticketing
- Data warehouse
Six modules. One shared foundation.
From question to resolution.
A secure natural language interface to your operational data. Ask what happened and why. The Copilot analyzes events across systems, identifies the root cause, and prepares the cases, reports and workflows your team approves.
Analyze
Queries events across connected systems, compares against baselines and isolates the cause.
Explain
Shows the figures, sources and reasoning behind every answer, within each user's permissions.
Act
Creates cases, drafts reports and starts approved workflows. Consequential actions wait for approval.
- Queried 48,210 payment events, 11:00 to 14:00
- Compared response times across 3 providers
- Grouped failures by provider and error code
- Matched failed payments against the settlement ledger
Understand relationships, not isolated events.
The Financial Operations Graph connects customers, accounts, devices, transactions, merchants, beneficiaries, identities, providers, alerts and cases. It is how Unde recognizes that a failed payment, a new device and an AML alert belong to the same story.
Entity
Transaction
Every payment event with its full lifecycle: initiation, provider response, confirmation, settlement and reversal.
Relationships
- AccountinitiatesTransaction
- Transactionrouted viaPayment provider
- Transactionpaid atMerchant
- Transactionsent toBeneficiary
- TransactiontriggersAlert
Typical sources
“Which transactions were debited without provider confirmation?”
Entity resolution
The same customer, account or device is recognized across core banking, payments, KYC and support records.
Relationship history
Links carry time: when a beneficiary was added, which device was used, what happened next.
Shared context
Every module, from payments and AML to KYC and compliance, reasons over the same graph and the same facts.
Four reasoning methods. One decision record.
No single technique is sufficient for regulated operations. Unde combines deterministic rules, statistical models, graph analytics and language models, and records how each contributed to the outcome.
Rule engine
Your existing scenarios, thresholds and policies: versioned, testable and explainable by design.
Machine learning
Behavioral baselines, anomaly detection and risk scoring calibrated to each institution's data.
Graph analytics
Linked accounts, shared devices and beneficiary networks surfaced from the Financial Operations Graph.
LLM reasoning
Language models that read the evidence, explain findings in plain language and draft narratives, grounded in retrieved records.
Combined into one recommendation: escalate to L2 review · confidence 0.81
→ routed to analyst for approval
Controlled automation for regulated environments.
Unde executes workflows derived from your standard operating procedures. Checks and data gathering run automatically; consequential actions pass through approval gates you define.
- Defined by your SOPs, versioned and reviewable
- Bounded by policy guardrails on every action type
- Gated by human approval where your policy requires it
- Recorded end to end in the audit trail
- Payment failure detectedTrigger
TX48213 · Provider B timeout · 11:52:04
- 2Check transactionCheck
Status FAILED at provider · QAR 2,450.00
- 3Check provider responseCheck
HTTP 504 after 4,210 ms · no confirmation received
- 4Check customer debitCheck
Customer wallet debited · hold H77310
- 5Check settlementCheck
Not present in today's settlement file
- 6Determine retry eligibilityDecision
Eligible under SOP PAY014 §3.2 · idempotency key verified
- 7Create case if unresolvedAction
Case OPS5512 created · linked to INC0412
- 8Notify operations teamAction
Payments Operations on call notified
- 9Prepare provider incident reportApproval
Draft ready · awaiting Payments Ops Lead approval
- SOP
- PAY014 · Failed payment handling · v3
- Trigger
- Provider timeout on debited payment
- Owner
- Payments Operations
- Mode
- Controlled · approval gated
- Maximum one automated retry per transaction
- Reversals and refunds require human approval
- Customer communication requires approval
- Every step is written to the audit log
The provider report is prepared automatically. It is sent only after the Payments Operations Lead approves it.
Enterprise grade by design.
Built for the security, governance and integration requirements of banks and regulated financial institutions, available as multi tenant SaaS, private cloud or on premise.
API first architecture
Every capability is available through documented APIs for integration with internal systems.
Event driven
Operational events are processed as they occur, not in overnight batches.
Secure integrations
Least privilege connectors, private connectivity options and credential isolation.
Role based access control
Permissions by role, team and data domain, enforced in the UI, APIs and the Copilot.
Full audit logging
An append only record of data access, AI outputs, approvals and automated actions.
Explainable AI
Recommendations carry their evidence, contributing signals and model versions.
Human in the loop
Approval gates are configured per workflow, action type and risk level.
Arabic and English
Bilingual interfaces, case narratives and reports, including right to left layouts.
Turn financial operations into an intelligent system.
See how Unde connects to your existing systems, investigates alerts and incidents with full context, and keeps every decision auditable.