> For the complete documentation index, see [llms.txt](https://docs.payengine.co/developer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payengine.co/developer-docs/master.md).

# Overview

Payments Platform Documentation

### Introduction

This payment gateway platform enables any Vertical Market SaaS company to offer payments solutions to their customers, without the headache, hassle, or cost of doing so.

Due to the nature of all the business layers involved for software vendors that serve vertical markets, it's important to understand all the layers that this technology serves. The following image illustrates the relationship between the three distinct layers that a payments solution would need to account order to provide a seamless experience for all the players involved.

![](https://2556322805-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MRlN2yYeruyG-6M2wZN%2F-MRp3I-Qd3yv5KTxeXtI%2F-MRp3zQT4UIv3Ejpk-Nw%2FScreen%20Shot%202021-01-24%20at%207.47.02%20AM.png?alt=media\&token=75a21c1a-6c54-4f11-8918-a4c8f68c74ac)

This document is split into multiple sections, each representing a lifecycle phase related to your merchants' payment processing journey.

1. New Merchant Onboarding
2. Processing Payments
3. Reporting


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.payengine.co/developer-docs/master.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.