Your website's till. The customer pays on your site, the money lands in your account, and you never handle card details.
You send an invoice and wait. Some pay after four weeks, some never.
Payment happens immediately, before the appointment is even fixed.
- Card details never reach you
The payment field belongs to Stripe, not your site. What you receive is only the confirmation.
- Strong customer authentication is built in
The second confirmation required in Europe, via banking app or code, runs along without anything being built.
- Recurring payments are anticipated
Monthly amounts, pausing, cancelling — part of the tool, not a custom build.
- Refunds run through the same place
A refund is a button, not a bank transfer.
- Customer enters card
- Stripe checks
- Bank confirms
- Money in your account
The card number never touches your site. It goes straight to Stripe — which is why you never have to secure it.
Payment handling. The customer enters card details in a form secured by Stripe — they never touch your server, which spares you the entire card-security burden. The money goes to your account and Stripe reports it back.
- Card details
- never on your server
- Methods
- card, SEPA, Apple and Google Pay
- Subscriptions
- built in
- Cost
- fee per payment
A deposit when booking an appointment
Gift vouchers bought directly online
Monthly fees billed automatically
A share of every payment goes to Stripe. If you issue a few large invoices, a plain bank transfer works out cheaper.
Worth it wherever a deposit prevents no-shows, or where you sell vouchers.