Payment & Cash Register Providers in IZI

Payment & Cash Register Providers in IZI

Providers in IZI are organization-level integrations with payment systems and fiscal receipt services. Configure them once and every club in your network can share the same connections. The section lives at Organization → Management → Providers and covers two distinct types: payment providers (accepting money from clients) and cash register providers (generating fiscal receipts for regulatory compliance). Both types appear in a single table with columns for Name, Type, Usage, Status, and Last Updated. A provider is either Active (credentials entered and verified) or Not configured (created but keys not yet filled in or invalid).

The separation between the two types matters because they serve different purposes and involve different external services. A payment provider connects IZI to an acquiring bank or payment gateway — the service that actually moves money from the client’s card or wallet into your account (see client payments). A cash register provider connects IZI to a fiscal receipt service — the system that generates legally compliant receipts and reports transactions to the relevant tax authority. Many clubs need both: the payment provider to charge clients, and the cash register provider to satisfy local tax law. Clubs that accept only cash and operate in markets without mandatory fiscal receipts may only need one or neither.

To add a provider, click the button in the top-right corner of the page, choose the integration type, and follow the form for that specific provider. Once created at the organization level, each provider is assigned to individual club cash registers inside their own settings. Providers cannot be created at the club level — the organization scope is intentional and ensures credential management stays centralized.

---

Payment Providers

A payment provider is your acquirer: the service through which a client pays by card, Apple Pay, or QR code. IZI supports four providers, each with its own supported payment methods.

Supported providers and payment methods

Provider	Card	Apple Pay	SBP (QR)	Typical region
CloudPayments	Yes	No	Yes	Russia
Stripe	Yes	Yes	No	International
HyperPay	Yes	Yes + Mada	No	Middle East (UAE, Saudi Arabia)
MethodPay (Paygine)	Yes	No	No	Russia

How to create a payment provider

1. Go to Organization → Providers and click Add.
2. In the dialog, set Integration Type to Payment Provider.
3. Enter a Name for this integration (e.g., “Stripe Main” or “CloudPayments RU”).
4. Select the Provider from the dropdown.
5. Fill in the provider credentials (see sections below).
6. Click Save. The system generates a Webhook URL — copy it and add it in your provider’s dashboard.

CloudPayments settings

The form shows a CloudPayments Settings block:

• Public ID — the public store identifier from your CloudPayments dashboard.
• API Secret — the secret key used to sign requests.

After saving, copy the Webhook URL and paste it into the notification settings in your CloudPayments account.

Stripe settings

The form shows a Stripe Settings block:

• Publishable Key — your public key (pk_live_...).
• Secret Key — your secret key (sk_live_...).
• Webhook Secret — the signing secret for webhook verification. Must start with whsec_ (find it in Stripe Dashboard → Webhooks, not in the API keys section).

Optionally, the Apple Pay Settings block:

• Toggle Enable Apple Pay on.
• Enter the Merchant ID from Apple Developer (must start with merchant.).

HyperPay settings

The form shows a HyperPay Settings block:

• Access Token — your HyperPay API access token.
• Entity ID — the merchant entity identifier.
• Webhook Secret — a 64-character hex string (AES-256 key for webhook verification).
• API URL — the HyperPay API endpoint for your region.

Optionally, an Apple Pay Settings block (same structure as Stripe, with additional support for the Mada network in Saudi Arabia).

MethodPay settings

The form shows a MethodPay Settings block with fields provided by your MethodPay/Paygine account manager. This provider supports card payments only — Apple Pay and SBP are not available.

---

Cash Register Providers

A cash register provider generates and transmits fiscal receipts. IZI supports two adapters, each covering a specific regional compliance model.

Adapters and their regions

Adapter	Supported countries	Key features
Printer	UAE (AE), Morocco (MA), Saudi Arabia (SA)	5% VAT toggle, TRN when VAT is enabled, legal entity name required
KKM	Russia (RU)	Tax regime required per operation category

How to create a cash register provider

1. Click Add → select Cash Register Provider.
2. Enter a Name for the integration.
3. Choose an Adapter (Printer or KKM).
4. Set the Country.
5. Fill in the Cashier field — the name or identifier that appears on receipts.
6. Configure Tax Settings (vary by adapter, see below).
7. Click Save.

Tax settings — Printer (UAE / Morocco / Saudi Arabia)

• VAT — toggle. When enabled, a 5% VAT rate is applied to receipts.
• TRN (Tax Registration Number) — your VAT registration number. Required when VAT is enabled. Must not exceed the allowed character length.
• Legal entity — the company name printed on receipts. Required for the Printer adapter.

Tax settings — KKM (Russia)

For the KKM adapter, specify a tax regime separately for three operation categories:

Category	What it covers	When a receipt is issued
Balance top-up	Client deposits funds — credited as a prepayment	At the moment of top-up
Services	Purchase of gaming tariffs and session time	When a tariff is purchased
Goods	Purchase of bar items and merchandise	When a product is purchased

IZI supports all current Russian tax regimes: PSN (patent), USN (revenue), USN (revenue minus expenses), AUSN (revenue) 8%, AUSN (revenue minus expenses) 20%, OSNO with various VAT rates (0%, 10%, 20%, 22%, and calculated rates), as well as reduced regional USN rates of 5% and 7%.

---

Managing Providers

The providers table

All created providers appear in a single table. Click any row to open the edit form. The Usage column shows how many cash registers each provider is linked to — this helps you assess the impact before making changes.

Editing

Credentials can be updated at any time — for example, after a key rotation. After saving, the provider continues working without interruption. If you update the Webhook Secret or Webhook URL, remember to update it on the provider’s side as well.

Deleting

Deleting a provider is irreversible. Before deleting, confirm it is not linked to any club cash register — otherwise those registers lose their connection to the acquirer or fiscal system. The number of linked registers is shown in the Usage column.

---

Frequently Asked Questions

Do I need to configure both provider types?

It depends on your market requirements. A payment provider is needed if clients pay by card through a terminal or the mobile app. A cash register provider is needed if local law requires fiscal receipts — as in Russia (54-FZ) or UAE (VAT). Clubs that operate exclusively with cash and have no fiscal compliance requirement may skip the cash register provider.

Can one payment provider serve multiple clubs?

Yes. A provider is created once at the organization level and then linked to cash registers in any number of clubs in your network. This lets you manage API keys in a single place rather than per club.

How does IZI use the Webhook URL?

After you create a payment provider, IZI automatically generates a unique Webhook URL. The payment system sends transaction status notifications (success, decline, refund) to this address. Without a correctly configured webhook, IZI will not receive real-time payment confirmations.

What should I do if a provider still shows “Not configured” after saving?

Check that all credentials are correct. Common mistakes: for Stripe, the Webhook Secret is an API key instead of the signing secret (must start with whsec_); for HyperPay, the Webhook Secret is not a 64-character hex string; for Apple Pay in Stripe or HyperPay, the Merchant ID does not start with merchant..