Integrations
Platform & Operations
What it does
Integrations connect Memvera to the services your gym relies on, so data flows automatically instead of being copied by hand. Payments clear through your gateway, receipts and reminders go out by email, the member and trainer apps get real-time push, tax-compliant invoices are generated on the spot, and your dashboards read a single, trusted stream of operational data. And because everything runs on an open API with outbound webhooks, connecting a new tool is a configuration exercise — not custom development.
Key concepts
- Payment gateways (pluggable) — cards, Apple Pay and 3-D Secure run through Tap, and Tabby and Tamara add Buy-Now-Pay-Later. The layer is pluggable, so switching provider or adding a new method is configuration, not a rebuild — and card tokenisation, saved cards, and a member wallet come built in.
- Email delivery (Resend) — every transactional email — login codes, receipts, renewal reminders — and every marketing campaign is sent through Resend under your gym's own sender identity.
- Push notifications (Firebase) — real-time push to the member and trainer apps (bookings, dues, chat, community, challenges), configured per gym with the gym's own Firebase keys.
- BI dashboards (Metabase) — the Insights screen embeds signed, live dashboards — revenue, membership, sales, scheduling and more — in matching Arabic and English sets.
- In-app chat — a dedicated real-time service carries member ↔ trainer messaging, with a push notification on every new message.
- E-invoicing (ZATCA) — receipts carry a ZATCA simplified-tax-invoice QR code, so Saudi VAT invoicing is generated automatically at the point of sale.
- Access gate — memberships are validated in real time by the Memvera gate using a rotating QR check-in; physical turnstiles connect through the same gate API.
- Open API & webhooks — every back-office function is reachable through a documented REST API, and Memvera emits outbound webhooks so external systems react to events — a sale, a check-in, a new member — the moment they happen.
Main tasks
Connect a system to Memvera
- Identify the system and the data it needs (finance totals, member lookups, class schedules).
- Choose the channel — the documented REST API for reads and writes, or outbound webhooks to be notified of events.
- Configure credentials and endpoints, then run a test exchange to confirm the data matches on both sides.
- Switch the integration live and monitor the first reconciliation.
Swap or add a payment provider
- Add the new provider's keys in the gateway configuration.
- Map its charge, refund, and webhook events onto Memvera's pluggable layer.
- Run test transactions (charge, refund, recurring) before enabling it for live checkout.
Turn on push and email
- Add the gym's Firebase credentials to enable push to the member and trainer apps.
- Email works out of the box through Resend — just set the sender name and brand.
- Send a test notification and a test email to confirm delivery before going live.
React to events with webhooks
- Register an endpoint URL under Webhooks and choose the events to subscribe to (sale, payment, check-in, membership change).
- Verify the signed payload on your side so you can trust each delivery.
- Use the delivery log to inspect, retry, or debug any missed event.
Tips
INFO
Memvera is API-first: every back-office function is reachable through a documented REST API and outbound webhooks, so connecting a new tool — a data warehouse, a CRM, an accounting system — is a configuration exercise rather than custom development.
TIP
Payment providers are pluggable — adding a new gateway or a Buy-Now-Pay-Later option is a matter of adding keys and mapping events, with no change to how checkout or settlement works.
INFO
Push is per-gym: each gym adds its own Firebase project, so notifications are sent under that gym's app identity and never mixed between brands.
Related modules
Finance & Payments · Payment Gateways & Methods · Notifications · Reporting & Analytics · Performance & Security