The store with no middleman on payments: inside a live eDukan build

A payment gateway is the easiest thing to add to an online store and the most expensive thing to keep. The standard 2–3% fee sounds small until you put it against MSME retail margins — for many product categories, the gateway quietly takes a tenth of the profit on every order.

When we built this retailer's store, that fee was treated as a design problem. The answer: for UPI, remove the middleman entirely.

At checkout, the store creates the order and renders a UPI QR that points directly at the store's own UPI ID — the customer pays from GPay, PhonePe, or any UPI app, and the money lands in the store's account with no gateway between them. A one-tap WhatsApp button lets the customer send their payment screenshot against the order number; the store confirms it from the admin, which triggers the automatic "payment approved" message and writes an audit-log entry.

Card checkout via Razorpay is built in behind a switch — with server-side signature verification and an idempotent webhook that can't double-process a payment event — for the day the store wants it on. The point is choice: the free rail is the default, the paid rail is optional.

After payment, the engine runs the conversation. Seven order events — placed, payment approved, payment failed, refunded, shipping update, delivered, cancelled — each send automatically on both WhatsApp and email, from 14 message templates the store can edit without a developer. The WhatsApp side runs on Meta-approved templates, most of them in Hindi, because that's the language the customers actually read.

It goes further than order updates. A cart abandoned for 30 minutes gets a WhatsApp nudge with a coupon. A delivered order gets a review request the next day. And an inbound WhatsApp bot answers the routine questions — track my order, show categories, payment help — including a product carousel, with every rule editable from the admin. STOP and START keywords work in English, Hindi, and Gujarati, with consent recorded the way India's DPDP Act expects.

Behind the storefront sits a 15-module admin: orders, products, categories, promotions, banners, FAQs, users, reviews, trending, store settings, message templates, communication logs and more — plus camera-scan order lookup, CSV bulk product import, one-click database backup, and a maintenance-mode switch. Two staff roles (admin and manager) keep sensitive areas gated.

One module deserves its own mention: Counter Rewards connects the physical shop to WhatsApp. Staff photograph a bill and send it with one structured caption; the system logs the sale, applies the customer's tier discount, and issues partner coupons automatically — a loyalty programme with no loyalty software for the customer to install.

Festival season is when an MSME store earns its keep — and when cheap builds fall over. Order numbers are generated without database contention (the design target in the code: 100+ orders a minute). Notifications send after the customer gets their confirmation, so checkout never waits on WhatsApp. Images live on Cloudflare R2, logs stream to Axiom, a token-guarded health endpoint watches the database and storage, and 176 automated tests cover checkout, promos, consent, and the payment webhooks.

Stock logic is honest too: inventory is deducted when an order actually ships, and restored automatically if a shipped order is cancelled — so festival-rush overselling and phantom stock-outs don't happen by accident.