BP-061Grade C12 supporting cases (12 counted), 0 counter-examples
Govern digital credit growth as a credit book, and watch the core franchise's asset quality throughout
The practice
When digital channels speed up lending, build collection discipline into the same workflow, slow credit deliberately when quality turns, and monitor the core book's asset quality alongside digital metrics.
Why it works
Digital channels make credit fast and cheap to originate, which is their value and their risk: losses arrive months after the growth metrics look good. Governing mobile lending as a credit book, with underwriting, collection and loss metrics, rather than as a channel metric, keeps growth honest. Slowing credit deliberately when quality turns, and saying so, protects the franchise and credibility. Transformation can also mask a weakening core: inherited exposures after a merger, or a micro-loan book under stress, need separate review.
KB synthesis: the mechanism is the knowledgebase's own reasoning, drawn from the member lessons. Factual support is the case claims under evidence.cases and the research under evidence.research (R-refs).
How to apply it
- Report digital lending with vintage loss curves, not only disbursement volume.
- Build collection steps into the same digital workflow as origination.
- Set triggers for slowing origination when early-delinquency rates rise, and disclose when you pull them.
- Review inherited loan books separately after a merger.
- Track the core franchise's asset quality on the same dashboard as digital adoption.
Warning signs
- Digital loan growth is reported without loss data.
- Early delinquencies rise while targets are raised.
- Merger integration reports omit inherited credit quality.
When it applies
- Banks, fintechs, insurers and marketplaces offering digital credit.
When it does not
- Non-lending digital channels.
Evidence grade: Grade C
Anything below B. Plausible, but not yet tested in the KB at the B bar.
Why this grade
Grade C by schema 4.10 route: below the B bar of 14 counted cases across 4 primary regions (6 per 100 cases in the knowledgebase, 235 cases). B needs at least 14 counted supporting cases across at least 4 primary regions; this practice has 12 counted case(s) across 6 region(s). A needs a systematic, peer-reviewed study that tests this practice. None of the research cited in the KB does.
Where it applies
- Transformation type
- Topic (business problem)
- Function
- Starting situation
- Industry
- Region
Supporting and counter cases
Researched and fact-checked knowledgebase · Knowledgebase built 5 November 2026
Practices, their evidence grades and case summaries are public. Full case studies are available in AXIOM to subscribers and AXIOM Discover participants.

