Plan: All plans. Safety features are never gated.
Chasing someone who has already paid is the failure the product is built to avoid. Payment detection is therefore treated as a never-gated safety rail.
How payments get into PayBlah
- Accounting sync (all plans) — when Xero, QuickBooks, or your connected books show the invoice paid or reduced, PayBlah is designed to pick that up on sync.
- Payment-link / provider webhook (Growth+) — faster signal when the customer pays through a connected provider.
- Mark paid / Record payment (all plans) — you enter amount and date yourself for bank transfer or cash.
What should happen next
- Automated sequence sends for that invoice stop.
- Last-second checks before send are designed to drop anything already paid, credited, or voided so a queued message does not go out after the money landed.
- Your concurrent balance meter falls as invoices leave the chase set.
Delays
The portal itself tells customers a payment can take a day or two to reach the records. If someone says they paid and the invoice is still open, check the bank and the books first, then mark paid or wait for sync — do not keep escalating while you investigate.
Related stops
Disputes, active promises, and kill-switch / halt controls also stop or pause chasing. Payment is the cleanest stop: the debt is gone or reduced because money moved.