| API app | A set of keys in the developer console: a publishable key, a secret key, restricted keys and webhook endpoints, in test or live mode, pinned to an API version. |
| Secret key (sk_test_, sk_live_) | Your server’s key: full access to the merchant API. Never in a browser, an app or a repository. |
| Restricted key (rk_) | A key with one scope per resource (none, read or write), for a system that needs only part of the API. It can expire. |
| Publishable key (pk_) | The key a browser or app uses to show the checkout. It can only pay a checkout session, a payment link or an invoice; it never decides an amount. |
| Test mode | What a test key does: payments run on the sandbox driver, never move money, and are marked livemode: false. |
| Checkout session | A payment your server prepared (amount, currency, reference). The customer pays it on its hosted page, with Watenga.js or in a mobile sheet using its client_secret. |
| Transaction | A payment or refund, with its status, amounts, fees and your metadata. |
| Merchant transaction id / reference | Your own order number on a payment; checkout.create is idempotent on it. |
| Metadata | Your key-value pairs on an object, returned as you set them and in its webhooks. |
| Idempotency-Key | A header that makes a write safe to repeat: the same key answers the first result for 24 hours. |
| Webhook endpoint | An HTTPS address that receives signed events, with its own events and signing secret. |
| Watenga-Signature | The header on every delivery: t=<unix time>,v1=<HMAC-SHA256 of "<t>.<raw body>">, one v1 per secret while a secret rotates. |
| Listen session | A short-lived endpoint the CLI polls (watenga listen) to forward your test events to your machine. |
| API version | A date (2026-10-29) that fixes response shapes. Your app is pinned to one; Watenga-Version changes it per request. |
| Cursor | An opaque value (next_cursor) you pass back as cursor for the next page of a list. |
| Checkout Studio | Where a business designs its checkout; the same design is drawn by hosted pages, Watenga.js and the mobile sheets. |
| Mobile money | A wallet payment confirmed by the customer on their phone (a USSD or app prompt); pending until they approve. |
| Test clock | Your account’s simulated time in test mode, to run renewals, trials and overdue invoices without waiting. |
| Payout | Money sent from your Watenga balance to your bank: dashboard-only, with two-step verification. |
