Payments, Service Providers, Team & Outsourcing

Payment Gateways & Payment Systems

Your business now has a legal identity and a bank account. Today we answer the question that sits between them: how does money actually travel from a customer's hand into your account?

This is the part of an online business that founders most often get wrong by accident — they pick whichever gateway they have heard of, discover six weeks later that settlements are slow, that the fees eat their margin on small transactions, or that card payments fail for half their customers, and then they try to migrate while money is still flowing through the old system.

We will look at what a gateway really does, the ways Nigerian customers actually pay, what verification demands of you, and the questions that separate a good provider from a bad one for your specific business.

A payment gateway is the software layer that moves money between your customer and your bank account. It does four jobs: it presents the payment request, it verifies the customer's details, it takes the money, and it settles that money into your account minus a fee.

Behind the gateway sit a payment processor and the banks. The customer pays; the gateway passes the request to the card network or the transfer network; the money lands in the provider's collection account; and the provider settles the balance to your business account on a schedule. You never touch the customer's card details — and you should never want to.

This is why a gateway is not optional for an online business. Without one, every sale depends on a customer manually transferring money and sending you a screenshot, which does not scale past a handful of orders a day and cannot be automated at all.

There are three ways to collect a payment, and most businesses need all three. A payment link is a URL you send to a customer — in a WhatsApp chat, a DM, an email — that opens a checkout page for a specific amount. It is the fastest way to sell before your website exists, and it stays useful afterwards for one-off sales.

A hosted checkout is the same page embedded in your website or app, so a customer can pay without leaving your funnel. Your customer never sees your server, and the provider handles the security-sensitive part.

An invoice is for anything that needs a record and a description: a service delivered, a retainer, a bulk order. A numbered invoice with a pay-now link gives you both the paper trail and the speed of online payment — which is exactly what corporate customers expect.

In Nigeria, bank transfer is the default way people pay. Card payments are convenient but fail more often than founders expect — insufficient funds, expired cards, bank restrictions on online transactions, and network timeouts all reduce your completion rate. If you support only cards, you are quietly turning away customers who would happily have sent a transfer.

USSD and mobile transfer matter for customers without data or without a card. The dedicated account numbers per customer you mapped in the banking session are issued by the gateway — and the gateway is what tells your system the moment one of them is paid.

Whatever mix you support, always confirm the payment on your side before you deliver. A screenshot is not a payment. Your gateway's webhook — the automatic notification it sends your system when a transaction succeeds — is. Treat delivery as triggered by the webhook, not by the customer's word.

If your business charges monthly — a retainer, a membership, a software subscription — you want the charge to happen without you chasing anyone. That requires the provider to store a token or a mandate from the customer's first payment, then bill against it on schedule.

Expect failures. Cards expire, accounts run dry, banks decline recurring debits. A serious subscription business plans for this: automatic retries over several days, a clear email when a payment fails, and a grace period before access is cut. Most churn in a subscription business is not a decision to leave — it is a failed payment nobody noticed.

Before a gateway will let you collect money, it has to verify you — this is KYC, know-your-customer. In practice you will be asked for your CAC certificate, your TIN, identification for the directors, a bank account in the exact registered business name, and sometimes proof of address or a live website describing what you sell.

This is the moment the work you did in the last session pays off. A business registered properly, with a matching bank account, clears verification in days. A business trying to run payments through a personal account, or under a name that does not match its registration, gets stuck — and the fix is not in the gateway, it is in the registration.

The settlement account matters too: money must settle into an account in the business's registered name. If you give a personal account, the provider will refuse, and rightly so.

Settlement speed first. Some providers settle next working day, some settle instantly for a fee, some hold funds for days when you are new. For a business that pays suppliers and contractors weekly, settlement speed is a cash-flow decision, not a detail.

Fees second — and read them properly. A percentage with a cap behaves very differently from a flat percentage. On a small transaction the flat fee can be most of your margin; on a large one the cap is a real saving. Work out what a typical sale of yours actually costs.

Then the operational questions: what is the transaction success rate, is the API well documented, is there a sandbox to test in, how do refunds and chargebacks work, how do payouts to your bank run, does it support the currencies you will earn in, and — the one founders forget — can you reach a human when something breaks on a Saturday night?

Real-world examples:

Business Service Ecosystem

No online business runs on its own. Every part of it — the domain, the email, the database, the messages, the reports — is somebody else's service that you rent. Today you identify which ones your business actually needs and build a shortlist you can act on.

The temptation is to sign up for everything that looks useful. Resist it. Every service you add is another monthly charge, another set of credentials to secure, another invoice to track and another thing that can break at 2 a.m. — and each one needs an account, a login, and a person who knows how it works.

The goal of this session is a short, deliberate list: the fewest providers that cover everything the business needs, chosen for reasons you can write down.

Start with the foundation: a domain registrar for your name, and hosting or a cloud platform where your site and app live. Then identity: a professional email address on your own domain, and an authentication service if your product has user accounts.

Then communication: an email sending service for receipts and notifications, an email marketing tool for campaigns, an SMS provider for one-time codes and alerts, and WhatsApp if your customers live there — in Nigeria, most of them do.

Then the running of the business: a CRM to hold your contacts and pipeline, an AI provider for the models you build on, an analytics tool to see what people actually do, an automation tool to connect the pieces, a support tool for customer questions, and bookkeeping software for the money.

Compare on price, but compare the right price. The advertised plan is rarely your real cost — you pay for the tier that includes the feature you need, plus anything you exceed. Work out your expected usage and price that.

Then weigh the things that decide whether you will still be happy in a year: reliability and uptime, whether there is a real API and how well it is documented, security posture, whether it serves customers in your region, whether it scales with you, and how easily it integrates with what you already use.

And always ask the exit question: if this provider doubles its price or shuts down, how do I leave? Can I export my data, my contacts, my content? A cheap service you cannot leave is more expensive than a fair one you can.

Free tiers are genuinely useful and you should start on them — they let you build and launch without spending money you have not earned yet. But know your upgrade trigger in advance: the moment you cross a limit, the price changes and the product may stop working mid-month.

The hidden cost is lock-in. When a provider holds your customer list, your content or your data in a format nobody else can read, you are no longer choosing them — you are stuck with them. Prefer providers that let you export, and keep your own copy of anything that would hurt to lose.

There is also a support cost. Free tiers rarely come with fast human help. If a service is critical to taking money or serving customers, the paid tier is not a luxury — it is insurance.

Given two options that both work, choose the one that covers more of your needs. A platform that handles your database, authentication and file storage in one place is easier to run than three separate services stitched together — fewer credentials, fewer invoices, fewer dashboards to check.

But do not over-consolidate. If one provider holds your domain, your hosting, your email and your payments, a single outage takes your entire business offline at once. Spread the critical pieces enough that no one failure stops you from selling.

Write the shortlist down with a reason for each choice and the cost you expect to pay. When a new option appears in six months, you will be able to judge it against your own criteria instead of starting over.

Real-world examples:

Team, Technology & Outsourcing Strategy

You have the structure, the registration, the accounts and the providers. Now: who does the work, and with what tools? This is where most founders either overspend on people they do not yet need, or quietly become the bottleneck in their own business.

The rule for today is simple: start from the requirement, not from the person. Do not ask 'should I hire a developer?' Ask 'what does the business need done, how often, and how central is it?' The answer points you straight at one of the six ways you already learned in the last session.

By the end of this section every requirement in your business has an owner — even if that owner is a subscription rather than a person.

Write down what the business needs done before you write down who will do it. Requirements are concrete: a website that takes bookings, a monthly newsletter, someone to answer WhatsApp enquiries within an hour, a report of last month's sales.

Once the requirement is written plainly, the decision gets much easier. A one-off website build is not a job — it is a project. Answering enquiries every day is a job or a service. Producing a monthly report is a task that software can do.

Founders get into trouble by hiring for titles they think a real business should have. The business does not need a CTO. It needs someone who can keep the site working — and for the first year, that can be a contractor on a monthly retainer.

An employee is someone you bring into the business, paid regularly, working under your direction. Best for work that is continuous, central, and needs someone who understands the business deeply: sales, support, development once the product is your edge.

A freelancer is paid per project and works independently — a logo, a landing page, a set of product photos. Best for clearly scoped, occasional work where you can judge the result by looking at it.

A contractor works on a defined scope or a retainer for a period: a developer on a monthly arrangement, an accountant for a few hours a week. This is the middle ground most small businesses live in — continuous work without a full-time salary.

An agency is a team you buy as a package: a marketing agency, a design studio. Best when the work is broad and you do not want to manage individuals. You pay more, and you get less control over who actually does it — so check references carefully.

Alongside people, list the technology the business needs: a website or landing page, a web application if customers log in, a mobile app if they use it on their phones, a database to hold everything, AI where it genuinely saves time or adds a feature, APIs to connect your tools, hosting to run it, a CRM to hold relationships, and automation for the repetitive parts.

Be honest about which of these you actually need now. A landing page that takes payments and captures leads will out-earn a beautiful app nobody has asked for. Build the smallest thing that lets the business sell, then expand once customers tell you what is missing.

For every technology requirement, name the provider you chose in the last section and the monthly cost. If a requirement has no provider and no owner, it is not a plan — it is a gap.

Before any outsourced work begins, agree in writing on four things: exactly what is being delivered, when, what it costs, and what happens if it is late or wrong. Vague briefs produce vague work, and then an argument about whose fault it was.

Insist on owning what you pay for. The accounts, the domains, the source code, the design files, the ad accounts — all of it in the business's name and credentials, never the contractor's personal ones. Founders who let a developer register the domain in their own name have lost a business's identity over a disagreement.

Pay in milestones rather than all upfront: a portion to start, a portion on delivery, a portion when it works. And ask for handover documentation — how to run, update and access what was built. If only one person on earth understands your setup, you do not own it.

Real-world examples:

Task for Today — Open an Account With Every Payment Gateway