Kora payment method is a pan-African payments platform built by Kora, founded in 2017 in Lagos, focused on helping businesses collect payments and run payouts across key African markets through one payments stack.
Merchants accept Kora when they want to reach customers who pay with local rails such as mobile money and bank transfers, not only cards, and still keep a predictable back office process.
Kora is usually offered next to cards, wallets, and local bank options. Once several methods and providers sit side by side, the real pressure lands on operations, because statuses, disputes, and payout reports start to diverge. Akurateco helps teams run that setup from one place for payment management, visibility into approval performance, and consistent reporting across the full checkout.
What is Kora?
Kora is a PSP and payment gateway that supports payment collection and money movement through regional payment channels.
It’s used by e-commerce teams, digital services, and platform businesses that need to track payment outcomes cleanly, keep support workflows simple, and give finance reporting they can reconcile without guesswork.
Where Kora is used
Kora is most associated with African markets where customers rely on local rails for everyday payments, with strong relevance in Nigeria, Kenya, Ghana, and South Africa, plus additional coverage in selected markets such as Côte d’Ivoire and Egypt. An internal check of which Kora supported countries apply to your merchant account, since enabled payment options can differ by market and setup scope
You will often see it in cross-border e-commerce, digital services, logistics and delivery, and education payments, where conversion improves when customers can pay the way they already do.
How Kora works
- The customer selects Kora at checkout and chooses an available option for their country and currency.
- Your system creates a payment request through the Kora API and receives a transaction reference.
- Kora presents the required flow, which may involve an in-page form, a redirect, or an in-app approval, depending on the method.
- If authentication is required, the customer completes the verification step and returns to your confirmation screen.
- Kora responds with an initial outcome so your system can update the order status, such as successful, failed, or pending.
- When the outcome is not final immediately, your system receives a later status update through callbacks or webhooks.
- You confirm fulfillment only after a final success status, and route failures into your normal retry logic and customer messaging.
- Finance reconciles payouts, fees, and reversals using the transaction reference and settlement reporting, then matches results back to orders and invoices.
Merchant requirements and setup basics
Common requirements for Kora integration:
- Merchant onboarding and account approval, including standard business verification and a payout account
- Kora API credentials and environment configuration for your website or app
- Redirect and callback handling where required, plus a webhook endpoint so payment and refund events reach your system
- Clear rules for pending outcomes so you do not fulfill too early
- Testing before launch with success, failure, and cancellation cases in a test environment
Fees, settlement, and refunds overview
Kora fees are set by your commercial agreement and often vary by market, payment method, merchant profile, and processing model. Most teams treat pricing as account-specific and validate it for the countries and channels they plan to scale.
Kora settlement depends on the method and your payout cadence, so it is usually measured in business days. A short refresher on how settlement works can help align expectations, because a customer seeing success and money reaching your bank do not happen at the same time.
Kora refunds are generally supported, but timing and workflow depend on the underlying method and transaction status. Support teams usually track each refund to its final status, then finance reconciles it back to the original payment reference in reporting.
Pros and cons of Kora for merchants
Pros:
- Strong fit for African markets where local rails drive customer preference
- Useful for merchants that sell across borders and need local payment options per market
- Keeps back office work simpler when statuses and reporting are handled consistently
- Supports operations teams that need clear references for support cases and reconciliation
Cons:
- Coverage and enabled methods vary by market, so the onboarding scope needs to be confirmed early
- Some flows can return pending outcomes, which requires careful order handling and customer messaging
- Refund timing can differ by method, so support and finance need clear tracking and reconciliation habits
Using Kora in a multi-method checkout
Kora is usually one part of a broader payment mix. Cards keep a broad reach, while local bank options and mobile money can lift competition in markets where customers do not default to cards.
As soon as you add another provider, workflows can fragment across different dashboards, different status models, and different reporting cutoffs. That is where using a payment orchestration platform benefits teams. With orchestration, teams get one operational view for payment monitoring, approval performance, and consistent reporting across methods, so investigations and reconciliation stay manageable.
Integration via Akurateco
Akurateco supports building a multi-method payment setup where teams can add payment methods and providers under one orchestration layer. If a specific payment method is required for your use case, we can enable it upon request. Reach out to our team and let’s discuss options.
FAQ about Kora
What is Kora?
Kora is a PSP and payment gateway that helps businesses accept payments through regional payment channels and manage transaction outcomes. Teams use it when they need clean status tracking and reporting that works for support and finance.
Where is Kora available?
Kora is most associated with African markets, with strong relevance in Nigeria, Kenya, Ghana, and South Africa, plus additional coverage in selected markets such as Côte d’Ivoire and Egypt. Kora supported countries depend on your onboarding scope and enabled products, so confirm coverage during setup before planning a rollout.
Does Kora support refunds?
Yes, Kora refunds are generally possible, but the exact flow depends on the payment method and transaction status. In practice, teams track the refund until it reaches a final outcome, then reconcile it back to the original payment reference in reporting.
How long does the settlement take?
Kora settlement depends on the method and your payout schedule, so it is usually not instant. A customer can see success quickly, while the payout arrives later based on banking cutoffs and reporting cycles.
Is Kora good for subscriptions or recurring?
It depends on your markets and which payment options you use for renewals. Many teams keep cards as the main renewal option and add local methods where customers expect them, then focus on clean handling for failures and retries. In multi-provider setups, payment orchestration helps keep reporting unified so every renewal attempt is easy to trace across providers.
Can I offer Kora alongside cards and other local methods?
Yes, many merchants do, especially when they serve multiple regions or customer segments. The operational challenge is keeping one view of payment status, performance, and reports across the full mix, and that is where payment orchestration matters. When you add the Kora payment gateway alongside other providers, orchestration helps keep monitoring and reporting consistent in one place.
