Razorpay
The default choice for Indian D2C stores. Best card + UPI success rates, same-day settlement options, subscriptions with e-mandate support and native UPI intent flow.
Cards · UPI · Netbanking · Wallets
Payment gateway integration
in WordPress
Razorpay, Stripe, PayU, Cashfree, Instamojo, PayPal — integrated properly into WordPress and WooCommerce. Custom integration that reconciles payments, handles failed transactions and manages subscriptions, not a plugin that silently drops webhooks and loses orders.
50+
Integrations
₹0
Card data stored
100%
Reconciled
3–5d
Single gateway
Free · No obligation
Get a free quote
Tell us which gateway. We reply in 1 business day.
What happens next
A 30-min call about your payment flow
Fixed written quote with timeline and price
You meet the developer building the integration
50+
Gateways integrated
Payment gateway integration in WordPress is the bridge between your customer clicking "Pay" and money landing in your bank account. It covers the checkout flow, the redirect or hosted checkout page, the callback or webhook that confirms payment, and the reconciliation between the gateway's records and your WooCommerce orders.
Most stores start with a free payment plugin. It works — until it doesn't. Webhooks get dropped, refunds don't sync, orders get marked as paid when the payment actually failed. We build custom integrations that treat payment as what it is: your business's most important transaction. Reconciled, logged, and matched to your GST invoices.
A payment gateway is a service that authorises and processes card, UPI, netbanking and wallet payments — Razorpay, Stripe, PayU, Cashfree. The gateway handles the actual money movement. Integration is the work of wiring that service into your WordPress site so it fits your checkout flow, your orders and your accounting.
It's not just "customer clicks pay, money appears". A proper integration handles: initiating the payment, verifying the response, handling the callback or webhook, marking the order as paid, generating a GST invoice, recording the payment for accounting, and retrying or escalating when things go wrong.
Minimal example — a Razorpay webhook receiver
// Verify Razorpay signature, then mark order paid $body = file_get_contents( 'php://input' ); $sig = $_SERVER['HTTP_X_RAZORPAY_SIGNATURE']; $secret = defined( 'RAZORPAY_WEBHOOK_SECRET' ) ? RAZORPAY_WEBHOOK_SECRET : ''; if ( hash_hmac('sha256', $body, $secret) !== $sig ) { status_header( 401 ); exit; } $event = json_decode( $body, true ); // ... idempotency check, order lookup, mark paid
Signature verification is non-negotiable — the plugin route often skips it.
Every webhook the gateway sends must be signature-verified. If the signature doesn't match, we reject it with a 401 and log the attempt. Without this, anyone can POST "order paid" to your endpoint and mark orders as complete without payment.
Gateways retry webhooks. Networks duplicate them. Without idempotency, a single successful payment can be recorded three times, and a customer sees three invoices. Every webhook handler we build checks if the event has already been processed before acting.
Every payment in the gateway dashboard must map to a WooCommerce order. Every refund to a cancelled or refunded order. Every settlement in your bank to the sum of payments minus fees. A nightly reconciliation job catches drift before it becomes a financial loss.
The moment a payment succeeds, a GST-compliant invoice gets generated with HSN codes, CGST/SGST/IGST split by shipping state, and a proper invoice number series. For B2B customers, their GSTIN is captured and printed on the invoice for input tax credit.
What most integrations get wrong: treating "payment succeeded" as the end of the flow. In reality, that's the beginning. Failed webhooks, delayed settlements, partial refunds, disputes and chargebacks all come later — and a good integration handles them as reliably as the initial payment.
Every gateway has its own API quirks, webhook formats and settlement cycles. These are the ones we've integrated most — and the ones you're most likely to need for Indian and international payments.
The default choice for Indian D2C stores. Best card + UPI success rates, same-day settlement options, subscriptions with e-mandate support and native UPI intent flow.
Cards · UPI · Netbanking · Wallets
The best choice for international payments and SaaS subscriptions. Excellent developer docs, strong fraud protection, subscription management built in. Higher fees for Indian cards than Razorpay.
Cards · Wallets · Subscriptions
Popular for higher-volume Indian stores. Strong UPI performance, decent netbanking coverage and competitive card rates. Good fallback gateway when Razorpay failures are high.
Cards · UPI · Netbanking · EMI
A modern Indian gateway with same-day settlements, subscription mandates and UPI-first checkout. Popular with startups and digital businesses that want fast settlement cycles.
UPI · Cards · Netbanking · Subscriptions
Best for small businesses, digital products and quick-pay flows. Simple API, low setup friction, popular with consultants, educators and creators on WooCommerce.
Cards · UPI · Netbanking
Best for international buyers who don't want to enter card details on an Indian site. Slower settlement, higher fees, but trusted worldwide. Works well as fallback for international orders.
Cards · PayPal balance
A familiar checkout for Amazon customers. Strong UPI and wallet coverage, growing card success rates. Adds credibility for small stores that customers haven't heard of yet.
Cards · UPI · Amazon balance
One of India's oldest gateways with wide coverage, but a slower integration experience. Used by established businesses and some government-adjacent sectors where its reputation matters.
Cards · UPI · Netbanking · EMI
Route payments to whichever gateway has the best success rate by card type, currency, customer location or order value. Failed payments automatically retry on the next gateway. Best for stores above ~₹10L/month.
Any combination · Fallback routing
Free payment plugins work — until they don't. This is what you actually get from each approach, in the failure cases that matter.
Very small stores (under 20 orders/month), test stores, or businesses still validating demand. If payments are occasional and lost orders cost little, the tradeoff is reasonable.
Any store above ~₹3L/month in payments. One lost order or unreconciled refund covers the cost of custom integration. Most clients see payback within the first 30 days.
Not optional add-ons — baseline on every payment integration we build. If a payment flow is missing any of these, it isn't finished.
Every payment method the gateway supports — enabled, tested and styled to match your checkout. No methods left disabled because a plugin didn't expose them.
Card data goes directly to the gateway from the customer's browser — never touches your server. Keeps you out of PCI DSS scope and protects you from card data breaches.
Every webhook is HMAC-verified before we act. Failed signatures are logged and rejected. This is the single biggest gap in free plugins, and the reason orders get marked paid without payment.
Duplicate webhooks are detected by event ID and skipped. Failed webhooks retry on a queue. If the gateway goes down mid-payment, the order recovers automatically when it comes back.
A nightly job matches every gateway payment to a WooCommerce order, every refund to a cancelled order, every settlement to the sum of payments minus fees. Discrepancies surface in an admin dashboard.
Invoice generated on payment success with HSN codes, CGST/SGST/IGST based on shipping state, GSTIN for B2B. Auto-emailed to the customer. Downloads available from the account page.
Refunds initiated from the WooCommerce order screen — full or partial — sync back to the gateway automatically. Order status updates, invoice adjusts, customer gets a refund notice.
Recurring billing with RBI-compliant e-mandate registration, pre-debit notification, retry on failed charges, and a customer self-service portal for pausing, skipping or canceling.
Route by card type, currency, customer location or real-time success rate. When one gateway fails, retry on the next. Conversion typically improves 3–8% on stores that add fallback routing.
Every payment attempt logged — success, failure, reason code, gateway reference. Filterable by date, gateway and status. Your team can answer "what happened to this order?" without the gateway dashboard.
Customers with failed payments get an automatic email with a retry link. Pending orders are retried before they expire. Recovers 15–25% of failed transactions without manual intervention.
The integration is delivered as a plugin or theme module in your repository — GPL, yours forever. No license servers, no per-site restrictions, no dependency on us for updates.
Payment integration isn't hard if you're disciplined about testing. Every failure case — declined cards, timeouts, refunds, duplicate webhooks — gets tested before launch, not after.
We discuss your order volume, average order value, payment methods used by your customers, and whether you need subscriptions or marketplace splits. Based on that, we recommend which gateway(s) — sometimes Razorpay, sometimes Stripe, sometimes both.
You provide sandbox API keys (test mode credentials) from your gateway dashboard. We confirm the API supports everything you need — UPI, EMI, subscriptions, splits — and quote the work with a fixed written scope.
The integration is built as a custom plugin or theme module on a staging copy of your site — never on production. Every callback, webhook and status transition handled explicitly. Credentials stored outside the database.
We test: successful payment, declined card, insufficient funds, gateway timeout, duplicate webhook, refund, partial refund, subscription charge failure. Each case has a defined behaviour — no "we'll handle it if it happens" hand-waving.
Live API keys are added, credentials rotated, webhook URLs configured in the gateway dashboard. You make a real ₹1 test payment yourself before we hand over. Both the order and the gateway dashboard must show the transaction correctly.
Written documentation on how to change gateways, rotate keys, view logs and run reconciliation reports. First reconciliation runs alongside you so your team understands the numbers. 30 days of bug-fix support included.
Three tiers based on complexity. Every quote is fixed in writing after the requirements call.
Standard checkout + webhooks
3–5 days
2+ gateways, routed + reconciled
1–2 weeks
Subscriptions, marketplaces, B2B
2–4 weeks
All prices exclusive of GST · Gateway setup fees (charged by Razorpay/Stripe) are not included · Reconciliation retainer from ₹5,000/mo · Payment 50% advance, 50% on go-live
Three projects where custom integration solved something a plugin couldn't.
A Kolkata fashion brand's Razorpay plugin was silently losing ~3% of orders per month — successful payments marked as failed because webhooks weren't being processed. We rebuilt the integration with signature verification, idempotency and a nightly reconciliation job. First month caught ₹42,000 in missing payments.
₹42k
Recovered/mo
0
Lost orders
100%
Reconciled
Recurring payments for a Kolkata F&B subscription brand — Razorpay e-mandate registration, pre-debit notification, dunning for failed charges, and a customer self-service portal for pause/skip/cancel.
PayU + Razorpay fallback routing for a Kolkata B2B supplier. If PayU fails on card, Razorpay picks it up automatically. GST invoices with customer GSTIN printed. Payment success rate went from 91% to 97.4%.
Feedback from founders whose payments are now boring — the way they should be.
The questions we hear most before every payment integration project.
Payment gateway integration in WordPress connects your site to a payment processor like Razorpay, Stripe, PayU or Cashfree, so customers can pay by card, UPI, netbanking or wallet. The integration handles the payment flow, order confirmation, webhook notifications and reconciliation between the gateway's records and your WooCommerce orders.
Razorpay, Stripe, PayU, Cashfree, Instamojo, PayPal, Amazon Pay and CCAvenue. We also integrate custom payment processors for B2B, education and healthcare where standard gateways don't fit. Every integration supports cards, UPI, netbanking and wallets where the gateway provides them.
A standard Razorpay or Stripe integration on WooCommerce starts at ₹15,000. Multi-gateway setup with reconciliation, custom checkout or subscriptions ranges ₹30,000–60,000. Complex payment workflows (e-mandates, split payments, marketplaces) range ₹60,000–1,50,000. Every quote is fixed in writing.
A single gateway integration takes 3–5 business days. Multi-gateway with reconciliation takes 1–2 weeks. Subscriptions with recurring mandates and dunning typically take 2–4 weeks. Timeline is confirmed in the written quote.
Free plugins work for simple stores, but they often drop webhooks, fail silently on refunds, and miss reconciliation between gateway and orders. Custom integration handles every edge case properly — failed payments, partial refunds, retries, webhook idempotency — and matches WooCommerce orders to gateway settlements to the rupee.
Yes. UPI is supported by Razorpay, Cashfree, PayU and Instamojo — we enable it within the gateway's checkout flow. For some use cases we also integrate direct UPI intent flows (GPay, PhonePe, Paytm deep links) for mobile-first checkouts, though these require custom handling and are usually only worth it above certain transaction volumes.
Yes. Recurring payments on Indian gateways require RBI e-mandate compliance — registration, pre-debit notification and AFA authentication. We implement these workflows with Razorpay or Stripe and integrate with WooCommerce Subscriptions for renewal, dunning and customer self-service portals.
Payment reconciliation is the process of matching every payment in your gateway dashboard to a corresponding WooCommerce order, and matching every refund to a cancelled or refunded order. Without reconciliation, you silently lose money — failed orders marked as complete, successful payments marked as failed, refunds issued but not recorded.
We never store card data on your server. All sensitive payment data goes directly from the customer's browser to the gateway via their hosted checkout or tokenisation. Your WordPress server only receives a payment token or order reference. This keeps your site out of PCI DSS scope almost entirely.
Yes. Most stores benefit from Razorpay or PayU as primary (best UPI and card success rates in India) plus PayPal or Stripe as fallback for international customers. We build gateway routing rules — by currency, customer location, order value or success rate — so failures on one gateway automatically retry on another.
Failed payments are logged with the full gateway response. The order stays in "pending payment" status, and the customer sees a clear retry option. If the gateway later confirms the payment via webhook (e.g. a bank timeout resolved), we auto-recover the order and mark it as paid. No lost orders, no double-charging.
Yes. We integrate GST invoicing with the payment flow — invoice generated on payment success, HSN codes applied per product, CGST/SGST/IGST calculated based on shipping state. For B2B customers with a GSTIN, the invoice captures it correctly for input tax credit.
Tell us your current gateway, order volume and what's broken. We'll review the flow, recommend the right integration, and send a fixed quote with a clear timeline within one business day.