Loka Pay brings Nigeria’s leading payment gateways together in one WordPress plugin. Connect one or several providers, manage every transaction from a single dashboard, and take payments through WooCommerce, popular LMS and membership plugins, or your own payment forms.

Supported payment gateways

Paystack
Flutterwave
Monnify
Interswitch (WebPAY)
Remita
OPay
Squad
Paga
Bachs

You need a merchant account with each gateway you enable. Loka Pay does not process payments itself — it connects your site to the provider you choose.

Features

Payment forms — build as many forms as you need with the drag-and-drop builder (text, email, phone, dropdowns, radio buttons, checkboxes, amounts and more). Each form has its own shortcode, and customers’ answers are saved with each transaction. Dropdown and radio options can carry a price, for example “Gold — ₦5,000”.
Payment links — shareable, hosted payment pages with optional usage limits and expiry dates.
WooCommerce — a full payment gateway with order sync and refunds.
Subscriptions — recurring billing with automatic retries and dunning emails.
Invoices — create, send and download invoices as PDFs.
Customer portal — customers can view their payments, invoices and subscriptions with [loka_pay_account].
Refunds — issue full or partial refunds from the transaction screen.
Split payments — revenue sharing for LMS instructors and marketplace vendors, using Paystack and Flutterwave sub-accounts.
Smart routing — send each payment to the gateway with the best recent success rate.
Fraud screening — rule-based risk scoring with an admin review queue.
Offline bank transfers — record and approve manual bank payments.
Webhook monitoring — signature-verified webhooks with health tracking and an automatic retry queue.
Analytics and reports — revenue, success-rate and gateway charts, plus CSV export.
Email notifications — receipts, invoices, failed-payment and renewal emails.
Test mode — use each gateway’s sandbox keys before going live.
White-label — rebrand the admin screens through filters.

Integrations

Loka Pay adds a payment option to these plugins when they are active:

WooCommerce
LearnDash, LifterLMS, Tutor LMS, LearnPress
Paid Memberships Pro, MemberPress, Restrict Content Pro
The Events Calendar, Event Espresso, WP Event Manager
Dokan, WC Vendors
Page builders: Block Editor, Elementor, Divi, Beaver Builder

Shortcodes

[loka_pay_form id="123"] — a form built in Loka Pay Forms (copy the shortcode from the forms list).
[loka_pay_form] — a simple name, email and amount form.
Optional attributes: amount (fixed amount in Naira), gateway, redirect, title, button_text.
[loka_pay_account] — the customer portal.
[loka_pay_status] — a payment status lookup.

External services

Loka Pay relies on third-party payment gateways to take payments. It connects only to the gateways you enable. No data is sent to a gateway until you enable it in Loka Pay Gateways and enter your own API keys. In Test Mode, the gateway’s sandbox address is used instead of the live one.

Customers enter card and bank details on the gateway’s own payment page, so those details never pass through your site. Every request to a gateway is authenticated with the API keys you entered. Each gateway also sends payment notifications (webhooks) to your site’s webhook URL.

Paystack

Provided by Paystack Payments Ltd. Used to take, verify and refund payments, charge subscription renewals and set up split payments.

When a customer pays with Paystack, the plugin sends the transaction reference, amount, currency, the customer’s email address and name, and your site’s return URL to https://api.paystack.co/transaction/initialize.
After the customer returns, or when a webhook arrives, the payment is checked at https://api.paystack.co/transaction/verify/{reference}.
When you issue a refund, the transaction reference and refund amount are sent to https://api.paystack.co/refund.
When a subscription renews, the customer’s email, the amount, currency, reference and the saved Paystack authorization code are sent to https://api.paystack.co/transaction/charge_authorization.
When you set up split payments for a vendor or instructor, their business name, settlement bank, account number and percentage share are sent to https://api.paystack.co/subaccount, and the split rules to https://api.paystack.co/split.
Terms of Service, Privacy Policy

Flutterwave

Provided by Flutterwave Inc. Used to take, verify and refund payments, charge subscription renewals and set up split payments.

When a customer pays with Flutterwave, the plugin sends the transaction reference, amount, currency, the customer’s email address, name and phone number, and your site’s return URL to https://api.flutterwave.com/v3/payments.
Payments are verified at https://api.flutterwave.com/v3/transactions/verify_by_reference?tx_ref={reference}, and refunds are sent to https://api.flutterwave.com/v3/transactions/{id}/refund.
When a subscription renews, the customer’s email, the amount, currency, reference and the saved card token are sent to https://api.flutterwave.com/v3/tokenized-charges.
When you set up split payments, the vendor’s settlement details and share are sent to https://api.flutterwave.com/v3/subaccounts.
When you turn on US dollar payments, the plugin asks Flutterwave for the current Naira to US dollar rate at https://api.flutterwave.com/v3/transfers/rates (at most every few hours). Only the currencies and an amount of 1 are sent; no customer data.
Terms of Service, Privacy Policy

Monnify

Provided by Moniepoint Inc. Used to take, verify and refund payments.

Requests go to https://api.monnify.com (live) or https://sandbox.monnify.com (test mode).
Your API key and secret key are exchanged for an access token at /api/v1/auth/login.
When a customer pays with Monnify, the transaction reference, amount, currency, the customer’s name and email address, and your site’s return URL are sent to /api/v1/merchant/transactions/init-transaction.
Payments are verified at /api/v2/transactions/{reference}, and refunds are sent to /api/v1/refunds/initiate-refund.
Terms of Service, Privacy Policy

Interswitch WebPAY

Provided by Interswitch Group. Used to take and verify payments.

When a customer pays with Interswitch, their browser is sent to https://webpay.interswitchng.com/collections/w/pay (live) or https://sandbox.interswitchng.com/collections/w/pay (test mode), with the transaction reference, amount, currency, the customer’s name and email address, your merchant code and pay item ID, and your site’s return URL.
The payment is then verified by sending the reference and amount to https://webpay.interswitchng.com/collections/api/v1/gettransaction.json (live) or https://sandbox.interswitchng.com/collections/api/v1/gettransaction.json (test mode).
Terms of Use, Privacy Policy

Remita

Provided by SystemSpecs Ltd. Used to take and verify payments.

Requests go to https://login.remita.net/remita (live) or https://remitademo.net/remita (test mode).
When a customer pays with Remita, the transaction reference, amount, the payer’s name, email address and phone number, and your site’s return URL are sent to /ecomm/split/payment/init. The customer then completes payment at /ecomm/finalize.reg.
Payments are verified at /ecomm/split/payment/query/{RRR}.
Terms and Conditions, Privacy Policy

OPay

Provided by OPay Digital Services Ltd. Used to take and verify payments.

Requests go to https://api.opayweb.com (live) or https://sandboxapi.opayweb.com (test mode).
When a customer pays with OPay, the transaction reference, amount, currency, the customer’s name, email address and phone number, and your site’s return URL are sent to /api/cashier/initialize.
Payments are verified at /api/cashier/query.
Terms of Service, Privacy Policy

Squad

Provided by HabariPay Ltd. Used to take, verify and refund payments.

Requests go to https://api-d.squadco.com (live) or https://sandbox-api-d.squadco.com (test mode).
When a customer pays with Squad, the transaction reference, amount, currency, the customer’s name and email address, and your site’s return URL are sent to /transaction/initiate.
Payments are verified at /transaction/verify/{reference}, and refunds are sent to /transaction/refund.
Terms and Conditions, Privacy Policy (HabariPay Ltd. operates Squad)

Paga

Provided by Pagatech Ltd. Used to take and verify payments.

Requests go to https://www.mypaga.com (live) or https://beta.mypaga.com (test mode).
When a customer pays with Paga, the transaction reference, amount, currency, the payer’s email address and phone number, and your site’s return URL are sent to /paga-webservices/business-rest/secured/collectMoney.
Payments are verified at /paga-webservices/business-rest/secured/getTransactionDetails.
Terms of Service and Privacy Policy

Bachs

Provided by Bachs. Used to take, verify and refund payments.

Requests go to https://api.bachs.io (live) or https://sandbox-api.bachs.io (test mode).
When a customer pays with Bachs, the transaction reference, amount, currency, the customer’s email address, name and phone number (when the form collects one), and your site’s return URLs are sent to /v1/checkout-sessions. The customer then pays on Bachs’s hosted checkout page.
Payments are verified at /v1/checkout-sessions/{checkout_id}, and refunds are sent to /v1/refunds.
Merchant Terms of Service, Privacy Policy

Documentation links

The Gateways screen links to each gateway’s developer documentation (for example https://paystack.com/docs/api/ and https://developers.remita.net/). These pages open only when you click them, and no data is sent.

Loka Pay does not send any data to Danovate Solutions Ltd. or to any other third party, and includes no tracking.

Third-party libraries

Chart.js v4.5.1 — MIT License. Bundled as assets/js/vendor/chart.min.js. Unminified source: https://github.com/chartjs/Chart.js/tree/v4.5.1