> For the complete documentation index, see [llms.txt](https://docs.lumia.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumia.org/tokenize/the-asset-lifecycle/stage-4-service.md).

# Stage 4 Service

**Who this is for:** issuers and operators responsible for a tokenized asset after it has been distributed (see [Stage 3: Distribute](https://app.gitbook.com/s/chmhPiVNAafGw48c4oU2/tokenize/the-asset-lifecycle/stage-3-distribute)) and is now live with holders. This is concept content.

### What servicing means

Servicing is everything that happens while the asset is outstanding: interest or dividend payments, NAV updates, corporate actions (a restructuring, a rate change), and periodic re-attestation of backing (see [Stage 2: Attest](https://app.gitbook.com/s/chmhPiVNAafGw48c4oU2/tokenize/the-asset-lifecycle/stage-2-attest)). Unlike Issue, Attest, and Distribute, which typically happen once, servicing repeats for the life of the asset.

Every servicing event that touches a holder's balance or eligibility is also a compliance checkpoint, not just a payment. A distribution to a holder whose KYC has lapsed, or a transfer that should be screened for suspicious activity, is a KYT (Know Your Transaction) concern: see [KYT (Know Your Transaction)](https://app.gitbook.com/s/chmhPiVNAafGw48c4oU2/ecosystem/lumia/compliance/kyt-know-your-transaction) for how that check fits ongoing servicing specifically, as distinct from the one-time checks at issuance and distribution.

### What Lumia provides today

{% hint style="warning" %}
Lumia provides the execution environment for whatever servicing contract logic the issuer deploys, plus standard indexer integrations ([The Graph](https://app.gitbook.com/s/chmhPiVNAafGw48c4oU2/build-on-lumia/indexers/index-contract-events-with-the-graph), [Goldsky](https://app.gitbook.com/s/chmhPiVNAafGw48c4oU2/build-on-lumia/indexers/index-contract-data-with-goldsky)) for building a servicing dashboard off indexed on-chain events.
{% endhint %}

### What the issuer brings

* The servicing contract logic itself (payment distribution, NAV update mechanics).
* The off-chain process that feeds it: a payment processor, a NAV calculation, a corporate-actions workflow.
* Ongoing KYT monitoring on transfers and distributions, and a re-attestation cadence.