Why did my transaction expire?

It is a common scenario: your child is at the school canteen or a local shop in Nairobi, they initiate a KiddyCash payment, and by the time you open the app to authorize it, the request has vanished or marked itself as “Expired.”

While it can be frustrating to have to re-initiate a payment, the expiration window is a deliberate security feature designed to protect your KES balance and ensure that your family’s financial data remains accurate in real-time.

Symptoms of an Expired Transaction

You can usually identify an expired transaction by the following indicators in the KiddyCash app:

Status Label: In the parent’s “Activity” feed, the transaction status shifts from “Pending” to “Expired” (often highlighted in gray).
Child Notification: The child receives a push notification stating the request was not approved in time.
Wallet Reversion: Any funds that were temporarily “earmarked” or held from your parent wallet are immediately released back into your available balance.
Missing STK Push: If the transaction involved an M-Pesa top-up or outward payment, the USSD prompt fails to appear because the underlying KiddyCash request has timed out.

Technical and Security Causes

The primary reason for expiration is the 1-hour approval window. Every transaction initiated by a child requires an explicit green light from a guardian unless specific automation is active.

The Security Buffer: We limit the lifespan of a pending request to 60 minutes. This prevents “ghost” transactions from sitting in your queue indefinitely. If a child makes a mistake or double-taps a payment at a merchant, you wouldn’t want a 3-day-old request suddenly popping up for approval.
Liquidity Locks: When a child requests a transfer, KiddyCash ensures the funds are available. Keeping these funds in a “pending” state for too long would make it difficult for parents to manage their daily budget or pay for other subscriptions and campaigns.
Local Connectivity Latency: In areas with fluctuating network speeds, a push notification might arrive late. If the notification hits your phone 55 minutes after the request was made, you only have five minutes to act before our system scripts trigger an automatic expiration.
Device Battery Optimization: Some Android devices aggressively kill background processes to save battery. This can delay the sync between the child’s request and your notifications dashboard, leading to an accidental timeout.

How to Resolve and Prevent Expirations

If a transaction has already expired, it cannot be “revived.” The child must initiate a new request from their wallet. However, you can prevent this from happening in the future by optimizing your workflow.

Optimize your Approval Process The fastest way to handle requests is to understand the nuances of the interface. Reviewing our guide on how to approve transactions can help you navigate the “Pending” tab more effectively, especially when dealing with multiple children.

Automate with Smart Approvals For recurring or low-risk expenses—like a small daily lunch allowance at school—manual approval for every KES 100 spent can be tedious. By setting up smart approvals, you can define custom rules. For example, you can allow any transaction under KES 500 to go through automatically, while still requiring a manual check for larger amounts.

Find the Right Balance Managing a digital wallet involves balancing freedom and oversight. If you find transactions expire often because you are in meetings or busy, it might be time to increase the “Smart Approval” limits or assign a second guardian (like a spouse or older sibling) who can also receive and approve these alerts.

Summary Checklist

Check your notification settings to ensure “Instant Alerts” are toggled on.
Ensure your phone is not in “Low Power Mode,” which can delay KiddyCash syncs.
If a transaction expires, simply ask the child to re-send the request; it takes less than 10 seconds.

Related articles:

/kb/how-to-approve-transactions
/kb/setting-up-smart-approvals
/blog/balancing-freedom-and-oversight