# Ideas and use cases (/docs/products/dash-dots/use-cases)

Payments come with every dot, so anything a customer pays you for is a good place to start.

- **Bills**

  Buy EDSA units, pay the water bill or renew a TV package.

- **Airtime and data**

  Top up Orange, Africell or Qcell numbers.

- **Tickets**

  Sell seats on the Lungi ferry or for a show in Freetown, with a QR code for the gate.

- **Food and shopping**

  Take orders for a cookshop or a market stall.

- **Savings**

  Save towards a goal, or run the osusu with the group.

- **School fees**

  Collect fees and show parents what's still owed.

- **Health**

  Take payment for a clinic visit and send the receipt.

- **Donations**

  Collect donations for a church or a charity.

## What a dot can do

Besides taking payments, a dot can:

- show tickets as QR codes, and scan codes with the camera
- get live details from your server, like a balance or an order's status
- share a receipt, pick a contact, or dial a USSD code such as `*715#`
- remember things on the phone, like the customer's meter number
- use your brand colors and icons, in light and dark mode

Customers can also [share a link](/docs/products/dash-dots/how-customers-find-dots#share-links) to your dot, or to one page of it.

## Is a dot the right fit?

A dot suits customers who already use Dash. For a one-off payment, a [checkout page](/docs/developer-resources/guides/checkout-session/overview) may suit you better. If your customers use basic phones, try a [USSD flow](/docs/products/ussd-flows), which works on any phone.

> **Tip:** Start with one job people come back for, like buying units for a saved meter. Add more once that works well.