# Process Flow

Below is a high-level view of how a typical request is processed:

1. **Merchant System → Convergegate API**
   * Your system sends an HTTPS request to the Convergegate API using the **Sandbox** or **Production** base URL.
   * The request includes:
     * Required authentication headers (`Authorization` and, if applicable, `Signature`).
     * Required request body parameters for the selected endpoint.
2. **Convergegate** **API Validation**
   * The API validates the authentication credentials.
   * The API validates the structure and content of the request body against the endpoint’s schema.
3. **Processing**
   * The API executes the requested operation (e.g., create a transaction, check status, initiate refund).
   * If applicable, the API communicates with underlying payment networks or services.
4. **Response**
   * A JSON-formatted response is returned with:
     * `status` or `code` indicating success or failure.
     * Relevant data fields (such as transaction ID, status, timestamps).
     * Error details if the request failed validation or processing.

***

**Visual Process Diagram:**

<figure><img src="/files/nMPmXcVXa6gyQHqVcvow" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://developer.convergegate.com/v1/overview/process-flow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.