> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/changelog/legacy-changelog/uae-etisalat-channel-reopen-with-new-flow.md).
# UAE Etisalat Channel Reopen With New Flow
We are excited to announce UAE Etisalat Channel reopen with undergoes significant changes and provide more flexibility in transaction limits and payment processes.
## Details of Changes:
### **Transaction Limits**
Previous Minimum Amount: AED 5\
Previous Maximum Amount: AED 300\
Previous Other Limit: AED 1,000/Day/MSISDN\
**New Minimum Amount**: 0.50 AED \
**New Maximum Amount**: 1,000 AED 
### **Transaction Expiry**
Previous Expired Time: 20 minutes\
**New Expired Time:** 90 minutes 
## **Payment Flow**
Previous Payment Flow: Insert Etisalat and OTP
### **New Payment Flow**:
Users will be redirected to the Etisalat webpage, where they will be prompted to enter their mobile number and PIN for transaction authentication. 
## **Implementation**
The new changes will be effective from 7th Aug 2023. Merchants who integrated the UAE Etisalat Channel will automatically experience the updated transaction limits and payment flow.
For any further information or inquiries, please contact our support team.
---
# 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.coda.co/changelog/legacy-changelog/uae-etisalat-channel-reopen-with-new-flow.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.
