Run credit decisions through one decision flow

Rules sit in code, data calls in the application and scorecards in spreadsheets. Decisimo runs them in one decision flow, called through one endpoint with a JSON document.

Start free See one application

One credit application through the decision flow

  1. Send application data

  2. Call providers

  3. Apply credit policy

  4. Score application

  5. Return result

  6. Write decision archive

  7. Backtest the change

The whole decision in one flow

  • Joined in orderA data source, rule set, table and scorecard share one flow
  • One JSON documentEach part reads named inputs, and later parts can use earlier results
  • First matching branchA fork follows the first branch whose conditions match

See rules and tables

SME cash-flow facility canvas runs from Bank feed and ledger through decision nodes to Facility limit
SME cash-flow facility runs from bank feed and ledger data through rules, functions and a scorecard to a facility limit table.

Provider data during a decision

  • Provider APIsThe lender's providers return JSON or XML over REST or SOAP
  • Calls togetherOne data source calls several providers together
  • Failed provider callA rule reads the error and HTTP code to handle missing data

Connect a provider

Data source dialog for Eligibility lookups lists Credit bureau, Device and fraud signals, and Merchant profile
Eligibility lookups calls the credit bureau, device and fraud providers, and merchant profile.

Write decisions to your Postgres

  • Full JSON resultThe endpoint returns the document with each part's output
  • Decision archiveConnect a Postgres table to write each decision to your database
  • Outcome historyJoin later application outcomes to decisions in your database
Postgres decision archive lists fraud-check inputs, decline, refer and approve results, request IDs and receipt times
Application fraud check receives an application's JSON, returns the result to the lender's system and writes a row to Your Postgres, decision archive.

Measure a change against past decisions

  • Past decisionsA changed release runs over decisions production endpoints already made
  • Changed decisionsThe result lists every decision that would change
  • Recorded outcomesSee how the applications behind changed decisions performed

Backtesting guide

Backtest results show 30 of 1,001 decisions changing from approve to decline in the baseline comparison table
The backtest result shows 30 of 1,001 decisions changing against the baseline on the same rows, using demo data.

How a change reaches the endpoint

  • RevisionsCompare two saved revisions or releases
  • Regression testsSaved test cases run again against the change
  • Endpoint releaseAn endpoint with an approval sequence runs only after it is signed

Test a release

Fraud decisions in the same flow

The same decision flow runs fraud rules beside credit rules, using the lender's own fraud data.

Fraud decisioning

Questions we get asked

What is a decision engine?

A decision engine uses application data, policy logic and scoring to produce a decision. Decisimo runs data calls, rules, scorecards and models in one decision flow behind an endpoint.

How can I test a policy change before release?

A backtest runs the changed release over past production decisions and lists which would change. Where outcomes are recorded, it shows how those applications performed. Choosing a decision engine

Start with a decision your team needs to change

Start free