Skip to main content
Customers store buyer identity, contact details, addresses, metadata, and payment settings that can be reused across checkout and support workflows. Use the generated endpoint pages for exact request and response payloads.

Attributes

string
Unique customer identifier (cus_…).
string
Customer email address.
string
Empty string when not set.
string
Empty string when not set.
string
Empty string when not set.
object | null
Billing address; null when not set.
object
Payment configuration stored for the customer.
object
Custom key-value pairs for your use.
boolean
True when the customer has been soft-deleted.
See every field in the response of Retrieve a customer.

Endpoints

Notes

  • email is required on create. See the create endpoint for optional fields.
  • billing_address and shipping are optional on create.
  • On update, omitted address fields are left unchanged. Explicit null clears the nested value when supported by the handler.
  • Customer list responses include summary data such as payment counts and spend by currency.