Sending money to family in Kenya: remittance playbook

Supporting family in Kenya is a recurring corridor - not a one-off wire. Design it like a bill: fixed receive amount, predictable timing, clean records.

Recurring remittance design

1. Agree the monthly KES amount the family must receive
2. Pick a primary provider + backup corridor
3. Automate calendar reminders before rent/school dates
4. Keep a simple ledger for yourself (date, amount, reference)

How money should arrive

M-Pesa is Kenya’s mobile-money backbone. Daily life for residents runs on phone wallets; short-stay visitors usually cannot fully inhabit that stack and should not assume card parity everywhere.

Outbound from a KES account at Equity Bank, domestic legs should use M-Pesa / RTGS Kenya. The shoppable part is the cross-border hop to family or a home mortgage — compare delivered amount, not sticker fees. Recurring remittances from Nairobi get banks’ attention; keep contracts or support context ready when compliance asks. If both you and the recipient can use modern payout networks, avoid SWIFT-by-default just because the branch form still lists it first.

Fee control

• Compare delivered amount, not sticker fees
• Avoid cash-to-cash when bank payout is available
• Watch FX on weekends / thin liquidity hours
• Do not chain multiple conversions

Compliance

Regular support transfers are normal - but sudden size jumps get questions. Keep a simple purpose note (“family support / household”).

Numbers that matter

Mid-market FX vs the board you are shown

The mid-market rate is the midpoint between buy and sell on wholesale markets — the number Google and major FX feeds show for KES. Airport desks, hotel cashiers, and many bank boards price far away from that midpoint. A “0% commission” offer in Nairobi almost always hides the markup inside the rate.

Dynamic currency conversion (DCC) is the terminal prompt that offers to charge your home currency “for convenience.” In Kenya, refuse it: choose KES / local currency so your issuer converts near its published FX rules instead of the merchant’s padded rate.

True-cost matrix (illustrative)

Ignore “$0 fee” headlines. For money into or inside Kenya, rank options by total funded to deliver a fixed KES outcome — including FX distance from mid-market, flat fees, intermediary lifting, and time risk.

Domestic rails worth understanding

Inside Kenya, everyday bank value usually rides M-Pesa and sibling domestic systems — not SWIFT. Tourists meet these rails indirectly (hotel deposits, local contractors). Residents and long-stay expats should treat them as the default once a local account exists.

• M-Pesa is Kenya’s mobile-money backbone. Daily life for residents runs on phone wallets; short-stay visitors usually cannot fully inhabit that stack and should not assume card parity everywhere.
• RTGS Kenya is part of India’s bank transfer stack alongside UPI. RTGS/NEFT handle larger or batch-style bank credits; IMPS is faster retail. Visitors mostly meet them indirectly via hotel bank deposits.
• PesaLink is a domestic Kenya payment rail for KES account-to-account value. Use it for local rent, payroll, and bills once you have a participating account — reserve classic international wires for counterparties that truly cannot receive on local rails.

Week-one money calendar

1. Before you fly: enable issuer travel/security controls; order a backup card; save Equity Bank ATM brands on a map around Nairobi
2. Landing day: skip full-budget airport FX; keep a tiny KES float if you already hold near-mid-market notes
3. Day 1–2: test a small card purchase in KES; refuse DCC; confirm your backup card also works
4. Day 3+: map where cash is still required (markets, tips, intercity desks) and refill only at bank lobby ATMs
5. If staying 30+ days: start local-account checklist early — tourist KYC often fails at Equity Bank

Fee stack anatomy (read this before any big transfer)

Every cross-border move into or out of Kenya is a stack of (1) FX distance from mid-market, (2) explicit send fees, (3) intermediary or network fees, and (4) time risk if the payment misses a payroll or rent cut-off. Marketing that highlights only one of the four is incomplete.

If a card freezes in Kenya

1. Freeze the failed card in your issuer app; do not keep retrying and burning authorizations
2. Switch to the backup card on a different network/issuer — test a small purchase first
3. Withdraw a modest KES float from a Equity Bank lobby ATM if cash is required
4. Use a pre-arranged emergency top-up (partner, multi-currency balance, or stablecoin offramp) — not airport desks for large amounts
5. If both cards fail, contact issuer travel support with merchant name + city; document every fee for dispute

Decision checklist before you commit

1. Write the outcome first: “Recipient holds KShX KES by date Y.”
2. Quote at least two paths (local-rail fintech vs bank SWIFT vs card-funded cash) using the same outcome sentence
3. Confirm the beneficiary can actually receive on M-Pesa — if not, SWIFT may be forced
4. Refuse DCC on every terminal; screenshot rate screens when amounts are large
5. Document fees for expense reports and future disputes

What good looks like

• You can explain the mid-market KES rate vs the board in front of you
• You never accept DCC on POS or ATM prompts in Kenya
• Local outcomes ride M-Pesa when the counterparty can receive them
• Emergency funding does not depend on a single card or airport cash
• Teams use approval controls (multisig) for treasury-scale balances
• You know which Equity Bank (or peer) ATMs you will actually use in Nairobi

Worked example (illustrative — not a live quote)

Suppose the recipient in Kenya must receive exactly KSh1,000 KES (rent slice, tuition installment, or family support). Fix that delivered amount first, then compare providers on what you must fund in your home currency.