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

# How MERPI works

MERPI is a direct ticketing platform. That means every business listed on the platform, whether it is a cinema, transport company, event organizer, or hotel, has been onboarded and verified directly by Syticks. There are no third-party aggregators in between.

As a merchant, you connect to this verified inventory through the MERPI API and offer ticket purchasing to your customers, while the MERPI Dashboard gives you full visibility into what is happening on your end.

***

### How a Transaction Flows

{% stepper %}
{% step %}

### **Your customer browses**

Your app or website calls the MERPI API to fetch available experiences, movies, routes, or accommodations and displays them to your customer.
{% endstep %}

{% step %}

### **Your customer selects and purchases**

Your customer picks what they want. Your app calls the relevant MERPI purchase endpoint and the ticket is issued.
{% endstep %}

{% step %}

### **You earn a commission**

For every successful transaction made through your integration, you earn a commission. This is reflected in your MERPI Dashboard in real time.
{% endstep %}

{% step %}

### **You withdraw**

Your earned commissions accumulate in your MERPI wallet. You can withdraw to your registered payout account at any time from the Dashboard.
{% endstep %}
{% endstepper %}

***

### Two Environments

MERPI gives you two separate environments so you can build and test without touching real money or real ticket inventory.

<table data-view="cards"><thead><tr><th align="center"></th><th align="center"></th></tr></thead><tbody><tr><td align="center"><strong>Staging Environment</strong></td><td align="center">For development and testing. Uses test API keys and a test wallet that you fund with dummy money from the Dashboard. No real transactions occur here.</td></tr><tr><td align="center"><strong>Live Environment</strong></td><td align="center">For production. Uses live API keys and a real wallet funded with actual money. All transactions here are real.</td></tr></tbody></table>

{% hint style="info" %}
Always use your Staging API key during development and switch to your Live API key only when you are ready to go to production. Using your Live key during testing will result in real charges.
{% endhint %}

***

### Environments on the Dashboard

You switch between environments using the toggle at the top of your Dashboard. Everything you see, your wallet balance, transaction history, API keys, reflects the environment you are currently in.

<figure><img src="/files/LGvxRFqKe0MyP1ECN8gY" alt="Dashboard Environment toggle on MERPI By Syticks"><figcaption></figcaption></figure>

***

### Commissions

Every ticket category on MERPI carries a commission that you earn on each successful transaction. Commission rates are agreed on a per-merchant basis and are not publicly listed.

{% hint style="info" %}
To discuss commission rates for your integration, reach out to us at <hello@syticks.com>. Our team will walk you through the structure for each ticket category you want to offer.
{% endhint %}

***

### What's Next

With an understanding of how MERPI works, the next step is to create your merchant account, get your API keys, and fund your test wallet so you can start building.

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><strong>Getting Started</strong></td><td align="center">Create your account, get your API keys, and fund your test wallet</td><td><a href="/pages/ZNCIZZctsCFVuzhyQrsD">/pages/ZNCIZZctsCFVuzhyQrsD</a></td></tr></tbody></table>


---

# 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://syticks.gitbook.io/merpi-by-syticks/how-merpi-works.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.