Online payments
What it's for
Buyers pay straight into your company's own payment gateway account — by card, UPI, net banking or mobile money, depending on the gateway — and the payment becomes a receipt on its own. No one has to check a bank statement before the buyer's dues update.
The rules that protect your money
- A payment is marked paid only after the server checks it with the gateway. The app asks the gateway's own system whether the payment is paid, for our reference, for the right amount, in the right currency. The buyer returning to the page, or a message from the gateway, only starts that check; neither is proof on its own. Messages that fail the check are logged as rejected.
- Paid money always becomes a receipt — even if the link had expired or been cancelled, or your online payments module lapsed in the meantime.
- Each payment is recorded once. A second confirmation of the same payment changes nothing.
- If less arrived than was asked, the receipt is for what arrived, marked Short, and staff are alerted. If more arrived (a gateway fee added), the receipt is for the amount asked.
- Gateway keys are stored encrypted, can be replaced but never read back, are never logged and never sent to the browser.
Before you start
- The Online payments module. The platform team switches on what your company may use: pay links, paying dues in the buyer portal, Book online and EOI online.
- Connect your gateway in Integrations → Payments: enter the keys, press Test connection, Make default, and paste the webhook address shown there into the gateway's dashboard. Supported: Razorpay, Easebuzz, PayU, Cashfree, PhonePe (India); Stripe (international); Flutterwave, DPO Pay (Africa); Pesapal (Kenya, Tanzania, Uganda); Selcom, ClickPesa (Tanzania).
- Permissions: view payments, create pay links (per project), and payment settings.
Ways buyers pay
| Way | Started from | After payment |
| Dues in the buyer portal | The buyer presses pay on a demand in their portal. | Receipt on the booking, applied to demands. |
| Hold pay link | Blocked units & EOIs → Pay link on a hold. | Receipt on the hold; the hold is marked paid and kept; booked automatically if the project says so. |
| EOI pay link | Pay link on an EOI. | Receipt on the EOI; the EOI amount grows. |
| Book online / EOI online | The buyer, from your public map or link. | See Book online and EOI online. |
Send a pay link
- On Sales → Blocked units & EOIs, press Pay link on the hold or EOI.
- Check the Amount (the project's hold pay link amount is suggested) and tick Send to the buyer (email / WhatsApp).
- Press Create link. The buyer opens a pay page with the amount, a countdown and the pay button.
Follow payments
Collections & handover → Online payments shows the connected Payment gateway, every Payment link (for what, amount, status Open / Paid / Expired / Cancelled / Failed, badges Short, Late, Test, and the receipt) and the Gateway events received with whether their signature was valid. On a link: Copy pay link, Check with the gateway (records money already paid) and Cancel link.
Settings per project
Online payments → Settings shows which features are switched on and, per project: Hold pay link amount, Buyers may pay part of a demand in the portal, and the Book online and EOI online settings.
What happens automatically
- Every five minutes, payments that were started are checked with the gateway (in case its message never arrived), and expiring links get one last check before they close. Links expire after 7 days by default.
- The buyer gets their receipt by email and WhatsApp. Staff who subscribe get Online payment received, Unit reserved or EOI paid online and Online payment needs attention (short, late, or could not book automatically).
- When a hold becomes a booking, its receipts move onto the booking and pay its demands.
- A
payment.succeeded event goes to your outbound webhooks.
Who can do what (roles and access)
| Role | Reach & Scope | Allowed Actions |
| Owner & Admin | Workspace wide | Connect payment gateways (Razorpay, Cashfree, Stripe, etc.), configure webhook secrets, set platform checkout limits. |
| Finance Head | Financial operations | Manage payment gateways, inspect gateway exchange logs, issue online pay links, and verify settlements. |
| Sales Team | Assigned projects | Generate pay links on active holds and EOIs, send payment links to buyers via WhatsApp/email. |
| Accounts | Collections ledger | Track online payment receipts and match with buyer demand instalments. |
Where to set things up
- Online payments settings & gateways: Open Online payments → Settings (requires payments.settings.manage; Admin or Finance Head). Connect Razorpay, Cashfree, Stripe, or PhonePe credentials, test connections, and configure default booking/EOI amounts.
- Gateway event log: Open Online payments → Gateway log (requires payments.logs.view). Inspect every webhook exchange, checkout start, buyer return, and gateway API verification.
- Bank reconciliation: Open Accounting → Banking & reconciliation. Match lump-sum gateway settlements against individual buyer receipts.
Tips and common questions
- The buyer paid but the link still shows Open. Press Check with the gateway; the check also runs every five minutes.
- "Pay links are switched off for your company." Ask the platform team to switch them on.
- Gateway settlements into your bank are matched in Banking and reconciliation.
- To send booking, demand, receipt and payment events to your own systems, use Integrations → Webhooks.
Related: Receipts, cheques and refunds · Buyer portal · Holds and EOIs