Skip to content

Add UPI payments to website

PCI-aware checkout that converts and reconciles cleanly

  • Senior engineers · IST + EST overlap
  • NDA on day 1
  • 24-hour reply

Tell us what you need fixed

Reply in 24 hours · NDA on day 1 · No spam.

Add UPI payments to website — done properly, by senior engineers

Krapton’s engineers add UPI payments to website checkouts through Razorpay, Cashfree or PhonePe, covering mobile intent flows, desktop QR codes and the asynchronous confirmation that UPI depends on. UPI looks simple from the customer’s side, but the payment completes inside a separate app, so your page often loses context: the tab is backgrounded, the redirect is skipped, or the bank confirms several seconds later. Integrations that trust the browser callback create stuck orders, duplicate charges and refund disputes. We create one gateway order per checkout tagged with your own order reference, show UPI app buttons on mobile and a dynamic QR on desktop, and mark the order paid only after a signature-verified webhook or a server-side status call confirms it. Pending payments get a polling window and a clear on-screen state rather than a false failure. Refunds run through the gateway API from your admin, linked to the original order. You receive the integration code, webhook handlers with idempotent processing, a refund flow, and a daily reconciliation job that matches each UTR and settlement line to an order.

What you're seeing

You need UPI on the web with instant confirmation, QR fallback, and clean settlements.

Our approach

We integrate UPI through Razorpay / Cashfree / PhonePe, wire webhooks with idempotency, and add a refund + reconciliation flow.

Symptoms teams come to us with

  • Customers pay in their UPI app, but the order stays pending because the redirect never returned.
  • Desktop shoppers see no usable UPI option because only mobile app-switch links were implemented.
  • Duplicate orders appear when customers retry after a slow bank confirmation on the first attempt.
  • UPI refunds are issued by hand from the gateway dashboard, with no record inside your system.
  • Bank settlement amounts do not match order totals, and nobody can map UTR numbers back to orders.

What we build in

  1. Order status depends on the browser callback instead of signed webhooks plus a server-side status check.
  2. UPI’s pending state is not modeled, so late bank confirmations are recorded as failed payments.
  3. Intent links are shown on desktop, where no UPI app exists, with no dynamic QR fallback.
  4. Gateway orders are created without your own reference, which breaks idempotency and later reconciliation.
  5. Settlement reports, gateway fees and GST on fees are never imported, so net payouts cannot be matched.

Concrete deliverables, no fluff

Every engagement ends with measurable, documented outcomes — no black-box agency reports.

  • Integration with provider of your choice
  • Webhook handling with idempotency + retries
  • PCI-aware token flow, no card data on your server
  • Reconciliation report + admin dashboard

What changes after we ship

  • UPI that works on every device

    Mobile visitors tap a button that opens their installed UPI app, such as Google Pay, PhonePe or Paytm, while desktop visitors scan a dynamic QR tied to the same order and amount.

  • No more stuck pending orders

    Signed webhooks, a server-side status check and a short polling window resolve late bank confirmations, so orders move to paid or failed without manual dashboard lookups.

  • Refunds issued from your admin

    Support staff trigger full or partial UPI refunds from your own admin panel, the gateway refund ID is stored against the order, and refund webhooks update the order’s status.

  • Settlements matched to orders

    A scheduled job imports gateway settlement reports, separates fees and GST on fees, and matches each UTR to an order, flagging gaps for finance before month-end.

From brief to shipped fix

A transparent, low-risk process — a senior engineer reads your brief personally, and nothing starts until you approve a written plan and price.

  1. 01Day 0–1

    Diagnose

    A senior engineer reviews your brief, reproduces the issue, and pinpoints the real root cause — not the symptom — before any code is touched.

  2. 02Within 24h

    Scoped plan & quote

    You get a written plan to add UPI Payments to Website, a firm timeline, and a fixed quote. Nothing starts until you approve it — no surprise invoices.

  3. 031–3 weeks

    Ship the fix

    We implement on a branch and open a pull request you review, working to your code-review standards on your repo — never a black box.

  4. 04On delivery

    Verify & hand off

    We verify on staging and production, share before/after evidence where it applies, and leave you a short hand-off note so the fix sticks.

Situations we handle

  • D2C store adding UPI checkout

    A custom Next.js or WooCommerce store where UPI becomes the first payment option for Indian shoppers, with cards and netbanking kept as fallbacks inside the same Razorpay or Cashfree checkout.

  • Event and course registrations

    Ticketing or course sign-ups where seats are held while the customer approves the UPI payment, then released automatically if the payment expires or fails, and confirmation emails go out only after the webhook arrives.

  • Invoices with UPI payment links

    B2B or service businesses that send invoices carrying a UPI payment link or QR, with partial payments recorded and the outstanding balance updated from gateway events.

Why teams hand this task to Krapton

  • Senior engineers only

    Your brief is read and handled by a senior engineer — no junior hand-off, no sales-rep filter in between.

  • Root cause, not a patch

    We reproduce and fix the underlying cause, then add a guard so the same class of issue does not quietly return.

  • Your repo, your standards

    Every change lands as a pull request you review, on your repository, following your existing review process.

  • NDA on day one

    Confidentiality and IP are covered before we look at a single line of code. All work stays in your accounts.

  • Fixed quote up front

    You approve a written plan and price before work starts. If scope changes, we re-quote in writing — no surprise invoices.

  • Proof, where it applies

    Performance, SEO and reliability work ships with before/after evidence so the result is measurable, not anecdotal.

Three ways to engage

No retainer required. Pick the model that matches the work — pricing for this task starts from $500, with a fixed quote before anything starts.

  • Per task

    Most popular

    One clearly-scoped fix at a fixed price. Best when you know exactly what is broken and want it handled end to end.

    • Fixed quote up front
    • One PR, reviewed by you
    • No retainer required
  • Hourly

    Pay only for the hours worked. Best for diagnostics, audits, or exploratory work where the scope is still emerging.

    • Weekly timesheets
    • Pay for what you use
    • No minimum commitment
  • Per sprint

    A focused 1–2 week sprint when the work is bigger than one fix but smaller than a full project.

    • 1–2 week blocks
    • Clear sprint goal
    • Scale up or stop anytime

Industry-standard stack, no proprietary lock-in

  • Stripe
  • Razorpay
  • PayPal
  • Node.js
  • Webhooks

Add UPI payments to website — your questions, answered

How much does it cost to add UPI Payments to Website?

Pricing starts from $500 and depends on the scope we find during the diagnostic. You get a fixed, written quote before any work begins — most engagements like this run 1–3 weeks.

How long does it take to add UPI Payments to Website?

Typically 1–3 weeks for a focused engagement. After a short diagnostic we commit to a firm timeline so you know exactly what to expect.

Which gateway should we use to add UPI payments to website checkout?

Choose the gateway that fits the rest of your payment mix, because UPI acceptance itself works much the same across them. Razorpay offers broad method coverage plus subscription and payout products, Cashfree is well known for payouts and settlement options, and PhonePe’s gateway is a natural fit when much of your traffic already pays through its app. We compare the fee terms you were quoted, settlement timing, refund APIs and reporting exports before recommending one.

Do customers need to type their UPI ID on our site?

Usually not. On mobile, the intent flow lets the customer pick an installed UPI app and approve the payment there, and on desktop a dynamic QR does the same job from their phone. Entering a UPI ID for a collect request is still offered by some gateways, but we treat it as a secondary option because the customer has to switch apps and find the pending request.

How do you handle a UPI payment that stays pending?

We keep the order open in a pending state instead of failing it. The page polls your server, which calls the gateway’s status API, while the webhook handler waits for the final event; whichever arrives first settles the order, and the second is ignored by idempotency checks. If the payment expires unconfirmed, the order is released and the customer sees a clear retry option rather than a generic error.

Let's get this off your plate

Send a 60-second brief on Add UPI Payments to Website and a senior engineer replies within 24 hours with a plan and a fixed quote. NDA on day one, no retainer required.