Watenga

Migrate from Paynow / Zipit (Zimbabwe)

Zimbabwe merchants often combine Paynow redirects, Zipit, and manual USD/ZWG handling. Watenga unifies card, Zimswitch, and mobile wallet flows in a single embedded widget.

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

  • Decide default checkout currency per product — USD and ZWG are never mixed in one transaction.
  • Replace redirect URLs with Watenga.js on your checkout page.
  • Register webhook endpoint for async wallet and card confirmations.

Payment flows

  • International cards (Visa/Mastercard/Amex)— EFT PAY COPY&PAY iframe via Watenga.js Card tab. PCI SAQ A eligible when you do not touch PAN data.
  • Zimswitch local cards — Zimswitch tab in Watenga.js; routed by card brand per gateway auto-routing rules.
  • EcoCash / InnBucks / OneMoney — Mobile wallet tab; USSD push without leaving your site.

USD vs ZWG

Pass currency: "USD" or "ZWG" on checkout create. Settlement and descriptors follow your sub-merchant configuration. See Zimbabwe regulatory page.

Statement descriptors

Card statements show WATENGA*YOUR_SUFFIX (22 characters max). Configure suffix in merchant settings during onboarding.

Testing

Use sandbox test cards and test mobile numbers from the Testing & sandbox guide.

Go live

  • RBZ SI 80/2020 readiness — complete compliance wizard and UBO screening.
  • CDPA 2021 — data processing described in security policies.
  • Reserve: 5% held 90 days on card volume (platform default).

Engineering reference

Internal EFT PAY / Zimswitch integration details are documented in the repository EFT PAY Integration Deep Dive for gateway engineers — not required for standard Watenga.js integrations.