Settings and payments

FitSpace checkout vs own payments, webhooks, secret rotation, and per-offer external checkout.

The Settings tab configures how buyers pay for your Trainer Space offers. Author subscription billing lives under Billing & limits.

Open Settings.

FitSpace checkout (default)

By default every offer uses FitSpace-hosted checkout:

Stripe on the primary domain (USD)
YooKassa on the RU host (RUB)

FitSpace creates the order, activates access, and assigns a seat after confirmed payment. No webhook setup required on your side.

Use this unless you already collect payment on your own stack and need FitSpace only for delivery.

Own payments (planned; check availability)

Own payments let buyers pay on your external checkout page while FitSpace activates program access via webhook.

The public production USD/RUB catalog checked on 2026-09-30 marks Own Payments coming later. It is not a released benefit merely because a Starter-and-above card lists it. The workflow below documents implementation for explicitly enabled environments. Use available FitSpace checkout for a production launch and check Billing for current availability.

Setup flow

Open Settings → own payments section
Enter your external checkout URL (where buyers complete payment)
Connect — FitSpace generates a webhook secret (shown once; store securely)
On your server, after successful payment, call the FitSpace webhook with the secret so access activates
On each offer Products → Sale, set payment collection to External and the same checkout URL

Buyers leave FitSpace for payment and return per your redirect flow. Legal acceptance at student checkout follows the Trainer Space purchase terms bundle.

Secret rotation

If the secret is exposed, use Rotate secret in Settings:

Rotate in FitSpace
Update your server immediately with the new secret
Old secret stops working — in-flight payments may need retry

Never commit secrets to git or share them in support tickets.

Event log

Settings shows recent webhook events (success, rejection, duplicates). Use it when a client paid on your site but has no FitSpace access — see Troubleshooting.

Per-offer external checkout

Global Settings establishes the integration. Each offer still chooses:

Payment collection	Behavior
FitSpace	Checkout on landing (default)
External	Redirect to your URL; webhook required

External without a working webhook leaves buyers paid but without access.

FitSpace vs own payments

Topic	FitSpace checkout	Own payments
Setup	None	URL + webhook secret
Processor	Stripe / YooKassa	Your stack
FitSpace platform commission on direct sales	0%	0%
Access activation	Automatic on confirm	Your webhook

Processor fees apply on whichever stack charges the card.