Skip to content

Integrations · Going out

A link on the invoice. A webhook that stops the chase.

Connect a Stripe account and every invoice email carries hosted checkout. The successful charge marks the invoice paid the moment it happens, which is the off switch for Watchtower. The payout that lands days later, net of fees, is matched in bank rec.

Stripe mark

Stripe ← Sonic

How it flows

A pay-now link on the invoice. Payouts arrive net of fees — match them in bank rec, not one-to-one.

  1. 01

    Checkout on the invoice

    The public invoice number and amount open a hosted Stripe checkout — card or bank, depending on the account.

  2. 02

    Webhook marks paid

    charge.succeeded flips the invoice to paid and stops the collections cadence. No polling.

  3. 03

    Payouts in bank rec

    Stripe pays out in batches net of fees. Bank rec matches the deposit to the invoices it covers, with the fee as the difference.

What it does

  • Hosted checkout with the invoice number and amount pre-filled.
  • Paid status from the webhook; a failed or refunded charge reopens the invoice.

What it does not

  • Act as the billing system — plans, schedules, and invoices live in Sonic.
  • Reconcile the bank for you; a payout is still a deposit to match.

Before the first sync

  1. 01Stripe account keys and a webhook endpoint pointed at Sonic. Test it in sandbox first — a missing webhook is the classic 'money arrived, invoice still open'.
  2. 02Decide whether the customer or you carry the fee; it changes the bank rec difference.

Where it lands

Read more

Next

See it on your contracts

A walkthrough on the agreements and files you actually bill from — not a slide deck.