Merchant Transactions
Merchants work in merchant.conserworks.in (or the C Pay Merchant app). The Transactions list is the daily queue: pending payments from your assigned customers only. You do not see another shop’s customers. That isolation is intentional.
What a card shows
Each request shows the customer name, mobile, email, app, amount, coins to credit, user ID, UTR, time, and a screenshot button. Open the screenshot first. Compare payer name, amount, and UTR with what you received in UPI. If the screenshot is unreadable, reject with a short reason or ask the customer to resubmit — do not guess a UTR.
When the customer chose the wrong package
People often pay a round number (₹2,000) while the catalogue row was ₹2,091. Rejecting that payment after money arrived creates anger and extra UPI. C Pay lets you edit App, Amount, and Coins to credit with the same pencil-and-Save pattern as UTR. Change amount to what actually landed. Change coins to what you will really credit — do not leave the 2,091-row coins if you only received ₹2,000. Change app if they tapped the wrong live app.
Save each field, then Approve. Approve uses the values in the database at that moment: stock deduct follows the new app and coins; the Invoice Cum Receipt follows the new amount. If you approve first and edit later, stock and receipt are already done — same as UTR correction, which does not re-run payment.
UTR and payer name
UTR pencil fixes OCR or typing mistakes. Duplicate UTRs that are already used on a pending or verified payment cannot be saved. Payer name can be set when the UPI name differs from the profile name. That name is for this payment and receipts; it does not rewrite the customer’s registered profile.
Approve and reject
Approve is for money you accept. It notifies your C Us payment group, emails the customer, writes the sheet row, and deducts recharge stock. Reject is for money you did not get, wrong UTR, or a screenshot you cannot trust. Reject does not invent a catalogue row. After reject the customer may submit again with a new UTR if they pay correctly.
Master admin logins do not show these pencils. Shop owners and their team on that merchant do. Next: customer flow, receipts, how to apply.
Notifications after approve
Approve notifies the payment destination configured for your merchant — not a random other shop that happens to share a platform bot. If alerts go to the wrong chat, that is a credentials/config issue on this merchant, not “approve the neighbour’s queue”. Confirm C Us / Telegram targets before peak hours. Wrong chat is an ops bug, not a reason to approve blindly.
Stock and empty catalogue
Stock deduct follows the app and coins at approve time. If stock is too low, customers should not be able to complete a healthy submit for that package. Refill before you advertise a package. Approving a payment you cannot recharge creates a support ticket you will not enjoy. Low-stock alerts exist so you refill in time.
Manual recharge vs customer submit
Some shops also enter a payment from the merchant side (manual). The same UTR uniqueness and twelve-digit Paytm Ref No rules apply. Do not paste a customer UTR into a second manual row “for backup”. One payment, one row.