Money Follows, My Brotha. Money Follows

Every booking product eventually has to answer one question, and it is not about calendars. A creator does the work — the call, the class, the shoot, the consult — and then wants to know a single thing: where is my money, and when does it reach me? For a long time the answer to that in this market was a screenshot and a manual UPI transfer, and a small prayer. Not here. Money follows, my brotha. Money follows. Here is exactly how it moves, from the moment a client taps pay to the moment it lands in your bank.

This is the honest version, not a brochure. It includes the deductions, the holds, and the part most companies never write down: what happens when a step in the machine fails, so your money does not quietly get stuck somewhere between a gateway and your account with nobody watching.

The one-line version

A client books a time on your booking link and pays. The money goes to our payments partner, Razorpay, not into some pool we shuffle by hand. We take our small cut, the taxman takes his, and the rest is marked as yours. It is held for a short window while the service happens, then transferred to your own linked account and settled to your bank. Every step is recorded, and every step can be checked. That is the whole story; the rest is detail worth understanding.

1. 01A client picks a slot on your link and pays over UPI, card, or netbanking.
2. 02The payment is captured and verified on our server against Razorpay — never trusted from the browser.
3. 03We snapshot the price and compute your share: your listed price, minus a small platform fee, minus commission if you are on the free plan, minus the statutory bits.
4. 04Your share is sent as a held transfer to your own Razorpay Route linked account — held, not spent, until the service is done plus a short buffer.
5. 05When the booking completes, or the hold matures, the transfer releases and the money is yours.
6. 06Razorpay settles it from your linked account to your bank on its settlement cycle.
7. 07We reconcile the whole chain — payment, share, hold, transfer, settlement — so nothing falls silently between two systems.

Notice what is not in that list: us, moving money by hand. The old way — a screenshot, a manual transfer, a hope — is exactly the thing this replaces. The money rides a rail, and the rail is auditable end to end.

What the client pays, and what you keep

The number a host actually cares about is take-home, so here is where every rupee goes. On a paid booking we add a small flat platform fee — the price of a chai — on top of your price. If you are on the free plan we also take a small commission as you earn; on Host+ and Studio that commission is zero. Then the two bits that are not ours at all: TDS under section 194-O and TCS under GST section 52, which the law requires a marketplace to withhold and deposit against your PAN, and which you claim back when you file. We show every line, because a payout you cannot explain is a payout you do not trust.

That structure is not an accident. We collect through a regulated payment aggregator so that host money never sits in a place it should not — which is the entire point of the RBI's aggregator rules. We are the marketplace; the money rail is run by people licensed to run it.

The hold is a feature, not a delay

When your share is transferred, it does not hit your bank the same second, and that is deliberate. The transfer is created on hold and stays held until the service is over plus a short buffer. If a client cancels or a booking is refunded before then, the held money reverses cleanly instead of being clawed back after the fact. Think of it as an escrow the length of a booking: enough protection that a client pays confidently, and enough that you are not stuck in a refund fight over money you have already spent.

The part nobody blogs about: when a step fails

Here is the honest bit. A money pipeline has many steps, and any step can fail — a confirmation from the bank can go missing, an account can still be finishing verification, a transfer can be created just below the floor at which it can be reversed. If you only build the happy path, those failures do not announce themselves. The money simply stops, somewhere, quietly, and the host is the last to know. We know because we went looking, and we found exactly that.

So we built the boring machine most products skip. A reconciler runs on a schedule and asks the unglamorous questions: is there a booking that was paid but whose payout was never created? A transfer stuck waiting on a confirmation that never arrived? A host who just cleared verification and is now owed money for bookings that happened before? It creates what is missing, finishes what is stuck, and — the part that matters most — it raises an alarm the moment host money cannot be paid, instead of waiting for a host to complain. Money that gets stuck gets found.

A payout system is not the code that runs when everything works. It is the code that runs when something breaks. If nobody is watching the money, the money is not safe.

The bit worth keeping

None of this is glamorous. There is no screenshot of it, no animation on the homepage. But it is the difference between a booking link and a business you can rely on. You do the work, the client pays, and the money finds its way to you — through the fee, the tax, the hold, the transfer, the settlement — checked at every step. If you want to see the front of that machine, explore the hosts already getting paid on it, or read why we rebuilt the whole promise around getting you paid. And if you are the kind who measures things, we wrote about the only number that matters too.

That is the promise, and now it is machinery, not a mood. Make the thing worth paying for. The rest follows. Money follows, my brotha. Money follows.