Skip to main content
Integrations connect 1Club with external services so your bookings, payments, access control, and marketing work alongside the tools you already use. You manage every integration from one place - Settings → Integrations - where you install, configure, test, and remove each one. Connecting and configuring integrations is a paid-plan feature, so on the Free plan and during the Grow trial the catalog is visible but locked until you upgrade.

​
Overview

  • Browse the full catalog on the Settings → Integrations page, split into Installed integrations (active connections, with a count) and Available integrations (everything you can still add).
  • Eleven integrations across payments, Google services, access control, point of sale, messaging, and growth.
  • Each card carries a Learn more link (to these docs) plus an action - Install for an available integration, Configure for an active one.
  • Every integration stores its own configuration and status, so you can install several at once (for example Stripe for online payments and WebLock for door access).
  • Social Booking is built in and always active - it needs no install step, no external account, and stays usable even on the Free plan and the trial.

​
Available integrations

Stripe

Accept card and digital wallet payments, with a test sandbox and live Stripe Connect onboarding.

myPOS

Accept card payments through myPOS hosted checkout, with sandbox and live modes.

DatecsPay

Accept card payments through DatecsPay (BORICA) hosted checkout, with a test gateway and a live production environment.

Google Calendar

Sync area bookings to and from Google Calendar for scheduling and resource management.

Google Business Profile

Import verified business locations and details from Google into 1Club.

Google Tag Manager

Load a Google Tag Manager container (and your own GA4 tags) on the member portal and CMS website.

WebLock

Sync bookings and memberships to physical door access and per-usage PINs through WebLock (Valnes).
The following integrations live in the same catalog. They work today, but their dedicated guides are still in progress. The summaries below describe what each one does.

Hype POS

Send orders from 1Club to the Hype POS for fiscalization and kitchen display, and sync the Hype menu (categories and products) back into 1Club.

WhatsApp

Send and receive WhatsApp messages from the 1Club inbox using your own WhatsApp Business number, connected through Meta Embedded Signup.

Social Booking

Turn your Instagram, Facebook, and other social profiles into a booking channel with tagged “Book now” links, and see which platforms drive bookings.

​
How it works

Every catalog integration follows the same lifecycle, though the details differ per provider:
  1. Install - click Install on an available integration card. Some integrations open a configuration page immediately (myPOS, Google Tag Manager, Google Business Profile, WhatsApp), some create the connection and then open their page for setup (WebLock, Hype, Google Calendar), and Stripe kicks off account creation.
  2. Configure - on the integration’s own page, fill in credentials, mappings, or sync rules. Each integration has its own settings - see the per-integration pages above.
  3. Test or validate - WebLock exposes a Test connection action, myPOS has Validate configuration (a local check of your stored credentials), and Stripe and Google integrations validate during the OAuth or onboarding round-trip.
  4. Use - once active, the integration runs in the background. It appears under Installed integrations with its status, and you manage it from its Configure action.
  5. Deactivate - the Deactivate / Remove action removes the integration. Data already exchanged externally (events in Google, charges in Stripe, PIN grants in WebLock) is not retroactively deleted.
Installing, configuring, and testing integrations requires the settings.manage.organization permission (admins and users with full settings management). Viewing the catalog needs only settings.read.organization. Existing integrations stay visible and removable even when the paid-plan lock is active, so you never lose access to a connection you already set up.

​
Choosing a payment provider

1Club supports Stripe, myPOS, and DatecsPay as payment providers. You can run Stripe alongside one of the hosted-checkout providers, but most operators pick one based on country and preferences:
  • Stripe is the broader option - widest country coverage, digital wallets, Stripe Connect onboarding, automatic payouts, and a large dashboard ecosystem.
  • myPOS is a fit if you already have a myPOS merchant account or operate in a region where myPOS is the established provider. Customers pay on myPOS’s hosted checkout page, so card data never touches 1Club.
  • DatecsPay is a BORICA-backed hosted checkout for merchants who already have a BORICA e-commerce terminal, typically issued by a Bulgarian bank. Like myPOS, customers pay on the provider’s secure page. Unlike myPOS it has no shared sandbox - both Test and Live need your own BORICA credentials - and it does not support shareable payment links.
Every provider supports a test/sandbox mode so you can run the full checkout flow before charging real cards. Note that myPOS and DatecsPay both use hosted checkout for the same “pay by card” surface, so only one of them can be active at a time - you can, however, run Stripe alongside either.

​
Worked examples

Padel club taking online court payments (Stripe). A racket-sports club installs Stripe, runs a few bookings in test mode using Stripe test cards to confirm the portal checkout works, then upgrades to a paid plan and toggles Live mode to onboard its own Stripe Connect account. Court bookings and coach sessions now collect real payments at checkout. Boxing gym in a myPOS region. A martial-arts gym already banks with myPOS. It installs myPOS, pastes its Configuration Pack from the myPOS Checkout Store, validates the configuration, and starts collecting membership dues through hosted checkout - no second payment processor needed. Climbing centre with door access. A climbing gym installs WebLock so that an active membership or a confirmed booking opens the door, then maps its WebLock groups and readers to 1Club areas. It keeps Stripe installed in parallel for online payments. Yoga studio marketing its schedule. A yoga/Pilates studio uses the always-on Social Booking tool to generate a tagged “Book now” link for its Instagram bio, then checks Analytics → Bookings by source to see how many reformer bookings came from Instagram versus its website.

​
Tips & best practices

  • Try every payment provider in test/sandbox mode first. A test payment through the real checkout flow is the only reliable proof that live credentials will work.
  • Keep only the integrations you actually use active. Fewer active integrations means fewer places to reconcile and fewer moving parts when something looks off.
  • If you run more than one club, remember that integration configuration is per organization - installing Stripe once covers all clubs in that organization.
  • Upgrade to a paid plan before you plan to go live with payments. Live Stripe and live myPOS both require a paid subscription, not the Free plan or the Grow trial.

​
Troubleshooting

  • The whole catalog is greyed out / “not available” - your organization is on the Free plan or still in the Grow trial. Connecting and configuring integrations is a paid feature. Upgrade to unlock installs and configuration. Social Booking stays available regardless.
  • I can see integrations but cannot install or configure them - you are missing the settings.manage.organization permission. Ask an admin to grant it, or have an admin perform the setup.
  • An integration I removed still shows external data - deactivating stops 1Club from creating new activity, but it does not delete data already sent to the provider. Manage that from the provider’s own dashboard (for example refunds in Stripe or myPOS).
  • Google Tag Manager shows as “Available” even though I added a container ID - the container ID lives on your organization settings and syncs to the integrations list on load. Reopen Settings → Integrations to refresh the card, or re-save the container ID.