Payment gateway integration that makes getting paid simple
We connect your website, app or booking system to the right payment gateway and build a checkout your customers trust, with refunds, webhooks and reconciliation handled properly.
- Stripe
- Razorpay
- PayPal
- UPI
- Subscriptions
Which payment gateway suits which business
A gateway has to do two things: accept the payment methods your customers use, and open an account for a business registered in your country. Start with those two questions, then compare features. Fees, settlement times and onboarding rules change, so we confirm them with each provider at the time of your project.
| Gateway | Typical fit | Points to know |
|---|---|---|
| Stripe | Businesses in countries Stripe supports, selling online to local or international customers | Cards, wallets and many local payment methods, strong developer API, built-in subscription billing |
| Razorpay | Businesses registered in India selling to Indian customers | UPI, cards, netbanking, wallets and EMI, plus payment links and subscriptions |
| PayPal | Sellers whose overseas buyers prefer to pay from a PayPal account | Widely recognised by international buyers, often added as a second option beside a card gateway |
| PayU | Indian businesses and online stores | UPI, cards, netbanking and EMI, with plugins for common store platforms |
| CCAvenue | Indian businesses that need a wide choice of banks and payment options | Customers are usually redirected to a hosted payment page |
| Cashfree, Paytm, PhonePe | Indian businesses with heavy UPI and wallet use | Cashfree also offers payouts to vendors and customers |
| Authorize.Net | Merchants in the United States and Canada, often with an existing merchant account | Long-established gateway supported by most North American shopping carts |
| Square | Businesses that sell both in person and online in countries Square supports | One system for card readers, point of sale and online payments |
Integration types: hosted checkout, embedded or API
Hosted checkout
The customer is sent to a payment page run by the gateway and returned to your site afterwards. Fastest to build, lowest compliance burden, least control over the design.
Embedded checkout
The gateway's secure fields or pop-up appear inside your own page. The customer stays on your site while card data still goes straight to the gateway.
Direct API
Your server talks to the gateway's API and controls the whole flow. Needed for custom flows, and it brings a much larger security and compliance responsibility if card numbers touch your systems.
Payment links and invoices
A link or QR code created from the dashboard or API and sent by email, SMS or WhatsApp. No checkout page required.
Platform plugins
Official plugins for WooCommerce, Shopify and other platforms, configured and tested rather than coded from the beginning.
Payment integration services
Gateway selection
We compare supported countries, payment methods, currencies, settlement arrangements and approval requirements for your business type.
Website checkout
Hosted and embedded checkouts for WordPress, WooCommerce, Shopify, Laravel, Node.js and custom sites.
Mobile app payments
Card, wallet, UPI, Apple Pay and Google Pay payments in Android and iOS apps, within each app store's rules.
Subscriptions and invoices
Recurring billing, payment links, invoices and saved payment methods.
Refunds, webhooks and reconciliation
Webhook handling and a payments table so every payment, refund and failure is recorded and can be matched to settlements.
Multi-currency and international payments
Prices shown and charged in the customer's currency where the gateway supports it, with settlement to your account.
Webhooks: how your system learns what really happened
After paying, the customer's browser is redirected to your thank-you page. That redirect cannot be trusted as proof of payment: the customer may close the tab, lose connection, or pay through a bank app that never returns to the browser. The reliable signal is a webhook, a message the gateway sends from its servers to yours when a payment succeeds, fails, is refunded or is disputed.
A correct webhook handler verifies the signature on each message using the secret from the gateway, so forged requests are rejected. It is idempotent, meaning the same event delivered twice does not ship an order twice. It replies quickly with a success status and does slow work afterwards, because gateways retry messages that are not acknowledged. Every event is logged, and a scheduled job asks the gateway's API about payments still marked pending, in case a webhook never arrived.
Refunds and disputes
Refunds are sent through the gateway's dashboard or API, in full or in part, and go back to the payment method the customer originally used. The money reaches the customer according to their bank's timing, not instantly. We add a refund action to your admin panel with permission controls, record the gateway's refund reference against the order, and update the order status from the refund webhook.
A dispute, or chargeback, is different: the customer asks their bank to reverse the payment. The gateway notifies you and gives a deadline for evidence such as invoices, delivery proof and messages with the customer. We set up alerts for disputes and store the order records that are usually asked for.
Subscriptions and recurring payments
Recurring billing needs more than charging a saved card each month. The integration has to handle plans and price changes, free trials, upgrades and downgrades part-way through a period, failed renewals and retries, cancellation, and reminders before a charge. Gateways such as Stripe and Razorpay provide subscription objects that manage the schedule, and your system follows along through webhooks.
Rules differ by region. In India, recurring card and UPI payments run on mandates that the customer approves with their bank, and card details are stored as tokens rather than card numbers. In Europe, strong customer authentication can require the customer to confirm a payment with their bank. We build the flow for the regions you sell in.
Security first: keeping your PCI DSS scope small
PCI DSS is the card industry's security standard, and it applies to every business that accepts cards. How much of it applies depends on how card data flows. With a hosted checkout or the gateway's embedded fields, card numbers go from the customer's browser straight to the gateway and your server only receives a token, which keeps you on the shortest self-assessment. If your own server receives or stores card numbers, the full set of requirements applies.
We use hosted fields and tokenisation so card details never touch your server. Payment pages are served over HTTPS, API keys and webhook secrets are stored outside the codebase, and live keys are limited to the people and systems that need them.
Testing in the sandbox
- Use the gateway's test mode and test API keys, kept separate from live keys
- Successful payment with each method you will offer: card, UPI, netbanking, wallet
- Declined card, insufficient funds and expired card, using the gateway's published test cards
- Payments that need an extra authentication step such as 3D Secure or an OTP
- Customer closes the window or loses connection after paying
- Webhook delivered twice, delivered late and not delivered at all
- Full refund and partial refund, and the order status after each
- Subscription renewal, failed renewal and cancellation, where subscriptions are used
- Amounts with decimals, taxes and discount codes, checked against the gateway's record
- Emails and receipts sent to the customer for each outcome
Go-live checklist
- Business verification completed with the gateway and the live account activated
- Website shows the pages gateways ask for: contact details, terms, privacy policy, refund and cancellation policy
- Live API keys and webhook secret installed on the server, test keys removed
- Live webhook endpoint registered and its signature check confirmed
- A real low-value payment made and refunded on each payment method
- Order, invoice and receipt emails checked on the live site
- Settlement bank account and settlement reports confirmed in the dashboard
- A reconciliation routine in place to match orders against settlements
- Alerts set for failed webhooks, a rise in failed payments and new disputes
- Dashboard users reviewed, with two-factor authentication switched on
Gateways we integrate
- Stripe
- Razorpay
- PayPal
- PayU
- CCAvenue
- Cashfree
- Paytm
- PhonePe
- Authorize.Net
- Square
- Bank and UPI gateways on request
Frequently asked questions
Which payment gateway is best for my business?
Start with where your business is registered and how your customers pay. Businesses in India selling locally usually choose Razorpay, PayU, Cashfree or CCAvenue because they support UPI, netbanking and domestic cards. Businesses selling internationally often use Stripe where it is available to them, with PayPal as an additional option. Authorize.Net and Square are common in North America. Then compare settlement arrangements and features.
How do I add a payment gateway to my existing website?
First open and verify a merchant account with the gateway. Then the integration is added: an official plugin for platforms such as WooCommerce or Shopify, or the gateway's checkout and API for a custom site. It is tested in sandbox mode, the webhook endpoint is set up, live keys are installed and a real payment is made and refunded. Your site also needs policy and contact pages for approval.
What is the difference between hosted and embedded checkout?
With hosted checkout the customer leaves your site for a payment page run by the gateway, then returns. With embedded checkout the gateway's secure card fields or pop-up appear inside your page, so the customer never leaves. Both keep card numbers off your server. Hosted is quicker to build. Embedded gives a smoother experience and more control over layout.
What is a payment webhook and why do I need one?
A webhook is a server-to-server notification the gateway sends to a URL on your site when something happens to a payment: success, failure, refund or dispute. You need it because the browser redirect after payment is unreliable. Customers close tabs or lose signal. Without webhooks, paid orders can remain marked unpaid. Each webhook's signature must be verified before it is trusted.
Do I need PCI DSS compliance to accept card payments online?
Every business that accepts cards falls under PCI DSS, but the effort varies widely. If you use a gateway's hosted page or embedded secure fields, card data never reaches your server and you complete the simplest self-assessment questionnaire. If your systems handle card numbers directly, the full standard applies. Your gateway or acquiring bank tells you which questionnaire is required.
How do refunds work with a payment gateway?
A refund is started from the gateway dashboard or through its API, for the full amount or part of it, and is returned to the original payment method. The gateway confirms it with a refund reference and a webhook. The customer's bank then credits the amount on its own schedule. Refunds are deducted from your upcoming settlements or account balance.
Can a payment gateway handle subscriptions and recurring billing?
Yes. Stripe, Razorpay, PayPal and several others offer subscription features that store the payment method as a token and charge it on a schedule. Your system receives webhooks for each renewal, failure and cancellation. In India the customer approves a mandate with their bank for recurring charges. Failed renewals need a retry and reminder flow so access is not cut off wrongly.
Do you integrate payment gateways for travel portals?
Yes. Our travel technology team connects payment gateways to flight and hotel booking portals. These need extra care because the fare can change or the booking can fail after payment, so the flow covers payment holds or immediate refunds, partial refunds for cancellations and records for chargebacks. We are based in Kota, Rajasthan, India, and integrate gateways used in India and abroad.
Related
Website development
Website development company for custom business websites: design, copywriting, SEO setup and lead forms, with standard sites live in 3 working days.
Learn moreFlight API integrationFlight API integration
Flight API integration for travel websites and apps: Amadeus, Sabre, Travelport, NDC, low-cost carriers and consolidators such as TBO, TripJack and Mystifly.
Learn moreAndroid app developmentAndroid app development
Android app development in Kotlin and Flutter: design, device testing, AAB releases, Play Console testing tracks and Google Play policy checks.
Learn moreReady to start?
Tell us what you need and get a clear plan and price within 1 business day.