Billing that flows through your merchant account.
Recurring invoicing driven by Vendasta data, ACH and card payments through the processor of your choice, and auto-drafting that just works on the due date.
Two processor models. One UI.
Start on Stripe Connect for instant onboarding. Add a direct merchant when your volume justifies it. Migrate clients between them without changing how you bill.
Stripe Connect
Live in hours, no underwriting needed.
- Setup time
- Hours
- Card rate
- ~2.9% + $0.30
- ACH rate
- 0.8% (capped at $5)
- Best for
- New / growing agencies
Direct merchant (Authorize.net)
Lower rates once you're underwritten by a processor.
- Setup time
- 4–8 weeks
- Card rate
- ~1.7–2.2% + $0.15
- ACH rate
- ~$0.25 flat
- Best for
- $50K+/mo processing
The money-in lifecycle
From subscription generation to settled funds in your bank.
Subscription comes due
Inngest scheduler picks up subscriptions where next_invoice_at <= now and generates an invoice with line items pulled from Vendasta.
Invoice issued + emailed
Branded with your logo and colors. Sent to the client's billing contact via Resend. Hosted invoice URL works without login.
Auto-draft on due date
Saved card or ACH is charged automatically. Funds settle to your merchant account on the processor's normal schedule.
Dunning if it fails
Retry on your configured cadence with reminder emails. Late fees applied automatically per your tenant policy.
Card data never touches HubWho — handled by your processor.
Every charge is reconciled by signed webhook, not polled.
Every payment, refund, and credit is recorded with actor + timestamp.
Billing FAQ
Can I bring my own merchant account?+
Yes. HubWho supports both Stripe Connect (instant onboarding, ~2.9% + $0.30 cards) and direct merchant accounts via Authorize.net or NMI (~1.7–2.2% cards once underwritten). Connect both and choose per client or per invoice.
How does ACH work?+
End-clients link their bank account via Plaid during checkout or upfront in the customer portal. HubWho stores the ACH token at your processor and uses it for auto-drafting on due date. Failed pulls trigger your dunning sequence.
What happens when a payment fails?+
Your dunning policy kicks in. We ship three default policies — soft (3 retries over 14 days), standard (5 retries over 21 days), and aggressive (8 retries over 28 days) — and you can customize the cadence, retry strategy, and reminder email copy per tenant.
Can I add late fees?+
Yes — flat or percent, applied automatically once an invoice goes a configurable number of days past due. Recorded as a separate line item so the audit trail is clean.
Do you support refunds?+
Full and partial refunds, one-click through the invoice view. For Stripe, the refund is initiated through their API; for direct merchant, HubWho records the manual refund and updates the invoice.