Chetana helps shops and service businesses catch fake screenshots, suspicious UPI claims, local-language pressure messages, and handover fraud before they release goods, delivery, or service.
After install, staff can share suspicious payment messages or links into Chetana from WhatsApp, SMS, or browser tabs instead of retyping them at the counter.
This does not replace the backend. It repackages the current merchant packet logic into a simpler public landing page.
Capture the screenshot text, settlement claim, or chat proof. Add the amount, merchant UPI, and expected UTR if you have them.
Use the existing merchant assessment logic to see suspicious signals, next steps, and the safest immediate action.
Preserve the screenshot, order notes, UTR expectations, and official rails so staff can act consistently under pressure.
Screenshot text, pasted settlement claims, and buyer chat are treated as evidence input, not as proof of payment by themselves.
UPI handles, claimed amount, UTR or reference expectations, and missing settlement details all shape the release or hold decision.
Driver waiting language, hurry-up handover requests, and screenshot-only urgency are treated as real risk signals, especially in local-language messages.
Use light workflow first. Public checks can stay minimal; durable case records should be explicit operational decisions, not silent background storage.
Use this when the proof is screenshot-only, the UPI handle does not match, the UTR is missing, or the buyer is creating urgency.
Use this when the claim may be real but the money is not visible in the merchant ledger or bank app yet.
Use this only when the identifiers line up and the payment is visible in the official merchant account or settlement surface.
Printable counter sign that sets the rule before a buyer starts pushing with screenshot-only proof.
Short operating flow for staff: capture the proof, check identifiers, confirm settlement, and keep the state explicit.
Copy-paste responses for screenshot received, waiting for settlement, reference requested, and pressure handover refused.
Basic scam checks, evidence saving, and the consumer front door.
Merchant proof review, case history, poster and SOP pack, and simple daily summaries.
Multiple staff, richer queueing, exports, repeat identifier tracking, and stronger workflow controls.