# Other Objects
source: https://developer.mastercard.com/mastercard-processing-core/documentation/api-basics-section/other-objects/index.md

#### Addresses {#addresses}

Mastercard Processing allows you to store multiple addresses. However, when you create a main object, you can only provide one address on the client level when you send a `POST` request to `/clients`. You can store additional addresses on the account contract or card contract using a dedicated operationId. Each additional address must be defined during the onboarding process with a dedicated address type (for example, TAX, WORK, ABROAD).

#### Embossed Data {#embossed-data}

Embossed data specifies the text to be embossed on a physical card. It can be stored with the client or on the card contract level. When a new card is ordered, a card contract is created, and the CMS initiates the card [personalization process](https://developer.mastercard.com/mastercard-processing-core/documentation/guides/issuing-card/index.md#personalization-process). The process includes preparing the data required for physical card production and production in general. The storage rules for embossed data in card production are as follows:

* If the client embossed data and the card contract embossed data fields are filled, then the personalization process uses the values from the card contract.
* If the client embossed data fields are not filled and a `POST /cards` request is processed without providing embossed data, then the Mastercard Processing CMS will not allow the creation of a card contract. The request will be rejected with an error message. For more information about error messages, see [Error codes](https://developer.mastercard.com/mastercard-processing-core/documentation/code-and-formats/index.md).

Note: The `lastName` field is mandatory and must always be filled when using embossed data. If a company name is to be printed on a physical card, the name must be placed in the `lastName` field instead of the `companyName` field.

The Mastercard Processing CMS checks the length of the fields and limits the number of characters because they must be printed on the card with a standard font.
![](https://static.developer.mastercard.com/content/mastercard-processing-core/uploads/processing_13.png)

The Mastercard Processing CMS validates the types of characters submitted. If you provide a character that is not allowed, an error message will be returned, and your request will be rejected.