Customer Services Data Model

Representation of a customer for the system. Customers have various identifying properties such as email, name(s), username, and contact information.

The system has the ability to keep track of auditable notes that may apply to a customer account which can be useful for customer service or internal admin related purposes.

Representation of a saved payment for a particular customer. This domain also contains gateway-specific information needed to perform future transactions.

This representation is deprecated since 1.7.2, in favor of SavedPaymentMethod in PaymentTransactionServices. See Saved Payment Method Management Docs for more details.

Representation of an address that can be tied to a Customer or an Account

Domain that provides the ability to support fixed and dynamic customer segments. Segments enables the ability to create rule or list based groups of Customers that can be targeted for Offers, PriceLists, or ContentTargeters. This allows you to create and advertise promotions or pricing that targets a precise subset of your customer base.

Represents an organization or group of customers typically used in a B2B context.

Represents a member of an Account. An Account Member is created when a user is invited to an Account when a Customer may not yet have been created. Once a user registers as a Customer the Account Member entity will be updated to reference that Customer entity.

Represents a role within an Account. These are synced to Auth by default so that the auth token can be augmented with additional claims.

Represents special permissions associated with Accounts. These are synced to Auth by default so that the auth token can be augmented with additional claims.

Links a Role and its Permissions