> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-commerce/add-ons/payment-providers/worldpay/configuring-worldpay.md).

# Configure Worldpay

Learn how to configure Worldpay in order to implement the integration with your Umbraco Commerce installation.

## Step 1: Register with Worldpay

1. Go to [Worldpay Documentation](https://docs.worldpay.com/apis/bg350) and follow the registration instructions.
2. Obtain your **Installation ID** following the documentation.

## Step 2: Enable Payment Responses

1. Follow the [Enable Payment Responses Documentation](https://docs.worldpay.com/apis/bg350/enablepaymentresponses) to enable Payment Responses.
2. Configure the response URL as follows:

```bash
  https://{store_domain}/umbraco/commerce/payment/callback/worldpay-bs350/{payment_method_id}/
```

## Step 3: Enable Enhanced Security

1. Follow the [Enhancing Security with MD5 Documentation](https://docs.worldpay.com/apis/bg350/enhancing-security-with-md5) to configure advanced security.
2. When setting up Enhanced Security, you will be asked to configure an **MD5 secret**. Remember it for later.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-commerce/add-ons/payment-providers/worldpay/configuring-worldpay.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.