# Roles and Participants

City Protocol's payment domain scopes permissions and data access around participant identities, ensuring clean separation between merchants operating on the same platform.

<table><thead><tr><th width="175.96875">Role</th><th width="163.33984375">Scope</th><th>Description</th></tr></thead><tbody><tr><td><strong>Merchant (Participant)</strong></td><td>Checkout &#x26; Settlement</td><td>Creates checkout sessions, queries payment status, and receives settlement proceeds. Identified by a unique <code>participantCode</code>.</td></tr><tr><td><strong>Buyer</strong></td><td>Payment</td><td>The end user who fulfills a checkout session by sending crypto to the designated address. No SDK integration or account is required on the buyer side.</td></tr><tr><td><strong>Platform Integrator</strong></td><td>SDK &#x26; Configuration</td><td>Holds the <code>clientId</code> and <code>clientSecret</code> used to initialize the <code>McePaymentClient</code>. Manages API credentials, environment configuration, and may operate on behalf of one or more participants.</td></tr></tbody></table>


---

# 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://city-protocol.gitbook.io/docs/neofinance-as-a-service/payment-module/roles-and-participants.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.