> ## Documentation Index
> Fetch the complete documentation index at: https://docs.1club.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Connect 1Club with payment providers, calendars, analytics, and access control systems

Integrations connect 1Club with external services so your bookings, payments, and access control work alongside the tools you already use. Manage everything from **Settings → Integrations** - install, configure, and uninstall each integration from one place.

## Available integrations

<CardGroup cols={2}>
  <Card title="Stripe" href="/settings/integrations/stripe">
    Accept card and digital wallet payments, with a test sandbox and live Stripe Connect onboarding.
  </Card>

  <Card title="myPOS" href="/settings/integrations/mypos">
    Accept card payments through myPOS hosted checkout, with sandbox and live modes.
  </Card>

  <Card title="Google Calendar" href="/settings/integrations/google-calendar">
    Sync bookings to and from Google Calendar, per area or per instructor.
  </Card>

  <Card title="Google Business Profile" href="/settings/integrations/google-business">
    Import verified business locations from Google as gyms in 1Club.
  </Card>

  <Card title="Google Tag Manager" href="/settings/integrations/google-tag-manager">
    Inject Google Tag Manager and GA4 tracking into your public surfaces.
  </Card>

  <Card title="WebLock" href="/settings/integrations/weblock">
    Sync memberships and bookings to physical door access through WebLock (Valnes).
  </Card>
</CardGroup>

## How it works

Every integration on the **Settings → Integrations** page has the same lifecycle:

1. **Activate** - click **Activate** on an integration card. Some integrations open a configuration page immediately, others kick off an OAuth flow (Stripe, Google Calendar, Google Business Profile).
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** - integrations that take credentials (myPOS, WebLock) expose a **Test connection** button so you can validate before going live. Stripe and Google integrations validate during the OAuth round-trip.
4. **Use** - once active, the integration runs in the background. Status, last-sync timestamps, and any errors appear on its page.
5. **Deactivate** - the **Deactivate** action removes the integration. External data already exchanged (events in Google, charges in Stripe, grants in WebLock) is not retroactively deleted.

## Choosing a payment provider

1Club supports Stripe and myPOS as payment providers. You can have both installed at once, but most operators pick one based on country and preferences:

* **Stripe** is the broader option - widest country coverage, digital wallets, Connect onboarding, 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.

Both integrations support a test/sandbox mode so you can try them end-to-end before charging real cards.