innbucks-integrationlisted

# InnBucks Merchant API InnBucks is a Zimbabwean mobile wallet. The Merchant API is **code-based**: the merchant's server **generates a code**, shows it (digits + QR + deep link), the **customer pays against it** in the InnBucks app or on USSD `*569#`, and the server **asks** whether the code is paid. No callbacks are documented. Agents also move cash in and out (withdrawal codes, deposits, bank change). Money moves, so correctness beats speed: most rules below exist because breaking them charges 100x too much, pays out cash that was never claimed, or credits a deposit twice. This skill knows exactly what the InnBucks guide at https://67even.github.io/innbucks-merchant-api-integration/ knows (InnBucks Merchant API document v1.2.1, reviewed 22 Sep 2026). The `references/` files are generated from that guide. InnBucks' own documents are under NDA and are not included: when the user has them, they are the contract. ## 1. Setup and authentication 1. **Credentials come from InnBucks** at merchant onboarding: an **API key**, a **username** and a **password**, plus a private **base URL** per environment (test, production). There is no public sandbox or portal. Walk a newcomer through `references/onboarding.md` (test app, test funds, business administrator, merchant vs agent capabilities). 2. **Two credentials on every call:** `X-Api-Key: <key>` on **every** request, login included, and `Authorization: Bearer <accessToken>` on every request **except** login. 3. **Logi