PayU

PayU handles BLIK and cards (PLN POS) plus a separate EUR POS (EUR cards/wallets). Configure under Organization settings → Payment integrations → PayU. Steps below match the in-app instruction.

Account and activation in PayU

Registration and account verification

The merchant account is created automatically by Zevio. PayU emails you a Management Panel invitation - set your password from that message (not your Zevio password), sign in, and complete KYC/AML, the agreement, and the activation transfer following PayU registration instructions.

You're one step away from selling with Zevio - activate your PayU account. Check your email inbox. You should find a message from the payment gateway asking you to set a password for the PayU Merchant Panel. Set the password, sign in to the panel, then complete KYC and the agreement.

Payment point (POS) - REST API

In the PayU panel go to Shop → Payment points. When adding a point, choose REST API (Checkout) - not Classic API. After creating the POS, open its configuration and copy Pos ID, Client ID, Client Secret, and Second Key (MD5). Transparent BLIK (Level 0) and PAYID must be enabled on the same Pos ID you paste into Zevio. PAYID requires Sales/Customer Care boarding (sandbox and production). Card MULTI tokenization on sandbox REST is usually available automatically ~90 minutes after POS creation.

Configuration in Zevio

Credentials

During organization onboarding Zevio saves POS credentials (Pos ID, Client ID, Client Secret, Second Key) automatically. You can review them under Payment integrations → PayU.

  • Pos ID, Client ID, Client Secret, Second Key (MD5)
  • This is the PLN POS. Add a separate EUR POS later if you need EUR offers.
  • When attaching an existing account, use the credentials form (not Classic API).

Enter Pos ID, Client ID, Client Secret, and Second Key from the PayU panel (REST API) to connect an existing merchant account to this organization. This is the PLN POS. Add a separate EUR POS later under organization payment settings if you need EUR offers.

Webhooks and notifications

When registering a payment, Zevio passes webhook and return addresses to PayU automatically. You do not need to manually configure notification URLs in the PayU merchant panel.

Payment operator selection

After successful verification, select PayU as the card and BLIK payment operator in organization settings (Payment operator section). BLIK subscriptions: model O only. Cards: white-label Secure Form - one-time SINGLE_LONGTERM, subscriptions MULTI (TOK_), no hosted checkout redirect.

EUR POS

Enter credentials for a separate PayU payment point that supports EUR. EUR offers require this POS.

Partner auto-registration

Fill in the details required by PayU. Tax ID, address, phone, contact person, and website are taken from the organization settings form and are saved only after successful registration.

Sandbox testing (summary)

Organization settings → Payment providers → Configure PayU. Separate REST API POS for PLN (BLIK + PLN cards) and a separate EUR POS (EUR cards/wallets only). From the PayU panel copy Pos ID, Client ID, Client Secret, and Second Key. For BLIK, enable transparent BLIK on the PLN POS. BLIK subscriptions need to be enabled separately by PayU (Sales / Customer Care). Cards are entered in the form on the Zevio page (no redirect to PayU). After verification, select PayU as the BLIK and/or card operator.

  • BLIK works only on PLN offers and the PLN POS. In the BLIK field in Zevio, enter one of these 6-digit test codes:
  • With PayU, BLIK subscriptions work in model O only and only in PLN.
  • The same PayU test cards work for PLN and EUR offers. EUR offers need a configured EUR payment point. Use different cards for one-time payments and subscriptions.
  • Subscription offer: use card (Cards section) or BLIK. Apple Pay and Google Pay on subscriptions work only with Stripe.

Where in the dashboard

  • /dashboard/settings/organization → Payment integrations → PayU
  • Payment operator → PayU for card/BLIK

KYC / AML verification in PayU

Open this section first, then confirm

1. PayU email and first sign-in

Zevio has already created the firm, shop, and POS in PayU and submitted company data (NIP, REGON, legal form, address, website), IBAN, representative details with PESEL, and POS credentials. PayU emailed you an invitation - open it, set the Management Panel password, and sign in. The PayU panel password is not your Zevio password.

2. Upload documents in the PayU panel

Finish KYC in the panel: attach a scan of the representative's ID and any other documents PayU requests (for example a beneficial owners declaration). You do not need to re-enter company data, PESEL, or IBAN - they were submitted during registration via Zevio.

3. Accept the merchant agreement

Accept the merchant agreement online in the PayU panel. Without the agreement and successful verification, PayU will not activate production payment methods.

4. Activation transfer

Make the activation transfer from the bank account provided at registration (business account; for sole traders the owner's account is accepted). In the panel: Registration → Activation transfer. Only after it is credited does PayU start the AML review.

5. Wait for the AML decision

PayU runs KYC/AML on its own. Until approval, the account may stay restricted. After approval, finish any remaining setup in the PayU panel.

Merchant activation and payment methods

1. Wait for payment methods to activate

Right after registration the POS usually only has a disabled test payment method and no automatic payouts. Other methods appearing with ENABLED status in the PayU Management Panel means PayU has activated the merchant.

2. What happens next in Zevio

POS credentials are already stored in Zevio. When methods are active in PayU, you can accept payments (BLIK and card via PayU). While verification is pending, the organisation stays in test mode - turn it off in Zevio only after PayU activates the merchant.

Zevio submits registration data to PayU but does not run AML checks. Documents, the agreement, the activation transfer, and the KYC/AML decision are handled by PayU.

Detailed sandbox scenarios

Organization settings → Payment providers → Configure PayU. Separate REST API POS for PLN (BLIK + PLN cards) and a separate EUR POS (EUR cards/wallets only). From the PayU panel copy Pos ID, Client ID, Client Secret, and Second Key. For BLIK, enable transparent BLIK on the PLN POS. BLIK subscriptions need to be enabled separately by PayU (Sales / Customer Care). Cards are entered in the form on the Zevio page (no redirect to PayU). After verification, select PayU as the BLIK and/or card operator.

BLIK

  • BLIK works only on PLN offers and the PLN POS. In the BLIK field in Zevio, enter one of these 6-digit test codes:
  • successful one-time payment (or another 777xxx).
  • successful payment (also works for subscriptions).
  • payment declined.
  • code expired.
  • code cancelled.
  • code already used.
  • Subscription
  • PLN offer with BLIK subscription enabled (model O). First payment with a code; later renewals without a code.
  • use for the first subscription payment (successful registration).
  • one-time only. Do not use for subscriptions (later renewals will fail).
  • bank without BLIK subscription support.
  • Offer amount 39.30 PLN - next renewal: MIT not allowed error.
  • Offer amount 39.31 PLN - next renewal: limit exceeded.
  • Offer amount 39.32 PLN - next renewal: insufficient funds.
  • With PayU, BLIK subscriptions work in model O only and only in PLN.

Cards

  • The same PayU test cards work for PLN and EUR offers. EUR offers need a configured EUR payment point. Use different cards for one-time payments and subscriptions.
  • Enter card details in the form on the Zevio page. Unless noted otherwise: expiry 12/29, CVV 123.
  • One-time payment
  • Use the cards below on offers without a subscription. Do not use them for subscriptions.
  • successful payment (PLN or EUR).
  • successful payment (PLN or EUR).
  • payment declined.
  • successful only for amounts below 10.00 PLN or 10.00 EUR.
  • Subscription
  • For subscriptions use the cards below. Same numbers on PLN and EUR offers. The first payment may ask for bank confirmation.
  • recommended subscription test card (successful payment).
  • successful payment.
  • successful payment.
  • expiry 02/32, CVV 123 - successful payment.
  • successful only for amounts below 10.00 PLN or 10.00 EUR.
  • Do not use one-time cards for subscriptions - the subscription will not be saved.

Apple Pay / Google Pay

  • Redirect to PayU. Apple Pay in Safari, Google Pay in Chrome / on Android. For Apple Pay add a PayU test card to Wallet first.
  • Safari, add the card to Wallet → confirm on PayU → success.
  • Google Pay: Chrome or Android → confirm on the PayU page → success (card is not charged in sandbox).
  • in Wallet - payment declined (same cards as one-time card payments).
  • Subscription offer: use card (Cards section) or BLIK. Apple Pay and Google Pay on subscriptions work only with Stripe.
PayU Europe sandbox: https://developers.payu.com/europe/docs/testing/sandbox/