sc-doku

# /sc-doku — DOKU Checkout + MCP ## Language Reply in the user's language unless they request another language. ## Dashboard fields — do not interchange them Open `https://dashboard.doku.com/bo/developer/api-keys` (**Developer → API Keys**). Current DOKU Dashboard may show four related surfaces: - **Client ID** — merchant/brand identifier used by Checkout/REST and DOKU MCP. Current public examples include `BRN-...`; older examples also use `MCH-...`. - **Secret Key** — Checkout/Non-SNAP payment signing secret. Pair this with Client ID for DOKU Checkout. - **API Key** — DOKU MCP credential when MCP access is enabled. Pair this with Client ID for DOKU MCP; SC stores it under the internal key `DOKU_MCP_API_KEY`. - **SNAP settings** — separate advanced Direct API setup. SNAP can require OAuth tokens, client secret, and RSA public/private keys; it is not required for ordinary DOKU Checkout. ## Environment boundary — production and sandbox are different credentials - **Production Dashboard:** `https://dashboard.doku.com/bo/developer/api-keys` → Developer → API Keys. Credentials copied here belong to production and must not be stored in a connection labelled sandbox. - **Sandbox:** register/login at `https://sandbox.doku.com/bo/sandbox-registration` and use the Sandbox Client ID + Sandbox Secret Key issued there. Sandbox and production credentials are separate. - Keep SC connection labels explicit, for example `app-checkout-sandbox` versus `app-checkout-production`. Never infe...