Credit Score

How the flow works, end to end

1. User consent. You run a VIEW or AIS consent flow for the end user, same as any other data-access product (see AIS / Data Webhook). Credit Score is computed from this consent's data — there's no separate consent type for it.
2. Feezback enables the feature on your account. Credit Score isn't something you turn on yourself — ask your integration contact to enable it, and to configure your score bands and GO/NO-GO threshold (see below; there's a sensible default, but it's configurable per client).
3. Feezback computes the score. Once the consent is valid, the score is calculated as part of the regular insights pipeline (initial computation, then refreshed on the normal insights schedule) — you don't trigger this yourself.
4. You receive the result, two ways, both available once computed:
   • Pull it via the Insights API (creditScore field) whenever you want.
   • Get pushed a recommendation email (CreditScoreRecommendation) with a decision link the end user can click to approve/decline.
5. The decision gets recorded. The end user clicks through Feezback's hosted decision page to approve or decline the recommendation.

What you need to do, technically

• Stand up a VIEW/AIS consent flow if you don't already have one.
• Confirm with your integration contact that Credit Score is enabled on your account, and agree on your score-band configuration (or use the default).
• Call GET /tpp/v1/users/USERID/insights to read creditScore whenever you need the current value.

Score bands

The score is an integer. Bands map a score range to a label and a default recommendation:

Default recommendation logic: Fair and above is a GO by default. This threshold is configurable — you can ask your integration contact to set a different cutoff for your account.

⚠️ These bands and the default threshold reflect the current configuration and may be adjusted over time — treat this as a snapshot, not a permanent contract, and confirm current values with your integration contact if precision matters for your use case.

Getting the score: Insights API

If Credit Score is enabled for your account, the standard Insights response includes a creditScore object:

GET /tpp/v1/users/USERID/insights

{
  "creditScore": {
    "score": 750,
    "range": "good",
    "creditRecommendation": "100000"
  }
}

If the score doesn't fall into any configured band, range defaults to "poor" and creditRecommendation defaults to "0". If Credit Score isn't enabled on your account, this field is simply absent from the response.

⚠️ Only the total score, band label, and recommended amount are exposed via the API — internal factor-level detail behind the score isn't returned.

Getting the score: recommendation email

Separately, when a recommendation is ready, Feezback sends the CreditScoreRecommendation notification — by email only, not to your webhook URL. Full payload and details are on the Credit Score Webhook page. In short: it carries the score, recommended amount, a GO/NO-GO flag, and a decisionUrl + state pointing to a hosted decision page where the end user can approve or decline the recommendation.

Common questions