> For the complete documentation index, see [llms.txt](https://docs.useprivatus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useprivatus.com/using-privatus/sending-and-receiving.md).

# Sending & Receiving

Sending money on Privatus feels like sending a message, not filing a wire transfer. Under the hood, every payment is a zero-knowledge proof settling on Solana. You just see it work.

***

## Sending

### 1. Choose a recipient

You can send to:

* A `@handle` (the most common path)
* A QR code, scanned in person or from an image
* A payment request link someone sent you
* A raw Solana address (base58), for advanced users or sending to a non-Privatus wallet

### 2. Enter an amount and an optional memo

The memo field is encrypted and visible only to you and the recipient. It never appears in plaintext on-chain. What you write stays between the two of you.

### 3. Confirm

Review the amount and recipient, then confirm with your device's biometric prompt (the same passkey used at signup). Privatus encrypts the amount and generates the zero-knowledge proof on your device, then submits the transaction to Solana, where the proof is verified by the network's native ZK proof program. Your keys, your proof, your hardware.

### 4. Done

Settlement is near-instant. Solana produces a slot roughly every 400 milliseconds, and transfers typically confirm within a slot or two, so both you and the recipient see the transfer in your feed in well under a second. Faster than a card terminal, confidential from the first instruction. If the recipient is not on Privatus, sending to a raw Solana address still settles on-chain, but confidentiality requires the recipient's token account to have the confidential transfer extension enabled.

***

## Receiving

Receiving requires nothing from you at all. If someone sends to your `@handle`, address, or a payment request you generated, it lands in your account automatically and appears in your feed.

### Requesting a specific amount

Generate a payment request from **Send/Receive → Request**:

* Set an amount (optional, the sender can also enter their own if left blank)
* Set a memo describing what the payment is for
* Share the resulting link or QR code

Request links work in any browser, even for people without a Privatus account yet. Opening the link walks a new user through account creation before completing the payment, so your request doubles as their invitation.

***

## Sending to a non-Privatus wallet

If you send USDG to a raw Solana address whose token account isn't set up for confidential transfers, Privatus will prompt you that the transfer will settle as a standard, public SPL token transfer instead of a confidential one. You'll always see this trade-off before confirming. No silent downgrades, ever.

***

## Fees

There are no Privatus transfer fees during beta. You only pay the underlying Solana network fee, typically a fraction of a cent, which is covered automatically from your SOL reserve.

***

## Next

* [Privatus Handles](/using-privatus/privatus-handles.md)
* [Transaction Feed & History](/using-privatus/transaction-history.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.useprivatus.com/using-privatus/sending-and-receiving.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.