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

# Proving a Payment

Keeping a figure private is not the same as being unable to evidence it. MansaFi makes disclosure a scalpel: prove one payment to one party, on your initiative, leaving every other row in your history untouched.

***

## Disclosure proofs

A disclosure proof reveals a single transaction's amount to a recipient you nominate, signed with your account key so they can rely on it not being invented. Scope is yours to set, and it stops exactly where you set it.

Common reasons to issue one:

* Showing a landlord, employer, or supplier that a specific payment cleared
* Answering a tax authority or auditor asking about one transaction
* Meeting a Travel Rule screening obligation with a counterparty institution (see [Identity Verification](/compliance/identity-verification.md))

### Issuing one

1. Open the payment in your feed and choose **Generate disclosure**.
2. Decide what travels with it: the figure alone, or the figure plus its memo.
3. MansaFi produces a proof, signed by your key, attesting to that transaction's contents.
4. Hand the resulting link or export file to whoever asked.

Nothing adjacent is exposed in the process. The proof is bound to the single transaction you picked, and to nothing else in your account.

***

## Full history export

For bookkeeping or filing, your decrypted history exports in one action.

* Found at **Settings → Export → Transaction History**
* Emits CSV or JSON carrying decrypted figures, timestamps, counterparties, and memos
* Ingests cleanly into the usual crypto tax tooling (Koinly, TokenTax, CoinTracker)

The whole operation runs on your device: your key decrypts your records and the file is written locally. The decrypted export never reaches MansaFi's infrastructure, which has no mechanism to receive it.

***

## Things MansaFi will not do

* It will not decrypt your transactions for a third party. Every disclosure originates with you and carries your signature.
* It will not retain a cleartext mirror of your history on its servers.
* It will not forge a valid disclosure proof without your private key — an impossibility of construction rather than a promise of restraint, and therefore one that survives being pressured.

***

## The regulatory fit

This mechanism is precisely what lets MansaFi hold the confidentiality-not-anonymity line described in [Regulatory Posture](/compliance/regulatory-posture.md). Identity is verified when the account opens. Addresses are public. Figures stay sealed until you unseal one, or until lawful process directed at you as the account holder compels it.

***

## Continue

* [Identity Verification](/compliance/identity-verification.md)
* [Keys & Recovery](/privacy/keys-and-recovery.md)


---

# 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.mansafi.xyz/privacy/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.