> For the complete documentation index, see [llms.txt](https://safedpi.gitbook.io/safeguards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://safedpi.gitbook.io/safeguards/universal-dpi-safeguards-framework/processes/o3.10-enable-different-levels-of-privacy-between-payer-and-payee.md).

# O3.10 Enable different levels of privacy between payer and payee

{% tabs %}
{% tab title="Principle" %}
[O3 Ensure data privacy by design](/safeguards/universal-dpi-safeguards-framework/principles/operational-principles/o3-ensure-data-privacy-by-design.md)
{% endtab %}

{% tab title="Risk" %}
[RS1 Privacy Vulnerability ](/safeguards/universal-dpi-safeguards-framework/risks/risks-to-safety.md)

[RS2 Digital insecurity](/safeguards/universal-dpi-safeguards-framework/risks/risks-to-safety.md)
{% endtab %}

{% tab title="Life Cycle Stage" %}
[L2 Strategy and Design](/safeguards/universal-dpi-safeguards-framework/responsible-authorities/r3-donor/l2-strategy-and-design-old.md)
{% endtab %}
{% endtabs %}

## Practices

> * Establish options for asymmetric privacy for payment systems.
> * This provides stronger anonymity for the payer and weaker protections for the payee. Thereby, anti-money laundering and fraud prevention mechanisms can be combined with strong privacy protections for citizens, making the system comparable in its privacy standards with cash.

## Resources

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td></td><td><mark style="color:yellow;"><strong>Case Study</strong></mark></td><td>( to come soon..)</td></tr><tr><td></td><td><mark style="color:yellow;"><strong>References</strong></mark></td><td><a href="https://responsiblepayments.org/">Better than Cash Alliance (2024). UN Principles for Responsible Digital Payments</a></td></tr></tbody></table>


---

# 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://safedpi.gitbook.io/safeguards/universal-dpi-safeguards-framework/processes/o3.10-enable-different-levels-of-privacy-between-payer-and-payee.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.