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.

Cookie choice and reliability

This page describes how conversion tracking stays complete across real checkout paths - consent, redirects, abandoned sessions, plans, and checks before you go live.

Cookie choice

Google and Meta tags load only after Continue. Necessary only leaves browser analytics tags off for that visit. The choice is remembered for the browser session. Server-side delivery does not show this notice; enable it only when your privacy policy and agreements allow measuring started and completed payments from Zevio servers.

When the browser is not enough

Customers may be sent to your own success URL right after paying. Browsers may also block tags. Server-side Meta Conversions API and GA4 Measurement Protocol cover payment submitted, purchase, and expired checkout sessions so those moments still reach your tools.

Abandoned checkout

On the payment or checkout page, leaving without purchase can send abandon from the browser.
When a checkout session expires, Zevio can send abandon from the server and also notify your webhook endpoint with checkout_session.abandoned.
After payment submit and after a successful purchase, abandon is suppressed so a bank redirect does not look like a drop-off.

Plans

Conversion tracking settings are available from Premium (also Enterprise and Trial). Below that, the UI stays locked and hosted checkout does not expose tracking for the organization.

Go-live checklist

Tracking is enabled on an eligible plan.
A test payment shows view, begin checkout, payment submitted, and purchase in GTM Preview.
GA4 shows the same journey, with purchase carrying transaction id and value.
Meta shows Pixel and Conversions API purchase with the same event id when both are configured.
If you use an external success URL, server-side purchase still appears in Meta and/or GA4.
Continue and Necessary only both behave as expected on the cookie notice.

If something is missing

No tags on checkout - tracking is off, the plan is too low, the visitor chose necessary cookies only, or no GTM / GA4 / Pixel ID is set.
GTM works but GA4 is empty - add GA4 tags inside GTM; with GTM present Zevio does not also inject a separate GA4 browser loader.
Purchase appears twice in Meta - browser and server event ids do not match, or a second Meta tag invents its own id.
No server abandon - the payment path never created an expiring checkout session, or session expiry is not running in that environment.
Ads triggers listen for payment.success - switch them to purchase.