How to update a business transaction code

Transaction codes define how money moves between your business and a child’s KiddyCash wallet — they carry the payment flow logic, campaign hooks, and category rules that determine what happens when a transaction fires. When any of that changes (a new campaign goes live, you switch from one-time to recurring, or you’re restructuring your subscription tiers), you’ll need to update the code rather than create a new one, so existing transaction history stays linked.

Before you edit, it’s worth viewing the current state of the code to confirm which fields are active and whether the code is already attached to a running campaign. Editing a live code mid-campaign can have downstream effects — more on that below.

When to update vs. replace

Update a code when the change is incremental — a new label, an adjusted amount cap, or a currency correction (for example, shifting a hardcoded amount from USD to KES for your Nairobi-based customers). Create a fresh code when the payment flow itself changes fundamentally, such as moving from a one-time charge to an M-Pesa recurring pull. See how to create a business transaction code if you’re in that situation.

Steps to update a transaction code

  1. Open your transaction codes list. Navigate directly to your code using the business portal URL: https://business.kiddy.cash/business/:business_id/transaction-code/:transaction_code_id Replace :business_id and :transaction_code_id with your actual IDs. You can find both in Settings → Business Profile and the transaction codes table respectively.

  2. Click Edit on the target code. The edit button appears in the top-right of the code detail view. If it’s greyed out, the code is locked — this usually means it’s tied to an active campaign. Pause the campaign first.

  3. Update the relevant fields. Common edits include:

    • Display name and description — these surface to parents and kids in the wallet activity feed, so keep them clear and age-appropriate.
    • Amount or amount cap — if you’re adjusting pricing for a back-to-school promotion or correcting for KES denomination changes.
    • Category tag — affects how the transaction appears in spending reports and badge triggers.
    • Recurrence settings — switch between one-time, weekly, or monthly cadence.

  4. Check campaign linkage before saving. If this code is referenced in a campaign, your changes will immediately affect how that campaign processes payments. KiddyCash has expanded what campaigns can do — read what’s new in campaigns and get a closer look at campaigns to understand the knock-on effects before you commit.

  5. Save and verify. Hit Save changes. The system will validate the updated code and flag any conflicts — for example, if a new amount cap falls below the minimum threshold for your business tier. Resolve any warnings before exiting.

  6. Test the updated flow. Use the Simulate transaction tool (available on the code detail page) to fire a test event against a sandbox wallet. Confirm the correct amount, category, and badge triggers appear as expected before the code goes live to real customers.

A note on audit history

Every edit is logged under the code’s History tab with a timestamp and the account that made the change. If your business operates across multiple cities — say, Nairobi and Mombasa — and different team members manage codes, this audit trail is your first stop when diagnosing unexpected transaction behaviour.