After the payment
Zoho Books, Klaviyo and WhatsApp
Connect the business's own Zoho Books, Klaviyo and WhatsApp Business accounts, and work in them from Harbour.
Connectors link Harbour to accounts a business already holds with another company. The business switches the app on in Apps, then connects its own account (sign in with the partner, a Klaviyo private key, or a WhatsApp Cloud API token). Harbour only reads and writes within the permissions the business grants, keeps the tokens encrypted, and never shows them again. Disconnecting stops everything at once; what was already sent stays in the partner account.
What is sent, and when
Nothing is sent while a page loads: every Harbour event goes to a queue, is sent once (Harbour remembers what it created at the partner), and is retried with growing waits when the partner is busy or down. If the partner refuses the connection, the app is marked "needs reconnecting" and the owner reconnects from its page. Each app's Activity tab lists what was sent, skipped or failed.
Zoho Books
Live payments become customer payments in the business's Zoho Books, with the customer as a contact, and refunds
are recorded against them. Test payments are never sent. The region of the Zoho account (zoho.com, zoho.eu, zoho.in
and others) is read from Zoho's own sign-in reply, and only Zoho addresses are trusted. From Harbour the business sees
its unpaid Zoho invoices and can send a Harbour pay link for the balance; when the customer pays it, the payment is
applied to that Zoho invoice. GET /v1/apps/zoho-books/invoices lists them.
Klaviyo
Payment, order, invoice, refund and ticket events go to Klaviyo as metrics such as Harbour Payment
Succeeded, with the amount, so flows and campaigns can use real paid revenue. By default only customers who
agreed to marketing at a Harbour checkout or event form are sent. From Harbour, or your own system through the API, the
business creates, sends and cancels email campaigns and fills Klaviyo lists from its Harbour customers (paid in the last
30 days, left a checkout, invoice overdue), consented customers only.
curl -s -X POST https://api.harbour.africa/v1/apps/klaviyo/campaigns \
curl -s -X POST https://api.harbour.africa/v1/apps/klaviyo/campaigns/01J…/send \
WhatsApp Business
The business sends invoices, payment requests, receipts and tickets from its own WhatsApp Business number, through Meta's WhatsApp Cloud API, each with its Harbour pay link or receipt. It connects with Meta's sign-up (choose the WhatsApp Business account and number), or pastes a permanent system user token with the phone number ID and the WhatsApp Business account ID.
WhatsApp only lets a business start a conversation with a template Meta has approved. From
Work in WhatsApp, Harbour adds five utility templates to the business's account
(harbour_invoice, harbour_invoice_reminder, harbour_payment_request,
harbour_receipt, harbour_tickets) and shows Meta's decision; each message is sent once its
template is approved.
- Automatic messages are off until the owner switches them on and confirms the customers agreed to hear from the business on WhatsApp: each invoice when issued, a reminder when it becomes overdue, a receipt when an invoice or store order is paid, tickets when a ticket order is paid.
- Any invoice or payment link can also be sent from its page, or from your own system through the API.
- Only live money is messaged; test invoices, orders and payments never are.
- A customer who replies STOP is never messaged again by that business, until they reply START.
- Delivery and read receipts appear in the message log. Meta charges conversations to the business's own Meta account; Harbour adds nothing.
curl -s -X POST https://api.harbour.africa/v1/apps/whatsapp/messages \
type is invoice (an issued, unpaid invoice; the reminder template is used once it is
overdue) or payment_link (an open link). to is optional and overrides the customer's number.
A message that cannot be sent (no number, the customer replied STOP, the template not approved yet) is a
422 with the reason.