1.1Certifying
Refunds always approved
Terminal money actions never run on their own.
Product / Lanes / Collections and payments
Collections and paymentsCertifying
Payment link to receipt, every step checked.
One lane across three systems: a payment link, the payment confirmed by fetching it, the invoice marked in your books, and a receipt on WhatsApp.
Fig.1 · sample
WhatsAppT1
Certifying
- › Templates outside the 24 h window
- › Opt-in before first message
- › Signed webhooks only
GmailT1
Certifying
- › Recipient domain allowlist
- › Replies stay in the thread
- › Narrowest OAuth scopes
Google CalendarT1
Certifying
- › Free/busy before create
- › Idempotent event ids
- › Hours from your rules
Google SheetsT1
Certifying
- › Sheet and range allowlist
- › Header row protected
- › Read back, compare hash
RazorpayT1
Certifying
- › Amounts in paise
- › Refunds always approved
- › Fetch to confirm, never trust a webhook
Zoho CRMT1
Certifying
- › Upsert on email or phone
- › Stage order enforced
- › Data centre stored per connection
Zoho BooksT1
Certifying
- › Totals checked before create
- › GSTIN format checked
- › Void needs approval
How it works.
- 01 /
Link
A payment link tied to the invoice, so it cannot be paid twice.
- 02 /
Confirm
The payment is fetched to confirm it; a webhook alone is never trusted.
- 03 /
Record and receipt
The invoice is marked paid and a receipt template is sent.
What you get. Each point labelled with its real status.
1.2Certifying
Amounts checked
Link amounts must match the invoice balance.
1.3Certifying
Unknown, then reconciled
If a system is down, the step is unknown and reconciled later, never done.
1.4Certifying
Razorpay, Zoho Books, WhatsApp
Business Tier 1 connectors.