What payment models are available?

Recurring payments (fixed monthly fee), prepaid (term agreement with price guarantee), installments (use today, pay later in 4 instalments), and variable fees (access + variable fee based on usage).

Can I support different payment intervals?

Yes. Define daily, weekly, monthly and custom cycles. Combine intervals within a single product.

Does Zevio support variable invoice amounts?

Yes. Ideal for consumption-based billing such as utilities. Automatic collection after invoice issuance.

Do I need my own mobile app?

No. Use Zevio via QR, email or website. API/SDK available.

Does the user have full control over subscriptions?

Yes. Users see all cycles/history and can pause/resume instantly.

Can I test the system before going live?

Yes. Full access to test environment with API documentation.

Does the transaction fee include the payment gateway cost?

Yes. The percentage charged per transaction is the total cost — it covers both the payment gateway (PSP) fee and the Zevio commission. The gateway adds no extra per-transaction charges. The price includes the payment gateway and one-off payments too.

Przelewy24

Przelewy24 handles BLIK and cards. Configure under Organization settings → Payment integrations → Przelewy24. Steps below match the in-app instruction.

Account and activation in Przelewy24

Registration and account verification

Create a merchant account in Przelewy24 and complete seller verification as required by the operator. Company data must match the organization details in Zevio.

API credentials in the P24 panel

In the Przelewy24 panel go to Settings → Payment form → My data. Copy Account ID, Reports key, and CRC key - you will need them in Zevio. In the 'IP Address' field, enter '%' to allow connections from Zevio.

In the IP Address field enter % (also shown as a hint in Zevio).

Configuration in Zevio

Credentials

In Zevio open Payment integrations → Przelewy24 → Credentials. Paste the values copied from the P24 panel: Account ID, Reports key, and CRC key. Save - Zevio will verify the connection automatically.

p24MerchantId (Account ID)
p24ApiKey (Reports key)
CRC key (p24CrcKey)

Webhooks and notifications

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

Payment operator selection

After successful verification, select Przelewy24 as the card and BLIK payment operator in organization settings (Payment operator section). Only then will payments be processed through P24.

Sandbox testing (summary)

Organization settings → Payment providers → Configure Przelewy24 (account ID, reports key, CRC key). After verification, select Przelewy24 for BLIK and/or cards. Recurring BLIK in sandbox requires an account enabled by Przelewy24 support.

sandbox (BLIK entered in Zevio): successful test uses code 777XXX, where X is a digit 0-9. Failed payment: any other 6 digits.
Recurring BLIK alias registration in sandbox: amount ending in .08 (e.g. 8.08, 10.08). Set it manually in the offer.
Recurring BLIK: model O only (variable amount without confirmation).
If even a 777XXX code ends with an authorization error, ask P24 support to enable on-site BLIK (whitelabel) and recurring payments on your sandbox account.

Where in the dashboard

/dashboard/settings/organization → Payment integrations → Przelewy24

Detailed sandbox scenarios

BLIK

sandbox (BLIK entered in Zevio): successful test uses code 777XXX, where X is a digit 0-9. Failed payment: any other 6 digits.
Do not reuse the same BLIK code in quick succession - sandbox may return incorrect responses.
Zevio sandbox: same as Tpay - bank without recurring BLIK support; with manual recurrence on (refuseNoPayId: false) Zevio pays one-time, otherwise unsupported_blik_token / fallback offer.
Recurring BLIK alias registration in sandbox: amount ending in .08 (e.g. 8.08, 10.08). Set it manually in the offer.
Recurring BLIK: model O only (variable amount without confirmation).
First payment: customer enters a BLIK code and confirms saving for recurring charges in the banking app. Later charges: no T6 code.
If even a 777XXX code ends with an authorization error, ask P24 support to enable on-site BLIK (whitelabel) and recurring payments on your sandbox account.
Test: offer with BLIK subscription and .08 amount → first payment with 777XXX code → confirmation in the banking app → active subscription → next charge without a code.

Cards

Redirect to the Przelewy24 payment form. Card data is entered on the provider side.
sandbox test cards.
Recurring card payments work after the first successful card authorization.

Apple Pay / Google Pay

Redirect to Przelewy24. Apple Pay in Safari, Google Pay in Chrome / on Android.
Apple Pay: Safari on iOS/macOS → confirm in Wallet on the P24 page → success.
Google Pay: Chrome or Android → confirm Google Pay on the P24 page → success.
If Apple Pay is not enabled on the sandbox account, payment will not start - ask P24 to enable Apple Pay.
Subscription offer: use card or BLIK. Apple Pay and Google Pay on subscriptions work only with Stripe.

Przelewy24 sandbox documentation: https://www.przelewy24.pl/en/help-center/api-technical-support/how-do-i-set-up-the-sandbox-environment