> 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/adobe-commerce-magento/adobe-commerce-extension-integration/getting-started/faqs.md).

# FAQs

### Where can I find the latest extension version?

The latest Adobe Commerce extension release is available on the [Adobe Commerce Marketplace](https://marketplace.magento.com/eshopworld-module-checkout.html).

### How do I troubleshoot the integration?

Start with the extension logs.

Open **ESW → Integration Monitoring → Extension Logs** and review the entries around the failing action.

If you need to share a wider diagnostic snapshot with ESW support, export a health check report:

1. Go to **ESW → Integration Monitoring → Reports**.
2. Generate a new report.
3. Wait for the report to complete.
4. Click **Export**.
5. Send the exported JSON file to ESW support.

### Why do shoppers see a failure page after successful payment?

This usually means payment completed in ESW Checkout, but Adobe Commerce could not create the order from the order confirmation callback.

In many cases, the confirmation request never reaches the store or is blocked before the extension can log it.

Check these items:

* the store must be publicly reachable
* the store must be served over valid `https`
* if the environment is protected by Basic Auth, the same credentials must be configured in **Order Confirmation Configuration**
* the order confirmation endpoint must not redirect

If you are testing from a local environment, expose it with a public tunnel such as [ngrok](https://ngrok.com/).

For the order confirmation flow details, see [Order Creation](/adobe-commerce-magento/adobe-commerce-extension-integration/getting-started/order-creation.md).

### Why do some countries fail during order confirmation with `regionId is required`?

This error usually comes from native Adobe Commerce address validation.

It happens when Adobe Commerce requires a state or region for a country, but the incoming order confirmation data does not include a matching `regionId`.

Typical error:

```
ProcessRetailerOrderConfirmationResponse {"orderNumber":"2000000646","errors":{"message":"Please check the shipping address information. regionId is a required field. Enter and try again","code":1000}}
```

To fix it:

1. Go to **Stores → Configuration → General → General**.
2. Open **State Options**.
3. Review **State is required for**.
4. Remove countries that should not require a state or region during this flow.
5. Set **Allow to Choose State if It is Optional for Country** as needed.
6. Save the configuration.

Refer to the Adobe Commerce guidance on [State Options](https://experienceleague.adobe.com/en/docs/commerce-admin/config/general/general#state-options).

### Why do I get a shipping address validation error for `postcode is a required field`?

This is also controlled by native Adobe Commerce country configuration.

It happens when Adobe Commerce requires a postal code for a country, but the incoming ESW order confirmation does not include one in the format Adobe Commerce expects.

Typical error:

```
RetailerOrderConfirmationResponseContentInvalidEvent {"orderNumber":"2000000646","errors":{"message":"Please check the shipping address information. postcode is a required field.","code":100}}
```

To fix it:

1. Go to **Stores → Configuration → General → General**.
2. Open **Country Options**.
3. Find **Zip/Postal Code is Optional for**.
4. Select the countries where postal code should be optional.
5. Save the configuration.

### Related pages

* [Installation and Update](/adobe-commerce-magento/adobe-commerce-extension-integration/getting-started/installation-and-update.md)
* [Order Creation](/adobe-commerce-magento/adobe-commerce-extension-integration/getting-started/order-creation.md)
* [Webhook Integration](/adobe-commerce-magento/integration/webhook-integration.md)


---

# 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/adobe-commerce-magento/adobe-commerce-extension-integration/getting-started/faqs.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.