Experian KYB
Experian KYB retrieves operational and firmographic facts for a matched US business. Experian publicly describes Business Facts as including industry classifications, public-company status, sales, and employee information. The Experian KYB Workflow Builder block is available for business entities in the KYB category. It exposes one operation:Requirements
Business identification inputs
Run Experian KYB through the API
Use the application enrichment route to queue Business Facts without running a complete Data Orchestration template: Authenticate the Lendflow request with a Bearer integration token that can access the application and run underwriting services.- Call Enrich Business Credit Application for the application.
- Set
providertoexperian_business_facts. - Do not send service-specific
options; Business Facts has no configurable request options. - Include the applicable underwriting
stage_idwhen required by the application’s workflow. - Confirm that the response contains
data.onqueue: true. - Poll Get Commercial Data with
services[]=experian_business_facts.
data.onqueue: true means Lendflow queued the job; it does not mean Experian has returned a result.
Within the commercial-data response’s data object:
statuses.experian.factscontains the latest Lendflow lifecycle message.commercial_data.experian.factscontains the normalized provider result.request_data.experian.factscontains the stored provider request. Treat identifiers in this path as sensitive.
POST request to Experian’s /businessinformation/businesses/v1/facts endpoint with the matched BIN and configured subcode.
Run Experian KYB in Data Orchestration
- In the Lendflow Dashboard, open Builders > Data Orchestration.
- Create or edit a template and add Experian KYB from the KYB category.
- Connect the block to the appropriate next step, then save and publish the template.
- Run the published template with Execute Data Orchestration. Include
template_idandapplication_id, and includestage_idwhen applicable. - Confirm that the response contains
data.executed: true. - Monitor the asynchronous run with List Data Orchestration Logs and Get Data Orchestration Log.
- Retrieve Business Facts from
commercial_data.experian.factsafter the service completes.
What the service returns
Experian’s public product page confirms these result categories but does not expose the complete Business Facts schema or all code lists without provider access. The field names and null behavior below are therefore validated against Lendflow’s current fixture and frontend response model. Integrations should tolerate additional fields, omitted fields, and
null values.
Representative response
This shortened response follows Lendflow’s currentexperian/facts.json fixture. Business identifiers and values are sanitized.
Response attributes
Business identity
Industry and business characteristics
Provider results and Lendflow statuses
Do not treat a Lendflow lifecycle status as an Experian business finding.Errors
FAQ
Which operation does the Experian KYB block run?
Which operation does the Experian KYB block run?
The block exposes only Business Facts, with service ID
experian_business_facts.Is an EIN required?
Is an EIN required?
No. Business legal name, city, and state are required only when Lendflow must run automatic Business Match. Street address, ZIP code, telephone, and EIN are optional match inputs.
Do I need to provide an Experian BIN?
Do I need to provide an Experian BIN?
No. Lendflow uses the BIN already stored for the business. If the BIN is missing, Lendflow attempts Experian Business Match first.
Does data.onqueue true mean the result is ready?
Does data.onqueue true mean the result is ready?
No. It confirms only that the enrichment job was queued. Poll the commercial-data endpoint and check
statuses.experian.facts.Can Experian KYB run in Data Orchestration?
Can Experian KYB run in Data Orchestration?
Yes. Add Experian KYB to a Data Orchestration template, publish the template, execute it, and monitor the Data Orchestration logs.
Why are the employee-size and sales-size code ranges not listed?
Why are the employee-size and sales-size code ranges not listed?
The current Lendflow response shape includes
employeeSizeCode and salesSizeCode, but Experian’s accessible public documentation does not expose the complete current lookup tables. Integrations should preserve these provider codes without assigning undocumented ranges.