> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-theory/introduction/privacy-in-commerce.md).

# Privacy in Commerce

> With the possibility of reversal, the need for trust spreads. Merchants must be wary of their customers, hassling them for more information than they would otherwise need.
>
> \- Satoshi Nakamoto, Bitcoin Whitepaper\\

![](/files/ByRImjjAF570XC8ukm6l)

Due to the need to track customers to prosecute fraudulent behaviour, merchants who use legacy payment systems are forced to request details from customers that don’t relate to the nature of the commerce, and serve no purpose other than to back-stop the merchant’s liability in the case of fraudulent actions. Despite this, the cost of prosecuting fraudsters who abuse the payment system is prohibitive for smaller transactions, and merchants only recourse is to keep records of bad actors so that they can decline their business in future.

This represents a huge problem for the privacy of good actors within the system, as their identity details often end up being stored in large merchant databases with their corresponding payment details. Merchants do not often spend the time or money needed to adequately secure this information and breaches in customer privacy have created situations where thousands or millions of customer details have been leaked onto the dark web, causing financial and identity theft all over the world.


---

# 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://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-theory/introduction/privacy-in-commerce.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.