Watenga

Migrate from Flutterwave

Replace Flutterwave Rave redirects and direct charge APIs with Watenga.js embedded checkout and platform webhooks.

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

  • Inventory Flutterwave payment methods in use (cards, mobile money, bank transfer).
  • Map Flutterwave tx_ref to Watenga checkout idempotency keys.
  • Remove client-side secret keys — Watenga secret keys stay server-side only.

Concept mapping

FlutterwaveWatenga
Rave Standard / InlineWatenga.js widget (embedded)
vbvsecurecode / 3DSCOPY&PAY 3DS inside iframe
SubaccountsPayFac sub-merchant ledger
TransfersPayouts from Watenga balance
Virtual accountsNot applicable in v1 PayFac model

API mapping

FlutterwaveWatengaNotes
POST /paymentsPOST /v1/checkout/create—
GET /transactions/:id/verifyGET /v1/checkout/:id/status—
POST /transactions/:id/refundPOST /v1/transactions/:id/refund—
POST /transfersPOST /v1/payouts/request—
GET /transfersGET /v1/payouts—
POST /beneficiariesPOST /v1/merchant/bank-accounts—
POST /virtual-account-numbersNot applicablePayFac aggregate settlement
POST /subscriptionsPOST /v1/subscriptions—
POST /payment-plansPOST /v1/subscriptions/subscription-plans—
POST /mobile-moneyWatenga.js wallet tabUSSD push in-widget
vbvsecurecode (3DS)COPY&PAY 3DSHandled inside EFT PAY iframe
Rave redirectWatenga.js embeddedCustomer stays on merchant site

Webhooks

Flutterwave charge.completed maps to payment.capture.completed. See the webhook guide for signature verification and retries.

Embedded vs redirect

Watenga.js keeps customers on your site — no redirect to a hosted Rave page. See Watenga.js overview and integration paths.

Go live