> 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/new-channel-announcement-mobily.md).

# New Channel Announcement: Mobily

![:bangbang:](https://codapayments.readme.io/public/img/emojis/bangbang.png)We are excited to introduce "Mobily," our newest payment channel designed exclusively for our users in Saudi Arabia. With the inclusion of "Mobily," we are proud to offer a seamless and convenient payment option with Carrier Billing support.

<figure><img src="https://files.readme.io/5f75ca9-Mobily120_1679642766.png" alt=""><figcaption></figcaption></figure>

***

## Here are some key details about this new payment option:

📱 Carrier Billing Channel: Mobily operates as a carrier billing channel, allowing users to make purchases and pay using Mobily prepaid and postpaid accounts.

💲 Price Point Limit: Allows users to make transactions starting from a minimum price point of SAR 1, up to a maximum price point of SAR 500. Mobily requires publishers to provide denom price list to config in advance. CONTACT Business Development Team for further details.

🔒 Authentication via OTP: Mobily employs One-Time Password (OTP) authentication consisting of 6 digits.

⏰ Transaction Expiry: Please note that transactions made through Mobily have a validity period of 1 minute. Users may complete payment within this timeframe to ensure a successful transaction.

💻 Integration Details: For merchants and developers, please be aware that Mobily integration supports the payment page API. Unfortunately, the Backend API integration for Mobily is not currently available. We appreciate your understanding and cooperation in this matter.

We encourage all our users in Saudi Arabia to take advantage of this new payment channel, leveraging Carrier Billing for a hassle-free and efficient payment experience. By incorporating "Mobily" into our platform, we aim to provide a tailored and reliable payment solution that meets the specific needs of our Saudi Arabian users.

***

## Flow Description

<figure><img src="https://files.readme.io/530b83e-image.png" alt="1\. User selects Mobily as a payment channel"><figcaption><p>1. User selects Mobily as a payment channel</p></figcaption></figure>

<figure><img src="https://files.readme.io/5156f52-image.png" alt="2\. Mobily will send the OTP to the customer’s phone number. User input the OTP and confirm the payment"><figcaption><p>2. Mobily will send the OTP to the customer’s phone number. User input the OTP and confirm the payment</p></figcaption></figure>

<figure><img src="https://files.readme.io/01835e9-image.png" alt="3\. Waiting Mobily return success response"><figcaption><p>3. Waiting Mobily return success response</p></figcaption></figure>

<figure><img src="https://files.readme.io/e1f80ee-image.png" alt="4\. Coda displays success page"><figcaption><p>4. Coda displays success page</p></figcaption></figure>

Should you have any questions or require further assistance regarding Mobily or any other payment-related inquiries, please don't hesitate to reach out to Coda Business Development Manager.

Thank you for your continued support, and we look forward to serving you with Saudi Arabia New Carrier Billing Channel.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coda.co/changelog/legacy-changelog/new-channel-announcement-mobily.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.