Table of Contents

#80 — "Prepaid" payment method has no connection to the Customer Wallets module (Resolved)

← Back to Manara Bugs · View issue #80 in MantisBT


Reported by: Khaled Tarabay on 2026-07-27T12:07:54+01:00
Assigned to: Claude
Resolved by: Claude on 2026-07-27T12:46:52+01:00
Severity: major
Priority: normal
Reproducibility: always
Category: General

Description: Selecting “Prepaid” as a Payment Method when recording a payment does not check, deduct from, or create any record in the separate Customer Wallets module despite sharing the name and implying that relationship. The Payments module offers “Prepaid” as one of five payment methods (Cash, Mobile Wallet, POS, Postpaid, Prepaid). The app also has an entirely separate Customer Wallets module (/wallet) tracking real prepaid balances per customer. Recording a $45.00 payment with method=“Prepaid” against a customer with zero wallet history succeeded normally (invoice PAID updated to $45.00) but the customer never appeared in the Customer Wallets list no wallet entry was created, no balance was checked or drawn down, and there was no block despite the customer having no available prepaid funds. The two “Prepaid” concepts are functionally unrelated; the payment method is effectively just a label.

Steps to Reproduce: Pick (or create) a customer who does not currently appear in /wallet. Create and Issue an invoice for that customer with a line item (e.g. $45.00). Record a payment against it with Payment Method = “Prepaid” for the full amount. Confirm the invoice shows PAID = full amount, Status = Paid. Go to /wallet and confirm the customer still does not appear anywhere in the list (no entry, no balance change).

Resolution: NOT A BUG — confirmed as-designed, matching an existing, already-answered precedent in this codebase for the identically-shaped “Mobile Wallet” payment method.

The Customer Wallets module (/wallet) is this app's own internal prepaid store-credit ledger (customer_wallets / wallet_transactions) — a customer tops it up and spends it down over time. “Prepaid” (like Cash, POS, Mobile Wallet, Postpaid) is simply one of five entries in the payment_methods catalog recorded on a Payment row when money is collected — it's a LABEL describing how the money physically arrived (the customer had already prepaid for service via some external means before this transaction), not a pointer into the Customer Wallets feature. The two systems have always been intentionally unrelated in this codebase; the exact same question was investigated and answered for the “Mobile Wallet” payment method in an earlier session: “the two systems have ZERO code linkage today… that's correct, not a bug, since gating a payment collection method on an unrelated internal balance feature would be inconsistent with how every other payment method already works.” That reasoning applies identically to “Prepaid.”

Automatically wiring “Prepaid” (or any payment method) into the Customer Wallets balance would be a real, deliberate feature decision — not a bug fix — since it would mean every payment recorded with that method now also creates/draws down a wallet entry, a behavior change with real implications for existing invoices already paid that way. If that linkage is actually wanted going forward, it's the same well-tested bridge already built for Mantis #52 (wallet-sourced payments, via WalletTransaction::applyAsInvoicePayment()) — worth raising as a feature request with the intended direction of the link (does selecting “Prepaid” DRAW DOWN an existing wallet balance and block if insufficient, the way #52's wallet source does?) rather than assumed from this report alone.

Activity / Notes

The Customer Wallets module (/wallet) is this app's own internal prepaid store-credit ledger (customer_wallets / wallet_transactions) — a customer tops it up and spends it down over time. “Prepaid” (like Cash, POS, Mobile Wallet, Postpaid) is simply one of five entries in the payment_methods catalog recorded on a Payment row when money is collected — it's a LABEL describing how the money physically arrived (the customer had already prepaid for service via some external means before this transaction), not a pointer into the Customer Wallets feature. The two systems have always been intentionally unrelated in this codebase; the exact same question was investigated and answered for the “Mobile Wallet” payment method in an earlier session: “the two systems have ZERO code linkage today… that's correct, not a bug, since gating a payment collection method on an unrelated internal balance feature would be inconsistent with how every other payment method already works.” That reasoning applies identically to “Prepaid.”

Automatically wiring “Prepaid” (or any payment method) into the Customer Wallets balance would be a real, deliberate feature decision — not a bug fix — since it would mean every payment recorded with that method now also creates/draws down a wallet entry, a behavior change with real implications for existing invoices already paid that way. If that linkage is actually wanted going forward, it's the same well-tested bridge already built for Mantis #52 (wallet-sourced payments, via WalletTransaction::applyAsInvoicePayment()) — worth raising as a feature request with the intended direction of the link (does selecting “Prepaid” DRAW DOWN an existing wallet balance and block if insufficient, the way #52's wallet source does?) rather than assumed from this report alone.

Full History

Date User Field Change
2026-07-27T12:07:54+01:00 Khaled Tarabay issue-new New Issue
2026-07-27T12:46:45+01:00 Claude Assigned To ⇒ Claudine
2026-07-27T12:46:47+01:00 Claude tag-added Tag Attached: done-by-claude
2026-07-27T12:46:49+01:00 Claude note-added Note Added: 0000039
2026-07-27T12:46:52+01:00 Claude Status new ⇒ resolved

Synced automatically from MantisBT issue #80.