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

# Sending and Receiving

On Sectoral, a payment feels closer to a text message than to a bank form. Behind the scenes, every transfer is a zero-knowledge proof that settles on Robinhood Chain. On your screen, you just tap and it goes.

***

## Sending a payment

### 1. Choose the recipient

You can pay any of these:

* A `@handle`, the usual way people get paid
* A QR code, either scanned face to face or loaded from a saved picture
* A request link that someone shared with you
* A plain EVM address (`0x...`), for edge cases or for wallets that are not on Sectoral

### 2. Enter the amount and, if you like, a note

Memos are encrypted so that only sender and recipient can read them. They never appear on-chain as plain text.

### 3. Confirm

Double-check the amount and the recipient, then approve with the biometric prompt on your device, using the passkey you created when you signed up. The proof is generated on your device and sent to Robinhood Chain from there. The key, the proof, and the hardware all stay yours.

### 4. Done

Settlement is close to instant, with the payment showing in both parties' feeds in about 100 milliseconds. It beats a card reader, and the privacy comes built in. Payments to a plain EVM address also settle on-chain, but they only stay confidential if the receiving wallet supports Sectoral's confidential token contracts.

***

## Receiving a payment

There is nothing you need to do to get paid. Money sent to your `@handle`, to your address, or against a request you created lands automatically and shows up in your feed.

### Requesting an exact amount

Create a request under **Send/Receive → Request**:

* Set an amount, or leave it empty so the payer chooses
* Add a memo describing what the payment is for
* Share the resulting link or QR code

Anyone can open a request link in a normal browser, even if Sectoral is new to them. First-time payers are guided through opening an account before paying, which makes every request an invite as well.

***

## Sending to a non-Sectoral wallet

If you send USDG to a plain address that has not been set up for confidential transfers, Sectoral pauses and warns you that it will go through as a standard public ERC-20 transfer. You always see this before confirming. Privacy is never removed without telling you.

***

## Fees

Transfers on Sectoral are free for the duration of the beta. The only cost is Robinhood Chain gas, usually well under a cent, which is taken automatically from your ETH float.

***

## Read next

* [Handles](/using-sectoral/handles.md)
* [Activity Feed](/using-sectoral/activity-feed.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.sectoral.xyz/using-sectoral/moving-money.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.
