Skip to main content
Menu

Features

Everything PayMQR does today

Ask for a payment, let a customer pay it, collect the evidence and decide. Everything below is available today.

Payment links

A URL you send to a customer. Opening it starts a payment to your business.

  • One-time, fixed amount — stops working after the first payment is created from it.
  • Reusable, fixed amount — many customers, same amount, a separate payment each.
  • Customer-entered amount — you set an optional minimum and maximum.
  • Optional expiry, and a switch to disable a link without deleting its history.
  • A share QR of the link itself, to print or show.

Direct UPI QR codes

A saved, printable code that pays you straight from any UPI app.

  • Static — goes on your counter. The customer scans it and types the amount in their own app.
  • Fixed amount — your figure is inside the code, so their app opens with it already filled in.
  • Codes are drawn as inline SVG. Nothing is uploaded, cached or served from another host.
  • These pay you directly, so PayMQR does not see them — no checkout, no screenshot, no verification.
  • For those, use a payment link or the API. Both go through the full PayMQR checkout.

Hosted checkout

One PayMQR page your customer pays on, whatever started the payment.

  • Your business name and the exact payable amount, largest on the page.
  • A UPI payment QR, plus a deep link for a customer paying on that phone.
  • A unique-paise suffix so an amount can be matched back to one order.
  • Clear wording when a payment is already paid, under review, expired or closed.
  • Checkout links are time-limited and can be re-opened at any time.

Payment proof

The customer sends the screenshot on the same page they paid from.

  • JPG, PNG or WEBP, validated on the server — not just by the file picker.
  • Stored privately. Proof images are never web-served and never public.
  • A customer can send another screenshot; nothing already sent is replaced.
  • Clear, customer-safe messages when a file cannot be used.

Verification and manual review

PayMQR checks evidence against the order it belongs to.

  • Deterministic rules decide, against that order's own amount and destination.
  • Anything uncertain goes to your review queue rather than being guessed.
  • You approve or reject, with an optional reason code and a private note.
  • A decision is final, and the whole timeline stays on the payment.

Analytics

Counts and exact totals from your own orders. No estimates.

  • Today, last 7 days, last 30 days, or a date range you choose.
  • Computed in your own display timezone, not the server's.
  • Payments created, verified, still open, under review, rejected and expired.
  • The chart's figures are repeated as a table for anyone who prefers one.

REST API

Create payments from your own system and hand your customer a checkout URL.

  • Bearer API keys, separate for test and live.
  • Create a payment, read its status, open a hosted checkout.
  • Amounts are decimal strings. Repeating a request with the same idempotency key returns the same payment.
  • Every response says which environment it belongs to.

Webhooks

Signed events when one of your payments changes.

  • Six event types covering the payment lifecycle.
  • HMAC-SHA256 signature per endpoint, so your server can trust the payload.
  • Automatic retries with backoff. Secrets can be rotated with an overlap window.
  • Separate endpoints for test and live.

Test and live, kept apart

A test payment can never collect money.

  • A test key creates test payments; a live key creates live ones.
  • A test checkout shows no UPI ID, no QR code and no pay button at all.
  • Test and live payments, keys and webhook endpoints are listed separately.

Payment accounts

The UPI destinations you already use.

  • Add several, pick a default, deactivate one without losing its history.
  • The destination is frozen onto a payment when it is created — changing your default later never redirects an existing payment.

Security and audit

Your data stays separate, and every change is recorded.

How PayMQR is secured

  • Each merchant sees only their own data.
  • Every payment status change is recorded on the payment itself.
  • Privileged platform actions are written to an append-only audit log.

Try it on your own account

The free plan includes everything on this page. Add your UPI account and share a link.