Buyer notifications – BLIK manual recurring

This page describes the messages the buyer sees when a subscription runs in BLIK manual recurring mode. This mode is created when the customer's bank does not support recurring BLIK payments (no alias / payId) - the subscription then uses the BLIK_MANUAL_RECURRING method and the customer pays each period manually with a one-time BLIK code after a reminder. Whether such a subscription is created at all is controlled by the Enable BLIK manual recurring for unsupported banks toggle in the offer's Advanced tab.

All the messages below fire automatically - no separate configuration needed. It is enough that the offer allows manual recurring (permissive mode or the BLIK manual rule) and a customer with a bank lacking recurring support goes through checkout.

1. Screen after the first payment (subscription created)

After a successful first payment the customer lands on a success screen that clearly states the subscription was created in manual mode and that we will ask for a new code at each renewal. The payment page carries the blikRecurringManual=1 URL parameter.

  • Heading: „Subscription created with a one-time BLIK code”.
  • Body: the subscription has been created, but the customer's bank does not support recurring payments, so it was set up using a one-time BLIK code - and we will remind them to enter a new code at each renewal so the payment can be completed.
  • Action: a Manage subscription button leading to the customer portal.

2. Email: subscription ready to renew

Because Zevio does not charge the customer automatically in manual mode, before each renewal we send an email asking for a fresh BLIK code. Sender: Zevio <no-reply@zevio.io>.

  • Subject: „Enter a new BLIK code to renew your subscription”.
  • Heading: „Your subscription is ready to renew.”
  • Body: because the bank does not support recurring BLIK payments, a new one-time code is needed to renew; click the button, enter the code and confirm the payment to keep the subscription active.
  • Summary: product, payee, subscription ID, renewal date and amount due.
  • Action: a Go to payment → button leading to the offer's payment page with a renewal token; footer with a link to the support team.

Reminder schedule

For BLIK_MANUAL_RECURRING subscriptions the cron sends emails relative to the next payment date (nextPaymentDate):

  • One day before the due date - a heads-up that renewal is approaching.
  • On the due date - the subscription moves to PAST_DUE and we repeat the request for a code.
  • After 2 days without payment - the subscription is cancelled (MANUAL_RENEWAL_TIMEOUT) and a final email is sent.

3. Payment screen at the next renewal

After clicking Go to payment the customer reaches the offer's standard payment page, switched into manual recurring payment mode (blikManualFallback=1 in the URL). The customer enters the current 6-digit BLIK code and confirms in their banking app.

  • Payment method section: „Manual recurring payments” with the description: „This is the next payment for your subscription. Pay it with a BLIK code to extend access for the next period.”
  • Field: „BLIK code” - a single field for the 6-digit one-time code (card is usually hidden in this mode).
  • Summary on the left: amount, tax, „Due today”, payment frequency, next payment date and „Subscription valid until”.
  • Consent: „By paying, you agree to BLIK subscription payments confirmed with a code.”
  • Optional: a Switch to automatic payments link - if the customer's bank starts supporting the BLIK alias, the subscription can be upgraded to BLIK_RECURRING and future periods run automatically.
If a Tpay ALIAS_REGISTER webhook arrives after the subscription is created, Zevio stores the alias and upgrades the method to `BLIK_RECURRING` - from then on the customer no longer receives code requests and renewals run automatically (see „Late alias registration” in the advanced settings).
Buyer notifications – BLIK manual recurring | Zevio