Address entities hold billing address information for a customer. They're sub-entities of customers.
Addresses store components of a customer billing address. They're always created against a customer 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:
- ZIP/postal code
- State (region)
- A short, internal description for this address
You can't bill a customer without an address. To make buying as frictionless as possible, Paddle only requires a country except in some regions where a ZIP or postal code is also required.
Unique Paddle ID for this address entity, prefixed with
Memorable description for this address.
First line of this address.
Second line of this address.
City of this address.
ZIP or postal code of this address. Required for some countries.
State, county, or region of this address.
Supported two-letter ISO 3166-1 alpha-2 country code for this address.
Your own structured key-value data.
Whether this entity can be used in Paddle.
RFC 3339 datetime string of when this entity was created. Set automatically by Paddle.
RFC 3339 datetime string of when this entity was updated. Set automatically by Paddle.
Import information for this entity.
null if this entity is not imported.
Reference or identifier for this entity from the solution where it was imported from.
Name of the platform where this entity was imported from.