Payment Configuration
Stripe setup, cards and ACH.
All payment processing goes through Stripe — cards and ACH both.
Connecting Stripe
A real Stripe account (test mode while setting up, a real business account before processing live customer payments) needs its API keys configured and its webhook registered so the platform receives real-time events (payment succeeded, subscription renewed, payment failed).
Moving from a test-mode or personal Stripe account to a real business account is a full migration — new API keys, a re-registered webhook, a new signing secret, and no continuity of historical test charges. Plan it as a real pre-launch step, not a one-line environment variable change.
Cards and ACH
Both payment methods are supported on the same checkout flows. ACH settlement takes a few real business days — an invoice paid by ACH can briefly show as "Invoiced" rather than "Paid" during that window, which is accurate, not a display bug.
Refund threshold
See Approval Rules — this is configured alongside payments since it directly governs how refunds are processed.
Where keys are used
The same Stripe keys back every payment surface — public checkout, the portal, the native customer app, and staff-initiated charges from admin. There's no separate payment configuration per surface.