Nigeria software delivery: payments, phone sign-in and a state-by-state rollout

OutsourcingVN is operated by Netbase JSC, so this guide is written by a supplier that would like your project. It rests on a Nigeria platform Netbase has built, two related West African records and official Nigerian references for the payment and data questions. The guides index lists the guides for other markets.

Contents

• What makes a Nigeria-facing build different?
• What did Netbase build for a Nigerian directory platform?
• Who owns each payment state?
• How should you test the provider boundary?
• Worked scenario: a pending payment that arrives twice
• Which questions should you ask a supplier?
• What usually goes wrong?
• How this guide is sourced and where it stops
• Common questions
• Plan the first release

What makes a Nigeria-facing build different?

Four design choices come up in almost every Nigeria-facing brief, and each changes what has to be tested.

• Payments through two providers. Buyers often integrate a second provider for resilience or coverage. That doubles the events to reconcile and raises the question of which provider's message is authoritative.
• Phone-first identity. Phone one-time-password sign-in is common, which makes SMS delivery part of the sign-in journey rather than a notification detail.
• Messaging with a fallback. Business messaging apps reach many users, but a message still needs a fallback route, often SMS, when the first channel fails.
• A staged geographic rollout. Launching in one state and scaling to others means configuration, administrators and reporting must work per state from the start.

The Central Bank of Nigeria publishes payment-service-provider categories and licensee lists, and the Nigeria Data Protection Commission publishes the Nigeria Data Protection Act 2023. Your commercial and legal advisers use those sources to choose providers and set data rules; engineering turns their decisions into states, fields and access rules.

What did Netbase build for a Nigerian directory platform?

For Dey Page, Netbase built a multi-state business directory in Nigeria, designed to launch in one state and scale to all 36. The registered scope maps directly onto the four choices above.

• Payments: featured-listing and badge subscriptions through two payment providers.
• Identity: phone one-time-password accounts.
• Messaging: business messaging with SMS fallback, plus click-to-chat from listings.
• Rollout: state, city and category pages, and five administrator roles with per-state dashboards.
• Field verification: a location-confirmed badge verified in the field with geotagged photos, identity capture, offline sync, a head-office review queue, 12-month expiry and an audit trail. Field capture runs in the mobile web app.
• Mobile: a cross-platform app with consumer and business-owner modes, push, deep links and in-app browser checkout, on a 12-week web and mobile plan.

The multi-state business directory record describes the built scope. It reports scope only: no public launch, app-store availability or user numbers are claimed.

Two related records add context. Netbase has built Magento stores with companion Android and iOS apps for an omnichannel fashion retailer in Nigeria, and an English-first multi-vendor marketplace for West Africa with vendor approval, commission deductions, payout requests and 90 days of post-launch support, described in the RB Marketplace and shopping app record.

Who owns each payment state?

Write the states down before choosing an integration, and give each one a single owner. The table assumes a subscription such as a featured listing.

The rule that matters most: "the provider accepted a request" and "the business may release the benefit" are different states. Keep them apart even when a demonstration would look simpler with one.

Worked scenario: a pending payment that arrives twice

A business owner in the launch state buys a featured listing and pays through the second provider. The browser returns to the app before the provider confirms.

1. Pending. The app shows "payment being confirmed" and stores the provider reference. The listing is not yet featured.
2. Status check. No notification arrives within the agreed window, so a scheduled check queries the provider, which reports success.
3. Activation. The subscription becomes active with a 12-month expiry, and a confirmation goes out by business messaging, with SMS as the fallback.
4. Duplicate event. Ten minutes later, the provider's own notification arrives for the same payment. Because processing is keyed to the provider reference, the system records the event and changes nothing.
5. Reconciliation. The next day, finance compares the provider report with orders. The payment appears once and matches one active subscription.
6. Support. If the owner calls during step 1, the agent sees "pending, second provider, reference recorded" instead of guessing.

Every step names a record and an owner. A proposal that cannot describe steps 2, 4 and 5 has not yet scoped payments.

Which questions should you ask a supplier?

• Which provider's event is authoritative for each state? A good answer names the event and the check behind it.
• What happens to a duplicate notification? Look for idempotent processing keyed to a provider reference.
• How do you handle an OTP that never arrives? Expect retry limits, a fallback and a support route.
• How do you roll out state by state? Look for per-state configuration, administrators and reporting.
• How does field data sync when the connection drops? Expect offline capture, queued sync and a review queue.
• Who owns provider accounts and credentials at handover? It should be your organisation.
• What exactly is in the first release? Ask for a written boundary, including which provider launches first.

What usually goes wrong?

• One status for two meanings. Signal: benefits go live before payment is confirmed. Owner: the finance owner.
• SMS treated as guaranteed. Signal: users locked out when codes are delayed. Owner: the product owner, with a tested fallback.
• Rollout hard-coded for the first state. Signal: the second state needs code changes. Owner: engineering.
• Field records lost offline. Signal: agents repeat visits. Owner: the operations lead, with a sync and review queue.
• Provider accounts held by the supplier. Signal: you cannot rotate credentials after handover. Owner: the business sponsor.

How this guide is sourced and where it stops

This guide uses the Nigeria Data Protection Act 2023 published by the NDPC and the CBN's payment-service-provider pages, both accessed on 2026-09-27, and Netbase delivery records approved in the OutsourcingVN claim register. It is written for founders, product and operations leads preparing a brief. It does not select a provider or decide licensing; your advisers do. Netbase JSC's head office is in Hanoi, Vietnam, and it is the company's only office, so Nigerian projects are delivered remotely.

Plan the first release

Bring your payment journey, your provider shortlist, your OTP and messaging approach, your rollout order and the names of your finance, operations and support owners. The order and payment operations solution shows how payment states connect to fulfilment, and the total software delivery cost worksheet helps compare proposals line by line. The methodology explains how the records on this page are sourced. For other markets, the UAE guide covers bilingual Arabic products and identity, the Mauritius guide covers continuity and reconciliation, and the Ghana guide covers Data Protection Commission registration and mobile money interoperability for a neighbouring West African market.

Custom Product Engineering is the service for a bounded build, and global delivery explains how remote delivery is organised. OutsourcingVN is Netbase's own outsourcing-services platform: submit a project with your first payment journey, and a person will reply with whether discovery or a bounded implementation is the right next step.

Related services and solutions

Sources

• Nigeria Data Protection Commission, Nigeria Data Protection Act 2023
• Central Bank of Nigeria, Payment service providers