---
# System prepended metadata

title: Sending bitcoin

---

# Sending bitcoin
Bitcoin wallets don't have a balance in the conventional sense. Instead it keeps track of all the previously received [UTXOs](https://bitcoin.design/guide/glossary/#unspent-transaction-output-utxo). The balance applications usually show is actually a total of those UTXOs available to spend.

When designing a payment experience choosing if you are optimising for privacy, lower transaction fees, or speed are things you need to be considerate about. Your choice will directly impact the amount of steps the user needs to make.

You should also consider what enviroment the application will be used in. If you are paying a vendor at your local market you probably won't have their contact details to exchange a payment request via chat. Scanning a QR Code to get the address would likely make more sense in this scenario than manually typing it also.

## Receieving a payment request
## Inputing the address
### Methods
#### Scanning a QR code
There 
#### Copy / Paste
#### Automatically detect from clipboard and paste into address field
#### Manually typing the address (not recomended)
## Inputting the amount to send
### Methods
#### Denonimiated in BTC
#### Denominated in the users local currency
- link to units, symbols and amount displays
#### Manually typing the amount
#### Detecting from the payment requesst

## Adjusting the fee
...
### Variants 
#### Fast
#### Medium
#### Slow
#### Custom

## Reviewing the payment and approval
## Processing
## Confirmation