Skip to main content

Experian Business Match

Experian Business Match searches Experian for businesses matching the application. The Workflow Builder block runs experian_business_match for business entities, returns ranked candidates, and saves the highest-reliability candidate’s Experian BIN or GBIN on the business when available.

Requirements

Lendflow chooses the US Businesses search when the business country is US; other countries use Experian Global Data Network (GDN).

Run through the application enrichment API

  1. Call PUT /api/applications/{application_id}/enrich through Enrich Business Credit Application.
  2. Set provider to experian_business_match.
  3. Do not send service-specific options; the service has no configurable options.
  4. Include stage_id only when the application workflow requires a specific underwriting stage.
  5. Confirm that the response contains data.onqueue: true.
  6. Poll Get Commercial Data with services[]=experian_business_match.
The request is asynchronous. data.onqueue: true confirms that Lendflow queued the job; it does not mean Experian returned a candidate. For US results:
  • Provider result: data.commercial_data.experian.business_match
  • Latest lifecycle message: data.statuses.experian.business_match
  • Stored provider request: data.request_data.experian.business_match

Data Orchestration availability and flow

The Experian Business Match block is available in Workflow Builder’s underwriting Match group for business entities. It runs experian_business_match.
  1. Add Experian Business Match to a business underwriting workflow.
  2. Ensure the required application fields, Experian access, and subcode are available before the block runs.
  3. Connect the block before downstream Experian services that need a BIN or GBIN, then save and publish the workflow.
  4. Execute the published orchestration through Execute Data Orchestration with template_id, application_id, and stage_id when applicable.
  5. Confirm that the response contains data.executed: true.
  6. Monitor the asynchronous run with List Data Orchestration Logs.
  7. Read the match status and provider result from the commercial-data paths above.
Business Match has no upstream data-service dependency. It is itself a prerequisite when a later Experian service needs an Experian business identifier and the application does not already contain one.

What the service returns

The attributes below describe the US Businesses response. GDN uses a different candidate shape, including gbin, rbbid, name, area, matchReliabilityCode, and creditIndicator.

Representative response

This abbreviated response follows Lendflow’s current Experian fixture. Business identifiers, names, addresses, and coordinates are sanitized.

Response attributes

Candidate identity and reliability

Do not use the stale high, medium, and low thresholds from the previous guide. Current Lendflow code treats reliabilityCode as a numeric provider value and sorts candidates by it, but does not define those threshold bands.

Address and matching context

Data-availability indicators

These flags indicate data availability in Experian’s record. They are not underwriting decisions and do not indicate whether the business passed or failed.

Business geocode

Errors and statuses

FAQ

No. A business-address country is required for authentication, and business legal name, city, and state are required US match inputs. Street, ZIP, telephone, and EIN are optional.
No. It only confirms that Lendflow queued the asynchronous job. Poll the commercial-data endpoint and inspect statuses.experian.business_match.
Lendflow sorts returned candidates by reliability descending and saves the first candidate’s US bin or GDN gbin when available.
No. Lendflow resolves the subcode from the configured Experian access. The enrichment request does not require service-specific options.
Treat null or an omitted key as unavailable provider data. Candidate arrays can also be empty. Check the Lendflow status before deciding whether the service is still running, failed, or completed without a match.
Yes. Lendflow routes non-US countries to Experian GDN. The required inputs and candidate attributes differ from the US response documented above.