Pushback Resolution

Use this page to identify how to resolve each pushback code. The webhook ReasonCode tells you which row to follow.

After you submit the requested document, data, clarification, or merchant action, call the Submit a response to pending information endpoint where required to notify YouLend that the pushback has been resolved.

Upload a document

Send the requested file through the relevant document endpoint, then submit a response to pending information where required.

Send additional information

Use the pending information endpoint and provide the requested clarification in additionalInfo.

Update application data

Use the relevant update endpoint when the pushback requires corrected lead, organisation, or significant person details.

Complete merchant action

Some pushbacks require the merchant to complete an external flow, such as Open Banking or Onfido verification.

Resolve by pushback code

Use the accordions below as a code-first lookup. Each pushback code is listed in numerical order with the action, artifact type, and accepted document formats where applicable.

PB001–PB007

PB001 — Proof Of Identity

Use Submit a KYC document for a significant person.

Artifact: Document
Accepted formats: PDF, JPEG, JPG, PNG

PB002 — Proof Of Residential Address

Use Submit a KYC document for a significant person.

Artifact: Document
Accepted formats: PDF, JPEG, JPG, PNG

PB003 — Previous Residential Address

Use Submit a KYC document for a significant person.

Artifact: Document
Accepted formats: PDF, JPEG, JPG, PNG

PB004 — Drop In Revenue Clarification

Submit a response to pending information and send the reason in additionalInfo.

Artifact: additionalInfo

PB005 — Chamber of Commerce fillings overdue

Submit a response to pending information.

Artifact: additionalInfo

PB006 — Bank statement or payment data issue

Submit payment documents or JSON statements, other than a bank statement.

Artifact: Document or JSON statements
Accepted formats: PDF, JSON

PB007 — Additional significant person details

Update the significant person details using the significant persons API.

Artifact: API request body

PB008–PB014

PB008 — Proof of bank - sole trader

Submit a bank statement or JSON statement.

Artifact: Document
Accepted formats: PDF

PB009 — Proof of bank - limited company

Submit a bank statement.

Artifact: Document
Accepted formats: PDF

PB010 — Proof of Bank - limited partnership

Submit a bank statement.

Artifact: Document
Accepted formats: PDF

PB011 — Management Accounts

Submit a management account document.

Artifact: Document
Accepted formats: PDF

PB012 — Bank statements - specific months

Submit a bank statement.

Artifact: Document or JSON statement

PB013 — Proof of outstanding balance

Submit a management account document using POST /onboarding/Leads/{leadId}/documents/managementaccount as the supporting-document upload workaround, then submit a response to pending information.

Artifact: Document
Accepted formats: PDF, JPEG, JPG, PNG

PB014 — Registry - accounts

Submit a response to pending information.

Artifact: additionalInfo

PB015–PB021

PB015 — Companies house - confirmation statement

Submit a response to pending information.

Artifact: additionalInfo

PB016 — Unlock Experian

Submit a response to pending information.

Artifact: additionalInfo

PB017 — Bank statements - specific months - open banking

Submit a bank statement or use an Open Banking connection.

Artifact: Document or Open Banking connection

PB018 — Overdraft limit confirmation

Submit a management account document using POST /onboarding/Leads/{leadId}/documents/managementaccount as the supporting-document upload workaround, then submit a response to pending information.

Artifact: Document
Accepted formats: PDF, JPEG, JPG, PNG

PB019 — Merchant identification number confirmation

Submit a response to pending information and include the MID or merchant ID confirmation in additionalInfo. If available upfront, Create Lead supports mid or merchantIds.

Artifact: additionalInfo
Accepted formats when sending supporting evidence: PDF, JPEG, JPG, PNG

PB020 — Open banking only

Use the openBankingURL returned by the Create Lead endpoint for the merchant to complete the Open Banking connection. Partners should store this URL when the lead is created. If it was not stored, YouLend can resend or share the Open Banking link. Then submit a response to pending information.

Artifact: Open Banking connection

PB021 — Supplier's invoice

Submit a management account document using POST /onboarding/Leads/{leadId}/documents/managementaccount as the supporting-document upload workaround, then submit a response to pending information.

Artifact: Document

PB022–PB028

PB022 — Onfido - identity verification

No partner document-upload or API resolution is available. The merchant must complete Onfido identity verification through the YouLend flow; partners should treat this as a merchant-action or support item.

Artifact: Connect to Onfido

PB023 — Website

Submit a response to pending information and include the website or social media links in additionalInfo.

Artifact: additionalInfo

PB024 — Additional Information Required i.e. Other

Submit a response to pending information.

Artifact: additionalInfo

PB025 — Trading address + trading name

Update the organisation details endpoint.

Artifact: API request body

PB026 — Personal bank statement required

Submit a bank statement.

Artifact: Document or JSON statements

PB027 — Missing processor statements/ Specific months bank statement

Submit a bank statement or complete the required action.

Artifact: Document, JSON statements, or Open Banking connection
Accepted formats: PDF, JSON

PB028 — Residence Permit

Submit a KYC document for a significant person with kycDocumentType=proofOfIdentity, then submit a response to pending information.

Artifact: Document
Accepted formats: PDF, JPEG, JPG, PNG