The Kuda Business API lets approved businesses connect their own systems to Kuda Business for banking operations such as collections, transfers, bill payments, account information, and transaction status checks.
This guide gives you the recommended integration path before you start writing code.
What you can build
You can use the Kuda Business API to:
retrieve supported banks
validate account names before transfer
make single transfers
make bulk payments
create dynamic virtual accounts for collections
pay bills
retrieve balances, statements, and transaction history
receive transaction and bill notifications through webhooks
check the status of pending or uncertain transactions
Recommended integration order
Start with low-risk, read-only or validation calls before adding money movement.
Generate your API key from the Kuda Business dashboard.
Generate an access token.
Configure the UAT environment first.
Make a safe starter request with
BANK_LIST.Add
NAME_ENQUIRYto validate account details.Add the product-specific flow you need, such as transfers, bills, or dynamic accounts.
Persist every
requestRefyou generate.Add status-query handling before retrying any uncertain transaction.
Configure webhooks if your product needs asynchronous updates.
Move to production only after UAT testing is complete.
Integration architecture
Keep your Kuda integration on your server. Do not call the Kuda Business API directly from browser or mobile frontend code.
Your app should look like this:
User interface -> Your backend -> Kuda Business API
|
Your database
request refs, status, audit logs
Your backend should handle:
access token storage or token generation
Kuda request construction
request reference generation
response parsing
transaction status checks
webhook ingestion
retries and support logs
Safe starter calls
Use these calls first:
Operation |
| Why it is useful |
Bank list |
| Confirms base URL, token, and request envelope. |
Name enquiry |
| Confirms account validation without moving money. |
Balance |
| Confirms account information access. |
Money movement safety
For transfers, bulk payments, bill purchases, and dynamic account creation:
validate inputs before execution
show the user a preview before charging or transferring funds
generate a unique
requestRefstore the request and response
require explicit confirmation in your product
check transaction status before retrying an ambiguous request
Do not build money movement as a one-click frontend-only action.
What to read next
Read these guides in order:
Kuda Business API Request Format and Environments
How to Authenticate Kuda Business API Requests
Making a Transfer with the Kuda Business API
Checking Transaction Status and Recovering Pending Payments
Handling Kuda Business API Webhooks
If you are building collections, read Getting Paid with Dynamic Virtual Accounts before webhooks.
Common mistakes to avoid
Exposing API keys or access tokens in frontend code.
Using production before testing in UAT.
Reusing UAT bank codes in production.
Hardcoding bill item identifiers without refreshing the catalog.
Losing the original
requestRefafter submitting a transaction.Retrying a transfer or bill payment before checking its final status.
Treating every successful HTTP response as final transaction success.
Need help?
If you need access to the API or need help validating your integration, contact Kuda Business support through the approved support channel for your business.