# Configuring a second web site, store, or store view

The Magento Extension is configurable by the website in the Magento Admin Panel interface. This enables administrators to offer different payment methods and different currencies to different regions. 

The only field that changes is the **Base Configuration** locale field. Digital River will provide the locale needed to meet the client’s language, payment, and currency requirements. See Appendix [Exhibit F](/adobe-commerce-extension/1.0.0/appendix.md#exhibit-f-klarna-supported-countries-and-currencies) for the base configuration reference. Payments are also configurable via Magento by the website. 

See [Set up multiple websites, stores, and store views in the Admin](https://devdocs.magento.com/guides/v2.3/config-guide/multi-site/ms_websites.html) for additional information.

## Localization and translations

All content displayed via the Digital River extension can be modified by adding an `/i18n directory` to the `DrPay` folder. By default the extension supports the following languages: \
\[en, es, it, fr, sv, da, fi, cs, pl, hu, de, nl, pt, nl, fr] */app/code/Digitalriver/DrPay/i18n*

![](/files/-MP6QIo4hD8uXaWss2br)

After translation files are added or updated, rerun the upgrade command: \
     `$ php bin/magento setup:upgrade`

To ensure translated text is reflected on the Magento website/store view, it is important to update the locale option for that website/store view via the general Magento settings: \
Navigate to **Stores**, then to **Configuration**, then to **General**, and then to **Locale Options**.


---

# Agent Instructions: 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:

```
GET https://docs.digitalriver.com/adobe-commerce-extension/1.0.0/configuring-a-second-web-site-store-or-store-view.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.