One call goes in. An explained decision comes out.
Automated credit decisioning isn't magic: it's a short sequence of steps you can read, audit and change. This page shows all four, in the order they happen.
From request to result, no black box
Your system sends the input — taxpayer ID, amount, term — with your account's key. One synchronous request.
It fetches what's missing from the sources you declared, all at once, each with its own timeout.
The DMN decision table evaluates the complete input. The first rule that matches wins.
Approve, decline or flag for review — with the rule, the version and each source's timing.
One line, in place of the if
The rest of the service stays the same. The policy moves out of it and becomes a call — now with versions, an audit trail and simulation. Changing a threshold becomes the risk team's job, not the engineering queue's.
Same logic, just outside the code: readable by the people who decide, auditable by the people who supervise.
// before — the policy lives in the code - if (score < 500) return 'RECUSA' - if (score < 700 && comprom >= 0.3) return 'RECUSA' - if (comprom >= 0.4) return 'ANALISE' - return 'APROVA' // after — the policy lives outside, with versions + const d = await decide('credito-pf', { score, comprom }) + return d.outcome
Between approve and decline there's review
The policy doesn't have to be sure about everything. What it can't settle on its own comes out flagged for review, with the rule that stopped it and the reason — and your team decides.
The rule matched within what the policy accepts. Amount and term come from the same table.
A borderline case, an amount above what the rule approves alone, mismatched data: the decision comes out flagged.
With the reason stored in the decision — the wording that answers the customer and the regulator.
Every step leaves a trace
- Input
- What your system sent, and what the pipeline added — kept apart, so you know who brought each field.
- Sources
- How long each one took. An optional source that failed is recorded; a required one that failed aborts with a reason.
- Rule
- Which row of the table matched and why — the evaluation's trace.
- Version
- The exact policy version that decided, frozen at that moment. Publishing another doesn't rewrite the past.