Skip to main content

Experian GDN Business Credit

Use the Experian GDN Business Credit Workflow Builder block for Experian Global Data Network (GDN) business profiles and international credit reports. The block ID is experian_gdn_business_credit and it is available for business entities.

Services

The Canadian Profile Report uses its Canada-specific credit endpoint. The other four services use the common GDN report request. The current application service catalog accepts these GDN service IDs for US and Canadian applications. Other country codes are not listed in the current requested-product availability map.

Requirements

When no GBIN is stored, Lendflow runs GDN matching and stores the highest-reliability result’s GBIN. Select the Canadian Profile Report for a Canadian report; the other reports require the GBIN and business country.

Availability window

The dashboard marks Experian GDN unavailable during its scheduled Eastern Time window: This is a dashboard availability indicator. The public Experian availability endpoint checks domestic Experian token authentication and is not a GDN report-specific health check.

API flow

  1. Create or update an application with an existing GBIN or the GDN match fields above.
  2. Select the exact GDN service in a published Data Orchestration template.
  3. Add any condition that depends on the report after the service step.
  4. Call Execute Data Orchestration:
The endpoint schedules asynchronous execution and returns a Data Orchestration log resource. It does not return the GDN report inline.
  1. Read execution with Get Data Orchestration Log at GET /api/applications/{application_id}/data_orchestration_logs/{log_id}.
  2. Retrieve responses with Get Commercial Data at GET /api/applications/{application_id}/commercial_data. Filter the response with exact IDs when needed:
Stored provider requests appear under data.request_data.experian.gdn, and latest service messages appear under data.statuses.experian.gdn.

Data Orchestration availability

The Business Credit Data Orchestration category exposes report conditions as follows: These are availability summaries, not an attribute catalog. Conditions read an already stored report synchronously, so place the service before conditions that use it. Has Unexpected Error? reads the latest finished underwriting attempt even when no report body was stored.

What the services return

Representative response

This shortened, sanitized example combines representative fields from separately stored reports.

Key response attributes

Identity and report metadata

Risk and commercial capacity

Canadian credit

Null and missing values

  • GDN content differs by country and supplying bureau. A field documented for one market may be absent in another.
  • A successful report can contain null, empty arrays, or objects whose description says the value is unavailable.
  • Treat missing and null as unavailable. Do not infer zero, false, or no adverse facts unless the provider explicitly returns that value.
  • When a service has not run, its filtered commercial-data path can be null while its status remains Not yet started.
  • Lendflow stores the results object when present. If results is missing or empty, it stores the full provider response so error details are preserved.

Statuses and errors

If no stored GBIN exists and GDN search returns no result, the report stops with No Business found - {business name}. Other failures include a missing country code, invalid country-specific state, postcode, or identification number, a missing configured subcode, inability to retrieve an Experian bearer token, and provider errors. Lendflow reads client messages from errors[0].message, server fault text from errors[0].fault.faultstring, or other recognized provider error fields before using a generic fallback.

FAQ

A BIN identifies a business in Experian’s US business-information flow. A GBIN identifies a business in GDN. Lendflow stores either identifier on the business and resolves the appropriate value through country-routed business match when one is missing.
Business legal name and country are required. Street, city, state or area, postcode, and a country-specific business identification number are optional and can improve matching.
No. The current integration intentionally omits phone from GDN business search.
Not through a Company Profile-specific condition today. The service can run and its full response is available in commercial data, but no Company Profile result conditions are registered in the Business Credit category.
GDN coverage depends on the country, bureau, report, and available source records. A successful request confirms report delivery, not that every possible measure is populated.