Your delivery operation is moving. Orders are being created, parcels are leaving your hubs, riders are covering routes and merchants are waiting for their money.
This dynamic environment is only set to grow, with Nigeria's e-commerce market projected to reach $11.08 billion by 2027, with a compound annual growth rate (CAGR) of 13.9% from 2023 to 2027. From the outside, everything may look like a successful delivery operation. Then finance asks a simple question: Where is the money for this order, and who should receive it?
The customer may have paid. The rider may have collected cash. The order may be marked as delivered. Yet the payment may still be difficult to trace, reconcile or settle correctly. That is when payment stops being just a checkout problem. It becomes an operations problem.
For a delivery company handling hundreds or thousands of orders, the financial journey needs to stay connected to the delivery journey. Your team should be able to follow each transaction from the order and parcel through payment collection, delivery and remittance to eventual merchant settlement.
The goal is straightforward: every delivery should have a clear payment status, every collection should have a traceable reference, and every merchant, rider and partner should receive the correct amount. Finance should also be able to reconcile payment records with delivery records without piecing together information from different spreadsheets and systems.
A standard payment gateway may be enough to accept a card or bank transfer, but it may not solve the wider payment problems created by a delivery operation.
Consider a customer paying ₦50,000 for an order.
That payment may need to be connected to a specific order, parcel or waybill, delivery route, rider, merchant, delivery fee and commission before the correct amount can eventually be settled.
If your payment system only tells you that ₦50,000 was received, your finance team may still have to determine:
That is why a delivery company should evaluate payment infrastructure based on more than payment acceptance.
The real question is: can the payment operation remain connected to the order, delivery outcome, collection, payout and settlement process?
A delivery payment operation should connect the payment reference to the relevant order or parcel and preserve that connection through delivery, collection, remittance and settlement.
When an order is created, the relevant payment reference should be associated with it. When a parcel is assigned to a rider, the collection responsibility should be clear. When delivery takes place, the business should be able to establish whether the expected payment was received.
For a cash-on-delivery order, the system should also make it possible to compare the amount expected with the amount actually collected and remitted.
Once the money has been collected, the business needs to determine what belongs to the merchant, what the delivery company has earned, what should go to a rider or partner, and whether any adjustment is required before settlement.
When these records remain connected, operations and finance have a much clearer view of the financial status of each delivery.
Without that connection, teams may have to compare delivery reports, bank records, rider updates, and spreadsheets manually. That becomes increasingly difficult as transaction volume grows.
The problem with this, is that the payment information is not moving with the delivery information.
COD reconciliation should compare the amount expected for an order with what the rider actually collected and remitted, with any difference becoming a visible exception for investigation.
Before dispatch, your business needs to know:
After the delivery attempt, the business needs to know:
If an order is worth ₦35,000 and the rider is expected to collect ₦35,000, but only ₦30,000 is remitted, the ₦5,000 difference should be visible as an exception.
It should not disappear into a spreadsheet or remain unnoticed until a merchant raises a complaint.
The same principle applies when:
COD reconciliation is therefore more than counting cash. It is about matching the expected amount to what was actually collected and remitted across riders, routes, branches, merchants and settlement periods.
For a prepaid order, the payment should remain linked to the order and its eventual delivery outcome.
When a customer pays before delivery, the payment should be associated with the relevant order or transaction reference. Your delivery operation should then be able to establish that payment has been received before completing the relevant delivery process.
If the parcel is delivered, the payment can move into the appropriate settlement process.
But what happens when the customer refuses the parcel? What happens when the order is returned? What happens when delivery fails after the customer has already paid?
Your business needs a defined financial treatment for each situation.
Depending on the circumstances, the payment may need to remain settled, be refunded, be partially adjusted, or be held for investigation.
The important point is that the payment record and delivery outcome should remain connected so that the financial treatment can be determined without reconstructing the transaction later.
Different delivery outcomes can require different financial treatment.
A paid and delivered order can move into the appropriate settlement process.
A COD order needs to be checked against the amount the rider was expected to collect and remit.
A prepaid order that is refused or returned may require a refund or adjustment, depending on the business's policy.
A partial collection should make the difference between the expected and actual amount visible.
A missing collection should become a reconciliation exception rather than another unexplained entry in a spreadsheet.
Your payment infrastructure does not replace your delivery-management process. It provides the payment information that operations and finance need to apply the correct financial treatment to each delivery outcome.
A delivery company may handle money for several parties in the same transaction.
There may be a customer, online merchant, delivery company, rider, vendor or delivery partner.
These amounts should not be treated as one undifferentiated pool.
A customer payment may contain the product value, delivery charge, commission, service fee or other approved deductions.
Your business therefore needs to know:
This becomes particularly important when your delivery company operates on behalf of multiple merchants.
A merchant may want to know exactly how much was collected from customers, how much was deducted for delivery or other agreed charges, and when the remaining amount will be settled.
Your finance team needs the same information to close the books accurately.
A connected payment and settlement workflow makes these amounts easier to identify and manage.
A delivery company does not necessarily need to replace the systems already managing its logistics operation.
Your logistics platform may already manage orders, dispatch, riders, routes, and proof of delivery. Your accounting system may already manage financial records.
The payment infrastructure should connect with these systems and provide the payment information they need.
Payment APIs can connect payment functionality with order-management systems, dispatch platforms, rider applications, accounting platforms, merchant portals and customer-facing applications.
This can allow your business to improve payment operations without rebuilding the entire logistics environment.
The right integration depends on how your current systems are structured, what payment events need to move between them, and how your business manages orders, collections, and settlement.
Payment-status webhooks can notify connected systems when relevant payment events occur.
Instead of requiring your team to repeatedly check individual transactions, your systems can receive relevant payment updates as they happen.
The implementation should also account for delayed notifications, failed payments, reversed payments, duplicate notifications, and unmatched transactions.
These details matter because a payment status that does not reach the system managing the order can create another reconciliation problem.
Every payment should contain enough information to connect it to the relevant order, parcel, or transaction.
Depending on your workflow, that may include an order number, parcel or waybill number, transaction reference, merchant reference, or rider or partner reference.
The purpose is straightforward: when finance sees a payment, they should be able to identify what it relates to without manually searching through several systems.
Finance and operations need visibility into payment status, expected collection, actual collection, rider remittance, merchant settlement, refunds, returns, deductions, and exceptions.
As delivery volume increases, manually comparing payment records with delivery reports becomes increasingly difficult.
Good reporting should make it easier to identify:
If your business needs to move money to merchants, riders, vendors or partners, your payment infrastructure should support the required outgoing payment flows.
You should also understand when collected funds become available, how settlement is calculated, which deductions apply, where funds settle, and how settlement records connect to the original payment and delivery records.
This becomes particularly important when one customer payment ultimately needs to be distributed across several parties.
The right payment gateway for a delivery company is not simply the one that accepts cards or transfers. It should support the payment workflows that connect customer collections with orders, delivery outcomes, payouts, settlement, and reconciliation.
Evaluate the complete payment operation rather than choosing a provider based on checkout features or transaction fees alone.
Can each payment be connected to the relevant order or parcel?
Consider:
Can payment information connect with delivery status?
Determine whether the setup can:
Can the business pay merchants, riders and partners?
Confirm:
Can finance reconcile payment records with delivery records?
Look for reporting that helps identify:
Can the provider integrate with your existing logistics systems?
Check for:
These questions help you evaluate the entire payment operation rather than choosing a provider simply because it can accept a payment.
For a delivery company operating only in Nigeria, payment infrastructure may initially appear straightforward.
The complexity can increase when the business begins serving merchants or customers across other African markets.
PayOnUs operates across Nigeria, Ghana, Kenya, Côte d’Ivoire, South Africa, Zambia, Senegal and Cameroon.
Across these markets, PayOnUs provides customer collection, merchant onboarding, payouts, settlement, Payment API capabilities, and analytics and reporting.
For a delivery business expanding across these markets, this creates a payment infrastructure option to evaluate across its operating or expansion markets rather than automatically creating an entirely separate payment relationship in every country.
The applicable payment methods, settlement arrangements, onboarding conditions, and configuration depend on the merchant's business model, transaction flows, and operating requirements.
The value is not simply in the payment features PayOnUs provides, but in what those capabilities can change across your delivery operation.
| Delivery- business problem | PayOnUs capability | Potential commercial effect |
|---|---|---|
| Digital payments are difficult to confirm against orders | Customer collection and Payment APIs | Faster payment-status updates and fewer manual checks |
| Merchant funds, delivery charges and deductions are difficult to track | Analytics and reporting | Clearer settlement records and easier reconciliation |
| Rider, vendor or partner payments are manual | Payout capabilities | More structured disbursement workflows |
| Collected funds are difficult to monitor | Settlement infrastructure | Better cash-flow and settlement planning |
| Several markets require separate payment relationships | Multi- market infrastructure | Potentially less provider fragmentation |
| Existing logistics systems need payment connectivity | API integration | Payment improvement without replacing the entire logistics platform |
For Naira and most mobile-money collections, PayOnUs supports settlement on the following day, with flexible settlement configurations available for some merchants based on their
Your logistics platform may already manage your orders, dispatch, riders, routes and proof of delivery.
Your accounting system may already manage your financial records.
You do not necessarily need to replace either one simply because your payment operation needs improvement.
The payment infrastructure can sit alongside these systems and provide the collection, payment, payout, settlement and reporting capabilities they need.
The important requirement is that the systems communicate properly.
When they do, your business can create a clearer connection between payment confirmation, COD reconciliation, merchant settlement, rider and partner payouts, payment visibility and exception handling.
PayOnUs can support this through API-based payment infrastructure designed to connect with existing business systems where integration is required.
A connected payment operation should make it possible to answer the financial questions around a delivery without reconstructing the transaction manually.
For every order, your team should be able to establish whether payment was received.
For every cash collection, it should be able to see what was expected and what was actually collected.
For every delivered, refused or returned order, there should be a clear financial treatment.
For every merchant, rider or partner, the business should be able to determine what amount is due.
And for finance, payment and settlement records should be easier to reconcile with the operational records already being used by the business.
That is the real value of connecting payments to delivery operations.
It is not simply about accepting more payment methods.
It is about being able to follow the money from the customer to the order, through delivery and collection, and into the correct settlement.
A suitable payment gateway should support the payment methods your customers use while helping your business connect payments with orders, delivery outcomes, collections, payouts, settlement and reconciliation. For delivery businesses, payment acceptance alone may not address the operational problems created by COD, rider remittances, merchant settlement and returned or failed deliveries.
A payment gateway or connected payment infrastructure can support the payment information required for COD reconciliation, but the exact workflow depends on how the delivery company's logistics and payment systems are integrated. The business should be able to compare expected collections with actual collections and remittances and identify differences for investigation.
Yes. Payment APIs can connect payment functionality with existing order-management, dispatch, rider, accounting and merchant systems. The exact integration depends on the systems already used by the business and the payment events that need to move between them.
The business should have a defined financial treatment for returned prepaid orders. Depending on the circumstances and the company's policies, the payment may remain settled, be refunded, partially adjusted or require investigation. The important requirement is that the payment remains linked to the original order and delivery outcome.
Potentially, yes. The appropriate setup depends on the business's payout requirements, recipient types, markets and provider capabilities. Before implementation, the company should confirm how payouts are initiated, processed, tracked and reconciled with the original payment and settlement records.
The company should evaluate payment coverage, COD and collection workflows, payment-status handling, payment references, payouts, settlement, reconciliation, API capabilities, support, transaction limits, merchant eligibility and commercial terms. The provider should be evaluated against the actual payment and delivery workflows of the business rather than checkout features alone.
PayOnUs operates across Nigeria, Ghana, Kenya, Côte d’Ivoire, South Africa, Zambia, Senegal and Cameroon. The applicable payment methods, settlement arrangements, onboarding requirements and configuration depend on the merchant's business model and requirements and should be confirmed with PayOnUs before implementation.
If your business manages customer payments, cash collections, rider remittances, merchant settlements or payment reconciliation across different systems, the next step is to review the payment workflow behind the delivery operation.
A useful conversation should start with how your business actually works.
That includes your payment channels, COD workflow, delivery and dispatch systems, rider and partner payout process, merchant settlement requirements, integration environment, reconciliation process and expansion markets.
Talk to PayOnUs about your logistics payment requirements →
The objective is not simply to find a provider that can process a payment.
It is to determine whether your payment infrastructure can support the way your delivery operation actually works.