AssureShift.in · Mover Portal v2 · wallet

Wallet — same manual top-up, made clear

No payment gateway this pass. The vendor pays out-of-band (UPI / bank) and self-reports a reference; ops verify and credit. The polish: a clearer pay-then-report flow and a visible "top-up under review" status so nobody wonders where their money went.

Balance + ledger

AssureShift · Leads
₹4,250
Wallet balance
₹4,250
≈ 9 leads at current prices
+ Add funds
Top-up under review. ₹2,000 · UPI ref 4471…8821 · reported 2h ago. We'll credit once verified (usually same day).
Recent activity
Lead · Pune → Mumbai− ₹450
Refund · Pune → Nagpur+ ₹300
Top-up · UPI+ ₹5,000
Lead · Pune · within city− ₹300

Add funds · step 1 — pay

AssureShift · Leads
₹4,250

Add funds

Step 1 of 2 · pay to our account, then tell us below.

Amount to add
Pay to
assureshift@okhdfcbank
UPI · or bank transfer — A/c 5011xxxx · IFSC HDFC00xxxx
I've paid — next ›

Add funds · step 2 — report the payment

AssureShift · Leads
₹4,250

Confirm your payment

Step 2 of 2 · so we can match & credit it fast.

Amount paid
UPI / bank reference no.
Paid from (optional)
We verify against our account and credit your wallet — usually the same day. You'll see a "top-up under review" note until then.
Submit for verification
Small change, big clarity

Pay → report → "under review" → credited

Backed by the existing topup-requests + transactions collections — no gateway, no new money rails. The wins are all trust:

  • Split into pay then report, so the reference number is captured right after paying.
  • A persistent "top-up under review" banner (+ on Home) until ops credit it.
  • Pay-to details come from env (PORTAL_TOPUP_UPI_ID / _BANK); unset → "contact your manager" fallback stays.

Gateway-ready later: this same screen swaps the "pay to" block for a checkout button without a redesign.

Throwaway mock · mockup.csoul.cloud/as-leads-portal-v2/wallet.html · noindex