Value-added services your merchants will use
Zeal builds value added services payment terminals can run as software: loyalty, vouchers and customer insight on the devices already in the field. Value added services for PSPs, acquirers and ISOs — VAS for payment providers that works inside the permissions and responsibilities your payment stack already has, without changing merchant hardware.
Print your own branded receipt
Type a company name (payment provider or merchant, either works), then keep scrolling. The card machine does the rest: your name on the screen, your receipt out of the printer, and your customer's loyalty balance already on it.
Your brand on the receipt
Works for a payment provider or a merchant. Prefer a click? Use the button.
Runs on the card machines merchants already use. Trusted by industry leaders.
The differentiation problem
Terminal hardware and acceptance pricing have converged. Two providers can quote the same device at the same rate, and the merchant has no way to tell them apart. Value-added services are one of the few remaining ways to differentiate an estate and give a merchant a reason to stay past the end of the contract.
What Zeal is, and is not
Zeal is a value-added service that runs alongside the certified payment application. It does not become the payment application, the acquirer, the processor or the settlement system by running on the same device. Authorisation, clearing and settlement remain exactly where they are today.
Deployment model
Compatibility is proven per terminal model, firmware version, payment application, TMS profile and acquirer route. Rollout runs by cohort with version control and rollback, rather than a single estate-wide push that cannot be undone.
Value-added services for payment providers, from first cohort to full estate
A value-added service is judged on two things: whether merchants use it, and whether it can be deployed across a real estate without disrupting the payment. Most VAS propositions fail the second test long before anyone gets to test the first.
Estates are heterogeneous. A provider with several thousand merchants is usually running four or five terminal models across two or three firmware generations, on more than one acquirer route, with a TMS profile that differs by cohort. A service that only works on the newest device is not an estate proposition.
Zeal is deployed as software to supported terminals through the estate management tooling you already operate. Merchants keep the hardware they have, staff keep the process they know, and the customer keeps paying the way they always did.
The service runs at the moment of payment, which is where the value sits. A customer is recognised, a reward is applied or an offer is shown while the transaction is happening, rather than through an app the customer has to remember to open before they arrive.
Everything is bounded by what your contracts already allow. Deployment, data access and release approval remain subject to partner approval, device compatibility, certification, privacy requirements and market-specific controls, and those boundaries are agreed before the first cohort goes live.
What sits inside the service
Customer recognition at the point of payment, loyalty and stamp schemes, vouchers and redemption, digital receipts, feedback capture and estate-level reporting. A provider chooses which of these to enable, and whether they are presented under Zeal's brand or its own.
None of it asks the merchant to add a device to the counter or the customer to download anything. The terminal already in place does the work, which is what stops adoption stalling in the first fortnight.
Who is responsible for what
Terminal manufacturer, payment application vendor, acquirer or processor, PSP, TMS operator, VAS provider, ISO and merchant each retain defined responsibilities. Confusion about which of them owns a failed transaction journey is the most common reason a VAS pilot quietly stops.
The contract should name who approves a release, who can stop one mid-rollout, who handles a customer-facing failure at the till and who answers the merchant's call. Zeal expects to be named explicitly in that matrix rather than assumed into it.
Commercial models
Per-terminal subscription, per-merchant subscription, usage-linked fees, portfolio licence, a bundled proposition or partner revenue share. Each shifts risk and margin differently between the provider, the merchant and Zeal.
The right model depends on who receives the value and which costs rise with estate size. A per-terminal fee suits a provider bundling value-added services into its own tariff; a revenue share suits one testing appetite before committing an estate. Both are workable, and the choice is usually better made before a pilot than after it.
What are value-added services on payment terminals?
Value-added services on payment terminals are software services delivered through the card machine alongside payment acceptance: loyalty, vouchers, customer recognition, digital receipts and merchant reporting. They run on the same device as the certified payment application without replacing it, and they are typically supplied by a PSP, acquirer or ISO to the merchants in its estate.
What a value-added service cannot do
It does not fix a pricing problem: a merchant leaving over rates will still leave. It does not create engagement on its own, because a service that is enabled but never used produces nothing. And it removes no obligation from the payment stack — authorisation, settlement, certification and data protection duties stay exactly where they sit today.
VAS questions payment providers ask
Does adding Zeal require recertification of the payment application?
Zeal runs alongside the certified payment application rather than modifying it. Whether any recertification is required is confirmed per terminal model, payment application version and acquirer route during the compatibility assessment, before a cohort is scheduled.
Can the service be white-labelled?
Yes. Merchant-facing screens, receipts and reporting can carry the provider's brand or the merchant's, depending on how the proposition is positioned. Providers who sell value-added services as part of their own tariff usually white-label it entirely.
How is a rollout staged across an estate?
By cohort. A small group of terminals goes live first, behaviour is observed against agreed criteria, and the next cohort follows only if those criteria hold. Version control and rollback apply throughout, so a cohort can be returned to its previous state without a site visit.
Who owns the customer data?
Data ownership, lawful basis, retention and deletion are agreed in the deployment contract before any terminal goes live. Field-level mapping is documented, and payment credentials are not treated as unrestricted customer identifiers.
The fastest way to judge this is against your own estate. Bring a terminal model, a firmware version and an acquirer route, and we will tell you what is deployable and what is not.
Discuss a deployment with the Zeal team
Activating Zeal on your card machines is a breeze
Choose your integration path
Connect host-to-host through our APIs or embed the on-terminal SDK. You get a sandbox, an integration guide and a reference implementation from day one.
Share your estate details
Send your merchant data file with TIDs, MIDs and terminal models. We prepare signed builds for each terminal type, with release notes and a rollback plan.
Pilot, then roll out
We prove the experience on a pilot cohort with hands-on support, then deploy remotely across your estate through your TMS. No hardware changes, no engineer visits.
Go live and activate
Your merchants get onboarding flows, training material and ready-made campaign templates for their first 90 days, and you track activation and usage by cohort.
This is how we’re revolutionising payments for our partners
See what Zeal delivers in the field. Our partners earn new revenue from their terminal estates, and their merchants get customer identification, loyalty and insight at the point of payment.
Merchants run Zeal on the card machines they already own.
More repeat visits for restaurants running loyalty on Zeal.
Customer profiles created for merchants using Zeal.
Don’t take our word for it
Manos Perdikaris
Business Unit Manager
Jean-Philippe Niedergang
CCO and CEO of EMEA Region
Boris Ferlet
SVP, Android & Partner Ecosystem
Ahmed Hanafi
Founder & CEO
Mostafa Al Sagheer
CEO
Zeal has flexible pricing to fit your business needs
Every agreement is shaped with your commercial team: revenue share on a joint go-to-market, or an annual licence across your MIDs.
Revenue share or annual licence
One integration, two commercial models. Partner on revenue share, where Zeal goes to market inside your merchant proposition and we share the value-added services revenue it creates. Or license annually, a fixed yearly fee that activates Zeal across the MIDs you nominate, with predictable costs from day one.
Enable your card machines to:
Identify customers and offer exclusive rewards
Offer zero-friction card-linked loyalty
Showcase merchant branding and collect feedback
Provide merchants with powerful analytics
Provide you with powerful customer behaviour insights
Want to learn more?
Frequently asked questions
Zeal transforms your card machines into intelligent customer engagement tools, enabling real-time customer insights, visibility over in-store customers, and frictionless loyalty programmes for your merchants.
By integrating Zeal, you open new revenue streams through value-added services, differentiate your offering in a competitive market, and significantly boost merchant retention.
Zeal enables your card machines to identify customers through their payment cards, recognising employees, airline passengers, or telecom customers at the point of sale. This allows you to offer tailored rewards linked to existing corporate benefits or loyalty programmes. With Zeal, you can strengthen strategic partnerships and drive higher transaction volumes for your merchants.
Yes. Zeal is fully compliant with PCI DSS, GDPR, and follows industry best practices for data protection and security. Our technology is designed with privacy and compliance at its core.
Zeal is also recognised by industry leaders such as Visa and Ingenico, and has trusted partners worldwide, reinforcing our commitment to innovation, reliability, and global scalability.
Choose your integration path (host-to-host API or on-terminal SDK), share your merchant data file with TIDs, MIDs and terminal models, and we handle the rest: signed builds, a supported pilot, then remote deployment across your estate through your TMS.
Zeal is card machine-agnostic and works with all devices, both Android models and older Linux-based ones. We support all manufacturers including Ingenico, PAX, Castles, Verifone, Aisino and others, allowing you to activate Zeal across all your existing hardware with ease.
Yes. Zeal is built for global scalability and there are active card machines with Zeal in multiple markets globally. With multilingual support, regional compliance, and flexible integration options, Zeal can be activated anywhere, enabling consistent value-added services for your merchants worldwide.