> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/features/privacy-and-security/payjoin.md).

# Payjoin

Every blockchain surveillance company leans on one assumption: all the inputs in a Bitcoin transaction belong to the sender. Payjoin quietly breaks it. In a Payjoin, the *receiver* contributes an input too — so the transaction looks ordinary on-chain, but the assumption behind most address clustering is simply wrong.

The best part: every Payjoin makes that surveillance assumption a little less reliable for *everyone*, even people who never use it.

## Why v2 matters

Early Payjoin required the receiver to run a server and be online at the exact moment of payment — fine for merchants, useless for everyone else. Cake Wallet implements **Payjoin v2**, which works asynchronously: sender and receiver don't need to be online at the same time, and neither needs a server. It just works between two compatible wallets.

## Turn it on

Open `Settings` → Wallet settings → `Privacy` on a Bitcoin wallet and enable `Use Payjoin`.

![Privacy settings with the Use Payjoin toggle enabled](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/payjoin_01_toggle-on_hl.png)

{% hint style="info" %}
Payjoin is available on Bitcoin wallets on mobile (Android and iOS).
{% endhint %}

## Receiving with Payjoin

Once enabled, your Receive screen shows a `Payjoin enabled` badge under the QR code — the QR now carries your address *and* the Payjoin link in one scan. Share it (or tap `Copy`) like any normal payment request. If the sender pays with a Payjoin-compatible wallet, the Payjoin happens automatically; if not, their payment arrives as a completely normal transaction. Nothing is lost by sharing it.

![Receive screen with the Payjoin enabled badge](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/payjoin_02_receive_hl.png)

{% hint style="info" %}
Payjoin needs an input from your side, so it becomes available once your wallet holds some Bitcoin. A brand-new, empty wallet receives normally until then.
{% endhint %}

While a Payjoin is in flight you'll see its state in the app (awaiting the sender's transaction, then in progress) — no action needed from you.

## Sending to a Payjoin link

Paste or scan the recipient's Payjoin link in the [Send screen](https://docs.cakewallet.com/features/basic/send-funds) and send as usual. Cake Wallet handles the Payjoin negotiation behind the scenes, and if it can't complete for any reason, your payment falls back to a standard transaction — the recipient always gets paid.

## What to expect

* **Fees are normal.** Both sides pay ordinary network fees; Payjoin adds no premium.
* **On-chain, nothing looks special.** That's the point — observers can't reliably tell a Payjoin from a regular payment.
* **Both wallets must support it** for the privacy benefit; otherwise payments gracefully fall back to standard sends.

## Learn more

For the deeper story on how Payjoin works and who supports it, see [payjoin.org](https://payjoin.org).


---

# 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.cakewallet.com/features/privacy-and-security/payjoin.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.