Official SDKs
Watenga ships official libraries at different maturity levels. Pick a full server SDK for end-to-end API access, or a webhook-verification library to validate incoming events in a language without a full client yet.
Same API, one host
Every SDK talks to
https://api.watenga.africa — there is no separate sandbox host. Test vs live is selected by the key prefix (sk_test_… / sk_live_…). The base URL is configurable via the constructor only.Capability matrix
| SDK | Type | API resources | Webhook verify |
|---|---|---|---|
| Node.js (@watenga/node) | Full server SDK | All resources (checkout, transactions, refunds, customers, invoices, subscriptions, payment links, payouts, account) | Yes |
| PHP (watenga-php) | Full server SDK | At parity with Node.js | Yes |
| Python (watenga) | Minimal server client | checkout.create, transactions (retrieve/refund), list customers/invoices/subscriptions | Yes |
| Go (watenga-go) | Webhook verification library | — | Yes |
| Flutter (watenga_flutter) | Webhook verification library | — | Yes |
| React Native (@watenga/react-native) | In-app mobile payments SDK | Embedded checkout UI | n/a |
All SDKs verify the canonical Watenga-Signature header (t=<unix>,v1=<hmac> over <unix>.<rawBody>, 300-second tolerance). See Webhooks for the event envelope and verification details.