Payments

Beta

Take payments for every client, straight into their own Stripe.

Run a client’s products, pay pages, subscriptions and refunds from here, on their own Stripe account. The money goes straight to the client, and there is no platform fee.

Every payment lands on the person’s CRM record, so you can show what a lead from the website went on to spend.

Get early access See pricing

Thrum opens soon. Sign up now and you’ll be among the first in.

A client's payments: recurring revenue, subscribers, six months of revenue and where payers first came from.

Products and offers

Set up products, prices and offers without opening Stripe.

One-time, monthly or yearly prices, made in the client’s Stripe from here. Changing a price keeps current subscribers on the old one.

An offer is a percent or an amount off, once, for some months or for good, with an optional code and an end date.

The client's products, with one-time, monthly and yearly prices.

Pay pages

A pay page in the client’s brand, and a checkout link in any message.

Each product gets a pay page on the client’s portal address, handing off to Stripe Checkout.

A workflow can make a checkout link for one person and one price and send it by text or email, so the customer can pay straight from the message.

A pay page for a client's boiler service plan on a phone, in their colour.

Customers

Refunds, cancellations and access, from one drawer.

Refund all or part of a payment, with the exact amount shown before you confirm. Cancelling waits for the end of the period by default, with Resume until then.

Give someone access without paying, and take it back with Undo.

One customer's payments and subscription, with Refund and Cancel.

Every client

Every client’s revenue and failing payments on one screen.

See each client’s Stripe connection, recurring revenue, subscribers and failing payments side by side. Once a client is live, their portal shows them their own revenue, and their monthly report gains a payments section.

If a live Stripe key is disconnected, the records stay in view and billing carries on in Stripe; nothing here updates until it is connected again.

Payments across every client: each client's Stripe connection, recurring revenue, subscribers and failing payments.

Specs

Payment details

Whose Stripe: The client’s own, connected with a restricted key
Platform fee: None
Checkout links from a workflow: Valid 7 days
Missed events: Caught by a sync every 5 minutes
Revenue report: 6 months, and revenue by where the payer first came from

Questions about payments

Does the money pass through you?

No. Everything runs on the client’s own Stripe account, connected with a restricted key, and the money goes straight to them. There is no platform fee.

Can I set it up without taking real money?

Yes. Everything starts in test mode, kept apart from live data and never counted in reports. Going live needs a paid plan.

Can a payment start a workflow?

Yes. A payment succeeding or failing, a subscription starting, set to cancel or ending, or a trial ending can each start one, such as a thank-you text or a chase for a failed card.

Can my client sell a paid newsletter?

Yes, in beta. Paid tiers on the client’s blog check out through the same Stripe account, and paid subscribers show up here and in the newsletter’s paid reports.

What about tax?

Stripe Tax can be switched on for checkout once Stripe says the client’s tax is set up.

What does Beta mean?

Beta means the module is built and tested, and hasn’t yet run against the live service it depends on, such as Stripe or Twilio. The tag comes off once it has.

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.