> For the complete documentation index, see [llms.txt](https://docs.sectoral.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sectoral.xyz/privacy-and-cryptography/proving-a-payment.md).

# Showing Proof of a Payment

A private amount can still be proven. Sectoral treats disclosure as a precise tool: you show one payment to one party, when you decide to, and the rest of your history stays sealed.

***

## What a disclosure proof is

A disclosure proof shows the amount of one transaction to a recipient of your choosing. It is signed with your account key, so the recipient can trust that you did not make it up. You define its scope, and it reveals nothing beyond that.

Typical situations where you would create one:

* Demonstrating to a landlord, employer, or vendor that a particular payment went through
* Responding to a tax authority or auditor about a single transaction
* Satisfying Travel Rule screening with a counterparty institution (see [Verifying Identity](/compliance-and-identity/identity-verification.md))

### Creating a proof

1. Find the payment in your feed and select **Generate disclosure**.
2. Pick what to include: just the amount, or the amount together with its memo.
3. Sectoral builds a proof, signed with your key, that attests to what that transaction contained.
4. Send the link or exported file to the person who requested it.

No neighboring data is revealed along the way. The proof covers only the transaction you selected and nothing else in your account.

***

## Exporting your full history

When you need records for accounting or a tax return, a single action exports your decrypted history.

* Located under **Settings → Export → Transaction History**
* Produces CSV or JSON with decrypted amounts, timestamps, counterparties, and memos
* Imports without fuss into common crypto tax tools (Koinly, TokenTax, CoinTracker)

Everything happens on your device: your key decrypts the records and the file is saved locally. Sectoral's infrastructure never receives the decrypted export and has no way to.

***

## What Sectoral cannot do

* Decrypt your transactions on behalf of someone else. Each disclosure starts with you and bears your signature.
* Keep a plaintext copy of your history on its servers.
* Produce a valid disclosure proof without your private key. This is impossible by construction, not a matter of self-restraint, so it holds even under pressure.

***

## How this fits regulation

This is the mechanism that allows Sectoral to stand on the confidentiality-without-anonymity position laid out in [Our Regulatory Approach](/compliance-and-identity/regulatory-posture.md). Your identity is checked when you open the account. Your address is public. Amounts remain sealed until you choose to reveal one, or until lawful process aimed at you, the account holder, requires it.

***

## Read next

* [Verifying Identity](/compliance-and-identity/identity-verification.md): how accounts are verified
* [Keys and Account Recovery](/privacy-and-cryptography/keys-and-recovery.md): the key that makes disclosure yours alone


---

# 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://docs.sectoral.xyz/privacy-and-cryptography/proving-a-payment.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.