Onboarding

The client application: open one, amend it, and feed it the documents and beneficial owners its review asks for. Creating a client IS opening an application, so it starts here.

📄️Create a client application

Create a client application

📄️Upload a document to support a client application

multipart/form-data, one file per call. **No `Idempotency-Key`** — the application is reviewed against the document set as a whole, so re-sending a file is safe. The service stores nothing: the bytes are relayed to the programme and never written down. Acceptance shows up as a change in the client’s `status`, not as a per-document receipt. The issuer treats this as a document slot, so a successful relay returns 204 with no body.

📄️Add a new UBO to a client application

Add a new UBO to a client application

📄️Update a client UBO’s application

Update a client UBO’s application

📄️Upload a UBO’s document to support a client application

Upload a UBO’s document to support a client application

📄️Update a client application

The issuer restarts verification after an amendment. `externalRef` is immutable and cannot be changed.