Pesapal Payment Pages: A Kenyan Merchant’s Guide to Requests, Bookings and Reconciliation

An online payment page is most useful when the customer can understand what is being bought and the business can connect the payment with the promised service. For a Kenyan business taking bookings or remote orders, Pesapal is one product worth evaluating through that complete workflow.

This guide uses Pesapal’s payment-page description, account FAQs and payment-link instructions, checked on 27 October 2026. It focuses on the Kenyan merchant context. Country availability, onboarding, methods, currencies and settlement terms must be confirmed for the actual account. ITBank has not opened a merchant account or processed a live payment for this article.

Start with a clear commercial agreement

Before creating a payment request, record the customer’s purchase or reservation, agreed currency, total due, deposit requirement and cancellation conditions. For a service booking, make clear whether payment confirms availability or whether the booking still requires a separate acceptance.

Consider a fictional Nairobi tour operator taking a deposit for a particular date. The payment record should connect to a booking reference and the agreed service. A generic message saying “pay here” leaves too much unresolved if the customer later asks which trip was reserved or whether the money was a refundable deposit. The example is a planning exercise, not a reported Pesapal customer case.

Confirm your merchant setup

Pesapal’s Kenyan business FAQs describe merchant registration, business documentation and an agreement as part of going live. Do not confuse opening an account with having every collection or settlement capability approved.

Use the official business-account route and ask which documents, bank-account details and service permissions apply to your organisation. Keep a record of the support channel and the person responsible for the account. A third party offering to bypass verification is not a substitute for the provider’s approval process. Never send account passwords or customer card information to someone assisting with setup.

Build a request around the order

Pesapal’s payment-link instructions describe entering the amount, currency and a description, generating a link and sharing it with the customer. Its payments-page offering also describes a branded page that can collect payments without a separate merchant website.

Treat those controls as a way to carry order context, not just visual branding. Check the business name, amount, currency and reference against the agreed booking or invoice. Confirm which payment methods your account presents to the intended payer. A product page listing multiple methods is not proof that every option is enabled in every country or for every currency.

Explain the next step to the customer

Send the request through the agreed communication channel with a short explanation of what the payment covers and how the customer will recognise confirmation. Avoid asking the customer to send card details in the conversation. Keep payment information inside the authorised checkout.

If you accept deposits, explain when the remaining balance becomes due and how it will be requested. Do not let the same reusable link silently become an instruction for several different amounts or services. Keep the customer’s booking confirmation distinct from a payment-provider receipt when they represent different things.

Reconcile payment before marking the order complete

Pesapal’s product material describes successful-payment visibility in its merchant dashboard. Check the provider’s actual record and match it with the order, currency and amount. A screenshot received in a message is useful context for an enquiry, but should not be the sole basis for releasing goods or marking a booking paid.

Use an exception log for missing references, unclear amounts, reported debits with no corresponding confirmation and duplicate-looking receipts. Record the support reference and the next follow-up action. If a payment status is uncertain, investigate before instructing the customer to pay again. A second attempt can create an additional reconciliation problem rather than solve the first one.

Check settlement and refund arrangements in writing

Pesapal’s public materials describe settlement, but different pages can refer to particular products or market arrangements. Obtain the current terms that apply to your merchant account instead of assuming one advertised timetable covers every method.

Your daily records should distinguish the order amount, confirmed payment, fees, expected net settlement and actual receipt into the bank. Establish who may request a refund and how the customer will be informed. Do not promise a refund completion time unless the applicable procedure supports it.

A sensible first rollout

Choose a limited set of authorised orders, document the full process and review the resulting records before expanding. Staff should be able to answer four questions: what was sold, which payment belongs to it, what the business received and what remains unresolved.

Pesapal’s hosted collection tools can be useful when an eligible merchant needs a remote checkout. Their value depends on the process around them: accurate requests, recognisable confirmation, market-specific terms and records that survive beyond the original sales conversation.