> For the complete documentation index, see [llms.txt](https://dev.hybrid-chain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.hybrid-chain.com/guides/financial-infrastructure/issuing-digital-claims-and-invoices.md).

# Issuing Digital Claims & Invoices

**Overview:** Hybrid-Chain allows enterprises, creditors, and service providers to issue legally binding digital claims and invoices in a tokenized format. These claim-tokens represent payment obligations or contractual liabilities, enabling fully traceable, programmable, and enforceable digital debt instruments on a decentralized infrastructure.

**Platform Benefits:** By tokenizing invoices or claims, operators can enable real-time tracking of obligations, support automated settlement flows, create transparent audit trails, and even allow trading or assignment of claims in secondary markets. Hybrid-Chain ensures all tokens are linked to wallet-based identity, have cryptographic proof of issuance, and support expiry, metadata, and status transitions.

**Integration Flow:**

1. Authenticate as an enterprise operator (e.g., using Whitelabel Admin or backend credentials)
2. Use the `TokenCreate()` API to generate a digital claim token with custom parameters:
   * Payer and payee wallet address (or email identifier)
   * Amount, due date, invoice number, terms
   * Optional metadata (e.g., reference to service rendered, jurisdiction, notes)
   * Optional expiration logic (auto-burn if unpaid after 90 days)
3. Distribute the token to the debtor using `SecureSend()` (email or wallet-based delivery)
4. Monitor claim status:
   * Use `GetTokenOwnership()` to track if the claim has been received
   * Use `GetTokenStatus()` to determine if claim has been paid, expired, or cancelled
5. Upon payment, the claim token may be marked as “paid” or programmatically destroyed (burned), depending on logic
6. Record all updates in the Hybrid-Chain ledger, which supports audit exports, immutable logs, and regulator-readiness

**Optional Add-ons:**

* Enable partial settlement logic for recurring invoices or milestone-based billing
* Use margin wallets or smart vaults to enforce escrow-like behavior
* Create a claim marketplace to allow factoring, assignment, or refinancing
* Tie the claim-token to real-world court-enforced contracts or commercial registries

**Note:** Legal enforceability of tokenized claims may depend on local contract and financial law. Hybrid-Chain supports infrastructure and verification, but the issuer is responsible for legality and regulatory compliance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dev.hybrid-chain.com/guides/financial-infrastructure/issuing-digital-claims-and-invoices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.