How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Kora Charges API

Pay-ins - card, bank transfer, mobile money, and pay-with-bank.

Kora Charges API is one of 7 APIs that Kora publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Charges. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 8 operations across 8 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.korapay.com/merchant/api/v1.

8 operations 8 paths 10 schemas 2 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.korapay.com/merchant/api/v1
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Kora Charges API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (secretKeyAuth). It accepts HTTP bearer tokens (publicKeyAuth). By default, every request must be authenticated.

  • secretKeyAuth — Secret API key passed as Authorization: Bearer sk.... Required for server-side and financial operations (payouts, balances, virtual bank accounts, refunds, con…
  • publicKeyAuth — Public API key (pk...) used from client-side code to initiate charges. Cannot access financial data.

Paths & Operations 8

Across 8 paths, the API surfaces 8 operations — 2 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Charges 8

Pay-ins - card, bank transfer, mobile money, and pay-with-bank.

POST
/charges/initialize
Initialize a charge
initializeCharge body → 200401
POST
/charges/card
Charge a card
chargeCard body → 200401
POST
/charges/card/authorize
Authorize a card charge
authorizeCardCharge body → 200401
POST
/charges/mobile-money
Charge a mobile money wallet
chargeMobileMoney body → 200401
POST
/charges/mobile-money/authorize
Authorize a mobile money charge
authorizeMobileMoneyCharge body → 200401
POST
/charge/pay-with-bank
Charge with Pay with Bank
chargePayWithBank body → 200401
GET
/charge/pay-with-bank/banks
List Pay with Bank banks
listPayWithBankBanks → 200401
GET
/charges/{reference}
Verify / query a charge
verifyCharge 1 param → 200401404

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are InitializeChargeInput (8 properties), MobileMoneyChargeInput (8 properties), PayWithBankInput (6 properties), ErrorResponse (3 properties). Each schema is shown below with its type and property counts.

MobileMoneyAuthorizationInput
object
2 properties 2 required
ChargeResponse
object
3 properties
MobileMoneyChargeInput
object
8 properties 5 required
EncryptedChargeInput
object
1 property 1 required
CardAuthorizationInput
object
2 properties 2 required
PayWithBankInput
object
6 properties 4 required
Customer
object
2 properties
ErrorResponse
object
3 properties
InitializeChargeInput
object
8 properties 4 required
BankList
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

korapay-charges-api-openapi.yml Raw ↑

Other APIs Kora publishes across the network.

Kora Balances API
Kora Currency Conversion API
Kora Misc API
Kora Payouts API
Kora Refunds API
Kora Virtual Bank Accounts API
Where this information came from

This is an independent, third-party profile of Kora Charges API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.