Settings › Payment Gateways
Payment Gateways connects Servetic to your own Stripe, PayPal and/or Square account. Nothing about how deposits or invoices work depends on which one you pick, and you can connect more than one: a customer paying a public invoice or a deposit at booking is shown whichever of your connected gateways is actually available.
The four tabs
| Tab | What it's for |
|---|---|
| General Settings | Your Default Currency. Set it to match your business currency and your payment account's currency before connecting anything. |
| Stripe | Enable Stripe, choose Test or Live Mode, and connect with your Publishable Key and Secret Key. |
| PayPal | Enable PayPal, choose Sandbox or Live Mode, and connect with a Client ID and Client Secret. |
| Square | Enable Square, choose Sandbox or Production Mode, and connect with an Application ID and Access Token. |
The Stripe tab: enable it, choose Test or Live Mode, then connect your own account.
Why it's your own account, not Servetic's
Servetic never holds customer funds. A payment made through a connected gateway goes straight to your own Stripe, PayPal or Square account, on that provider's normal payout schedule and under their fees. A booking, deposit or invoice is only marked paid in Servetic after the gateway itself confirms the charge went through.
Test mode before you go live
Each gateway has a separate test environment: Test Mode on Stripe, Sandbox Mode on PayPal and Square. Use test or sandbox keys first and make sure a small booking or invoice shows as paid, then switch to live keys from the same provider account and repeat with a real card for a small amount.
What happens if nothing is connected
Nothing breaks: bookings, quotes and invoices all still work. A service's per-visit or refundable deposit just can't be charged online until a gateway is connected, and the public invoice link never shows a Pay Online section — it's left out entirely rather than shown broken, so a customer is never offered a payment option that wouldn't work.