Skip to content

Integrate Razorpay

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.

Integrate Razorpay — done properly, by senior engineers

Krapton’s payment engineers integrate Razorpay into web and mobile products so UPI, cards, netbanking, wallets, EMI and recurring payments all settle into one ledger you can reconcile. The integration looks simple in the docs, and that is where production bugs tend to start: amounts taken from the browser instead of a server-created order, success screens trusted without verifying razorpay_signature, payments stuck in authorized because capture settings were never configured, and webhooks processed twice when Razorpay retries. We build it server-first. Your backend creates each Order through the Orders API in paise, Standard Checkout or a Custom Checkout UI collects payment, and the server verifies the HMAC SHA256 signature before marking anything paid. Webhooks such as payment.captured, order.paid, refund.processed and subscription.charged are verified against the raw body, deduplicated by event ID and processed from a queue, with a scheduled job that polls Razorpay’s Orders API for anything a webhook missed. For recurring billing we configure Plans and Subscriptions with UPI Autopay or card mandates under RBI rules. You receive the integration, test-mode scenarios for each payment method, and a reconciliation report matched against Razorpay settlements.

What you're seeing

You want Razorpay live in India / globally with proper UPI, cards, EMI, and subscription support.

Our approach

We integrate Razorpay Standard + Custom Checkout, wire webhooks with retries, and ship a subscription + recurring-payment flow you can audit.

Symptoms teams come to us with

  • Customers are charged, but your database still shows the order as pending or failed.
  • The Razorpay dashboard lists payments in authorized state that were never captured and later auto-refunded.
  • Duplicate fulfillment or double credit happens when the same webhook event arrives more than once.
  • UPI payments on mobile time out or never return the user to your app after approval.
  • Finance cannot match Razorpay settlements, fees and GST to individual orders without spreadsheets.

What we build in

  1. Payment success is decided by the checkout handler in the browser, not by a server-side verification.
  2. Webhook handlers parse JSON before checking X-Razorpay-Signature, so the HMAC never matches the raw body.
  3. Handlers are not idempotent, so Razorpay’s retries or out-of-order events trigger repeated side effects.
  4. Amounts are sent in rupees instead of paise, or currency handling assumes INR for international cards.
  5. Payment capture settings were left manual, and no job captures authorized payments before they expire.

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

  • Server-verified payments only

    An order is marked paid only after the server checks razorpay_signature or receives a verified webhook, so a tampered client callback cannot release goods.

  • Payment methods tested end to end

    UPI intent and QR, cards, netbanking, wallets and EMI are each exercised in test mode, including failures and user cancellations, before live keys are switched on.

  • Recurring billing on proper mandates

    Subscriptions use Razorpay Plans with UPI Autopay, eMandate or card recurring, and halted or pending subscriptions trigger dunning emails and access rules you define.

  • Reconciliation down to each settlement

    A daily job pulls the Settlements and Payments APIs, matches each settlement to orders, refunds, fees and tax, and flags any mismatch for finance to review.

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 integrate Razorpay, 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 checkout in India

    A custom Next.js or React Native storefront accepts UPI, cards and EMI through Razorpay Checkout, with order status driven by verified order.paid webhooks rather than redirects.

  • SaaS subscriptions for Indian customers

    Monthly and annual plans bill through Razorpay Subscriptions with UPI Autopay, GST-compliant invoices are generated per charge, and plan changes are prorated in your own billing logic.

  • Marketplace payouts with Route

    A multi-vendor platform collects once and splits funds to sellers through Razorpay Route linked accounts, holding transfers until delivery and reversing them when an order is refunded.

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

Integrate Razorpay — your questions, answered

How much does it cost to integrate Razorpay?

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 integrate Razorpay?

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.

Should we integrate Razorpay Standard Checkout or Custom Checkout?

Start with Standard Checkout unless you have a clear design reason not to. It handles payment method UI, UPI intent on mobile, saved cards and RBI tokenization flows, and Razorpay updates it as rules change. Custom Checkout gives full control over the UI but makes your team responsible for every method’s edge cases, so it suits products with an established design system.

Can Razorpay accept payments from customers outside India?

Yes, once international payments are enabled on your account, which requires Razorpay’s approval and additional documentation. International cards, and other methods Razorpay supports for your account, can then be accepted in supported currencies, with settlement in INR. We store the charged currency and amount beside the INR settlement value on each order for reconciliation.

What happens when a customer pays but closes the app before returning?

The payment still completes, and the order is updated from the server side. Razorpay sends payment.captured and order.paid webhooks regardless of what the browser does, and our scheduled job fetches the order’s payments as a backstop. The customer sees the confirmed order on their next visit, and receives the confirmation email or WhatsApp message triggered by the webhook.

Let's get this off your plate

Send a 60-second brief on Integrate Razorpay and a senior engineer replies within 24 hours with a plan and a fixed quote. NDA on day one, no retainer required.