> For the complete documentation index, see [llms.txt](https://docs.ecommerce.seb.ee/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecommerce.seb.ee/guides/merchant-portal/manage-your-account/settings.md).
# Settings
Use Settings to review merchant and shop configuration and, where permitted, request changes to the parts of your account that are managed through the Merchant Portal.
Access to Settings is controlled by role-based permissions. What you see depends on your merchant agreement, the services enabled for your account, and the shop you are currently working with.
***
### What Settings is for
Settings brings together the configuration areas that define how your merchant account operates.
Depending on your setup, you can use it to:
* review merchant-level and agreement-related information
* inspect shop-specific configuration
* view enabled payment methods, currencies, banks, and technical parameters
* review fees and transaction limits
* manage checkout presentation, where enabled
* submit configuration change requests where approval is required
***
### Business settings
Business Settings gives you visibility into merchant-level information and agreement-related data.
This may include:
* your merchant agreement information
* the list of registered shops
* whether a shop is in Sandbox or Production
* the operational status of each shop
Where permitted, authorized users can also submit requests for new shop creation from this area. New shop requests are reviewed and approved according to the Customer’s internal procedures and are not activated automatically.
Use this area when you need a high-level view of your merchant setup rather than shop-by-shop operational details.
***
### Shop settings
Shop Settings shows the configuration for a specific shop.
Depending on your service scope and integration setup, this may include:
* shop details and identifiers
* enabled payment methods
* accepted currencies
* PCI DSS compliance status
* supported banks for PSD2/Open Banking
* settlement or account identifiers
* technical integration parameters
* applicable fees
* transaction limits
The technical section may include URLs, callback endpoints, payment capture delay settings, authorization type, API client ID, and API credentials.
Use Shop Settings when you want to understand how a shop is configured or when you need to request a configuration change that affects how the shop operates.
{% hint style="info" %}
PCI DSS compliance status shows whether the Merchant is compliant. API integration is unavailable for non-compliant Merchants.
{% endhint %}
***
### Request configuration changes
Where permitted, you can submit change requests from Shop Settings.
Typical requests may include:
* adding or modifying settlement accounts
* changing technical endpoints such as callback URLs
* requesting additional payment methods or service features
* other supported configuration changes
Submitted requests are sent for review and do not take effect until they have been approved and activated by the Customer according to internal compliance, risk, regulatory, and operational procedures.
You cannot unilaterally change agreement terms, fees, limits, or regulated service parameters from the Merchant Portal.
Track submitted requests in [**My Requests**](/guides/merchant-portal/manage-your-account/my-requests.md).
***
### Checkout customization
If checkout customization is enabled for your account, you can use it to adjust the look and presentation of [Hosted Checkout](/integration/hosted-checkout.md).
Available options may include branding, colours, fonts, button style, language preferences, and how payment methods are displayed. Preview is available so you can review changes before applying them. Checkout customization changes only the visual presentation of the page; it does not change payment logic, authentication, fraud controls, or settlement behaviour.
See [**Customize your checkout**.](/guides/merchant-portal/customize-your-checkout.md)
Settings differ between Sandbox and Production - see [Sandbox and Live are separate environments](/guides/merchant-portal.md).
***
### When a setting is not available
If you cannot change a setting directly, it usually means one of three things:
* the setting is managed at the agreement or Customer level
* your user role does not include access to that action
* the change requires review and approval before it can take effect
In those cases, the Merchant Portal may still let you view the configuration and submit a request.
***
### Best practices
Review Settings whenever you:
* activate a new shop
* change a callback or integration endpoint
* add a new payment method or service
* check why a setting differs between Sandbox and Production
* confirm transaction limits, fees, or payment-method availability before going live
If you manage multiple shops, check the selected shop before making assumptions about configuration. Settings are shop-specific and may differ from one shop to another.
***
### Frequently Asked Questions
Why didn’t my change take effect immediately?
Changes that affect shop configuration, payment methods, or other agreement-controlled parameters may need approval before they become active.
---
# 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.ecommerce.seb.ee/guides/merchant-portal/manage-your-account/settings.md?ask=&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.
