Integrations

Platform & Operations

What it does

Integrations connect Memvera to the other systems your gym already runs, so data flows automatically instead of being copied by hand. Sales and revenue feed your finance system, the turnstiles check live membership before opening, class terminals confirm attendance, your call centre can look up a member by phone, and your BI warehouse receives a single, trusted stream of operational data. The goal is one source of truth — no more shadow spreadsheets.

Key concepts

• Oracle Fusion ERP (via OIC) — Memvera sends summarised daily sales, invoices, and deferred-revenue reports to Oracle so month-end closing and VAT reporting are automatic.
• Payment gateways — HyperPay, Mada, Apple Pay and others plug in through a pluggable layer, so switching provider or adding a new BNPL is a configuration, not a rebuild.
• Access control & terminals — Pocket Key opens turnstiles by validating membership in real time (with female face-hashing and offline edge cache); Gantner terminals sync class schedules and capture wristband check-ins.
• Bab call centre — looks up a member's details by phone number for support and sales follow-ups.
• FitnessKPI (BI) — the data warehouse that streams all operational data for executive and operations dashboards.
• InovFitness — provides the PAR-Q health questionnaire and the WhatsApp/SMS communication gateway.

Main tasks

Connect a system to Memvera

1. Identify the system and the data it needs (e.g. finance totals, member lookups, class schedules).
2. Choose the channel — Memvera exposes open APIs and outbound webhooks for most flows.
3. Configure credentials and endpoints, then run a test exchange to confirm data matches on both sides.
4. Switch the integration live and monitor the first reconciliation.

Swap or add a payment provider

1. Add the new provider's keys in the gateway configuration.
2. Map its payment and refund events to Memvera's pluggable layer.
3. Run test transactions (charge, refund, recurring) before enabling it for live checkout.

Plan the integration cutover

1. List every existing integration (Oracle OIC, Pocket Key, Gantner, Bab, FitnessKPI, InovFitness, Orbit4) and decide which to reuse versus rebuild.
2. Define the parallel-operation window so the old and new systems run side by side during handover.
3. Confirm fallback paths and reconcile data across systems before the old links are retired — no integration may be left in a "scheduled-to-break" state.

Tips

INFO

Memvera is API-first: every back-office function is reachable through documented APIs and webhooks, which is what makes adding the Bab call-centre lookup, the FitnessKPI stream, or a new gateway a configuration exercise rather than custom development.

TIP

The access-control integration keeps an offline edge cache of valid memberships, so turnstiles keep opening even if the cloud connection drops — critical for 24/7 clubs and multi-club members.

Related modules

Performance & Security · Data Migration · Finance & Payments · Client Portal