> For the complete documentation index, see [llms.txt](https://developer.esw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.esw.com/checkout-api/checkout-api/core-concepts/contact-details.md).

# Contact Details

The `contactDetails` array carries the shopper's delivery and billing addresses. A single confirmation can include both types. The `contactDetailType` field distinguishes them.

## Contact detail types

### **IsDelivery**

The shipping address — where the order is physically sent. Always present for standard orders. Used to generate shipping labels and customs declarations.

### **IsPayment**

The billing address associated with the payment method. May differ from the delivery address. Used for card fraud checks and invoicing.

### Address fields reference

All address fields except `contactDetailType` and `country` are optional. However, a delivery address should contain at minimum first name, last name, address lines, city, postal code, and country for successful carrier processing.

{% hint style="info" %}

#### **Native script name fields**

For Japanese and other CJK-language deliveries, ESW may populate `nativeFirstName` and `nativeLastName` with Katakana renderings of the shopper's name. Pass these through to your carrier integration if it supports native script labels.<br>
{% endhint %}

### Key Address Fields

<details>

<summary>Fields</summary>

| Field             | Req      | Max Len | Description                                                                     |
| ----------------- | -------- | ------- | ------------------------------------------------------------------------------- |
| contactDetailType | Required | —       | `IsDelivery` or `IsPayment`                                                     |
| country           | Required | 2       | ISO 3166 two-letter code (e.g. `"DE"`)                                          |
| firstName         | Optional | 70      | Recipient first name                                                            |
| lastName          | Optional | 70      | Recipient last name                                                             |
| address1          | Optional | 150     | Primary address line                                                            |
| address2          | Optional | 150     | Secondary address line                                                          |
| address3          | Optional | 150     | Tertiary address line                                                           |
| city              | Optional | 150     | City                                                                            |
| postalCode        | Optional | 50      | Postal or ZIP code                                                              |
| region            | Optional | 150     | State, province, or county. ISO preferred.                                      |
| email             | Optional | 128     | Shopper email address                                                           |
| telephone         | Optional | 150     | Phone number                                                                    |
| nativeFirstName   | Optional | —       | First name in native script (e.g. Japanese Katakana)                            |
| nativeLastName    | Optional | —       | Last name in native script                                                      |
| status            | Optional | —       | `Unedited` \| `Added` \| `Edited` — whether address was changed during checkout |
| isSelected        | Optional | —       | True if this is the address chosen for this order                               |
| isDefault         | Optional | —       | True if shopper set as default for future orders                                |
| saveToProfile     | Optional | —       | True to persist this address to the shopper's saved addresses                   |

</details>

\ <br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.esw.com/checkout-api/checkout-api/core-concepts/contact-details.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.