> 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/my-requests.md).
# My Requests
Use **My Requests** to submit operational requests that need review and approval. This is the part of the Merchant Portal where authorized users can ask for changes that cannot be applied directly from a settings screen.
### What Requests is for
Requests is the place to use when a change affects your merchant setup, shop configuration, or enabled services and must be reviewed before it becomes active.
Depending on your service scope, requests may include:
* activation of new payment methods
* creation of new shops
* changes to technical endpoints such as callback URLs
* addition or modification of settlement accounts
* other supported configuration changes
Use Requests when the change is part of the approval flow. Use Settings when you are only reviewing configuration or when the setting is directly available to you.
***
### How approval works
Not every change can be applied immediately from the Merchant Portal.
Where approval is required, the request is sent for review and only becomes effective after it has been approved and activated by the Customer according to internal compliance, risk, regulatory, and operational procedures.
This means that a request can be visible in the Portal before the requested change is actually live. Always wait until the request has completed the approval flow before relying on the new configuration.
***
### When to use Requests
Use Requests when you need to ask for a change that is not directly editable in the Portal.
Typical examples include:
* enabling a new payment method or service feature
* creating a new shop
* changing a callback URL or other technical endpoint
* updating settlement account details
* requesting another supported configuration change that requires approval
If the change is already available in [**Settings**](/guides/merchant-portal/manage-your-account/settings.md), manage it there. If it requires review, submit it through **My Requests**.
***
### Track submitted requests
Use **My Requests** to follow configuration or service requests that require review and approval.
This gives you a single place to check whether a request has been submitted and where it sits in the approval process. If the requested change has not taken effect yet, My Requests is the first place to check.
***
### What Requests does not do
Requests is not the place for direct day-to-day payment monitoring.
Use [**Dashboard** ](/guides/merchant-portal/monitor-your-business/dashboard.md)for aggregated performance monitoring, [**Orders** ](/guides/merchant-portal/monitor-your-business/orders.md)for transaction-level investigation, and **Settings** for configuration that is already available to you. Requests is specifically for changes that must be reviewed before they become active.
***
### Best practices
Before submitting a request, make sure you are asking for the right type of change.
A request should clearly match the setting, shop, or service you want to change. If the Portal shows a setting as view-only, centrally managed, or approval-based, use Requests rather than expecting the change to take effect immediately.
***
### Frequently asked questions
Why can't I change this directly?
Some settings are controlled at the agreement or Customer level, and some changes require review and approval before they can take effect. In those cases, the Merchant Portal may let you submit a request instead of changing the setting directly.
Does a request take effect immediately?
No. When approval is required, the request must be reviewed and approved before it becomes active.
Where do I check the status of a request?
Use **My Requests**. It is the section for following configuration or service requests that require review and approval.
What kinds of requests can I submit?
That depends on your service scope, but supported examples include new payment methods, new shops, technical endpoint changes, settlement account changes, and other approved configuration requests.
---
# 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/my-requests.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.
