SuperControl Private beta

Stripe for bookings SuperControl already knows about.

Operators want guests to pay deposits, balances and extras through Stripe, associated with the SuperControl booking reference, using the operator's own Stripe account. The default SuperControl checkout does not always cover that job.

This is private beta. It focuses on existing bookings and transparent reconciliation. A complete Stripe checkout for brand-new bookings depends on supported SuperControl booking and payment APIs. We do not claim PCI certification, official Stripe partnership, or API capabilities we have not implemented.

Enquire about private beta

What it collects today

Deposits
Outstanding balances
Part payments
Additional charges
Booking extras
Refundable deposits

Why someone needs it

Outstanding balances, extras and deposits sitting outside a clean Stripe trail. Finance wants reconciliation against SuperControl booking IDs without copying numbers by hand.

How implementation works

Payments go through the operator's Stripe account. We associate them with the SuperControl booking we can see. We do not invent write APIs SuperControl does not expose.

Stripe / SuperControl reconciliation UI placeholder

Private beta enquiry

We reply within one working day. Mon–Fri, 9am–6pm GMT.

Also in SuperControl

Independent specialist technology around SuperControl. SuperControl stays the operational system.

SuperControl hub All specialist SuperControl products, plus custom work. Analytics See demand your SuperControl admin does not make obvious. WordPress Keep SuperControl operational. Give guests a better website. Last Minute Marketplace A marketplace for SuperControl-connected last-minute availability. WordPress platform Suite, Nought.io and Local when the job is the CMS, not the PMS. Engineering Custom work that is not one of the SuperControl products. Agency partner If you are a studio bringing a SuperControl client.