CloudPayments in IZI: Setup

CloudPayments in IZI: Setup

CloudPayments is a payment provider that allows club clients to top up their gaming balance online through the IZI mobile app. Supports Visa, Mastercard, MIR cards, and SBP (Faster Payments System). Connection takes a few steps: register with the provider, get keys, configure in IZI, test.

Step 1. Register with CloudPayments

Go to cloudpayments.ru and create an account.

Registration requires:

• Organization or sole proprietor tax ID
• Bank account details for payouts
• Information about your website/app (indicate you’re working with IZI)

After document verification, CloudPayments activates the account and provides dashboard access.

Step 2. Create a Project in the Dashboard

In the CloudPayments dashboard, create a project for your club:

1. Navigate to Projects → Create Project.
2. Enter a name (e.g., “Arena Club”).
3. Project type — Website or Mobile App (choose as appropriate).
4. Enter your domain URL (if any) or the IZI domain.

After creation, the project receives a Public ID and API Secret — these are your integration keys.

Step 3. Get API Keys

In the project settings, find:

• Public ID — public identifier, used on the client side
• API Secret — secret key, used for server-side requests

Copy both — they’re needed in the next step. The secret key may not be shown again in some interface versions — save it immediately.

Step 4. Configure the Integration in IZI

Navigate to Club Settings → Payment Methods → CloudPayments.

Enter:

• Public ID from CloudPayments
• API Secret from CloudPayments

Save settings. IZI will automatically generate a Webhook URL — copy it; you’ll need it in the next step.

Step 5. Configure the Webhook in CloudPayments

A webhook is the address CloudPayments sends a notification to after each payment. Without it, IZI won’t know the client paid.

In the CloudPayments dashboard:

1. Navigate to Project Settings → Notifications.
2. In the Notification URL field, paste the Webhook URL that IZI generated.
3. Ensure the URL starts with https:// — CloudPayments requires a secure connection.
4. Save.

Additionally, it’s recommended to enable notifications for these events:

• pay — successful payment
• fail — failed payment
• refund — refund

Step 6. Test in Sandbox Mode

Before accepting real money, run a test.

In the CloudPayments dashboard, switch to Test Mode. This uses test cards (numbers published in the CloudPayments documentation).

Run a test payment through the IZI mobile app:

1. Open the app and navigate to balance top-up.
2. Enter a minimum test amount.
3. Use a test card from the CloudPayments documentation.
4. Verify the transaction appears in IZI history.
5. Verify the client’s balance updated.

If the test succeeds — switch to production keys.

Step 7. Switch to Production Mode

In CloudPayments settings, switch the project to Production Mode.

In IZI, verify that production API keys are entered (not test ones). Test and production keys are different in CloudPayments — don’t mix them up.

Run one real test payment with a minimal amount, confirm the funds were credited to the client’s balance in IZI.

Working with Russian Fiscal Requirements (54-FZ)

If your club operates in Russia and must use an online cash register — every online payment through CloudPayments must be accompanied by a fiscal receipt.

CloudPayments supports this through the FFD (Fiscal Data Format) protocol. Configuration:

1. In the CloudPayments dashboard, navigate to Fiscalization.
2. Connect an online cash register (Atol Online, OFD.ru, and other fiscal data operators are supported).
3. Configure receipt parameters (item name, VAT, payment subject).

54-FZ configuration details depend on your fiscal data operator — contact CloudPayments support for the current guide.

Troubleshooting Common Issues

Payment Went Through, Balance Didn’t Update

1. Check the Webhook URL in CloudPayments — must exactly match the URL from IZI settings (case, trailing slash, https protocol).
2. Check CloudPayments history: is the payment recorded? Status “Paid”?
3. Check webhook logs in CloudPayments — was a notification send attempted?
4. Verify the IZI server is accessible at the webhook URL (not blocking CloudPayments IPs).

Card Declined

Check:

• Card is supported by CloudPayments (MIR, Visa, Mastercard — yes; UnionPay — not in standard configuration)
• Transaction limit not exceeded (CloudPayments has default daily limits)
• Card not blocked by the bank for internet payments

401 Error / Authentication Failed

Incorrect API Secret. Re-paste the key — ensure you copied it completely without extra spaces.

Refunds via CloudPayments

When processing a refund in IZI:

1. IZI sends a refund request to CloudPayments via API.
2. CloudPayments processes the refund and returns funds to the client’s card.
3. Credit timeframe — 3–10 business days (depends on client’s bank).
4. A “Refund” entry appears in IZI transaction history.

Refunds work automatically if the API Secret is correctly entered and the CloudPayments project has no refund restrictions.

What to Do Next

After successful connection:

• Verify the online payment button appears in the mobile app for clients
• Configure top-up bonus — it fires for online payments too
• Tell clients about the self-service balance top-up option — reduces cashier load during peak hours

See Also

• Payment Providers: Integrations — other supported providers
• Payment Methods: Setup — where to enter keys in the CRM
• Top-Up via App — how the client sees the process
• Refund Process — how to process refunds for online payments