Skip to main content
A sub-client is one of your customers — the business on whose behalf money is held and moved. You create sub-clients, and Kira verifies each one before it can do anything. Everything that touches money belongs to a sub-client: the accounts money arrives in, the counterparties it goes to, and the transfers themselves.

​
Verification comes first

A sub-client exists as soon as you register it, and can do nothing until it is verified. That check is not a formality — it is the legal basis on which money can be held, and it is the step most likely to hold up an integration. When something is missing, Kira says exactly what, so you can collect it from your customer and send it on. Verification can also be re-run later if circumstances change.

​
What a sub-client is not

A sub-client is not a person using your product, and not a login. It is the legal entity money belongs to. One sub-client may have many people acting for it; the model does not track them separately, beyond the individuals verification requires.

​
What it is called elsewhere

In the API reference a sub-client is a user. If you are reading about creating, listing or updating a user, that is this. The naming is historical and the two words mean the same thing throughout. See The user object for every field one carries.