Pulling the score, grade and alerts behind a Credit Sesame login

Credit Sesame shows a member one number on the home screen — a VantageScore 3.0 refreshed daily, supplied by TransUnion per the app's own report-summary page — and a stack of derived data sits behind it. A weekly letter grade. Real-time change alerts. A personal-loan and card marketplace. For a lender, a personal-finance product, or a credit-coaching tool that wants any of that in its own backend, the question is how to reach a member's view without screen-scraping a phone by hand. That is the integration we scope here.

The bottom line: nearly everything a buyer wants here lives behind a single member login, and it is the member's data. So the dependable way in is an authorized read of that member's own authenticated session — the same calls the app makes after sign-in, captured and re-implemented under the account holder's consent. That returns the score, the Sesame Grade, the alert feed and the offers exactly as the member sees them. Where a buyer specifically needs the full three-bureau report rather than the TransUnion-based free view, we drive a Sesame+ session instead. We get into both in the route section below.

What sits behind a Credit Sesame login

Each row is a real surface of the app, named the way Credit Sesame names it where possible. Granularity matters more than the label — a daily single score is a different integration than a tradeline-level report.

Authorized routes to a member's credit profile

Two or three routes genuinely apply, depending on which slice of the data a buyer needs and which plan the member holds.

1 · Member-consented session read

The account holder authorizes access; we replay the app's authenticated calls under that consent. Reaches the score, the Sesame Grade, the alert stream and the offers — the free-tier surface in full. Effort is moderate and the result is durable as long as we account for the app's front end shifting. This is the route we run for most buyers because it depends only on the member's authorization, not on a bureau or partner relationship.

2 · Sesame+ session for three-bureau reports

The same consented-session technique, but against a member on a paid Sesame+ plan, which is where the Experian, Equifax and TransUnion reports and the simulator live. Reaches richer data; the trade is that it only exists for members who pay for that tier, so we scope it per plan type.

3 · Native report capture

A backstop for a member who wants their own report summary archived as a document rather than a feed — we capture what the app renders and normalize it. Narrow, but useful when a buyer's need is record-keeping rather than a live sync.

Onboarding for any of these — a consenting test account, or a Sesame+ sandbox where the work needs paid-tier fields — is arranged with you during the build, not something you hand over before we start.

What lands in your repo

The deliverable is working code and the documents that let your team own it, scoped to the surfaces above:

• An OpenAPI / Swagger specification for the score, summary, alerts and offers endpoints as we reconstruct them.
• A protocol and auth-flow report: the login, token issue, bearer-token refresh and any cookie chain the session needs.
• Runnable source for the key calls in Python and Node.js — sign-in, score fetch, summary fetch, alert polling.
• Automated tests against a consenting account, including the free-tier-vs-Sesame+ field differences.
• A normalized schema so a VantageScore from TransUnion never gets confused with a FICO downstream.
• Interface documentation plus data-retention and consent-logging guidance for the credit data you hold.

A look at the session and score fetch

Illustrative. Endpoint paths and field names are reconstructed from the consented session and confirmed during the build; the point is the shape, not literal constants.

# member consents; we drive their own authenticated session
POST /auth/login
  { "email": "<member>", "password": "<member>" }
  -> 200 { "access_token": "...", "refresh_token": "...", "expires_in": 3600 }

GET  /v1/credit/score            # Authorization: Bearer <access_token>
  -> 200 {
       "model":       "VantageScore 3.0",
       "bureau":      "TransUnion",
       "value":       712,
       "refreshed_at":"2026-06-15",
       "delta_30d":   8
     }

GET  /v1/credit/summary          # the weekly "Sesame Grade"
  -> 200 {
       "grade": "B",
       "factors": {
         "payment_history": "A",
         "credit_usage":    "C",
         "new_inquiries":   "B",
         "open_accounts":   "B",
         "account_age":     "B"
       }
     }

# error handling we wire in:
#   401  -> token expired, exchange refresh_token, retry once
#   403  -> field gated to Sesame+; degrade to free-tier shape

One shape for the whole profile

We collapse the per-screen responses into a single record so a partner app reads one consistent object whether the member is free-tier or Sesame+. Bureaus and report detail simply fill in as the plan allows.

{
  "member_ref": "opaque-id",
  "score":  { "model": "VantageScore 3.0", "bureau": "transunion",
              "value": 712, "as_of": "2026-06-15" },
  "grade":  { "overall": "B",
              "factors": { "payment_history": "A", "credit_usage": "C",
                           "new_inquiries": "B", "open_accounts": "B",
                           "account_age": "B" } },
  "bureaus": ["transunion"],          // adds experian, equifax on Sesame+
  "alerts":  [ { "type": "new_inquiry", "bureau": "transunion",
                 "at": "2026-06-14T11:02:00Z" } ],
  "offers":  [ { "product": "personal_loan", "apr_low": 1.99,
                 "apr_high": 35.99, "source": "marketplace" } ]
}

Consent, and the FCRA backdrop

The credit-report data Credit Sesame surfaces originates at the bureaus and sits under the Fair Credit Reporting Act. The basis we actually pull on is narrower and steadier than any regime debate: the member's own authorization to their account, with that consent logged and scoped to the fields a buyer needs. The CFPB's Personal Financial Data Rights rule (12 CFR Part 1033) gets cited as the US open-banking path, but it is not in force — enforcement is enjoined and the rule is back in agency reconsideration — so we do not build against it as settled law. Where it would eventually touch an app like this is the Sesame Cash deposit side rather than the bureau-sourced score; either way, the consented session is what the integration rides today. We work under NDA where a buyer needs it, log every consent, and keep only the fields in scope.

What we plan around in a Credit Sesame build

Three specifics shape the work, and we handle each as part of the engagement:

• Tier gating. A free account exposes a TransUnion-sourced score and the Sesame Grade; the full three-bureau reports and the simulator only exist on a Sesame+ plan. We map which field requires which plan, so the integration returns a clean, predictable shape for a free-tier member instead of erroring on a missing report.
• Score model labelling. The number is a VantageScore 3.0, not a FICO, and lenders mostly decide on FICO. We carry the model and bureau through the normalized output so a partner's lending logic never silently treats one as the other.
• Session lifetime. A consented pull depends on a live token. We design the sync around the session-expiry and refresh window so it re-authenticates cleanly rather than going quiet, and when the app's front end changes we re-map the affected surfaces as routine upkeep.

Screens we mapped

From the app's store listing — the surfaces a session read has to reproduce. Tap to enlarge.

Where Credit Sesame sits among credit apps

Same category, neighbouring data — relevant when a buyer wants one normalized credit view across several of these rather than a single source.

• Credit Karma — free VantageScore from TransUnion and Equifax with report monitoring and offer matching.
• WalletHub — a free daily TransUnion score paired with a score simulator and monitoring.
• Experian — surfaces a FICO Score 8 from its own bureau file plus dark-web and report monitoring.
• myFICO — sells the FICO scores that lenders actually use, across all three bureaus.
• NerdWallet — bundles a free VantageScore with budgeting and product recommendations.
• Dovly AI — automated credit-repair and dispute tooling alongside score tracking.
• Nav — business credit profiles and scores aimed at small businesses.
• Aura — identity-theft protection with credit monitoring and change alerts.
• Discover Credit Scorecard — a free FICO Score from Discover with monitoring, no membership.

What we checked

On 15 June 2026 we read Credit Sesame's own report-summary and Sesame+ pages for the score model, bureau and the five Sesame Grade factors; TransUnion's announcement of the direct-to-consumer collaboration for the data partnership; and the CFPB's reconsideration docket to confirm the Section 1033 rule's unsettled status. Sources, each opening in a new tab:

• Credit Sesame — free credit report summary (Sesame Grade factors, daily VantageScore 3.0)
• TransUnion newsroom — collaboration with Credit Sesame
• Credit Sesame — Sesame+ three-bureau reports
• CFPB — Personal Financial Data Rights reconsideration

Mapped by the OpenBanking Studio integration desk, June 2026.

Questions integrators ask about Credit Sesame

Is the credit score Credit Sesame shows a FICO score?

No. Per Credit Sesame, the free score is a VantageScore 3.0 supplied by TransUnion, not a FICO. We label the scoring model and bureau in the normalized output so downstream lending logic never mistakes it for a FICO.

Can you reach all three bureaus, or only TransUnion?

A free Credit Sesame account is sourced from TransUnion. The full reports from Experian, Equifax and TransUnion sit behind a Sesame+ plan, so the integration adapts to whichever tier the member is on and degrades cleanly for free-tier accounts.

On whose authority do you pull a member's Credit Sesame data?

The member's own authorization to their account. The underlying bureau data is governed by the Fair Credit Reporting Act; the CFPB's Section 1033 rule is unsettled and back in reconsideration, so we treat it as a forward-looking possibility, not the basis we build on.

Can the credit-change alerts feed a webhook in near real time?

Yes. Credit Sesame's monitoring events map to an event stream, so we can forward score changes, new inquiries and report changes to a webhook or queue as they arrive in the member's session.

Source delivered as runnable code starts at $300, billed only after you have checked it over and it works against a consented account; or skip the build and call our hosted endpoints instead, paying per request with nothing upfront. Most projects run a one-to-two week cycle. Tell us the app and what you want out of its credit data at /contact.html and we will scope the route with you.