> For the complete documentation index, see [llms.txt](https://developer.paddle.com/llms.txt).

# Addresses

Address entities hold billing address information for a customer. They're subentities of customers.

---

Addresses store components of a customer billing address. They're always created against a [customer](https://developer.paddle.com/api-reference/customers.md) entity.

You can create as many addresses as you like against a customer — useful for billing companies with different locations.

Address entities hold address components like:

- Country.
- ZIP/postal code.
- State or region.
- A short, internal description for this address.

Customers, addresses, and [businesses](https://developer.paddle.com/api-reference/businesses.md) work with [checkouts](https://developer.paddle.com/concepts/sell/self-serve-checkout.md), [transactions](https://developer.paddle.com/api-reference/transactions.md), and [subscriptions](https://developer.paddle.com/api-reference/subscriptions.md) to let customers purchase [products](https://developer.paddle.com/api-reference/products.md) and [prices](https://developer.paddle.com/api-reference/prices.md).

Customers require an address to make a purchase. To make buying as frictionless as possible, Paddle only requires a country [except in some regions](https://developer.paddle.com/concepts/sell/supported-countries-locales.md) where a ZIP or postal code is also required.

{% callout type="info" %}
There's no delete operation for addresses. Use the [update an address operation](https://developer.paddle.com/api-reference/addresses/update-address.md) to archive addresses when you no longer need them. To learn more, see [Delete entities](https://developer.paddle.com/api-reference/about/delete-entities.md)
{% /callout %}