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. Zevio app handles the wallet. 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.

How payment looks for the customer

This section describes the payment flow from the customer’s side: opening the link (or scanning QR), entering email or logging in, choosing payment method (BLIK or card) and clicking Pay. Step by step from link to success or error page.

Step 1: Opening the link

Customer clicks the link or scans QR. Link must be full - truncated URL can cause an error. They may see:

Invalid product link - link broken or incomplete; offer does not load.
Product is not active - offer is disabled (Inactive in panel).
Link expired - message and Back.
Offer does not exist - Back to homepage.

Step 2: Payment screen - left (what customer sees)

Logo, Cancel.
Organization name, offer title.
Amount (net, tax), Amount due today.
If subscription: Frequency, Valid until, Next payment.
If promotions: reduced amount or trial info.
If promo codes enabled: Promo code field (Add promo code → enter code → Apply).
If additional charges: line items added to total or choice of one option (e.g. delivery).
If referral link in URL: referee benefit applied automatically (banner with discount info).
Offer details: images (gallery), description.

Step 3: Login or email (right)

If not logged in: Log in to continue payment, Log in with Google, Email and Next. After email: if account exists, Password and Log in may appear; if not, Continue with email. Email links the payment and creates or matches the customer in your org. If customer already has an active subscription for this offer they see You have an active subscription with Subscription details (portal).

Step 4: Payment method and pay

Payment method - BLIK or Card. Terms with Expand / Collapse. For BLIK: BLIK code (6 digits); validation: "Enter valid 6-digit BLIK code". For BLIK subscription - list of Banks supporting recurring BLIK. Optional Marketing consent. Bottom: Pay or Pay X.XX PLN, Secure payments by + Tpay logo.

Customer chooses method, fills field (BLIK or card on gateway), clicks Pay. They go to the payment gateway or "Please wait, confirming your payment…" - then status is polled; after confirmation redirect to success or error. Do not close while waiting. After settlement: success page or error page (or redirect to offer Thank you / Error URLs). Details: Payment success and failure.

Payment methods

BLIK - 6-digit code from bank app; authorized in the bank. For BLIK subscription the bank must support recurring BLIK - list is on the payment page. Card - redirect to Tpay; customer enters card data. In offer settings you can restrict to BLIK only or Card only; at least one method must be on.

When Pay is disabled

Pay is disabled when: email not provided, terms not accepted, offer inactive or link expired. Inactive offer shows inactive product message; expired link shows message and Back.

What happens after clicking Pay

After Pay with method and data (e.g. BLIK code, customer email) the system creates a payment record (PENDING) and redirects to Tpay. When the gateway confirms, status is updated (SUCCESS/FAILED); for subscription the subscription is created or updated; org is notified and - if configured - webhook is sent. Amounts are stored and shown in the offer currency (PLN, EUR or USD). Under Subscriptions and payments and on customers you see the transaction currency symbol.

Offer group (variant switcher)

When Offer group with switching is enabled in Advanced, the customer sees variant options (e.g. plans) with amounts. Choosing another variant reloads the page to that offer (qrId) in the same group. For subscriptions, separate subscription switching between group members may apply - see Offer - advanced settings.

Data collection, invoice and consents

With Collect company data at payment enabled (master switch in Advanced), the customer sees extra fields: company, tax ID/VAT (country validation), address, phone, marketing/terms consents configured on the offer. Invoice requires data collection enabled. Required fields must be filled - otherwise Pay stays disabled. Field details: Offer - advanced settings.

Fallback offers and manual BLIK

When payment on the primary offer fails (or BLIK needs manual confirmation) and Fallback offers on error are configured, the customer may see a transition screen with description and a button to a backup offer (e.g. cheaper variant or one-time payment). With manual BLIK, the customer confirms in the banking app; after timeout the system may offer fallback per rules. Merchant config: Offer - advanced settings.

reCAPTCHA protection

Before creating a payment the system may require a reCAPTCHA token (typically invisible to the customer). The token is sent with the payment request; missing or rejected token shows an error without creating a transaction.