One setup, every method
UPI, cards, netbanking, and wallets all work from a single connected gateway, removing the need to negotiate and integrate each payment rail on its own.
Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenThe business can accept payment the way most Indian customers actually pay — UPI, cards, netbanking, and wallets — without separately negotiating each rail.
Works with
What it does
Kuber connects the store's checkout to a payment gateway (such as Razorpay or a UPI-first provider) so a single integration surfaces all payment methods at once. Settlement reports and payout status are visible from the store dashboard.
A beauty and cosmetics seller ready to launch her online store discovers that accepting payment isn't a settings toggle — it's an application to a payment gateway that wants her PAN, bank account, and business proof, followed by a KYC review that runs on the gateway's own timeline, not hers. The store can be fully built and still unable to take a single online payment until that separate process clears.
UPI, card, and wallet collection connects the store's checkout to a payment gateway once that onboarding is complete, so every payment method Indian shoppers actually use — UPI, cards, netbanking, wallets — surfaces through one integration rather than the seller negotiating each rail separately by hand. Settlement reports and payout status stay visible from inside the store dashboard, so the seller can see when money from a sale is due to reach their bank account.
Kuber runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
The seller links their own payment gateway account — set up and verified independently with that gateway — to the store, which is what allows checkout to actually process a payment rather than merely display one at all.
Once connected, UPI, cards, netbanking, and wallets all surface as options at checkout through the same gateway integration, instead of the seller having to add and manage each individual payment rail entirely on its own separately.
A shopper's payment details are entered into the gateway's own secure hosted fields, and a webhook confirms success or failure back to the order, so sensitive data never actually passes through the store's own systems.
Settlement and payout reports pulled from the gateway show inside the store dashboard, so the seller can track exactly when money from confirmed sales is genuinely due to reach their own connected bank account eventually.
Why it matters
UPI, cards, netbanking, and wallets all work from a single connected gateway, removing the need to negotiate and integrate each payment rail on its own.
Settlement and payout reports appear inside the same store dashboard, so checking whether a sale has actually settled doesn't require logging into a separate gateway portal.
Card and payment details are handled entirely within the gateway's own secure fields, keeping the store itself out of the riskiest part of payment handling.
The detail
The gateway relationship sits outside what Kuber can control or expedite. Opening a payment gateway account involves KYC checks the gateway runs against the seller's own documents and bank details, and that review — not Kuber's systems — decides how long it takes and whether it clears; a seller can have every other part of their store ready and still be unable to accept payment until that approval lands. Planning a launch date around an assumed instant connection is the most common way this disappoints a seller who didn't budget for the wait.
Once connected, compliance responsibility follows a strict boundary that protects the seller as much as it constrains the build. Card data — full numbers, CVVs — must never be entered into or stored on anything other than the gateway's own hosted checkout fields, because doing otherwise exposes the seller to the same strict card-industry security obligations large payment processors are built to absorb and a small business is not equipped to meet alone. This is why payment fields at checkout belong to the gateway, not the store, even though they appear inline on the store's page.
Webhooks — the notifications a gateway sends confirming payment succeeded — mark an order as paid, and webhook delivery is not perfectly reliable end to end. A dropped or delayed webhook can leave an order showing as unpaid even though the shopper's payment went through on the gateway's side, which without reconciliation looks like a lost sale rather than a delivery hiccup a settlement check should catch and correct promptly.
Industry use cases
9 industries where Kuber applies this directly.
A car service center lists their repair packages with prices, lets customers book a slot for an oil change through the booking widget, and captures a lead form submission from someone asking about a specific part in stock.
See the automotive playbookA wholesale supplier publishes a catalog page with bulk pricing tiers, a buyer fills out the enquiry form asking for a quote, and the supplier issues a GST-compliant invoice once the order is confirmed.
See the b2b sales playbookA home-based cosmetics seller lists their skincare range with variant options for shade, accepts a UPI payment at checkout, and shares the same catalog as a WhatsApp link with a regular customer.
See the beauty and cosmetics playbookA coaching institute publishes pages for each course they offer, and a prospective student books a free demo class slot through the booking widget before enrolling.
See the education playbookA physiotherapy clinic lets patients book a session through the calendar widget, and the clinic issues a GST invoice for the consultation fee once payment is collected via UPI.
See the health and wellness playbookA home decor seller lists handcrafted furniture pieces with multiple images each, a customer places a COD order for a large item, and the owner updates the order status as it moves from packed to delivered.
See the home decor and furnishing playbookA restaurant publishes its menu as a product catalog with prices, a regular customer places a takeaway order and pays via UPI at checkout, and the owner tracks the order through to pickup.
See the restaurants and food playbookA salon sets up individual stylist calendars in the booking widget, a client books a haircut slot with their preferred stylist, and both receive a reminder notification the day before the appointment.
See the spas and salons playbookA local tour operator lists their guided tour packages with pricing, and a traveler submits an enquiry form for a custom itinerary that the operator follows up on directly.
See the travel and tourism playbookMore from Kuber
The business gets a ready-to-edit website or storefront within minutes of describing what they sell, without hiring a designer.
Learn moreThe business owner can change text, images, colors, and layout on their own without writing code or waiting on a developer.
Learn moreThe business's website is reachable at their own branded domain (e.g., theirshop.in) instead of a generic subdomain.
Learn moreThe business's site and store stay online and load quickly for shoppers across India without the owner managing any servers.
Learn moreThe business can list everything they sell with correct prices, options, and stock counts in one place instead of juggling spreadsheets.
Learn moreA shopper can browse products, add them to a cart, and complete a purchase entirely on the business's own site.
Learn moreQuestions
The payment gateway. A customer's payment settles into the seller's own gateway account, and from there into the seller's bank account according to that gateway's settlement schedule — Kuber displays the settlement and payout status reported by the gateway but never itself holds or moves that money at any stage. Any question about when a specific payout is due is ultimately a question for the gateway account holding it.
This depends entirely on the gateway's own KYC review of the seller's documents and bank details, which is a separate process Kuber has no ability to speed up or override in any way. A store can be fully built and ready in every other respect and still be unable to accept online payment until that review clears — start the gateway application well ahead of any planned launch date rather than assuming it happens instantly.
This usually points to a delayed or dropped webhook — the notification the gateway sends confirming payment success — rather than the payment itself having actually failed at any point. A settlement reconciliation check exists to catch and correct this, but periodically comparing the gateway's own settlement report against your order list is a useful habit rather than relying on the dashboard's paid status alone.
Yes, a new gateway can be connected in place of the old one, though switching means going through that new gateway's own onboarding and KYC process independently, since approval with one gateway doesn't transfer automatically to another provider. Any pending settlements from the old gateway continue on that gateway's own schedule and aren't affected by connecting a new one for future orders.
The rest of your stack
No rip-and-replace — accept upi, cards, and wallets works alongside the systems already running your business.
Coming soon