Updated
Accept Payments
Connect a payment provider to DataRadius so subscribers can pay for hotspot and PPPoE plans directly.
Connecting a payment provider
Go to Settings → Payments in the DataRadius dashboard. Select your payment provider and enter the credentials it requires. Each provider has its own setup:
- M-Pesa — requires your Safaricom Daraja API consumer key, consumer secret, online passkey, and business shortcode.
- Paystack — requires your Paystack secret key (found in your Paystack dashboard under Settings → API Keys).
- Flutterwave — requires your Flutterwave secret key and encryption key.
- Stripe — requires your Stripe secret key.
Detailed setup instructions for each provider are shown in the dashboard when you select it.
Enter your credentials and click Save. DataRadius validates them immediately — if they are valid, the status changes to Connected. If they are invalid, you get an error with the specific response code.
What happens after saving
Once credentials are validated, DataRadius automatically:
- Registers callback URLs with your payment provider. You do not need to configure webhook URLs manually.
- Refreshes authentication tokens as needed.
- Starts processing payments for any billing plans you create.
How payment collection works
When a subscriber selects a plan on the captive portal and provides their payment details, DataRadius initiates the payment with your provider. For mobile money providers, this sends a payment prompt to the subscriber's phone. For card providers, the subscriber enters their card details on a hosted payment page.
On success, DataRadius activates the subscriber on the router (or renews the PPPoE subscription) within seconds.
Subscribers can also pay directly through their mobile money app or bank. DataRadius receives the callback, matches the payment to a subscriber, and activates or extends their service automatically.
Testing with sandbox credentials
Most payment providers offer a sandbox environment with test credentials. To test:
- Obtain sandbox credentials from your payment provider's developer portal.
- In DataRadius, toggle the environment to Sandbox before entering credentials.
- Save and trigger a test payment from the dashboard.
- Verify the callback arrives and the test subscriber is activated.
Once satisfied, switch to Production, enter your real credentials, and save. DataRadius re-registers callback URLs for the production environment automatically.
Reconciliation
Every payment processed through DataRadius is logged with the provider receipt number, subscriber identifier, amount, timestamp, and plan. The payment history in Payments → History matches your provider statement — there is nothing to reconcile manually.
Revenue figures on the dashboard update in real time from confirmed callbacks. Export payment data as CSV at any time from Payments → Export.
Security
DataRadius encrypts your payment credentials at rest. Credentials are never logged, never included in error messages, and never exposed in API responses. Only the connection status (Connected/Error) is visible in the dashboard.
Callback endpoints validate request signatures and enforce rate limits. Duplicate callbacks (same receipt number) are deduplicated — a subscriber is never double-charged or double-activated.