Paga Engine Takes Direct Debit Beyond the Paga Wallet

A subscription business needs a way to collect the next payment without asking its customer to make a fresh transfer every month. Paga Engine’s Direct Debit service is built around that problem, allowing businesses to collect authorised recurring payments from customers’ bank accounts rather than relying only on a Paga wallet or a saved card.

The distinction matters in Nigeria, where a customer may use one app to sign up for a service but hold the money in a separate bank account. For a biller, an account-based mandate can turn repeated manual reminders into a scheduled collection flow. Paga describes subscriptions, loan repayments, utilities, insurance premiums and education fees as possible uses. Its public product page and developer documentation confirm the capability. They do not establish that it first became available today, so this is a look at how the service works and what its wider use could mean.

A business starts by creating an electronic mandate through Paga’s API. The customer must authorise the request through their bank. Once the mandate is approved, the business can initiate charges under the agreed terms. That approval is the central safeguard. Direct debit is a pull payment, but it is not permission for a merchant to take arbitrary amounts whenever it likes.

Paga’s technical guide separates customer verification from bank approval. It says an activation payment must go through an approved banking channel, after which Paga sends a verification callback. A second callback indicates that the bank has approved the mandate and it is ready to be charged. The guide gives a bank-approval window of four hours to seven days. Businesses therefore should not treat a customer’s initial authorisation as a guarantee that collections can begin immediately.

The wider payment rail is familiar to Nigerian financial institutions. NIBSS describes its Direct Debit system as a mandate-based service for recurring collections from bank accounts. It supports fixed or variable instructions and serves billers ranging from utilities and insurers to lenders. Paga Engine offers businesses an integration and workflow layer over this kind of account-based collection. The precise banks, fees and settlement arrangements available to a merchant should be confirmed during onboarding rather than assumed from the product description.

Cards can expire or fail, while manual bank transfers require customers to remember each due date and businesses to reconcile what arrived. A direct-debit mandate can reduce that friction, particularly for a school collecting instalments, an insurer billing premiums or a software firm charging for a subscription. It may also make cash flow easier to forecast. None of that removes the need to handle failed debits, customer disputes and cancellations clearly.

For Paga, the commercial opportunity is broader than its consumer app. Paga Engine sells payment infrastructure to other companies, positioning the group as a provider behind a merchant’s own customer experience. TechBooky has tracked Paga’s shift towards financial infrastructure, and direct debit illustrates that shift in a practical way. The merchant keeps the customer relationship while Paga supplies the collection tools.

The test will be reliability and transparency. Businesses will want to know how many mandates reach bank approval, how quickly failed collections are reported and what each successful debit costs. Customers need a clear view of the amount, frequency and means of stopping a mandate. Paga has documented the technical path. The value of opening that path to more businesses will depend on how consistently it works outside a demonstration.