Migration guides

Move from another African payment provider to Watenga without rewriting your entire commerce stack. Each guide maps concepts, API endpoints, webhooks, and go-live checklists.

Not legal advice

This documentation summarizes Watenga's integration and compliance posture for developers and merchants. It does not constitute legal, tax, or regulatory advice. Canonical policies live in our security documentation repository. Consult qualified counsel for jurisdiction-specific obligations.

Before you switch

Create a Watenga merchant account and complete KYC in the compliance wizard.
Register API apps in the Developer Console — use sk_test_ keys in sandbox first.
Configure webhooks for payment.capture.completed and payout events (see Webhooks).
Run parallel settlement for one billing cycle before cutting over production traffic.
Update statement descriptors to the WATENGA*<suffix> format (max 22 chars).

Provider guides

Effort: Medium

From Paystack

Map Paystack transactions, subaccounts, transfers, and webhooks to Watenga checkout and PayFac ledger.

Read guide →

Effort: Medium

From Flutterwave

Replace Rave redirects with embedded Watenga.js and align payouts with Watenga balance withdrawals.

Read guide →

Effort: Low–Medium

From Paynow / Zipit (Zimbabwe)

USD/ZWG duality, Zimswitch local cards, and EFT PAY COPY&PAY for international brands.

Read guide →

API version

Watenga pins API versions per app. See API versioning before upgrading production keys.