Stripe + SalesCrew
Two different things share one vendor name here, and neither ships yet. One is how you pay SalesCrew. The other is how your customer pays you.
- Both paths on the roadmap
- Your key stays yours
- Money actions stay human
The short answer
- Stripe for SalesCrew billing means Checkout and the Customer Portal for your own subscription. It is a roadmap item, so treat any checkout copy you see elsewhere as describing an intention.
- Stripe for your customers means a payment link on a quote, charged through your own Stripe key held in your instance's vault. Also a roadmap item, and part of the quotes feature rather than a separate connector.
- The design rule that will not change: anything that spends money stays a human decision under the default agent policy. An agent may draft a quote; it does not take a payment.
Mechanism
Two paths, both unshipped, kept apart because they are genuinely different features.
| What | Mechanism | Direction | Objects | Status |
|---|---|---|---|---|
| SalesCrew subscription billing | Stripe Checkout and Customer Portal | Two-way | Subscription, invoices, plan state | On the roadmap |
| Usage and billing page in the app | Reads plan state and AI usage | Internal | Usage, allowances | On the roadmap |
| Payment link on a quote | Your own Stripe key, held in your instance's vault | Outbound | Quotes, line items, deals | On the roadmap |
| Paid moves the deal stage | Payment event updating the deal | Inbound | Deals, timeline | On the roadmap |
| Typed e-signature on a quote | Part of the quotes feature | Internal | Quotes | On the roadmap |
| An agent taking a payment | Not planned. Spend is human-only by policy | None | None | By design |
Mechanisms read from the SalesCrew integration and roadmap tables, September 2026. Stripe's own site is the authority on its processing fees.
Why your own key matters
When quotes and payment links ship, the charge is planned to run on your Stripe account rather than through SalesCrew. That means the money reaches your bank directly, the customer sees your business on the statement, and there is no platform sitting between you and your revenue.
It also means the key lives in your instance's Supabase Vault, where credentials are never displayed again after entry. Each client instance is its own Supabase project, so one company's payment credentials are not stored beside another's.
The same principle already applies to AI. You can bring your own Anthropic key, which keeps model spend on your account and off the SalesCrew allowance for ninety-nine dollars a month. Payments are planned to work the same way, for the same reason.
Questions
- How do I pay for SalesCrew right now?
- Stripe Checkout is a roadmap item, so ask rather than assume. The published tiers are Core at $299, Local at $499, Outbound at $699 and Agency at $1,200 a month, with a 14-day trial that requires a card.
- Can I send a customer a payment link today?
- No. Quotes with line items, a PDF, a typed signature and a payment link are one roadmap feature and none of it is live.
- Will SalesCrew take a cut of my payments?
- The design is a payment link on your own Stripe key, so the transaction is between you, your customer and Stripe. Stripe's fees are Stripe's.
- Can an agent send an invoice by itself?
- No. Spend and anything outside the CRM is human-only in the default policy table, and every external send defaults to review regardless.
- Where will I see this go live?
- The changelog. A feature is real when it has an entry there, not when a roadmap page mentions it.
Read the roadmap before you plan around payments
Both Stripe paths are intentions today, and the changelog is where they become facts.