Connecting a Payment Gateway
A payment gateway is the service that takes online card (or similar) payments for the studio. Without it, staff can still record cash at the desk, but members cannot pay through Fitnez Studio online.
Stage 4 of the setup checklist is Get paid faster, including connecting a payment gateway so members can pay online.
Why the Business Needs One
Online payments need a provider to collect the card details securely and tell Fitnez Studio whether the transaction succeeded. Cash does not use that provider: you take notes or coins, then record the sale yourself.
| Cash | Online (gateway) |
|---|---|
| Taken at the desk | Taken through the connected provider |
| Staff record the sale after money is in hand | The gateway reports Success, Pending, or Failed |
| No gateway required | Gateway must be connected and enabled |
Where Gateway Appears on Transactions
On Finance → Transactions, staff can filter Payment method → Gateway and Gateway → Stripe or Gateway → Wallet. Cash rows show METHOD Cash and GATEWAY —.
Where to Find Gateway Settings
The topic plan places configuration under Settings → Payment Gateway (or Studio settings). Connecting providers is typically an owner or admin task.
Workflow — Connect Payment Gateway
Step 1 — Open gateway settings
From the Getting Started tab, open the payment gateway step if it is listed. Otherwise look under Studio or Settings for payment gateway.
Step 2 — Configure
Enter only the configuration Fitnez Studio asks for (account or public details). Keep secret credentials in the product, not in email or this documentation.
Step 3 — Save
Save the configuration.
Step 4 — Test, if supported
If Fitnez Studio offers a test or check connection action, use it.
Step 5 — Enable
Turn the gateway on if connect and enable are separate. See Viewing & Updating Gateway Settings.
What Happens Next?
After the gateway is connected and enabled, new online payments can go through it. Existing cash sales are unchanged. Transaction statuses for online attempts should then include successful, pending, and failed when those appear in the product.
Whether members pay from a public website, a member app, or only from the dashboard is not confirmed.