← Back

Country payment guide

Accept payments in Uganda

Uganda payment planning should begin with the routes customers can use comfortably, then test PSP fit for the merchant's setup. Use the page to compare mobile-money, bank, card, and gateway-style options only after asking which methods are live for the entity, industry, website, and customer geography. Confirm payout account, settlement currency, KYB documents, refunds, disputes, failed payments, reserves, reconciliation exports, support ownership, and fees.

Which PSPs and payment routes can you explore in Uganda?

Existing research for Uganda includes Pesapal Uganda, Yo Payments, Centenary Bank CenteVisa Merchant, Stanbic Bank Uganda Merchant Solutions, MTN MoMo Uganda Open API, Airtel Money. Explore their products and local payment methods, then use your business and company location to narrow the enquiries.

No local company, or no clear contact route?

These are research leads, not approval or industry-support guarantees. Tell us the market and your company location so we can help you explore further.

7Channel recordsPublic directory entries
AfricaRegionUG
Usually requires a local entity, Medium, verify entity and documentsOnboardingFrom structured fields
Real-time / T+0, T+1SettlementVerify on detail pages

Curated market guide

Uganda PSP routes to verify first

Which PSPs, mobile-money routes, and bank merchant services should a merchant ask first for Uganda?

4
local_psp_or_aggregator · curated

Ugandan PSP / gateway shortlist

Pesapal UgandaYo PaymentsRelworx UgandaPegasus Technologies

Use when you need mobile money, cards, and local collection through one PSP evaluation.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
acquirer_or_bank · curated

Bank/acquirer route

Centenary Bank CenteVisa MerchantStanbic Bank Uganda Merchant SolutionsGTBank Uganda GTPayInterswitch East Africa Uganda

Use when bank merchant services, card acquiring, or local enterprise support are important.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
direct_scheme_or_wallet · curated

Mobile-money and wallet route

MTN MoMo Uganda Open APIAirtel MoneyXenteMcash Uganda Limited

Use when mobile money or wallet checkout is central and direct/partner access must be compared.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
international_psp · curated

Africa PSP route

Flutterwave UgandaDPO Pay UgandaJjuma Global

Use when the merchant wants Uganda plus broader Africa coverage and can verify Uganda-specific onboarding.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
KYB prep

Documents to prepare

  • Company registration and Uganda entity or foreign onboarding question
  • Beneficial-owner and signatory ID
  • Website/app URL and product category
  • Bank account and settlement-currency requirements to verify
  • Refund and customer-support policy
Due diligence

Questions to ask

  • Can my current merchant entity onboard for this market, or is a local company required?
  • Which local payment methods are actually enabled for my merchant category and transaction model?
  • Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
  • Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
  • Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?
Contact route fallback

If the official contact route is unclear

If public contact details are not specific enough, ask LocalPayMap to identify the right official form, PSP sales route, or local acquiring partner before committing engineering work.

  • Which local payment methods are actually enabled for my merchant category and transaction model?
  • Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
  • Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
  • Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?

How local customers usually pay

Uganda is mobile-money-led, with MTN MoMo and Airtel Money central to local consumer payments. Cards and bank transfers have their place, but a local ecommerce or services checkout should usually inspect mobile money first. Providers such as DPO, MTN MoMo API and local gateways can differ sharply on onboarding, documentation, refund handling and dashboard quality. Ask whether customers approve payments by USSD, app prompt or payment link; how long pending payments remain open; and what settlement files show for each transaction. A foreign merchant should verify local entity, tax, bank-account and restricted-industry rules before assuming direct acceptance.

  • MTN MoMo and Airtel Money collection. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
  • Aggregator checkout for multiple wallet and bank routes. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
  • Cards and bank transfer for B2B, travel or higher-value orders. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.

Payment methods to check first

For Uganda, begin with the methods that match real customer behavior, then map each one to a provider that can actually onboard your merchant. Current public records point to Mobile money, Digital wallet, General commerce and Payment aggregator, but availability can vary by PSP, entity type and industry.

  • Start with the payment method customers already recognize, not the provider with the longest logo wall.
  • Check whether the method supports online checkout, payment links, QR, app redirects, refunds and clear transaction references.
  • Keep one fallback method for buyers who cannot or will not use cards.
  • Document which method is mandatory for launch and which can wait for phase two.

What to do if you do not have a local company

Do not assume a foreign company can use the same route as a local merchant in Uganda. Some PSPs can onboard overseas entities, some require a local company and local bank account, and some support only selected industries. The cleanest first email states your incorporation country, product, website, expected volume, average order value, customer location, settlement currency and refund model.

  • Ask whether foreign entities are accepted directly or only through a local subsidiary, distributor or merchant-of-record arrangement.
  • Confirm local company, tax ID, local bank account, local director, licence and proof-of-address requirements.
  • Ask which settlement currencies and payout countries are supported for your entity.
  • Get the onboarding answer in writing before promising a local method to customers.

PSP and four-party provider screening

Use provider discovery to separate customer-facing payment brands from the companies that can legally process and settle funds. Public PSP/contact leads for Uganda currently include DGateway by DesisPay, DPO Pay Uganda, GovBill / InstaPay Uganda, Jjuma Global, Mcash Uganda Limited and Micropay (U) Limited. Compare them by eligibility, method coverage, operational support and documentation quality rather than headline pricing alone.

  • DGateway by DesisPay: Payment gateway. Verify live coverage for MTN, Airtel, cards via Stripe, collections, disbursements and payment links, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • DPO Pay Uganda: Payment gateway. Verify live coverage for cards, mobile money, payment links, plugins and travel payments, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • GovBill / InstaPay Uganda: Payment gateway. Verify live coverage for mobile money, cards, merchant collections, payment links and API, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • Jjuma Global: Payment gateway. Verify live coverage for MTN MoMo, Airtel Money, M-Pesa, cards, payment links and WhatsApp payments, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • Mcash Uganda Limited: PSP / aggregator. Verify live coverage for Mobile money, Bank transfer and Cards, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • Micropay (U) Limited: PSP / aggregator. Verify live coverage for Mobile money, Cards, Bank transfer and QR code, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • MTN MoMo Uganda Open API: Mobile money operator. Verify live coverage for MTN MoMo, collections, disbursements, remittances, MoMo widget and merchant pay, entity eligibility, pricing, settlement and support before treating it as a launch option.

Settlement, currency, refunds and disputes

Treat all pricing and settlement information for Uganda as preliminary until confirmed by the official provider or contract. Fees, payout timing, rolling reserves, FX, chargeback costs and refund rules can change by industry, volume, risk review, settlement currency and integration route.

  • Ask for transaction fee, fixed fee, refund fee, chargeback fee, payout fee, FX spread, reserve policy and minimum monthly or setup charges.
  • Confirm payout timing, settlement currency, settlement account country, failed-payout handling and reconciliation file fields.
  • Check whether refunds must return through the original method and whether partial refunds are supported.
  • For cards, confirm dispute workflow, evidence deadlines, chargeback fees and fraud-monitoring rules.

Compliance and operating checks

Before launch in Uganda, prepare KYB and risk material as if the provider will ask for it. Most delays for new merchants come from unclear ownership, unsupported industries, missing licences, incomplete websites, weak refund policies or settlement accounts that do not match the merchant record.

  • Prepare company registration, ownership, director ID, website/app URL, product description, terms, privacy policy and refund policy.
  • Disclose regulated products, digital content, subscriptions, marketplace activity, high-risk categories and cross-border fulfilment.
  • Ask how the provider screens sanctions, fraud, AML risk, chargebacks and customer complaints.
  • Keep sensitive or restricted markets at compliance-review level; do not use unofficial workarounds.

Questions to ask service providers

Send a concise written checklist to every Uganda PSP or aggregator so responses can be compared side by side. The goal is to expose hidden entity, settlement, support and technical gaps before engineering work begins.

  • Which payment methods are live today for my exact merchant entity, industry and customer geography?
  • Do you support hosted checkout, API, plugin, payment links, webhooks, sandbox, refunds and reconciliation exports?
  • Who is the merchant of record, who handles chargebacks and who owns customer support for failed payments?
  • What documents are requested, how is approval reviewed, and what would cause rejection?
  • Can you provide official links for pricing, settlement terms, developer docs and support escalation?

Common beginner mistakes

The most common mistake in Uganda is treating payment acceptance as a logo checklist. Local conversion depends on customer habit, provider eligibility, settlement flow, refund support and operational reliability. A cheaper-looking route can become expensive if it cannot settle where you need, cannot refund cleanly or cannot support the methods buyers expect.

  • Choosing cards only when wallets, mobile money, bank transfer, QR or cash-style routes are normal for local buyers.
  • Building against an API before KYB, entity and settlement eligibility are confirmed.
  • Ignoring refund and dispute flows until the first customer complaint arrives.
  • Comparing providers without asking the same written questions of each one.

Next actions

Next actions for Uganda

Use these internal paths to move from market research to provider outreach without assuming eligibility, pricing, settlement, or local-entity access.

Questions merchants ask

Which payment methods should a new merchant check first in Uganda?

Start with Mobile money, Digital wallet, General commerce and Payment aggregator. Then confirm which provider can support your entity, industry, customer geography, settlement currency and refund model.

Can a foreign merchant accept local payments in Uganda without a local company?

Sometimes, but it must be verified provider by provider. Ask whether a local entity, local bank account, tax ID, licence, local director or merchant-of-record route is required.

Which PSPs or aggregators are worth screening for Uganda?

Public leads include DGateway by DesisPay, DPO Pay Uganda, GovBill / InstaPay Uganda, Jjuma Global, Mcash Uganda Limited and Micropay (U) Limited. Treat them as a shortlist for outreach, not as confirmed eligibility or complete market coverage.

Can I use public fee pages as a final quote?

No. Public fees are screening context only. Final pricing can vary by country, industry, volume, risk review, settlement currency, FX, reserves and contract terms.

What operational questions should I ask before integration?

Ask about onboarding documents, restricted industries, live payment methods, checkout flow, webhooks, sandbox, refunds, disputes, chargebacks, reconciliation files, settlement timing and support escalation.

What should I do if the provider has no public sales email?

Use the official contact form, support page or developer contact route, and send a short brief with your entity country, product, volume, currencies and required payment methods.