> ## 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. # Equifax Personal Credit ## Equifax Personal Credit Equifax Personal Credit retrieves a OneView Business Principal Report for the application's primary owner. The registered Workflow Builder block is **Personal Credit > Equifax Personal Credit**, its block ID is `equifax_personal_credit`, and it supports the **Individual** entity type. | Service | Service ID | Numeric provider ID | | - | - | - | | Business Principal Report | `equifax_business_principal_report` | `43` | | Business Principal Report PDF | `equifax_business_principal_report_pdf` | `43` | The PDF service depends on a report ID from the matching score-model report. If one is not stored, Lendflow first requests the Business Principal Report. ## Requirements | Application field | Requirement | Notes | | - | - | - | | Primary-owner first name | Required | Must not be empty. | | Primary-owner last name | Required | Must not be empty. | | Personal address line 1 | Required | Must not be empty. | | Personal address city | Required | Must not be empty. | | Personal address state | Required | Valid state value. | | Personal address ZIP | Required | Valid ZIP value. | | SSN | Optional | Must be a valid SSN when supplied. | | Telephone | Optional | Must be a valid phone number when supplied. | | Address line 2 | Optional | Use for an apartment or unit number. | ### Score models | Application field | Requirement | Notes | | - | - | - | | Consumer score model | Required | Valid options are `vantage4` for Vantage 4.0, `fico8` for FICO 8, and `fico5` for FICO 5. | ## Inquiry semantics The current Lendflow implementation fixes `ECOAInquiryType` to `Individual`, but the code does not label the report as a hard or soft inquiry and does not expose an inquiry-type option. Confirm the permissible purpose and inquiry treatment in your Equifax agreement before running the service; do not infer hard or soft behavior from the score model. ## API flow 1. Call [Enrich Business Credit Application](/api-reference/workflow-management/enrich-business-credit-application) for the application. 2. Set `provider` to `equifax_business_principal_report`. 3. Send one exact `options.consumerScoreModel` value. 4. Confirm `data.onqueue: true`. 5. Poll `GET /api/applications/{application_id}/commercial_data` through [Get Commercial Data](/api-reference/workflow-management/get-commercial-data) with `services[]=equifax_business_principal_report`. ```json theme={"system"} { "provider": "equifax_business_principal_report", "options": {"consumerScoreModel": "vantage4"} } ``` Commercial-data responses are grouped by score model at `data.commercial_data.equifax.business_principal_report`. Status is at `data.statuses.equifax.business_principal_report`, the latest date is at `data.dates.equifax_business_principal_report`, and the stored request is at `data.request_data.equifax.business_principal_report`. ## Data Orchestration availability and flow Equifax is available in **Builders > Data Orchestration > Personal Credit** as provider ID `43`, under **Business Principal Report**. 1. Add an Equifax Business Principal Report condition or service to a template. 2. Select the consumer score model used by the condition. 3. Connect outcomes, then save and publish. 4. Execute through [Execute Data Orchestration](/api-reference/data-orchestration/execute-data-orchestration) with `template_id`, `application_id`, and `stage_id` when required. 5. Monitor the Data Orchestration logs and retrieve the finished report through the commercial-data path. ## What the service returns | Response area | Meaning | | - | - | | `models` | Credit score, model identifier, and up to four reason codes. | | `hitCode` | Match quality or no-hit result. | | `fraudIDScanAlertCodes` and `fraudVictimIndicator` | Identity-scan and fraud-alert findings. | | `trades` | Tradelines, balances, limits, payment history, and delinquency counters. | | `inquiries` | Reported file inquiries. | | `addresses`, `subjectName`, and `identification` | Matched consumer identity details. | | `consumerReferralLocation` | Equifax consumer-dispute contact details. | ```json theme={"system"} { "status": "completed", "consumers": { "equifaxUSConsumerCreditReport": [{ "hitCode": {"code": 6, "description": "Hit and Automated Consumer Narrative"}, "models": [{ "score": 713, "modelNumber": "05402", "reasons": [{"code": "00029"}] }], "fraudIDScanAlertCodes": [], "trades": [], "inquiries": [] }] } } ``` Dates and code types in the provider payload are not fully uniform. Preserve strings and leading zeroes, tolerate `null` or omitted fields, and use each code's returned description when available. ## Errors and statuses | Condition | Meaning | | - | - | | `data.onqueue: true` | The job was queued; the report is not necessarily ready. | | Hit code `2` | Poor match/no usable search result; Lendflow records an anticipated no-results error. | | Equifax codes `401.01`, `401.02`, or `401.03` | Provider authorization failed. | | `Bearer token missing from response` or `Unable to retrieve bearer token` | Equifax OAuth authentication failed. | | `PDF generation in progress, please try again later.` | The PDF is not ready; retry after the provider finishes it. | | Provider description or nested report error | Correct the reported request, identity, credential, or service problem. | ## FAQ The current options are `vantage4`, `fico8`, and `fico5`. No. Lendflow sends an individual ECOA inquiry type but does not expose or label hard-versus-soft behavior. Confirm it with Equifax for your account and permissible purpose. The current request validator permits a missing SSN. A complete name and personal address are required, and match quality may depend on the available identity data. No. It retrieves the PDF associated with the report ID stored for the selected consumer score model.