Experian Fraud
Experian Fraud screens a matched US business for fraud-related conditions. The Experian Fraud Workflow Builder block is in the Fraud category, supports the Business entity type, and runs one service:Purpose
Use Fraud Shields to identify conditions that may require review. Its indicators are provider findings, not a Lendflow approval or decline decision.Requirements
Fraud Shields requires an Experian BIN. If the BIN is missing, the application must contain the inputs required for Lendflow to obtain one through Experian Business Match.Fraud Shields
Automatic Business Match when the BIN is missing
An EIN is not required. If Business Match returns no BIN, Fraud Shields does not run.
API flow
Use application enrichment to queue Fraud Shields without executing a complete Data Orchestration template:- Authenticate with a Bearer integration token that can access the application and run underwriting services.
- Call Enrich Business Credit Application at
PUT /api/applications/{application_id}/enrich. - Set
providertoexperian_fraud_shields. - Do not send service-specific
options; Fraud Shields has no configurable request options. - Include
stage_idonly when the application workflow requires a specific underwriting stage. When supplied, it must be a valid underwriting-stage UUID for the application. - Confirm that the response contains
data.onqueue: true. - Poll Get Commercial Data with
services[]=experian_fraud_shields.
stage_id when it does not apply. The enrichment request is asynchronous: data.onqueue: true means Lendflow queued the job, not that Experian returned a result.
Within the commercial-data endpoint’s data object:
Internally, Lendflow sends a
POST request to Experian’s /businessinformation/businesses/v1/fraudshields endpoint with the matched BIN and configured subcode.
Data Orchestration availability and flow
Experian Fraud is not included in the current Data Orchestration service catalog. Run it through the Experian Fraud block in an underwriting Workflow Builder stage or through the application enrichment API. When either path runs Fraud Shields without a stored Experian BIN, Lendflow attempts Business Match first. If no business is matched, Fraud Shields does not run and the service records the failure.What the service returns
Provider fields can be omitted or
null when Experian does not supply a value. Integrations should tolerate additional provider fields and should evaluate the indicators together with their accompanying definitions or statements.
Representative response
This shortened example is sanitized and reflects the response shape consumed by Lendflow.Response attributes
Business identity
Fraud indicators
OFAC codes
An OFAC warning indicates a possible match for review; it is not by itself a confirmed sanctions match.
Errors and statuses
Do not interpret a Lendflow lifecycle status as a Fraud Shields finding.FAQ
Which service does the Experian Fraud block run?
Which service does the Experian Fraud block run?
The block runs Fraud Shields with service ID
experian_fraud_shields for a business entity.Does Experian Fraud require a BIN?
Does Experian Fraud require a BIN?
Yes. The provider request requires an Experian BIN and subcode. If the business has no BIN, Lendflow first attempts Experian Business Match and stores the best returned match.
Which application fields are required when Lendflow must find a BIN?
Which application fields are required when Lendflow must find a BIN?
Business legal name, city, and a valid US state code are required for automatic Business Match. The business country is required for authentication and must be
US for this service. Street, ZIP code, telephone, and EIN are optional match inputs.Should I send options with the enrichment request?
Should I send options with the enrichment request?
No. Fraud Shields has no service-specific options. Send
provider: "experian_fraud_shields" and include stage_id only when the application’s underwriting workflow requires it.Does data.onqueue true mean the Fraud Shields result is ready?
Does data.onqueue true mean the Fraud Shields result is ready?
No. It confirms only that Lendflow queued the enrichment job. Poll the commercial-data endpoint and inspect
statuses.experian.fraud_shields and commercial_data.experian.fraud_shields.Can Experian Fraud run in Data Orchestration?
Can Experian Fraud run in Data Orchestration?
No. Experian Fraud is not included in the current Data Orchestration service catalog. Use the underwriting Workflow Builder block or application enrichment API.
Does an OFAC warning confirm a sanctions match?
Does an OFAC warning confirm a sanctions match?
No. Fraud Shields reports a possible name or address match. Review the returned code and definition through your organization’s compliance process.