Skip to content

IZI CRM External Integrations: Overview of Available Connections

Published: · IZI Team

IZI CRM integrates with external services: payment systems, POS hardware, marketing tools. Each integration is configured once — then it works automatically.

Where to open: left panel → SettingsIntegrations

A payment gateway allows accepting bank card payments — at the POS via a terminal or online through the IZI mobile app.

CloudPayments — primary supported gateway for Russia and CIS. Detailed connection instructions: Configuring CloudPayments.

When connecting a gateway you will need:

  • A contract with the payment provider (arranged on the provider’s side).
  • API keys (Public ID and API Secret) from the provider’s account.
  • Binding to the club POS (if using a fiscal printer).

After connection, a card payment button appears on the cashier’s screen. Transactions are automatically recorded in IZI analytics.

If your country’s legislation requires issuing fiscal receipts — connect a fiscal printer.

IZI supports integration with POS hardware via appropriate protocols. Specific models and protocols depend on the region. When configuring a fiscal printer in IZI you specify:

  • Device type and model.
  • Connection port (COM, USB or network).
  • Organisation details: name, tax ID/TRN, address.
  • Tax regime.

After setup, IZI automatically sends a receipt to the printer on every POS payment.

IZI has a built-in bonus engine and loyalty programme — no separate external integration is needed. All mechanics (accumulation, redemption, top-up bonus, multipass) work within the system.

If you already have an external loyalty programme — check with the IZI team about a custom API integration.

IZI supports basic channels for client communication:

SMS providers — for sending SMS notifications to clients (see Notification Templates). Connection requires a contract with an SMS provider and an API key. Supported providers — check regional documentation.

Email — built-in email notification sending via templates. No additional integration needed for basic transactional emails.

For mass marketing campaigns (promotions, tournaments, seasonal offers) — export your client base from IZI and use external email/SMS platforms.

IZI generates internal analytics in the Analytics section — without external BI tools. For integration with external systems (Google Sheets, Power BI, accounting software, etc.) — use IZI data export or the IZI API (API availability — check with support).

General process for most integrations:

  1. Open Settings → Integrations.
  2. Find the required integration in the list.
  3. Click Configure or Connect.
  4. Enter data from the external service (API keys, identifiers).
  5. Click Test Connection — IZI makes a test request.
  6. After a successful test, save the settings.

If the connection test fails — make sure the API keys are copied without extra spaces and have the required access rights on the provider’s side.

In the Integrations section, each connection shows its current status: active, error, not configured. On error — a description of the cause. Check statuses when opening a new shift, especially if there was network instability the previous day.

Frequently asked questions

Where in IZI CRM are the integration settings?

Left panel → Settings → Integrations tab. All available connections are listed there with a setup button for each.

Is a payment gateway required for IZI to work?

No. IZI works with cash payments without a gateway. A payment gateway is needed if you want to accept bank cards or online payments.

Can you connect multiple payment gateways simultaneously?

This depends on the version and region. In most configurations, one primary gateway is connected. Check with IZI support for your country.

Is a fiscal printer required?

Depends on your country's legislation. Where law requires issuing fiscal receipts — yes, mandatory. In jurisdictions without mandatory fiscalisation — optional.

How do you know if your POS model is supported in IZI?

Check the current list of supported devices with the IZI support team or in the regional documentation. The list is updated as new models are added.

Are integrations configured separately for each network club?

Some integrations (e.g. payment gateway) are configured at the organisation level and apply to all clubs. Others — at the club level. Clarified in the setup interface for each specific integration.

What happens if an integration breaks during club operations?

IZI continues to operate: accepts cash, starts sessions, maintains records. An unavailable integration (e.g. payment terminal goes down) is flagged as an error in the POS interface but does not block the whole system.