Run your credit policy for each application, then change it

Your credit decision sits in application code or a vendor system, behind change requests. Decisimo runs your policy and lets the risk team change it in the portal.

Start free See the decision

From credit data to an outcome in one decision flow

Bureau and fraud data enter through data sources, then knock-outs, affordability and a score feed the credit policy table. It returns approve, decline or refer with a limit, a price and a reason. Each decision flow has its own endpoint. The decision engine for any decision includes its archive and backtesting.

Consumer lending flow: Bureau and fraud > knock-outs > instalment > debt to income > risk score > Credit policy
The decision flow shows bureau and fraud data entering a policy flow and reaching the credit policy table. From that flow, the risk team can follow how supplied data produces the lender’s outcome.

Use the data and models you already have

A data source calls any provider with an HTTP API that returns JSON or XML, using your credentials. If a call fails, its output becomes a value that a rule can decide on. Models can run over HTTP or come as uploaded Python, R or Julia models, and Decisimo supplies no credit data or scores. Connect a provider through integrations.

See what a policy change does before it ships

The risk team edits the policy in the portal, and every save creates a revision. The impact analyzer replays a change on past decisions and shows approvals, declines and amount lent under each version. A challenger strategy runs beside the champion using a split value sent by the lender’s system. Nothing runs until a release is deployed.

Impact analyzer compares baseline and comparison charts for approvals, declines and amount lent
The impact analysis shows decision mix and amount lent under the baseline and comparison. This lets the risk team review the effect of a policy change before deploying its release.

See the reason behind a decline

Every row of the credit policy writes a reason in plain language. A test run shows each step in order, including the scorecard’s points and the row that fired. See the files that go to an underwriter.

Execution view shows score 660 and a fired credit-policy row declining at debt-to-income 0.541 above the 0.5 limit
The test run shows a score of 660, then the credit policy row that declines because debt to income of 0.54 is above the row’s 0.5 limit. That gives the risk team the reason written by the policy.

Questions we get asked

What is credit decisioning software?

Credit decisioning software runs a lender’s policy on the data it supplies and returns an outcome. Decisimo runs the decision flow from data sources through policy rules to an endpoint.

Is credit decisioning software a loan origination system?

No. Decisimo runs the credit decision, from supplied data through policy logic to an outcome with a limit, a price and a reason.

Does it provide credit data or scores?

No. Decisimo runs the lender’s policy on data the lender supplies. You connect the credit data providers and models used by your policy.

How do you test a policy change before it goes live?

The impact analyzer runs the current release and a changed one over past decisions or a file, then reports which decisions change. Saved cases can also run as regression tests.

Can the risk team change the policy without developers?

Yes. The risk team edits rule sets, decision tables and scorecards in the portal, where each save creates a revision. Start with the policy document in credit policy management.

Run your credit policy in one place

Start with your policy and connect the data it uses.

Start free