One single path
Every step of a payment is covered: create the client, save a card without charging it, take an online payment, open a hosted payment page, charge a saved card and confirm each payment.
All modules
Live
Paiements
The layer that takes payments: your Stripe account behind every checkout, subscription and invoice.
What gets you paid. One single path between Freelance OS and Stripe, using each workspace's own Stripe account. Everything that takes money runs through it: the shop, your clients' subscriptions and invoice payments.
Create my workspace
Free plan. 60 seconds. No CC required.
What it does for you
- Getting paid is infrastructure. The Payments module has no screen of its own: it is the technical layer the other hubs call when money has to change hands. A product order, an invoice to settle, a subscription to your app, a booking deposit: they all take money through the same path. You connect Stripe once and the rest works.
- Freelance OS isn't tied to a single payment provider. Today payments go through Stripe. More providers can be added without changing your payment pages.
- Each workspace connects its own Stripe account. Your clients' money lands directly in your account. Until you connect Stripe you cannot take payments: it is the only step to switch payments on.
How it works
One Stripe account per workspace
You connect your Stripe account in a few clicks. Your Stripe credentials are never stored by Freelance OS. A new workspace must connect Stripe before taking payments.
- Your Stripe account is recognized automatically on every payment
- The connected flag says whether the workspace wired its own account or falls back to the platform
- Your public payment pages use your workspace's Stripe account
What payments can do
Each payment step follows the same path, whatever the provider.
- Client: found or recreated automatically when needed
- Card capture (SetupIntent): saves a payment method without a charge
- On-session payment (PaymentIntent): the client pays on the page, with 3DS handled
- Hosted payment page: for a one-off payment, with a return to success or cancel
- Charging a saved card: without the client present, protected against double charges
- Payment confirmation: every notification is verified before it is trusted
Where the money comes in
Payments has no screen of its own: the pages that sell use it. An invoice payment opens a page in your brand colors and the client stays on your domain. The shop creates an order, applies shipping and coupons then takes the payment. A Collection subscription bills your client on top. A booking deposit follows the same path. On some flows a platform commission may apply.
Stripe today
To be clear: today only Stripe is available. PayPal, Mollie and Adyen are planned but not wired in yet. If a provider isn't available, the payment fails openly rather than quietly going through another one. And until Stripe is connected to your workspace, payments stay off.
Connected to
counselLe paiement de facture ouvre une page de checkout brandée montée sur cette coucheproductsThe shop creates an order and takes payment through StripebookingLes acomptes de réservation passent par le même gatewaycollectionsLes abonnements end-users à une app sont facturés par-dessus cette couche
Try Paiements in Freelance OS.
Free plan, no card. Test the module in real conditions.
Create my workspace
Free plan. 60 seconds. No CC required.