> For the complete documentation index, see [llms.txt](https://qosic.gitbook.io/qospay-eng/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qosic.gitbook.io/qospay-eng/overview.md).

# Overview

This document describes how a third party will connect to Mobile Payment interface from QOS-IC. Note that all all data formats and response definitions are in conformance with the REST standard. Here's what you need to do:

1. Create a[ <mark style="color:orange;">QOS account</mark>](https://dashboard.qosic.com/signup), if you haven't already.
2. Test QOS APIs using our sandbox
3. On your dashboard,
   * &#x20;Monitor your transaction in real time
   * &#x20;See all your accounts available balance
   * &#x20;Configure and generate payment links
   * &#x20;Payout to your account
   * &#x20;Subscribe to new services
4. You can accept payment (Collection) by,
   * Creating a payment link and sharing to your customer through email, whatsapp or social media
   * using QOS fast and beautiful Checkout template for fast integration with your website
   * Integrating our simple RESTful API with your website or mobile app to easily accept payment
   * Easily configure QOS wordpress plugin to your Wordpress (Woocommerce) website


---

# 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://qosic.gitbook.io/qospay-eng/overview.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.