Feature #11315
closedFeature #7963: In product quotation from admin panel will able to update the real time payment using card / pos terminal like landscaping invoice payment flow and send payment notifications based on the flag from admin side
What is the difference between the processing to paid and approved to paid..
100%
Description
a processing needs an confirmation rather record payment and
approved quotation need a record payment
Files
Subtasks
Related issues
Updated by Divya Inapakurthi about 10 hours ago
Issue: Clicking Confirm Payment on a quote where the customer already submitted their payment method (e.g. Cash $5.14) opened the full, unnecessary split-payment method selection modal.
Solution For Processing (inprogress) Quotes: Clicking Confirm Payment opens a dedicated 1-Click Verification Dialog showing the customer's submitted payment method, check number, and amount, with an optional note and a single "Confirm & Complete" button.
Fallback: Includes a "Change Method / Split" link in case the admin needs to switch methods.
For Approved / Partial Quotes: Continues to open the full Record Payment / Split Payment Modal for entering fresh payment details.
Updated by Divya Inapakurthi about 9 hours ago
for confirm payment why do we get this paid on twice after the payment submitted ?
Issue 1: Duplicate Paid on ... entry appearing right after Payment_confirmed
Why it happened: When you clicked "Confirm Payment", two separate backend services were saving the quote:
product-quote.controller.js added Payment_confirmed to the quote history.
sale.service.js then updated the sale status and automatically pushed a second entry (Paid on ... Note: Payment completed successfully via (cash)) to the same quote's history.
Solution:we updated the deduplication check. When a payment action (payment_confirmed or payment_recorded) has already been logged, sale.service.js skips adding the redundant Paid entry.
Issue 2: The text displayed Payment_confirmed by on ... with underscores and empty "by"
Why it happened:
Some database records had action stored with _by at the end (e.g. "payment_submitted by" or "payment_confirmed by").
The previous formatter rendered the word "by" even when no user name (history.performedBy) was attached, resulting in "Payment_submitted by on 11:05 AM".
Solution: we cleaned the title formatter:
Strips any trailing _by or by from the stored action string.
Replaces all underscores _ with proper spaces and Capitalizes Each Word.
Only renders "by [Name]" if a valid admin/user name actually exists.
Updated by Divya Inapakurthi about 9 hours ago
- Status changed from New to Closed