Moving money from your M-Pesa account into a KCB Bank account is one of the most common cross-platform transactions in Kenya, and it takes just a couple of minutes once you know the right steps. Here’s exactly how to do it, along with what to expect in terms of timing and fees.
Method 1: Using Lipa na M-Pesa (Pay Bill) — The Standard Method
This is the most widely used and straightforward option, and it works for depositing into any KCB account, whether it’s your own or someone else’s:
- Open the M-Pesa menu on your phone, either through the SIM Toolkit or the M-Pesa app
- Select Lipa na M-Pesa
- Choose Pay Bill
- Enter KCB’s business number: 522522
- When prompted for the account number, enter the recipient’s KCB account number (typically 13-16 digits) — note this is the account you’re depositing into, not your own M-Pesa number
- Enter the amount you want to deposit
- Enter your M-Pesa PIN and confirm
You’ll receive two confirmation messages once the transaction goes through: one from M-Pesa with your transaction code, and a second from KCB confirming the deposit has been credited to the account.
How Long It Takes
Deposits made through paybill 522522 are typically credited to the KCB account within 1 to 15 minutes during normal processing. During business hours, crediting is often close to instant; outside business hours or over weekends, it can occasionally take a bit longer, sometimes pushing into the next business day. Larger transfers — above KES 70,000 — may require additional review before crediting, which can also add some delay.
Method 2: Using KCB M-Pesa (If You Have a Linked Account)
If you already hold a KCB M-Pesa account — the linked savings and loan product accessible directly through the M-Pesa menu — you can move funds between that balance and your regular KCB Bank account without leaving the M-Pesa menu at all:
- Open M-Pesa, then select the KCB M-Pesa option from the menu
- Choose Send to my KCB Account (or the similarly worded option in your menu)
- If you hold multiple KCB accounts, select the correct destination account
- Confirm the amount and your PIN to complete the transfer
This method is specifically for KCB M-Pesa account holders and is separate from the general paybill deposit method above.
What Fees to Expect
M-Pesa charges a standard Lipa na M-Pesa transaction fee based on the amount you’re sending, and this cost is borne by you as the sender — KCB does not charge you separately to receive the deposit. The exact fee scales with transaction size, so it’s worth checking Safaricom’s current M-Pesa tariff guide or a fee calculator before sending a large amount, since fees are periodically updated.
A Few Things to Double-Check Before Sending
- Verify the recipient’s KCB account number carefully before confirming — this is the single most common source of delayed or misdirected deposits, since the “account” field in the paybill process refers to the destination account, not your own M-Pesa line
- Confirm you have sufficient M-Pesa balance to cover both the deposit amount and the transaction fee
- Make sure your phone has a stable network connection throughout the transaction to avoid it failing partway through
If Something Goes Wrong
If you sent money to the wrong account number or the wrong paybill entirely, contact Safaricom customer care at 100 (free from a Safaricom line) within seven days to request a reversal, though a successful reversal isn’t guaranteed once funds have already been credited. For deposits that appear stuck or unconfirmed on the KCB side despite a successful M-Pesa transaction, contact KCB customer support directly with your M-Pesa transaction code on hand — this speeds up their ability to trace and resolve the issue.
Join The Discussion
Have you used the M-Pesa to KCB paybill method regularly, and how has your experience been with transaction speed or fees? Share any tips for avoiding common mistakes, or a time you had to sort out a delayed or misdirected deposit. If you’re running into an issue with a transaction right now, feel free to ask — there’s a good chance someone here has dealt with a similar situation.
