> ## Documentation Index > Fetch the complete documentation index at: https://docs.lendflow.com/llms.txt > Use this file to discover all available pages before exploring further. # Experian Business Credit ## Experian Business Credit Use the **Experian Business Credit** Workflow Builder block for US commercial delinquency, financial-stability, and trade-payment data. The block ID is `experian_business_credit` and it is available for business entities. ## Services | Service | Service ID | Request option | Commercial-data path | | - | - | - | - | | Intelliscore | `experian_intelliscore` | `commercialScore: true` with the standard subcode | `data.commercial_data.experian.intelliscore` | | Intelliscore V3 | `experian_intelliscore_v3` | `commercialScore: true` with the V3 subcode | `data.commercial_data.experian.intelliscore_v3` | | Financial Stability Risk Score | `experian_fsr` | `fsrScore: true` with the standard subcode | `data.commercial_data.experian.fsr` | | Financial Stability Risk Score V2 | `experian_fsr_v2` | `fsrScore: true` with the V3 subcode | `data.commercial_data.experian.fsr_v2` | | Trade Data | `experian_trades` | Four independently selectable trade sections | `data.commercial_data.experian.trades` | Trade Data supports these exact options: `tradePaymentSummary`, `tradePaymentExperiences`, `tradePaymentTrends`, and `tradePaymentTotals`. Each is a boolean and defaults to `true`; the dashboard lets you deselect sections before running the service. ## Requirements | Application field | Requirement | Notes | | - | - | - | | Existing Experian BIN | Conditional | Required unless automatic Business Match is used. | | Business legal name | Conditional | Required for automatic Business Match when no BIN is stored. | | Business city | Conditional | Required for automatic Business Match when no BIN is stored. | | Business state | Conditional | Required for automatic Business Match when no BIN is stored; use a valid US state. | | Business country | Conditional | Required for automatic Business Match when no BIN is stored; use `US`. | | Business street | Optional | Improves match quality. | | Business ZIP code | Optional | Improves match quality; use a valid US ZIP code. | | Business telephone | Optional | Improves match quality; use a valid US phone number. | | EIN | Optional | Improves match quality; use a valid EIN. | When no BIN is stored, Lendflow runs Business Match and stores the highest-reliability result's BIN before requesting a score or trade report. ## API flow 1. Create or update a US application with an existing BIN or the minimum business-match fields. 2. Publish a Data Orchestration template containing the selected Experian service and any conditions that use its result. 3. Call [Execute Data Orchestration](/api-reference/data-orchestration/execute-data-orchestration): ```json theme={"system"} { "application_id": "00000000-0000-0000-0000-000000000000", "template_id": "11111111-1111-1111-1111-111111111111" } ``` The endpoint schedules asynchronous execution and returns a Data Orchestration log resource. It does not return the Experian report inline. 4. Read the log with [Get Data Orchestration Log](/api-reference/data-orchestration/get-data-orchestration-log) at `GET /api/applications/{application_id}/data_orchestration_logs/{log_id}`. 5. Retrieve responses with [Get Commercial Data](/api-reference/workflow-management/get-commercial-data) at `GET /api/applications/{application_id}/commercial_data`. Filter with exact IDs when needed: ```text theme={"system"} GET /api/applications/{application_id}/commercial_data?services[]=experian_intelliscore_v3&services[]=experian_trades ``` Stored provider requests appear under `data.request_data.experian`, and latest messages appear under `data.statuses.experian`. You can also check domestic Experian authentication availability with [Experian Service Availability](/api-docs/reference/get-api-v2-service-availability-experian). A `204` response means a bearer token could be fetched; `503` means the integration is unavailable. This check is cached briefly and does not validate a specific business report. ## Data Orchestration availability The **Business Credit** Data Orchestration category exposes conditions for all five related services: * Intelliscore and Intelliscore V3: score, percentile ranking, risk class, disputes, recommended credit limit, and unexpected-error conditions. * FSR and FSR V2: score, percentile ranking, risk class, recommended credit limit, and unexpected-error conditions. The original FSR also exposes disputes. * Trade Data: balance, high-credit, debt, trend, tradeline, dispute, and unexpected-error conditions. Place a service before a condition that reads its response. These conditions read stored results synchronously; an absent report provides no value to evaluate. The **Has Unexpected Error?** conditions inspect the latest finished underwriting attempt. ## What the services return | Result area | What it contains | | - | - | | `businessHeader` | Matched business identity, BIN, legal and display names, address, and dispute indicator when available. | | `commercialScore` | Intelliscore score, model, risk class, percentile, and recommended credit limit. | | `commercialScoreFactors` and `commercialScoreTrends` | Factors lowering the score and up to four recent quarterly observations when returned. | | `fsrScore` | Financial-stability score, model, risk class, percentile, and recommended credit limit. | | `fsrScoreFactors` and `fsrScoreTrends` | Factors affecting financial stability and recent quarterly observations when returned. | | Trade response sections | Requested summary, totals, experiences, and trends, including debt, balances, high credit, and delinquency measures. | ## Representative response This sanitized example combines representative fields from separately stored Intelliscore, FSR, and Trade Data results. ```json theme={"system"} { "data": { "statuses": { "experian": { "intelliscore_v3": "Success", "fsr_v2": "Success", "trades": "Success" } }, "commercial_data": { "experian": { "intelliscore_v3": { "businessHeader": { "bin": "123456789", "businessName": "Example Supply LLC", "customerDisputeIndicator": false }, "commercialScore": { "score": 72, "percentileRanking": 58, "riskClass": { "code": 3, "definition": "MEDIUM RISK" }, "recommendedCreditLimitAmount": 25000 }, "commercialScoreFactors": [ { "code": "011", "definition": "NUMBER OF COMMERCIAL COLLECTION ACCOUNTS" } ] }, "fsr_v2": { "fsrScore": { "score": 61, "percentileRanking": 45, "recommendedCreditLimitAmount": null } }, "trades": { "tradePaymentSummary": { "currentDbt": 12, "monthlyAverageDbt": 10, "currentAccountBalance": 12000 } } } } } } ``` ## Key response attributes ### Business and scores | Attribute | Type | Meaning | Possible values or units | When returned | | - | - | - | - | - | | `businessHeader.bin` | string | Experian identifier for the matched US business. | Nine-digit BIN. | When Experian returns a business header. | | `businessHeader.customerDisputeIndicator` | boolean or null | Whether the business disputes profile information. | `true`, `false`, or unavailable. | When provided by Experian. | | `commercialScore.score` | number | Likelihood of serious commercial delinquency in the next 12 months. | Model-dependent score; `998` can indicate recent bankruptcy and `999` insufficient data. | Intelliscore services. | | `fsrScore.score` | number | Likelihood of severe delinquency or bankruptcy in the next 12 months. | Model-dependent score; `998` can indicate recent bankruptcy and `999` insufficient data. | FSR services. | | `commercialScore.percentileRanking`, `fsrScore.percentileRanking` | number or null | Percentage of businesses expected to score lower. | Percentile or provider special value. | When the model can rank the business. | | `commercialScore.riskClass`, `fsrScore.riskClass` | object or null | Provider risk band. | Code and definition, including risk bands or insufficient-data outcomes. | When returned by the selected model. | | `recommendedCreditLimitAmount` | number or null | Experian's recommended credit limit. | Monetary amount or `null`. | When sufficient trade and profile data exists. | ### Factors, trends, and trades | Attribute | Type | Meaning | Possible values or units | When returned | | - | - | - | - | - | | `commercialScoreFactors[]`, `fsrScoreFactors[]` | array | Factors with the greatest negative influence. | Provider code and definition. | When the model returns factors. | | `commercialScoreTrends[]`, `fsrScoreTrends[]` | array or null | Recent score history. | Quarter label and numeric score; up to four quarters. | When historical scores exist. | | `tradePaymentSummary.currentDbt` | number or null | Current days beyond terms (DBT) across reported trades. | Days. | When the summary option is requested and data exists. | | `tradePaymentSummary.monthlyAverageDbt` | number or null | Average DBT over the reported monthly period. | Days. | When the summary option is requested and data exists. | | Trade balance and high-credit fields | number or null | Exposure, account balance, and recent high-credit measures. | Monetary amount or percentage, as named. | In requested trade sections when reported. | | Trade experience arrays | array | Individual or grouped payment experiences. | Accounts, balances, percentages, and dispute indicators. | When `tradePaymentExperiences` is requested and data exists. | ## Null and missing values * Experian can return a successful report with `null` trends, credit limits, factors, or trade measures. * A missing object or empty array means that Experian did not return that section or that its trade option was not requested. * Do not convert `null` to zero. Provider special score values such as `998` and `999` are numeric outcomes with specific meanings. * Lendflow stores `results` when Experian wraps a successful payload in that key. If `results` is absent or empty, Lendflow stores the full response so error details remain available. ## Statuses and errors | Signal | Meaning | | - | - | | `Not yet started` | No latest service log exists. | | `Started` | The asynchronous service job began. | | `Success` | The provider job completed; inspect each requested object for null or missing measures. | | Failure message | Match, authentication, validation, or provider failure recorded in `data.statuses.experian`. | If the BIN is missing and business match returns no result, the report stops with `No Business found - {business name}`. Other failures include missing country, inability to retrieve an Experian bearer token, invalid required match fields, missing configured subcode, provider client errors from `errors[0].message`, and provider server errors from `errors[0].fault.faultstring`. A safe fallback message is returned when Experian provides no recognized error field. ## FAQ No. When a BIN is missing, the required match fields are business name, city, and state. Street, ZIP code, phone, and EIN are optional but can improve match quality. Intelliscore predicts serious payment delinquency. FSR predicts severe delinquency or bankruptcy. Each version is a separate service ID and can use a different configured provider subcode. Yes. Summary, experiences, trends, and totals are independent boolean options. All four default to enabled. This block is the domestic US flow. For Canadian matching and reports, use the Experian GDN Business Credit block and its GDN service IDs.