Payment Integration Services in Nigeria: What They Cover and What They Cost

The difference between a business that has "added Paystack" and one that has integrated payments properly is visible at month-end. The first has a checkout button and a staff member who still opens the bank app to confirm transfers, matches references by hand, and argues with a customer who says they paid. The second has payments confirmed on the server, orders updated automatically, receipts sent without typing, and a reconciliation report that reconciles.

This guide sets out what a payment integration engagement actually covers in Nigeria, the methods your customers will use whether you plan for them or not, the verification and reconciliation work that separates a working integration from a fragile one, what compliance requires, and what it costs.

What payment integration actually involves

Payment integration is more than placing a pay button. A complete engagement covers five jobs, and quotations that only include the first will leave you doing the rest by hand.

• Collection. Presenting the right payment options at the right moment, in a checkout the customer trusts and completes.
• Verification. Confirming server-side that a payment genuinely succeeded and is for the correct amount and reference, rather than trusting what the customer's browser reports.
• Recording. Updating the order, invoice, subscription or student account, and storing the transaction reference against it.
• Notification. Sending the receipt or confirmation to the customer and alerting the team, usually by WhatsApp, SMS or email.
• Reconciliation. Matching what the provider settled into your bank account against what your system says was collected, and flagging the differences.

The fifth job is the one businesses discover late. Collection is a one-week problem; reconciliation is a permanent one, and it is where integration either saves finance staff days each month or does nothing for them at all.

The payment methods Nigerian customers actually use

A Nigerian checkout that only accepts cards will lose sales. Customers choose by what is convenient, what their bank allows that day, and what feels safe with a business they do not know.

The practical rule is to support the two or three methods your customers already use, make them equally prominent, and then measure which ones people complete. Adding a method that nobody in your market uses adds support work and no revenue.

Where payments get integrated

Payment integration work looks different depending on where the customer is paying.

• Website checkout. The classic case: cart, checkout, provider redirect or inline payment, callback, order confirmation. The integration must survive the customer closing the tab and returning.
• Mobile app. The provider's mobile SDK or a secure web view, with the same server-side verification. Note that app stores have their own rules about digital goods and in-app purchases.
• Payment links and invoices. For service businesses that quote by WhatsApp or email. Generating a link per invoice, with the invoice reference embedded, turns an informal request into a matched payment.
• WhatsApp and social selling. The order is agreed in chat, the payment link or virtual account is sent automatically, and confirmation updates the order without anyone checking the bank app.
• Customer portals and accounts. Schools, clinics, gyms, estates and subscription services where a balance sits against an account and payments must reduce it correctly.
• Recurring billing. Mandates, scheduled charges, failed-payment retries, expiry reminders and cancellation handling.
• Payouts and splits. Marketplaces and multi-vendor platforms that must pay sellers, riders or partners, often with a commission split. This is a separate integration from collection and carries its own compliance requirements.

How a payment integration project runs, step by step

The core sequence is: choose the provider, complete onboarding, build in test mode, verify server-side, handle every payment state, reconcile, then go live in a controlled way.

1. Choose the provider and confirm what you need. Check that the specific features you require, such as dedicated virtual accounts, recurring charges, splits or payouts, are available on your account tier.
2. Complete business onboarding early. Providers require business registration documents, a settlement account and identity verification. Start this before development, because approval, not coding, is often the critical path.
3. Design the payment flow on paper. What the customer sees, what is stored before payment, what happens on success, failure, timeout and abandonment.
4. Build against test keys. Simulate success, decline, insufficient funds, network failure and duplicate submission.
5. Verify every payment server-side. Call the provider's verification endpoint, or handle the signed webhook, and compare amount and reference against your own record before delivering value.
6. Make webhooks idempotent. The same notification can arrive more than once. Use the transaction reference to ensure the order is only fulfilled once.
7. Build the reconciliation view. A daily report of transactions in your system versus the provider's settlement, with unmatched items highlighted.
8. Handle refunds and disputes. Decide the process, who authorises it, and how the record is updated.
9. Go live with a limited rollout. One product, one branch or one payment method first, with monitoring, then widen.
10. Document and monitor. Where keys live, who receives failure alerts, and the monthly check of unmatched transactions.

Verification, webhooks and reconciliation

This is the section most business owners skip and most problems come from. It deserves plain language.

Verification means your server asks the payment provider directly, "did this transaction succeed, and for how much?" before you treat the payment as real. A customer's browser can be manipulated; a server-to-server confirmation cannot be, in the same way. Any integration that marks an order paid because the browser returned to a success page is unsafe.

Webhooks are messages the provider sends to your system when something changes: payment successful, transfer received, charge failed, settlement completed. They are how payments get confirmed when the customer has already closed the tab, which happens constantly on mobile. Your endpoint must be publicly reachable, must verify the signature, and must respond quickly and then process, rather than doing slow work before replying.

Reconciliation is the daily or weekly comparison between three things: what your system recorded, what the provider reports, and what reached your bank account. Differences arise legitimately from settlement timing, fees, refunds and chargebacks. An integration that produces a reconciliation report with an "unmatched" list saves finance staff the largest single block of manual work in the whole payment process.

A useful test when reading a quotation: if verification, webhook handling and a reconciliation view are not named as deliverables, the quote is for a pay button, not a payment integration.

What changes for Nigerian businesses

• Transfers are not an afterthought. In many Nigerian businesses, bank transfer is the majority payment method. Dedicated virtual accounts per customer or per order are the difference between automatic matching and a staff member reading transfer alerts.
• Customers send proof of payment. The screenshot habit exists because confirmation has historically been slow. A properly integrated flow that confirms within seconds and sends an automatic receipt reduces the screenshots and the disputes about them.
• Network interruptions mid-payment. A customer on mobile data may lose connection between authorisation and callback. Webhooks plus a "check payment status" action on the order page prevent the double-payment argument.
• Settlement timing. Money in your system today may settle to the bank tomorrow or later depending on the provider and method. Never treat the settlement report and the transaction report as interchangeable.
• Fees are the provider's to publish. Nigerian providers quote their own percentage and cap per transaction, and these change. Confirm current rates directly with the provider before pricing your products, and check how fees are treated for transfers and international cards.
• Naira and foreign currency. If you sell to customers abroad, confirm what the provider supports, how conversion is handled and how settlement works, because this affects both pricing and reconciliation.
• Exchange-rate exposure elsewhere. Hosting and any international tools around your payment stack are billed in US dollars, so your running cost moves even when transaction volume does not.

Compliance and security essentials

Payments attract more obligations than most integrations. The essentials for a Nigerian business:

• Use a provider licensed by the [Central Bank of Nigeria](https://www.cbn.gov.ng/) for the service you need, and confirm current licensing status rather than assuming. Verify requirements with the CBN where you are unsure.
• Keep card data out of your systems. Use hosted checkout or the provider's client-side library so card details never touch your server. This is the practical route to limiting card-security obligations.
• Verify webhook signatures and never expose an endpoint that can mark orders paid without authentication.
• Store transaction references, not sensitive instruments. Keep what you need to reconcile and prove a payment, nothing more.
• Apply the Nigeria Data Protection Act 2023. Payment records contain personal data. Limit who can see them, state the purpose in your privacy notice, and confirm current obligations with the Nigeria Data Protection Commission.
• Register the payment account to the business. Settlement should go to a business account tied to your CAC registration, with the owner's contacts as recovery, not a developer's or a staff member's.
• Plan for fraud checks. Decide your rules for high-value orders, mismatched delivery details and repeated failed attempts, and who reviews them.

This is general guidance, not legal or financial advice. Confirm current requirements with the CBN, the NDPC and your own professional adviser.

Example (hypothetical): an Ibadan school collecting fees

Example (hypothetical): a private school in Ibadan with about 700 pupils collects fees by bank transfer. Parents pay into the school account, send a screenshot to the bursar's WhatsApp, and the bursar matches payments to pupils in a spreadsheet. Each term produces a week of matching, several disputed payments, and a delay before teachers know which pupils are cleared.

The school integrates payments in three parts. Each pupil is issued a dedicated virtual account, so any transfer is matched automatically to that pupil's record. A parent portal shows the balance, part-payment history and a downloadable receipt, and also offers card and USSD options for parents abroad or without a banking app. A webhook updates the school's records the moment a transfer lands, sends the parent an automatic receipt on WhatsApp, and the bursar's screen shows a daily reconciliation of collections against the bank settlement.

The expected effect, from the design rather than a claimed result, is that screenshots stop being the confirmation mechanism, part payments are tracked without a spreadsheet, and the bursar's term-opening week is spent on exceptions rather than data entry. On the indicative bands below, this sits in the ₦1,500,000–₦4,000,000 range, plus the provider's transaction fees and monthly hosting and support.

How much does payment integration cost in Nigeria?

Costs split into three: the build, the provider's transaction fees, and ongoing support. The figures below are indicative 2026 ranges for the build; actual quotes vary with scope, vendor and exchange rate. Transaction fees are set and published by each provider and should be confirmed directly.

When comparing quotations, specify the methods to support, whether virtual accounts and reconciliation are included, whether refunds are handled in the admin panel, and what post-launch support covers. Request two or three written quotes on that identical scope.

Mistakes to avoid

• Trusting the browser callback. Always verify server-side. This is the most common and most expensive payment integration flaw.
• No webhook handling. Without it, payments completed after the customer leaves the page are lost to your system and generate support calls.
• Non-idempotent processing. A repeated webhook that creates a second order or a second credit will be noticed by customers before it is noticed by you.
• Only supporting cards. In Nigeria that excludes a large share of willing buyers.
• Manual transfer with no reference discipline. If customers transfer to a single account with no unique reference, matching cannot be automated and never will be.
• Ignoring failed and abandoned payments. These are recoverable sales. Record them, and follow up with a payment link.
• Starting development before provider onboarding. Documentation delays will hold up go-live more often than code will.
• Keys in the front end or the app bundle. Secret keys belong on the server only.
• No reconciliation report. Without it, finance continues to do the work the integration was supposed to remove.

Conclusion

Treat payment integration as an operations project, not a button. Decide which methods your customers genuinely use, insist on server-side verification and signed webhooks, make processing idempotent, and require a reconciliation view as a named deliverable. Start provider onboarding before development, keep card data off your servers, register the settlement account to the business, and confirm current transaction fees and licensing directly with the provider and the CBN. Done this way, payments stop being a daily checking task and become a record you can trust.

If confirming payments still means opening a banking app or reading screenshots, Linestech can integrate collections, virtual accounts, receipts and reconciliation into your website, app or internal system so money and records stay in step.

Frequently asked questions

Do I need a payment gateway, or can customers just transfer to my bank account?

Direct transfers work, but they cannot be matched automatically, they generate screenshots and disputes, and they give the customer no confirmation. A provider adds automatic confirmation, dedicated virtual accounts that identify the payer, receipts, refunds and a reconciliation trail. If you take more than a handful of payments a week, the gateway pays for itself in avoided admin.

What documents do I need to open a payment provider account in Nigeria?

Providers generally require your business registration from the Corporate Affairs Commission, a business bank account for settlement, identity documents for the owners or directors, and details of what you sell. Requirements differ by provider and account tier, so check their current onboarding checklist before you plan a launch date.

Can I accept payments on WhatsApp?

You can send a payment link or a dedicated virtual account into the chat, and have the confirmation update your order record automatically. The payment itself happens through your provider, not inside WhatsApp. This is the most practical upgrade for businesses that sell in chat, because it removes both the screenshot and the manual confirmation.

How do I handle a customer who was debited but the order did not complete?

Build a "check status" action against the transaction reference so support staff can confirm the true state from the provider. If the payment succeeded and the order did not update, the system should be able to complete it from the reference. Genuine failed charges are usually reversed by the bank within the provider's stated timeline, which you should quote to the customer.

Is it safe to store customers' card details for repeat payments?

Do not store card details yourself. Use the provider's tokenisation or authorisation feature, which returns a reference you can charge again without holding the card number. This keeps sensitive data out of your systems, reduces your security obligations and is the standard approach for subscriptions and repeat purchases.

What is the difference between a transaction report and a settlement report?

The transaction report lists what customers paid, when. The settlement report lists what the provider actually transferred to your bank account, after fees, refunds and any holds, usually on a different date. Reconciliation matches the two, and confusing them is a common cause of a business believing money is missing.

How long does payment integration take?

A hosted checkout on an existing website can be live in a few days once your provider account is approved. Verification, webhooks, receipts and a reconciliation view typically take two to four weeks. Virtual accounts, recurring billing or payouts add further weeks, much of it spent on provider approvals and testing edge cases.

Sources and further reading

Figures, platform rules and regulations change. These are the primary references behind this article and the places to check before you act on it.

• Corporate Affairs Commission (CAC)
• Nigeria Data Protection Commission (NDPC)
• Central Bank of Nigeria (CBN)
• Paystack developer documentation
• MDN Web Docs — web platform reference
• Flutter documentation
• Node.js documentation