> ## Documentation Index
> Fetch the complete documentation index at: /llms.txt
> Use this file to discover all available pages before exploring further.

# Support & Community

> How to reach the SohoPay team, response-time expectations, and where the community lives.

When something breaks or the docs don't answer your question, email support with the staging environment, the `paymentId` or borrower id, and the error code.

## Support channels

### Email

For account issues, integration questions, and anything involving private data:

* **`support@sohopay.ai`**

Put the environment (staging), the failing call, and the `paymentId` or borrower id in the first message.

### Slack (beta integrators)

Beta integrators get a shared Slack channel with the SohoPay engineering team — the fastest channel for integration questions and the place where incidents and maintenance windows are announced. Request an invite from the Dashboard (`https://staging.sohopay.ai`) under **Settings → Support → Request Slack invite**.

### GitHub

SDK bugs, documentation fixes, and feature requests belong in the open:

* Organization: [github.com/sohopay](https://github.com/sohopay)
* Signing bugs belong on `sohopay-agent-signer`. Facilitator bugs belong on `sohopay-backend`. Docs bugs belong on `sohopay-docs`.

> [!TIP]
>
> Not sure whether a merchant failure is your client or the API? Reproduce capture with cURL. If cURL fails too, email support with the `paymentId`.

### Office hours

The team runs weekly office hours for beta integrators — bring integration questions, architecture reviews, or anything that's easier live.

> [!NOTE]
>
> The office-hours schedule is announced in the beta Slack channel each week. If you're not in Slack yet, request an invite from the dashboard first.

### Community examples

The examples in [SDK examples](/sdks/examples.md) are the merchant capture call and the agent signer. Merchant demo apps live in the SohoPay GitHub organization.

## Response times

Staging is the integration environment. The table below is not a production uptime commitment. See [Service expectations](/compliance/sla.md).

| Severity | What to send | What to expect |
| - | - | - |
| Payments stuck, suspected key leak | `paymentId` or borrower id, and `SECURITY` in the subject if it is a key | A human reply. Revoke the merchant API key or the agent before you wait. |
| Integration questions | The call you made and the error code | A reply when the team is available. There is no published one-hour or eight-hour guarantee. |

> [!WARNING]
>
> For a suspected key leak, email **`support@sohopay.ai`** with `SECURITY` in the subject, and revoke the agent or the merchant API key. See [Key management](/guides/key-management.md).

## Before you file a ticket

A quick self-serve checklist that resolves most reports:

* **Error responses** — look the code up in the [error reference](/api-reference/errors.md); most codes have a specific recovery step.
* **Common failures** — [Troubleshooting](/help/troubleshooting.md) covers prepare errors, capture rejects, and a poll that stays `CREATED`.
* **Concept questions** — check the [FAQ](/help/faq.md) and [Glossary](/help/glossary.md).
* **"Is it me or is it down?"** — the maintenance window and any active incidents are posted in the beta Slack channel.

## Next steps

> [card] [Troubleshooting](/help/troubleshooting.md)
>
> Fixes for the most common integration failures.

> [card] [FAQ](/help/faq.md)
>
> Short answers to the questions everyone asks.

> [card] [SLA](/compliance/sla.md)
>
> Uptime targets, maintenance windows, and support commitments.
