Why a deposit does not complete

Deposits into a KiddyCash family wallet can fail silently or stall at different points in the payment pipeline. This article walks through the known failure modes, their root causes, and how to resolve them — with precision.

Symptoms

You may be dealing with a failed deposit if you observe any of the following:

  • The deposit form at https://kiddy.cash/family/:family_id/deposit submits but the balance does not update
  • An M-Pesa STK push is triggered but the transaction never reflects in the wallet
  • A KES deposit shows as pending for more than 15 minutes with no status change
  • The app returns a generic “deposit could not be processed” error with no additional detail
  • A parent or guardian receives an M-Pesa confirmation SMS, but the child’s wallet shows zero credit

Causes

Deposit failures typically originate from one of four layers: account state, bank integration, verification status, or transaction processing.

1. Account or family state issues

If the family account is suspended, incomplete, or flagged for review, inbound deposits are blocked at the gateway layer — even if the external payment (e.g. M-Pesa) succeeds. The funds may leave the sender’s mobile money account but will not settle into the KiddyCash wallet. Check the family’s status in the app. Subscriptions that have lapsed can also freeze deposit routing for child wallets within that family.

2. Unverified or rejected KYC/KYB

KiddyCash enforces identity verification before allowing deposits above certain thresholds. If your KYC submission was rejected — for example, a mismatched name on a Kenyan national ID or an expired document — deposits above the unverified limit will fail. Review the reasons a verification gets rejected to diagnose whether your identity state is the blocker. Businesses and schools using KiddyCash are subject to KYB checks; a pending KYB review will suppress deposit settlement for all associated wallets.

3. Bank integration failures

KiddyCash connects to local and regional bank rails to process deposits. These integrations occasionally experience degraded states — timeouts, mismatched transaction references, or provider-side errors. If you are depositing from a bank account rather than M-Pesa, read what’s new in bank integrations in KiddyCash and a closer look at bank integrations in KiddyCash to understand how these rails behave and what current limitations exist. A failed bank-originating deposit will typically not debit your account — but always confirm with your bank.

4. Transaction stuck in pending

Sometimes a deposit is not failed — it is simply taking longer than expected to confirm. Mobile money networks in markets like Kenya can experience delays during peak hours. Before treating a transaction as failed, check whether it is genuinely stalled by reviewing why a transaction stays pending too long.

Solutions

  1. Verify family and account status — Navigate to https://kiddy.cash/family/:family_id/deposit and confirm no banners indicate a suspended or restricted state.

  2. Resolve KYC/KYB holds — Re-submit verification documents if rejected. Ensure the name on your document matches the registered account name exactly, including hyphens and spacing.

  3. Retry with a different payment method — If a bank transfer is failing, try M-Pesa or another available rail as a diagnostic step.

  4. Wait and monitor for pending deposits — Allow up to 30 minutes before escalating. M-Pesa network delays in Nairobi and other urban centres are common during evening peak periods.

  5. Contact support with the transaction reference — Every deposit attempt generates an internal reference. Provide this to the support team so they can trace the deposit through the payment pipeline, including any webhook or callback failures on the provider side.