solves.
Menu
Integrations / Stripe

Billing runs on Stripe, so your inbox never stops.

Solves prices the GBP team bands and applies plan entitlements and limits, with a billing system built on Stripe's signature-verified, idempotent webhook model. Live Stripe checkout is coming; when it ships your card details will stay with Stripe, not with Solves. A billing hiccup never blocks the support email coming into your queue.

GBP team bands, ex VAT  ·  Built on Stripe's webhook model  ·  Email keeps arriving during billing issues

GBP team bandsPlan limits and entitlements per band
Built on Stripe webhooksSignature-verified, idempotent; live checkout coming
Billing never blocks emailTickets keep arriving even if a charge fails
Annual = twelve months for tenPay yearly for twelve months at the price of ten

The short answer

Stripe is the billing engine, Solves runs the desk

Solves prices the GBP team bands and applies plan entitlements and limits, with a billing system built on Stripe's signature-verified, idempotent webhook model. A live customer-facing Stripe checkout is coming; for now the pilot is founder-led and the Starter band is the self-serve way in. When checkout ships, Stripe will take the payment and set up the recurring subscription, and Solves will read back the result through verified webhooks to decide what your plan includes, what its limits are, and what to do if a charge does not go through.

Three things flow from a subscription. First, plan entitlements: the band you chose unlocks a set number of users, brands, mailboxes and monthly tickets. Second, plan limits: those numbers are the ceiling included in the band, and Solves prompts you to move up if you grow past them. Third, failed-payment states: once live checkout ships, if Stripe cannot take a charge your subscription goes past-due, Stripe retries, and Solves nudges an admin to fix the card.

The line that matters most is simple. None of this touches your inbound email. Over a limit, a card that expired, a charge that bounced: in every case, support email keeps landing in your queue, so your customers never feel it.

How it works

What the Solves billing system covers

The parts of billing that are built today, on Stripe's webhook model.

GBP team bands

Starter, Team, Growth and Agency/MSP are priced in GBP ex VAT. You size the band to your team rather than paying per seat for every helper.

Plan entitlements

Your band sets how many users, brands, mailboxes and monthly tickets are included, and Solves applies the right entitlements for the band.

Plan limits, handled gently

Limits are about what the plan includes. Approach one and Solves prompts an upgrade; it never silences your inbox to enforce a cap.

Built on Stripe webhooks

The billing system uses Stripe's signature-verified, idempotent webhook model. Live Stripe checkout, with card data held by Stripe, is coming.

Failed-payment states

Once live checkout ships, a failed charge has Stripe retry on its schedule and the subscription go past-due, and Solves prompts an admin to update the card.

VAT-visible invoices

Prices are ex VAT and invoices show VAT separately, so the numbers match what a UK accounts team expects.

From Starter to a paid band

How you move onto a paid band

Pick a band

Choose the team band that fits your users, brands and ticket volume. Pricing is GBP ex VAT, and annual billing is priced as twelve months for ten.

Get set up, founder-led

The pilot is founder-led, so we set up your paid band with you directly. Live Stripe checkout, where card details go into a secure Stripe-hosted form, is coming.

Entitlements apply, email keeps flowing

Solves applies your plan entitlements and limits and keeps your queue running. Once live checkout ships, a future failed charge will not interrupt it.

Security

Where your card details will live

When live Stripe checkout ships, card data will be handled by Stripe, not stored by Solves. Your card number will be entered into fields hosted by Stripe and sent straight to Stripe, so it does not sit in the Solves database. Stripe is a PCI DSS Level 1 service provider. Solves keeps only the subscription references it needs, such as which band you are on and when it renews. Until then the pilot is founder-led, so there is no self-serve checkout to complete.

How this fits the rest of Solves

It mirrors how Solves treats customer support content. Ticket bodies, subjects and contact details are encrypted at rest with per-organisation keys, access is limited to authorised teammates, and logs carry metadata only, never message bodies, email addresses or secrets.

What we do not claim

Solves is at pilot stage, so the honest framing matters. Solves does not promise guaranteed delivery, zero-knowledge storage or enterprise-grade compliance, and it is not a payments product. Stripe is the payment processor; Solves is the support desk that uses it. The security page covers encryption, access and logging in plain terms.

Over a limit? Your support email still arrives

This is the rule the billing integration is built around. Passing a plan limit, or a charge that fails, prompts you to sort out billing, but it never blocks incoming support email. Tickets keep landing in your queue, so customers never wait on a reply because of an invoice.

FAQ

Stripe billing questions

Is my card data safe with Solves?

When live Stripe checkout ships, your card details will be handled by Stripe, the payment processor, not by Solves. Card numbers are entered into Stripe's own hosted fields and never reach the Solves database, so Solves does not see or store your full card number. Stripe is a PCI DSS Level 1 service provider. Today the pilot is founder-led and the Starter band is the self-serve entry, so there is no self-serve card checkout yet; Solves keeps only the references it needs to manage your subscription.

What happens if a payment fails?

A failed payment does not lock you out and does not stop tickets arriving. The billing system is built on Stripe's signature-verified, idempotent webhook model: once live checkout ships, Stripe retries the charge on its usual schedule and your subscription moves into a past-due state. Solves shows an in-app prompt to an admin to update the card, and inbound support email continues to flow into your queue throughout, because billing problems should never cost your customers a reply.

How are the GBP team bands billed?

Solves uses team bands, not per-agent pricing: Starter at GBP 29, Team at GBP 79, Growth at GBP 149 and Agency/MSP at GBP 299 per month, all ex VAT. You pick a band that fits your team and brands rather than paying a seat fee for every occasional helper. The billing system is built on Stripe's webhook model, with live Stripe checkout coming; for now the pilot is founder-led and annual billing gives twelve months for ten.

What does a plan limit actually cap?

Each band sets entitlements such as the number of users, brands, mailboxes and monthly tickets included. Limits are about what the plan includes, not a switch that silences your inbox. If you approach or pass a limit, Solves prompts you to move up a band, but your existing tickets stay open and new support email still lands in the queue.

Can I see VAT on my invoices?

Yes. All prices are quoted ex VAT and your invoices show VAT separately, so the figures match what your accounts team expects from a UK supplier. Once live Stripe checkout ships you will update billing details and download invoices from the billing area; during the founder-led pilot we handle invoicing with you directly.

Do I need a Stripe account to pay?

No. When live Stripe checkout ships, Stripe will be how Solves takes payment and you will not sign up for Stripe yourself: you enter your card on a secure Stripe-hosted form inside the Solves billing flow, and Stripe handles the rest, so card data goes to Stripe, never to Solves. Today the pilot is founder-led and the Starter band is the self-serve way in, so there is no checkout to complete yet.

See the GBP team bands

Compare the bands, what each one includes, and how annual billing saves you two months.