← Back

Country payment guide

Accept payments in Rwanda

Rwanda entry work should start by matching the merchant's checkout to the local routes customers recognize, then checking whether mobile-money, bank API, or PSP routes can board the business. Ask each provider about entity requirements, settlement currency, payout bank needs, KYB files, refund and dispute handling, failed or pending payments, reserves, reconciliation exports, webhooks, support ownership, and written fee terms.

Which PSPs and payment routes can you explore in Rwanda?

Start with the payment methods and provider directory below for Rwanda. Research does not cover every route; contact us if you cannot find a suitable option.

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.

0Channel recordsPublic directory entries
AfricaRegionISO pending
To be confirmedOnboardingFrom structured fields
To be confirmedSettlementVerify on detail pages

Curated market guide

Rwanda PSP routes to verify first

Which PSPs, acquirers, gateways, and local payment routes should a merchant ask first for Rwanda?

6
licensed_payment_service_provider_or_aggregator · curated

licensed payment service provider or aggregator

Prioritize this when you need a local PSP contract, wallet aggregation, collections API, or a single integration for multiple payment methods.

Do not infer foreign merchant eligibility from consumer wallet or processor pages. Ask whether a Rwandan company, local bank account, RDB registration, local tax profile, or local representative is required for the exact route and business category.

  • Which National Bank of Rwanda payment-service category or regulated role applies to this product?
  • Can my current entity onboard directly, or do you require a Rwandan company, local bank account, or local tax registration?
  • Which methods, refunds, failed-payment flows, reconciliation files, and support escalation routes are available for my use case?
mobile_money_operator · curated

mobile money operator

Prioritize this when local consumers are expected to pay from mobile wallets at checkout, in app, by USSD, or through merchant pay.

Do not infer foreign merchant eligibility from consumer wallet or processor pages. Ask whether a Rwandan company, local bank account, RDB registration, local tax profile, or local representative is required for the exact route and business category.

  • Is this a direct MoMoPay or wallet merchant route, a collections API route, or a PSP-aggregated route?
  • Does the route support ecommerce, invoices, recurring collections, in-person merchant pay, or only selected flows?
  • What onboarding path applies if the merchant is foreign-owned or lacks a Rwandan company?
bank_or_processor · curated

bank or processor

Prioritize this when you need card acceptance, 3-D Secure processing, bank sponsorship, or local settlement control.

Do not infer foreign merchant eligibility from consumer wallet or processor pages. Ask whether a Rwandan company, local bank account, RDB registration, local tax profile, or local representative is required for the exact route and business category.

  • Which acquiring bank or processor owns card acceptance, settlement, disputes, and chargebacks?
  • Can you support SmartCash, Visa, Mastercard, UPI, mobile payments, or other methods for online merchants?
  • Which official merchant application route should be used if there is no named sales contact?
mobile_money_collection_or_momopay_through_the_wallet_operator_or_psp_partner · curated

Mobile money collection or MoMoPay through the wallet operator or PSP partner

Mobile money is a central consumer payment behavior in Rwanda, and official MTN Rwanda material distinguishes merchant and corporate MoMo use cases.

Do not infer foreign merchant eligibility from consumer wallet or processor pages. Ask whether a Rwandan company, local bank account, RDB registration, local tax profile, or local representative is required for the exact route and business category.

  • Ask whether you are contracting with the wallet operator directly or through a PSP partner, and confirm entity eligibility before integration.
  • Which National Bank of Rwanda payment-service category or regulated role applies to this product?
  • Can my current entity onboard directly, or do you require a Rwandan company, local bank account, or local tax registration?
rswitch_or_bank_processing_route_for_cards_and_online_payments · curated

RSwitch or bank processing route for cards and online payments

RSwitch states that it is connected to commercial banks, mobile networks, and some microfinance institutions, and describes merchant online processing across schemes and mobile payments.

Do not infer foreign merchant eligibility from consumer wallet or processor pages. Ask whether a Rwandan company, local bank account, RDB registration, local tax profile, or local representative is required for the exact route and business category.

  • Ask the processor or bank to identify the acquiring bank, supported schemes, merchant category review, and settlement model.
  • Which National Bank of Rwanda payment-service category or regulated role applies to this product?
  • Can my current entity onboard directly, or do you require a Rwandan company, local bank account, or local tax registration?
KYB prep

Documents to prepare

  • Company registration certificate and operating entity details.
  • Beneficial-owner, director, and signatory identity documents.
  • Business website/app URLs, product description, refund policy, terms of service, and restricted-category explanation where relevant.
  • Bank account, settlement currency, tax/VAT/GST information, and expected processing volume.
Due diligence

Questions to ask

  • Can my current merchant entity onboard, or is a local company or bank account required?
  • Which local payment methods are live for my business category and customer flow?
  • What documents are required for KYB, technical review, and production approval?
  • How are refunds, chargebacks, reconciliation files, reserves, FX, and payout currencies handled?
  • Which public email, form, dashboard, or partner manager should be used for merchant onboarding?
Contact route fallback

If the official contact route is unclear

Use the official merchant signup, developer portal, bank relationship channel, or NBR-regulated provider directory first. If no merchant owner is obvious, ask LocalPayMap to route the question to a Rwanda PSP, wallet operator, bank, or processor path.

  • Which local payment methods are live for my business category and customer flow?
  • What documents are required for KYB, technical review, and production approval?
  • How are refunds, chargebacks, reconciliation files, reserves, FX, and payout currencies handled?
  • Which public email, form, dashboard, or partner manager should be used for merchant onboarding?

How local customers usually pay

Rwanda is mobile-money-heavy, with MTN MoMo and Airtel Money important for everyday payments. Bank of Kigali API, IremboPay and RSwitch-type routes may also matter depending on whether the merchant is selling public-service-like payments, ecommerce, digital content or local services. Cards are useful for hotels, travel and higher-value customers, but many domestic buyers expect mobile money, USSD or wallet-based confirmation. A small merchant should ask providers for the exact wallet networks, payment confirmation flow, refund process and settlement timing. Because public channel coverage is still thin, provider discovery and licensing checks should come before integration design.

  • MTN MoMo and Airtel Money collection through a PSP or aggregator. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
  • Bank or API routes for account-based payments and invoices. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
  • Cards for travel, hospitality and international buyer segments. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.

Payment methods to check first

Rwanda still has limited public payment-channel records in LocalPayMap, so use local PSP conversations to verify the actual customer-facing methods before designing checkout. The first shortlist should cover MTN MoMo and Airtel Money collection through a PSP or aggregator., Bank or API routes for account-based payments and invoices. and Cards for travel, hospitality and international buyer segments..

  • 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 Rwanda. 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 Rwanda currently include Airtel Money Rwanda, Bank of Kigali (BK Open API), BK Open API, Centrika, Efashe (Future Dynamic Innovations) and Esicia Ltd. Compare them by eligibility, method coverage, operational support and documentation quality rather than headline pricing alone.

  • Airtel Money Rwanda: Mobile money operator. Verify live coverage for Mobile money, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • Bank of Kigali (BK Open API): Bank merchant services. Verify live coverage for Bank transfer, Mobile money and Cards, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • BK Open API: Open banking / pay by bank. Verify live coverage for BK payments, collections, payouts, open API and bank account services, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • Centrika: Payment gateway. Verify live coverage for Mobile money, Cards, QR code and Bank transfer, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • Efashe (Future Dynamic Innovations): PSP / aggregator. Verify live coverage for Mobile money, Bank transfer and Cash, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • Esicia Ltd: Payment gateway. Verify live coverage for Mobile money, Bank transfer, Cards and QR code, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • IremboPay: Payment gateway. Verify live coverage for MTN MoMo, Airtel Money, cards, bank transfer, cash agents and payment links, 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 Rwanda 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 Rwanda, 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 Rwanda 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 Rwanda 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 Rwanda

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 Rwanda?

Start with MTN MoMo and Airtel Money collection through a PSP or aggregator., Bank or API routes for account-based payments and invoices. and Cards for travel, hospitality and international buyer segments.. Then confirm which provider can support your entity, industry, customer geography, settlement currency and refund model.

Can a foreign merchant accept local payments in Rwanda 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 Rwanda?

Public leads include Airtel Money Rwanda, Bank of Kigali (BK Open API), BK Open API, Centrika, Efashe (Future Dynamic Innovations) and Esicia Ltd. 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.

Public sources