Confirming Orders and Receiving Payments Safely

Move from an enquiry to a clear agreement and verify payment before marking an order paid.

Part 6 of 10 | Starting an Online Business in The Gambia

Learning goals

Confirm the exact order, choose a suitable payment route and record the payment status accurately. Recognise the difference between a provider's advertised capability and an arrangement verified for your business. Practise responding to screenshots, alleged overpayments and future-order deposits. All exercises use fictional transactions; no live payment, account opening or customer message is required.

Before you begin

Use the price and fulfilment terms already prepared. Choose payment methods that your customers can use and that you can verify and reconcile. Do not promise every mobile wallet, international card or overseas transfer option before checking it. A payment logo on a website or a checkout demonstration does not establish that your own account can receive and settle that transaction.

Step 1 Agree the order before collecting money

Give the order a unique reference. Confirm item code, quantity, variation, item price, delivery charge, total, stock status and expected handover. For a service, confirm the scope, customer inputs and completion arrangement. Keep the final confirmation in a form both parties can understand. A long chat containing several changed prices is not a clear final agreement.

In the fictional shop example, one item costs GMD 500 and agreed delivery is GMD 100, giving GMD 600 total. If GMD 200 is accepted as a deposit, GMD 400 remains due under the agreed terms. Explain when the balance is paid and what happens if the order cannot be fulfilled. A deposit is linked to a customer obligation, not unrestricted profit.

Step 2 Verify the provider arrangement

QMoney's official site describes merchant payment using a merchant number or QR code. Africell Gambia's Afrimoney information describes payments for goods and services. These are useful local options to investigate, not recommendations that every transaction or business account is automatically supported. Confirm the correct arrangement, current fees, limits, settlement access and support route with the provider.

Keep provider questions separate from the course's business-registration exclusions: the operational question is whether the selected payment route actually works for the intended sale. Do not use another person's account to bypass restrictions or misrepresent where the business operates. For international buyers, confirm the sending and receiving currencies, charges, settlement and refund route before giving payment instructions.

Step 3 Check the actual receipt

Open the genuine payment or bank interface through your normal trusted route. Match the amount and reference to the order. A forwarded screenshot, edited SMS or customer assurance is not sufficient evidence of receipt. If the transaction is pending or uncertain, mark it pending and investigate through official support rather than dispatching because the buyer is impatient.

Never request the customer's PIN or one-time login code, and do not disclose your own. Ignore a supposed support contact asking you to send money to activate an incoming payment until independently verified through the provider's official route. A real transaction may still be disputed later; keep appropriate evidence and understand the provider's actual rules instead of promising that confirmation makes every payment irreversible.

Step 4 Handle exceptions once and consistently

If someone claims an overpayment, check the actual account entry and use the provider's proper resolution process. Do not send a refund to a different account merely because a message asks. Track any refund against the original order so it is not paid twice. If the business made an error, explain it promptly and agree a suitable resolution rather than hiding behind a vague pending status.

For cash on delivery, decide who collects, how much is due and how money returns to the business. The order is not paid simply because a rider has collected the parcel. Separate dispatched, delivered and cash remitted. A simple payment status beside the order prevents staff from treating every completed delivery as money already available in the account.

Guided exercise

1. Complete the GMD 600 order confirmation with its GMD 200 deposit and GMD 400 balance. State the agreed payment and handover points.

2. Prepare five questions for a provider covering business suitability, costs, limits, settlement and disputes. Use official contact details from the provider rather than a forwarded message.

3. Rehearse checking a fictional payment reference against an order. Do not include real account screenshots or secret codes.

4. Explain your response to an unverified screenshot and an alleged overpayment requesting a refund elsewhere.

5. Define unpaid, deposit received, pending verification, paid and refunded states. Keep delivery status separate.

Knowledge check

1. Does a payment screenshot prove funds were received?

2. Can one provider's advertised service establish another provider's capabilities?

3. Is dispatched cash-on-delivery stock already collected revenue?

Answer guide

1. No. Check the genuine account and transaction details.

2. No. Verify each intended route separately.

3. No. Delivery, collection and remittance are separate events.

Completion standard

Produce a clear order confirmation, correct balance and a payment-verification process with exception handling. Identify the provider details still needing confirmation. No real funds or credentials are needed to demonstrate a reliable process.

Sources and verification notes

QMoney Gambia official website. Checked 18 September 2026. Provider describes merchant payment options. Confirm the correct merchant arrangement, current fees, limits, settlement and dispute process directly; no account was opened or tested.

Africell Gambia Afrimoney FAQs. Checked 18 September 2026. Official provider describes payments for goods and services. Availability for the exact business and transaction must be confirmed; no universal integration or cross-border promise is made.