Payment Providers in IZI: Integrations
Payment Providers in IZI: Integrations
Section titled “Payment Providers in IZI: Integrations”A payment provider is an intermediary between IZI and the banking system. The client pays in the app, the provider processes the transaction, notifies IZI via webhook, and IZI credits the balance. For offline payments (POS terminal), no provider is needed — the terminal and CRM work independently.
Offline vs Online Acquiring
Section titled “Offline vs Online Acquiring”Before choosing a provider, it’s important to understand the difference:
| Type | What It Is | Provider Needed in IZI? |
|---|---|---|
| POS terminal (offline) | Physical terminal, card is tapped at the register | No. Amount is entered manually |
| Online acquiring (app) | Client pays on their smartphone | Yes. Provider processes the transaction |
A POS terminal connects to the bank directly under a separate agreement — IZI is not part of that chain. Online payment through the app requires a configured integration in IZI.
How the Integration Works
Section titled “How the Integration Works”Standard online payment flow in IZI:
- Client selects an amount in the mobile app and taps “Pay”
- IZI redirects the request to the provider via API
- Client enters card details on the provider’s page (or uses a saved card / Apple Pay / Google Pay)
- Provider processes the payment
- Provider sends a webhook notification to the IZI URL
- IZI receives confirmation and credits funds to the client’s balance
The entire cycle takes a few seconds under normal operation.
Integration Parameters
Section titled “Integration Parameters”To connect any provider in IZI, you’ll need:
- API key (public) — for initializing the payment form on the client side
- Secret key — for server-side communication (stored encrypted)
- Webhook URL — generated by IZI automatically, entered in the provider’s dashboard
- Test keys — for verification before going live
These parameters are entered in Club Settings → Payment Methods → Online Payment.
Supported Providers
Section titled “Supported Providers”List current as of publication date. Check with IZI support for provider availability in your region.
Russia
Section titled “Russia”CloudPayments Russian provider supporting Visa/Mastercard/MIR cards, SBP (Faster Payments System), recurring payments. Well-suited for clubs with high online top-up volume — special pricing tiers for high throughput. Step-by-step connection guide — CloudPayments in IZI: Setup.
YooKassa (formerly Yandex.Kassa) Supports cards, YooMoney, SBP, installments. Convenient for clubs with an audience accustomed to the Yandex ecosystem. Registration — via the YooKassa website, electronic agreement.
Tinkoff Acquiring Cards, SBP, Tinkoff Pay. If the club’s account is with Tinkoff — setup is faster. Commission depends on volume.
Sberbank Acquiring For clubs with a large share of clients paying via SberBank Online and SberPay. Integration requires a technical review from Sber’s side.
International / UAE
Section titled “International / UAE”Stripe One of the largest international providers. Supports Visa/Mastercard/Amex, Apple Pay, Google Pay, many local payment methods. Available in most countries outside Russia. API documentation is among the best in the industry.
PayTabs Oriented toward Middle East markets. Supports local cards, MADA (Saudi Arabia), KNET (Kuwait). Popular among clubs in the UAE, Saudi Arabia, and Egypt.
HyperPay Another MENA provider. Supports international cards and regional payment methods.
Other Regions
Section titled “Other Regions”IZI operates in various countries — request the provider list for your market from support. The general integration principle is the same: API keys + webhook — only format details are provider-specific.
Key Parameter Comparison
Section titled “Key Parameter Comparison”| Provider | Market | Methods | Notes |
|---|---|---|---|
| CloudPayments | RU | Cards, MIR, SBP | Good docs, fiscal support |
| YooKassa | RU | Cards, YooMoney, SBP | Yandex ecosystem |
| Tinkoff | RU | Cards, SBP, Tinkoff Pay | Faster with Tinkoff account |
| Stripe | International | Cards, Apple/Google Pay | Best API, not available in RU |
| PayTabs | MENA | Cards, MADA, KNET | MENA specialist |
Fees are not shown as absolute numbers: they depend on volume, card type, and contract terms. Request a commercial proposal directly from the provider.
Typical Setup Mistakes
Section titled “Typical Setup Mistakes”Incorrect Webhook URL
Section titled “Incorrect Webhook URL”The most common mistake. The webhook URL is generated by IZI and must be entered in the provider’s dashboard exactly as IZI provides it. A single extra character or wrong path — and IZI will not receive payment notifications.
Production Keys Instead of Test Keys at Start
Section titled “Production Keys Instead of Test Keys at Start”Always test in sandbox mode first. Every provider supplies test keys and test cards. Testing takes 10–15 minutes but protects against real money in unexpected situations.
Mixing Public and Secret Keys
Section titled “Mixing Public and Secret Keys”Public key — in the “Public key” field, secret — in the “Secret key” field. Swapping them causes payments to initialize but confirmation to fail.
Switching Providers
Section titled “Switching Providers”If you need to switch providers:
- Configure the new provider in sandbox mode and verify
- Ensure all incoming webhooks from the old provider are processed (no payments in “pending” status)
- Replace the keys in IZI settings with new ones
- Update the webhook URL in the new provider’s dashboard
- Run a test payment in production mode
Running two providers in parallel is not supported — IZI configures one active provider for the online channel.
See Also
Section titled “See Also”- CloudPayments in IZI: Setup — detailed instructions
- Payment Methods: Setup — where to enter keys in the CRM
- Top-Up via App — how online payment works
Frequently asked questions
Is connecting a provider required for IZI to work?
No. IZI works without a provider integration — cash and manual card entry via POS terminal are available without API keys. A provider is only needed for online payments through the mobile app.
How many providers can be connected simultaneously?
Usually one provider per club for the online channel. If multiple methods are needed (e.g., cards + local payment systems), this depends on the specific provider's capabilities — some support multiple channels under one agreement.
Does IZI charge an additional fee for acquiring?
IZI does not charge a fee on top of the provider's rate. Payment processing fees go directly to the provider under the terms of your agreement with them.
Can a foreign provider be used?
Depends on the region and the provider's legal entity requirements. Stripe, for example, operates in many countries but requires compliance with local requirements. Check with IZI support for the current list for your market.
What is a webhook and why is it needed?
A webhook is a URL to which the provider sends a notification about the payment result (success/failure). IZI generates this URL automatically when setting up the integration. Without the webhook, the client's balance won't update automatically — the payment will go through, but IZI won't know about it.
How do I verify the integration works before going live?
Most providers offer a sandbox mode with test keys and test cards. Run a test payment — confirm the transaction appears in IZI history and the balance updated.