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.

Recurring payments (BLIK)

Recurring payments (subscriptions) mean the customer pays regularly - e.g. weekly, monthly or yearly - instead of once. Used for memberships and recurring services. You enable them in the offer form with Enable subscription mode; below: what you set in the panel, how BLIK models work and what the customer sees.

BLIK recurring (model O)

Zevio creates and updates recurring BLIK subscriptions as model O: variable amount with automatic subsequent charges after the first authorization (no per-cycle bank confirmation). Existing A/M offers in the system can still run for active subscriptions; the panel and REST write paths always store O for new and unlocked edits.

At a glance

Amount - can change between cycles (usage, invoice, post-visit fee) within offer and API rules.
Subsequent charges - automatic on schedule after first BLIK authorization.
Max payments - optional cycle limit (1-999) in Zevio.
Plans - available on all plans (subscriber limits apply).
Org permissions - some payment providers require BLIK Model O agreement with the operator.
Promotions - trial, general discount, and date-based discount schedule.
Schedule - charge after service is available with recurring enabled.

What you set in the offer (panel)

In Basic tab enable Enable subscription mode, set Payment frequency and optionally Max number of payments. Optionally Monthly billing day (1-31) and first-payment prorate for monthly cycles. Frequency is stored as count + unit (e.g. 1M = monthly). In Advanced add cancellation lock in the customer portal. Form field details: Offer - basic information.

What the customer sees on the payment page

Customer sees frequency, subscription validity and Amount due today; below, info that amounts are charged automatically. Chooses BLIK or card; for BLIK enters code (or confirms in bank) and accepts recurring consent. List of banks supporting recurring BLIK is on the page. Screen details: How payment looks.

After first payment (subscription active)

The subscription appears under Subscriptions and payments → Subscriptions and in the customer portal. Later cycles are charged automatically on schedule after the payment instrument is saved. Payment history is in subscription details; the customer can cancel (subject to the Advanced cancellation lock) or in the banking app.

Payment providers and saved instruments

New offers store BLIK as model O. PayU, P24 and AutoPay accept only model O on the offer. Tpay may still run legacy A/M on already active subscriptions. AutoPay additionally supports BLIK model M charges (AutoPay gateway) when the subscription already has model M stored.

Tpay - BLIK: aliasValue (+ aliasType PAYID/UID); card: tpayToken. Alias reconcile: daily cron.
PayU - BLIK: payId (PAYID); card: payuCardToken. Charge only when registered !== false.
P24 - BLIK: aliasValue type ALIAS + stored PSU (IP/User-Agent); card: p24CardRefId. Charge requires registered !== false.
AutoPay - BLIK/card: clientHash (aliasValue / autopayClientHash, type CLIENT_HASH). Registration via RPAN/ITN; charge requires registered !== false and a remoteID from the charge response.