> ## Documentation Index
> Fetch the complete documentation index at: https://docs.endl.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Country restrictions

> Why a create can be refused before anything is created

Onboarding can be blocked for specific countries under sanctions or risk policy.

The check runs **on create, before anything is created**, in the onboarding
direction. A blocked country returns `403` and no customer or applicant is made —
there is nothing to clean up afterwards.

```json 403 theme={null}
{
  "code": "403",
  "message": "Onboarding is not permitted for this country",
  "name": "PartnerOnboardingCreate failed to process"
}
```

## What is checked

The country on the customer being created — an individual's `country`, or a
business's `company.country`.

## Who controls the list

The allow/deny list is two-tier: a platform-wide list, plus an optional
per-partner list layered on top. Both are managed by Endl operations through an
internal service API.

<Note>
  This is **not** something a partner can set or read. There is no partner-facing
  endpoint for country restrictions. If you need a country enabled, ask Endl
  rather than looking for an API.
</Note>

## Handling it

Treat `403` from create as a policy decision, not a transient fault — retrying
will not help, and neither will changing another field.

Because the check runs first, a `403` here means the rest of your payload was
never evaluated. Fixing the country may simply surface validation errors that
were waiting behind it.

<Tip>
  `403` is also returned when your key lacks the `onboarding` permission, or when
  the customer belongs to another partner. The `message` distinguishes them —
  only the country case says `Onboarding is not permitted for this country`.
</Tip>