Autopay that doesn't need a button press
Stripe charges the stored card on the billing date. Christina doesn't push autopay. Diane doesn't push autopay. Nobody pushes autopay.
The story
On the studio's current platform, autopay isn't autopay — staff manually clicks a button each month to push charges. That work shifts to Diane after Christina's day-shift ends, and a missed click means a missed charge and a snowballing past-due balance.
Pirouette uses Stripe Subscriptions directly against the studio's own connected Stripe account. The billing date arrives, the charge fires, the family inbox gets a receipt, the past-due flag clears if it was raised. If a payment fails, the family sees a clear in-app reason and a one-tap retry — not a confused email round-trip with Christina.
What this looks like in practice
- Stripe Subscriptions on the studio's own connected Stripe account
- Smoothed monthly billing — 34 classes over 10 months priced as one recurring charge
- Stored-card on file, with 'tap to charge' at the desk for walk-up payments
- Front-desk kiosk mode lets parents enter their own card at peak rush
- Failed-payment retries surface in the parent portal with a plain-language reason
Related
No 1% middleman markup. The studio's connected Stripe account receives the money directly. We are not in the payment path.
One running invoice per family. Line items per student. Credits and discounts visible. No screen that reads backwards.
Want to see this running on your studio's data?
Walk through a demo with us. We'll show this feature in context against the day-to-day workflow your studio actually has.