Workspace/Oscilar
← All platforms

Oscilar

Cross-domain risk decisioning

Oscilar combines configurable workflows, rules, ML models, case management, and AI agents across onboarding, credit, fraud, and AML. Its breadth is in the decision and operating layer. Identity sources, business records, screening data, and processor actions still need a defined integration and contract.

Our assessment

One of the broadest decision-layer candidates. Full coverage still depends on connected data and downstream controls.

Best fit and limitations

A strong candidate when a team wants one configurable decision layer across several risk domains. For a payfac, test merchant acceptance and portfolio management alongside AML and fraud.

  • A unified workflow does not mean all data sources are native or included.
  • Credit underwriting capability does not prove native reserve calculation, delayed settlement, or network loss controls.
  • Confirm reporting submission, screening content licenses, model portability, and exit exports.

Tools 5

Workflow and policy builderDecision orchestration
+
  • No-code and natural-language policy design
  • Rules and model logic in the same decision flow
Source 1
Onboarding + account opening fraudAcceptance decisions
+
  • Risk-adaptive onboarding workflows
  • Coordinate verification and fraud checks
Source 2
Credit and underwriting workflowsRisk policy execution
+
  • Consumer and business credit use cases
  • Connect policy decisions to required data inputs
Source 1
AML + case managementDetection to review
+
  • Transaction monitoring and screening workflows
  • Context-rich investigations and review queues
Source 3
Agent HubGoverned risk-workflow assistance
+
  • Prepare policy workflows from natural language or diagrams
  • Recommend rules and threshold changes with impact analysis
  • Assemble AML review evidence and reporting narratives
  • Record human confirmation, changes, and overrides
Source 5

AI capabilities

Predictive models + configurable risk agents

Oscilar describes agents for building policies, analyzing performance, and investigating cases, alongside ML models used in risk decisions.

Build decision workflowsAnalyze policy performancePrepare case investigations
What to validate

Test change approvals, sandbox execution, deterministic replay, external tool permissions, and protection against untrusted document instructions.

Source 4

Implementation

Integration checklist
  • Inventory connected vendors, data rights, and individual provider contracts.
  • Keep merchant, owner, transaction, and case identifiers consistent across domains.
  • Test versioned decisions, external failures, rollback, and processor action delivery.
Commercial scope

Quote required. Separate platform and decision volume, data-provider costs, case seats, models, agents, and implementation.

Questions for the demo
  1. Which data checks are native, resold, or bring-your-own-contract?
  2. Can we replay a decision with its exact policy, model, and data versions?
  3. Show a merchant underwriting change flowing into monitoring and settlement controls.

Engineering

Rutter marketplace integrationChecked 2026-09-18Oscilar integration modelChecked 2026-09-18Oscilar data and policy testingChecked 2026-09-18Agent Hub context and approval contractChecked 2026-09-18
Your systemInputs & context
OscilarChecks & signals
Your controlsDecision & review
Illustrative integration boundary. Confirm the actual interfaces and decision authority.
Inputs
Connected commerce and financial records, including transactions, invoices, orders, and balances · Customer and transaction data, device/behavior signals, and selected external checks · Institution SOPs, policies, prior cases, transaction context, and analyst feedback
Outputs
Configured fraud, credit, onboarding, and compliance decisions · Configured workflow outcomes, case queues, risk profiles, and relationship graphs · Versioned workflow proposals, rule recommendations, evidence summaries, and decision rationale
Webhooks
Not verified in public documentation.
Decision timing
No measured latency or contracted response time verified.
Deployment
Deployment options not verified.
Dependencies
Connected KYC checks and provider contracts · Backtesting and A/B testing before policy changes · Configured policy boundaries, approval workflows, and human ownership of outcomes
Verified details 10
  • Inputs

    Connected commerce and financial records, including transactions, invoices, orders, and balances

    Source Checked 2026-09-18
  • Connected provider

    Rutter

    Source Checked 2026-09-18
  • Outputs

    Configured fraud, credit, onboarding, and compliance decisions

    Source Checked 2026-09-18
  • Inputs

    Customer and transaction data, device/behavior signals, and selected external checks

    Source Checked 2026-09-18
  • Outputs

    Configured workflow outcomes, case queues, risk profiles, and relationship graphs

    Source Checked 2026-09-18
  • Dependency

    Connected KYC checks and provider contracts

    Source Checked 2026-09-18
  • Dependency

    Backtesting and A/B testing before policy changes

    Source Checked 2026-09-18
  • Inputs

    Institution SOPs, policies, prior cases, transaction context, and analyst feedback

    Source Checked 2026-09-18
  • Outputs

    Versioned workflow proposals, rule recommendations, evidence summaries, and decision rationale

    Source Checked 2026-09-18
  • Dependency

    Configured policy boundaries, approval workflows, and human ownership of outcomes

    Source Checked 2026-09-18
Illustrative contract

An example for your internal adapter. This is not a vendor endpoint, request, or response.

json
{
  "contract": "internal-risk-review/v1",
  "vendorId": "oscilar",
  "internalCorrelationId": "example-001",
  "vendorRecordId": null,
  "control": "Decision orchestration",
  "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.
  • This is one documented marketplace connection. Availability, credentials, fields, and data permissions depend on the selected provider and contract.
  • The public page describes an API-first platform. It does not supply request schemas, signed-callback rules, or deployment-region guarantees.
  • Graphs cover users, devices, accounts, and shared identifiers. They do not establish complete beneficial-ownership discovery.
  • The launch describes both platform use and integration over existing risk systems. Endpoint, rollback, and per-agent action specifications are not provided.

Sources 5

Platform and Agent Huboscilar.com2026-09-18 · Reviewed
Product
Account opening fraudoscilar.com2026-09-18 · Reviewed
Product
Current risk platform and use casesoscilar.com2026-09-18 · Reviewed
Product
AI architecture and usesoscilar.com2026-09-18 · Reviewed
Product
Agent Hub launch and approval boundariesoscilar.com2026-09-18 · Reviewed
Announcement

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