FINANCE, POLICY & MARKETSPublished by Paul Ivinskas
fc.The Financial CurrentDAILY INTELLIGENCEWhat matters across finance
Deep-dive library

Nova Credit: cash-flow information, customer access and lending economics

7 min read · estimatedAI-generated analysis · Methodology
Historical version · 3 versions · Publication details

First published . This version published .

Version history

About this historical version

Added three named adoption examples, attributed customer commentary and implementation questions that distinguish Cash Atlas selection from a specific NovaScore deployment or proven portfolio outcome.

Compare with an earlier version →
Related research, policy & entities ↓

At a glance

Excerpts from this version
What it covers
Cash Atlas and NovaScore explained through dated Chase, PayPal and Imprint relationships, with clear boundaries between permissioned data, proprietary scoring and the final lending decision.
0% through article

Tap a dotted-underlined term for a definition; terms are highlighted once per section. Use Aa in the navigation for reading preferences.

In this article

What the public documentation establishes

Nova Credit describes Cash Atlas as a product that analyzes bank transactions and supplies cash-flow attributes, reports and scores for underwriting. Its NovaScore Cash Flow page describes a credit-risk score built from bank-account information, accompanied by factors. These are distinct outputs. A lender may use transaction-derived attributes in its own policy or evaluate a proprietary score; purchasing the report does not resolve which approach is appropriate.

The reviewed public pages identify intended uses but do not disclose a complete model specification, training population or independently reproducible performance study. Accordingly, this article distinguishes documented interfaces from vendor claims about predictive improvement. It does not assume that Cash Atlas, NovaScore and Nova Credit’s other products are interchangeable, or that an adoption announcement establishes a measured loss benefit.

Adoption evidence: three different credit workflows

These original 2025 announcements provide customer context for the September 29, 2026 review. They establish selections or intended integrations, not a current utilization percentage. None should be read as proof that the customer uses every Nova Credit product or that the announced scope is identical to an institution-wide production rollout.

Scroll horizontally to see all columns.

Customer / original dateAnnounced scopeBoundary for the reader
Chase / September 3, 2025Selected Cash Atlas for and separately Credit Passport for international credit information. [4]Cash-flow analytics and cross-border credit history are distinct products. The announcement does not establish universal use in Chase lending.
PayPal / September 4, 2025Selected Cash Atlas for U.S. consumer-credit underwriting; the release discusses buy now, pay later. [5]The stated aim is expanded access and richer risk assessment. The release does not provide a comparable, matured loan-loss series.
Imprint / June 25, 2025Announced integration of Cash Atlas via Alloy for co-branded-card underwriting. [6]Illustrates a data-to-workflow integration, not proof that a named score directly approves applications.

Customer commentary: right-sized credit is a different claim from more credit

In the September 3, 2025 announcement, Chris Reagan, then identified as President of Chase Branded Cards, described an objective to “approve customers with right-sized lines of credit.” That is a management statement of intended use, not a published measurement of incremental approvals or subsequent losses. [4]

The distinction matters analytically. Cash-flow information might support a different line, term, repayment schedule or request for evidence without changing the approve/decline result. A lender evaluating value should identify which decision actually changed. An improvement in reported income coverage should not automatically be credited as an improvement in creditworthiness or affordability.

What to ask these adoption examples to prove

For a card portfolio, test whether the additional data improves initial line assignment and later performance at comparable utilization and pricing. For a short installment product, examine the cash available around each payment date and whether obligations elsewhere are visible. For a co-branded program, analyze the effect of merchant mix and application channel before transferring results between programs. These are proposed evaluation methods, not claims about the named customers’ internal policies.

Ask for the exact module and version deployed. A Cash Atlas customer can use attributes or reports without relying on NovaScore as its decisive score. A customer reference should identify the application segment, connection-completion rate, fallback for missing accounts and the period over which outcomes matured. No announcement above supplies all of those details.

The practical status is a vendor with named relationships across banking and fintech, while the strength of a specific lending case still depends on implementation evidence. Preserve that distinction when comparing Nova Credit with bureau scores, data aggregators or document-analysis services. The market overview on supplies the broader provider map; this profile focuses on the decision contract and the evidence needed to evaluate this product.

The data contract matters as much as the score

The Cash Atlas V1 API reference exposes details useful to governance: source identifiers, income-model versions, recent and annual income fields, confidence measures and report-related status information. Its documentation distinguishes three complete months of recent income from a twelve-month annual measure. Those definitions matter when comparing a report with an applicant’s stated annual earnings or a lender’s existing debt-to-income calculation.

The implementation lesson is to preserve meaning through the decision system. A missing value must not silently become zero. An annualized recent observation is not a full year of actual income, and a confidence measure about a derived field is not the borrower’s probability of repayment. The bank should document units, observation windows and null handling for each attribute it uses, then test that the downstream decision engine interprets the response correctly.

Why cash flow can add information

A repayment history describes how a consumer has managed previously reported credit. Bank transactions can add evidence about current inflows, recurring obligations and the timing of . The practical opportunity is to distinguish applicants who look similar on conventional variables but have different capacity to absorb a new payment. That is an analytical rationale, not proof that every transaction-derived feature improves a specific portfolio.

A linked account can also present an incomplete picture. The customer may use several banks, split payroll deposits, move funds between owned accounts or pay major obligations in cash. A transfer can look like income if classification is wrong. Those limitations are particularly consequential when the model’s apparent precision encourages a lender to stop asking what the account does not show.

A hypothetical seasonal-income example

Assume an applicant receives $18,000 of net income during the latest three complete months and $48,000 during the latest twelve complete months. Annualizing the recent period produces $72,000; the twelve-month measure remains $48,000. Both calculations can be arithmetically correct while answering different questions. If the recent months reflect a seasonal peak, using $72,000 as durable annual capacity could materially overstate what supports a fixed installment.

Suppose the proposed loan requires $450 monthly and the applicant’s typical off-season cash remaining after existing expenses is $300. A strong recent inflow measure cannot eliminate the $150 monthly gap. The lender could consider a smaller obligation, additional evidence or another decision according to its policy. These are hypothetical figures, not a NovaScore forecast, product recommendation or claim about any customer outcome.

Separate score validation from policy validation

A proprietary score can rank applicants well and still produce poor decisions when combined with inappropriate cutoffs, amounts or terms. Recommended testing first assesses discrimination and calibration against the lender’s relevant outcome. Then evaluate the full policy, including income rules, fraud checks, overrides and the offer the borrower actually receives. The objective is to understand the incremental contribution of the score rather than attribute every policy change to it.

Use a later validation period and report results by account-history length, income variability, product and data completeness. Compare performance at similar approval rates and approvals at similar expected loss. Include connection abandonment and unusable reports in the business case. Restricting analysis to applicants with clean, complete transaction histories can overstate the value available in production.

Reason codes, corrections and operational ownership

Nova Credit’s materials describe factors associated with the score. A bank should test whether those factors remain understandable and accurate in its own decision process, particularly when several models and policy rules contribute. A list of reasons why a score is not higher is not automatically a complete account of why a particular application was denied or offered different terms.

Operational controls should identify who handles disputed inputs, corrected reports and reconsideration. Retain the report version, relevant attributes and policy version used at the time. A later refresh may change the transaction history or a derived estimate; it should not erase the evidence needed to explain the original decision. The lender also needs clear access, retention and permitted-use controls for the underlying financial information.

Costs, evidence gaps and the adoption decision

Cost includes report retrieval, integration, validation, customer support and exception processing. A more complete report can save manual work, but only if it arrives early enough and is usable by the existing process. Repeated account connections or unexplained data gaps can increase customer burden. A pilot should therefore measure funded accounts and total operating effort, not just model lift among completed reports.

Evidence that would strengthen the case includes matured performance on the lender’s own applicants, robust treatment of incomplete accounts and stable explanations across versions. The case would weaken if gains disappeared after controlling for connection completion or if recent income systematically overstated durable capacity. Sources reviewed September 29, 2026 support evaluating Cash Atlas as a structured cash-flow input and NovaScore as a separate proprietary risk assessment. They do not establish a universal approval increase or remove the need for product-specific lending judgment.

Sources

  1. Nova Credit: Cash Atlas; undated product page, reviewed September 29, 2026Source
  2. Nova Credit: Cash Atlas V1 API Reference; undated documentation, reviewed September 29, 2026Source
  3. Nova Credit: NovaScore Cash Flow; undated product page, reviewed September 29, 2026Source
  4. Nova Credit: Chase selects Cash Atlas and Credit Passport; September 3, 2025SourceBack to text: ↑1↑2
  5. Nova Credit: PayPal selects Cash Atlas; September 4, 2025SourceBack to text: ↑
  6. Nova Credit: Imprint integration through Alloy; June 25, 2025SourceBack to text: ↑

Flag an error or suggest a correction →Public corrections log →