Skip to content
Credence
Decisioning
Book a demo

Decisioning Cloud

Credit decisions you can defend.

Configure the policy, run it, and inspect versioned outcomes with the evidence recorded for each run.

Book a demoSign in
Layered glass decision prism with an emerald core
DEC-4471-9F2Astpl-v14421 ms

Final verdict

Approve

bureau_score
762
foir
0.38
dpd_max
0
A Credence decision resolved through policy stpl-v14 with its verdict, latency, and driving features preserved.

One workflow owns the whole decision.

Current versioned workflows resolve sources, features, policy gates, and the verdict in order, then persist the available trace.

Workflow orchestration

stpl-underwriting

Policy version

stpl-v14

  1. External Connections

    Source responses

    Normalized Bureau, Account Aggregator, KYC, banking, and fraud outputs enter as source evidence.

  2. Feature Engine

    Declared features

    Named fields such as bureau_score, dpd_max, and foir are computed for the policy.

  3. Rule Engine

    Versioned policy

    Ordered gates read those features and resolve the strictest matched action.

  4. Decision Engine

    Final verdict

    Approve, Refer, or Reject is stored with the rule and reason that produced it.

Persisted decision

DEC-4471-9F2A

  • Source evidence recorded
  • Recorded stages timed
  • Policy version attached

One decisioning system. Four jobs.

Operate live decisions, build the policy path, work referred cases, and test the next change from one console.

Operate

Watch decisions resolve, then open a traced outcome with the evidence recorded for that run.

Decision streamunderwriting
DEC-4508-1C7BApprove
DEC-4508-1C84Refer
DEC-4508-1C92Approve

Build

Connect sources, compute features, apply rules, and version each workflow.

  1. 1Source
  2. 2Features
  3. 3Rules
  4. 4Verdict

Underwrite

Give analysts the available evidence for traced referrals, including policy context when recorded.

Manual reviewRefer

One case, full context

Applicant, policy gates, bureau features, and reason in one workbench.

Simulate

Compare a proposed policy with the current one before applicants feel the change.

Current policy

stpl-v14

Champion

Proposed policy

stpl-v15

Challenger

The verdict is only half the record.

Current versioned runs record source data, computed features, matched rules, and the final action in execution order.

Decision reference

DEC-4508-1C7B

Total execution

421 ms

  1. Source

    Bureau pull

    Credit Bureau through External Connections

    312 ms

  2. Compute

    Four features

    bureau_score
    739
    dpd_max
    0
    foir
    0.58
    obligation_emi
    ₹18,400

    48 ms

  3. Evaluate

    Policy rules

    stpl-v14
    • bureau_score >= 700
    • dpd_max <= 30
    • foir <= 0.50

    61 ms

  4. Resolve

    Refer

    FOIR is above the policy ceiling, so the case moves to manual underwriting.

    Human review

Bring the right evidence into the workflow.

Supported provider categories can feed configured workflow steps, and available source evidence can stay inspectable with traced decisions.

Six clear glass data nodes connected to one emerald decision core
External data categories connect through Credence and become reusable workflow steps.

  • Credit Bureau

    Scores, DPD, and enquiry history.

  • Account Aggregator

    Consented bank statement data.

  • KYC

    Identity checks for a confirmed applicant.

  • Banking

    Transactions, balances, and obligations.

  • Fraud

    Fraud checks plus device evidence captured for analyst review.

  • Agreement

    Execution after an approval.

Know the policy impact before launch.

Run the proposed policy beside the current one and inspect exactly how the outcomes move.

Illustrative portfolio, 4,812 decisions

+134

more approvals

Challenger stpl-v15 changes the decision mix before it reaches an applicant.

Illustrative outcome comparison for champion policy stpl-v14 and challenger policy stpl-v15.
Outcomestpl-v14Championstpl-v15Challenger
Approve+1342,9143,048
Refer-2941,057763
Reject+1608411,001
Champion and challenger
Compare both policies on the same population.
Policy impact
Change one input and inspect the outcome shift.
Stress testing
Run adverse assumptions before publishing.

Current decisions keep their evidence together.

Versioned workflows record the request identity, policy version, engine history, and final outcome in one place.

Decision reference

Each persisted run has a stable reference for retrieval and review.

Request identity

Request IDs connect current records to the originating engine call.

Concentric glass audit vault surrounding an emerald core
Decision-record facts surround a glass audit-vault sculpture.

Policy version

Versioned evaluator runs attach the policy used for evaluation.

Execution history

Traced runs record ordered engine stages and their latency.

Persisted outcome

The verdict and recorded reason stay with the decision record.

Make every decision answerable.

Run a versioned policy, keep its recorded evidence, and inspect the outcome whenever it matters.

Book a demoSign in