Recurring payments (BLIK A/M/O)

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.

What BLIK models A, M and O are

Three variants of BLIK Recurring Payment (autopayment) handled by Tpay and registered at the customer's bank as recurring charge consent. Pick one in BLIK model (Basic tab). The model defines whether the amount is fixed, variable, and whether the customer must confirm each charge in the banking app. In Zevio the model is stored on the offer and applies for the whole subscription lifecycle.

At a glance

  • Amount - A: always the same; M and O: can change between cycles (usage, invoice, post-visit fee).
  • Subsequent charges - A and O: automatic on schedule; M: initiated automatically but customer may need to confirm each one in the banking app (72 hour approval window).
  • Bank limits (Tpay) - A: requires single payment limit, total limit and authorization expiry; M/O: no such limits on alias registration - optional max payments in Zevio instead.
  • Zevio plan - A: Basic and Premium; M and O: Premium or Enterprise.
  • Org permissions - O additionally requires BLIK Model O enabled (Tpay agreement, activated by support).
  • Promotions - date-based discount schedule: M/O only; trial and general discount on A have stricter time limits.
  • Schedule - charge after service: M/O only.

Model A - fixed amount

Simplest variant: each period the customer pays the same amount as on the offer (including promotions for that cycle). After the first payment and BLIK alias registration, further charges are fully automatic - no per-transaction confirmation in the bank.

  • When to use - fixed-price subscriptions: gym, SaaS, membership fee, media.
  • Frequency - presets or Other (count + unit: day, week, month, year).
  • Subscription expiry date - required; end of BLIK authorization at the bank (not shorter than one billing period).
  • Amount limits - system computes max single payment and total of all payments from offer price, frequency and expiry (hidden form fields sent to Tpay).
  • Max payments - not available; subscription ends by expiry date (and optional customer cancellation).
  • Trial / discounts - trial at most 1 payment or one billing period; general discount at most one period; no date-based discount schedule.

On /pay the customer sees: amount will be charged automatically at the shown frequency until cancellation in the banking app or expiry.

Model M - variable amount with confirmation

For billing where cycle amounts can differ (usage, custom quote, post-visit fee). The system initiates recurring payment automatically, but the bank may require customer confirmation in the mobile app for each transaction. The customer has up to 72 hours to approve - then the payment expires (timeout).

  • When to use - variable pricing where the customer should see and accept each charge: consultations, visit fees, periodic bills with different amounts.
  • Frequency - same as A (presets or Other); no mandatory expiry date like model A.
  • Max payments - optional (1-999); subscription ends when limit is reached.
  • Discount schedule - available (percentage discounts in date ranges).
  • Schedule - only model (with O) supporting Charge moment → After service.
  • Amount changes - merchant can charge a different amount next cycle; customer sees it when confirming in the bank (unlike O).

On /pay: each recurring transaction will be initiated automatically and may require confirmation in the banking app.

Model O - variable amount

For variable amount without confirming each payment in the bank - after first authorization further charges are fully automatic even when the cycle amount changes (within offer rules and API). Requires a separate agreement with the payment operator: org must have BLIK Model O enabled (sign PDF, send to contact@zevio.io).

  • When to use - variable subscriptions without engaging the customer each cycle (media, hosting, usage-based with automatic billing).
  • Frequency and max payments - same as M.
  • Discount schedule and after-service schedule - same as M.
  • Difference from M - no per-transaction confirmation in the banking app; amount and frequency can change on the merchant side without extra customer confirmation flow.
  • Payment flow - with Model O enabled on the org, simplified BLIK flow is possible (confirm in bank without 6-digit code each time - bank dependent).

On /pay: amount will be charged automatically; customer can cancel in the banking app.

Which model to pick?

  • Same price every month → A (Basic plan is enough).
  • Variable price, customer accepts each payment → M (Premium).
  • Variable price, fully automated charges → O (Premium + Model O agreement).
  • Charge only after a schedule visit → M or O (not A).
  • Seasonal calendar discounts → M or O.

What you set in the offer (panel)

In Basic tab enable Enable subscription mode, pick BLIK model, Payment frequency and - depending on model - Expiry date (A) or Max number of payments (M/O). Optionally Monthly billing day (1-31) 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 (especially for A) and Amount due today; below, model-specific info (automatic charges vs possible bank confirmation). Chooses BLIK or card; for BLIK enters code (or confirms in bank with Model O) and accepts recurring consent. List of banks supporting recurring BLIK is on the page. Screen details: How payment looks.

After first payment (subscription active)

Subscription appears under Subscriptions and payments → Subscriptions and in the customer portal. Next cycles: A and O charge automatically; M initiates charge and the customer may get a confirmation request in the banking app (up to 72 h). Payment history is in subscription details; customer can cancel (subject to Advanced cancellation lock) or in the banking app.

Recurring payments (BLIK A/M/O) | Zevio