Compliance
Watenga operates as a payment facilitator across African markets. Merchants integrate as sub-merchants in our ledger — we hold the banking and card network relationships; you own customer relationships and fulfilment.
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.
Topics
PCI SAQ-A
Eligibility when using Watenga.js and COPY&PAY — card data never touches your servers.
PayFac model
How Watenga is merchant of record and you operate as a sub-merchant in our ledger.
Markets & regulation
Per-country status, regulatory bodies, currencies, and KYC requirements.
PayFac at a glance
- Watenga is merchant of record with NMB, Visa, Mastercard, and Zimswitch (Zimbabwe first).
- Sub-merchant identities are not exposed to NMB — aggregate settlement only.
- Card statements use descriptor
WATENGA*<suffix>per transaction. - KYC, AML, fraud, and chargeback recovery are platform-managed with merchant cooperation.
Canonical security policies
Full policies for procurement and audits live in the repository Docs/Security/ directory. Summaries on this site link to those documents — request PDF exports from security@watenga.africa.
- Information Security Policy
- Data Protection & CDPA (Zimbabwe)
- Incident Response Plan
- Access Control Policy
Status page: status.watenga.africa