Support¶
Whom to contact when something goes wrong, and what to prepare. Time: 2 minutes.
Where to go¶
To be announced
The developer support channel (e-mail, chat, tickets) and its response times (SLA) are not settled yet — they will be announced on this page. Until then, use the contract and registration channel you have with Gerege.
Check these yourself first:
- Error codes — what each
codemeans, what to do, whether to retry. - The console's «Deliveries» — webhook status, last HTTP code, error (Local webhooks).
- FAQ.
What to put in a request¶
| What | Example |
|---|---|
| Environment | test or live |
| The key's client id (not secret) | gk_live_… / gk_test_… or mapp_… / mapp_test_…; the key's name |
| Object ids | pi_… (intent), re_… (refund), evt_… (event), st_… (settlement), a webhook endpoint's id, a terminal's code |
| The request | method, path (POST /api/v1/miniapp/payment-intents), HTTP status, the answer's code |
| Request id | the answer's X-Request-Id header, if present |
| Time | with a time zone (2026-10-27T09:00:00+08:00 or UTC Z) |
| What you expected, what happened | briefly |
Never send¶
- A key's secret (
gks_live_…,gks_test_…,gma_cs_…), the webhook secret (whsec_…), access / refresh tokens (gma_at_…,gma_rt_…), launch codes (gml_…) — not even in a screenshot or a log excerpt. If you have sent one, revoke and replace it at once. - People's personal data (name, registration number, phone, account). Naming a payment by its
pi_…is enough.
Security issues¶
If you find a vulnerability in the platform (an attack, a possible data leak), do not post it publicly — report it privately through the support channel. A mini app must report a security breach of its own app to the operator within 24 hours (Review requirements).
Status and changes¶
- A platform status page — coming soon.
- Every version's changes are in the Changelog. A minor version only adds — ignore fields and events you do not know (API conventions).