Payments

No gateway in the middle

TiffinCloud doesn't process your customers' payments. There's no gateway sitting between you and their money, no cut taken on what they pay, and no delay waiting for a payout. Customers pay you directly, and you confirm it yourself. That's the whole model, and it's the reason zero commission is a real number here, not a promotional asterisk.

What a customer sees at checkout

When a customer subscribes or renews, what they're shown depends entirely on your Payment Setup in the dashboard. Turn on Cash on Delivery, UPI, or both, and the customer picks between whichever you've enabled, right on the portal.

If UPI is on, the customer gets a QR code generated from your own UPI ID, plus a "Pay with app" button that opens their UPI app directly. They pay you the way they'd pay a shopkeeper: scan, confirm, done. There's no redirect to a payment processor, no card form, nothing that looks or feels like a third party is involved, because there isn't one.

After paying, the customer uploads a screenshot of the transaction (a UTR reference number is optional but helps you match it faster) straight into their TiffinCloud portal. That payment shows up in your Payments list tagged as awaiting approval. You check it against your own bank or UPI app, and mark it approved. Once you do, their subscription goes live.

Cash on delivery works the same way, minus the screenshot: the customer tells you they'll pay on delivery, and you record it as collected once your driver or the delivery itself confirms it.

Why this is safer than it sounds

Every unapproved payment sits in a visible queue until you personally confirm it against real money you can see moving into your account. Nobody gets served on a screenshot alone. If something looks wrong, you just don't approve it. This is slower than an automated gateway confirming a transaction in real time, and that's the trade we've made on purpose: your money goes straight to your bank account, under your name, with nothing sitting in an intermediary's ledger waiting to be settled to you later.

Beyond the default: enterprise and custom setups

The COD/UPI flow above is what ships out of the box, built for the tiffin and mess operators who make up most of our customers today. It is not the ceiling.

For larger operators, franchises, or businesses running in a country or regulatory environment where a direct UPI QR code isn't the right fit, we build further:

• A real payment gateway integration, wired into your existing dashboard and portal, for automated card, wallet, or bank-transfer collection instead of manual approval.
• A fully white-labeled customer portal, on your own domain, with your own branding, so a customer never sees the name TiffinCloud at all.
• Payment flows for markets outside India. UPI is an India-specific rail, and it's not the only one we can support. If your customers pay through a different local system, we can build against it.

None of this is a fixed menu. If your business runs on something we haven't listed here, a different payment method, a different currency, a different compliance requirement, talk to us. TiffinCloud was built to run recurring local delivery businesses, and payments are one part of a system we can extend to match how your specific market actually works, not the other way around.