API reference

Decision reason: out_of_appetite

out_of_appetite is a decision reason value. The request fell outside current lending appetite. It appears in the <a href="/reference/event-decision-referred/">decision.completed</a> webhook payload under reason. Decline clearly; the customer can re-apply if their circumstances change.

2 min read

out_of_appetitereason value
decisionDomain
data.objectCarries reason

What it means

The request fell outside current lending appetite. Sector, size or structure outside the current policy window.

Where you see it

It arrives in the webhook payload:

{
  "data": {
    "object": {
      "id": "dec_5H2N8",
      "enquiry_id": "enq_9F3K2P",
      "outcome": "declined",
      "reason": "out_of_appetite"
    }
  }
}

How to handle it

Decline clearly; the customer can re-apply if their circumstances change.

Keep declines respectful and never expose the underlying assessment data. See how to apply and the eligibility criteria.

In practice

Treat out_of_appetite as one branch of your reason handling, not the whole story. For decisions, the value explains the outcome so you can present it honestly without exposing the assessment. Map it to clear, humane copy, and where relevant signpost a constructive next step — a smaller amount, more trading evidence, or a later re-application. Never surface the raw code to the customer.

Frequently asked questions

Is out_of_appetite final?

It reflects the decision at the time. Circumstances change; a future application can be assessed afresh.

Should I show this reason to the customer verbatim?

Map it to your own clear, humane copy rather than surfacing the raw code. See Map errors to user-facing messages.

Where does out_of_appetite appear in the payload?

Under data.object.reason in the decision.completed webhook. Verify the signature, then branch on it.

Funding for UK limited companies

Credicorp lends to your company, not to you personally — short-term working capital with no personal guarantee. See what your business could access.