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

# Instances & bank details

> Bind a template to a merchant, capture each party's bank account, and manage changes with maker-checker.

An **instance** binds a template to a specific merchant. It carries the
merchant's identity, per-party bank details, and optional overrides. Manage
instances under **Finance → Disbursement → Instances**.

## Create an instance

<Steps>
  <Step title="Pick a template and merchant">
    Choose a template, a **business**, and optionally a **brand** (leave brand
    empty to apply to the whole business). A merchant name labels the instance.
  </Step>

  <Step title="Overrides (optional)">
    A partial config deep-merged over the template — e.g. *this* merchant's
    landlord takes 5%. Overrides are re-validated to 100% (10000 bps); an invalid
    merge is rejected.
  </Step>
</Steps>

An instance is unique per `(template, business, brand)`.

## Bank details

Open an instance to the **Bank Details** tab and add each payable party's
account. `klikit`-role parties never get a bank row (internal — never in a bank
file).

* **Account numbers are masked** (last-4) by default. Viewing or editing the full
  number requires the `disburseit.bank-pii.edit` permission, and every change is
  audited with masked before/after values.
* Numbers are **encrypted at rest**.
* **Verify** a party's details (requires approve permission). Editing a bank
  detail resets its verified state — the new destination must be re-verified.

## Maker-checker on bank changes

Editing bank details can go through a two-person flow:

<Steps>
  <Step title="Propose">
    A user without direct bank-edit rights submits a **bank-change request**
    instead of editing directly.
  </Step>

  <Step title="Approve or reject">
    A different user (with approve permission, and **not** the proposer) reviews
    and applies or rejects it in the **Bank Change Requests** tab.
  </Step>
</Steps>

## Provisioning

An instance's parties can be **provisioned** into the payee registry (party type,
external ref, bank details) for downstream use. Provisioning seeds the registry
only — it does not push fee math anywhere.