Put loyalty inside your software, not beside it
For ISVs and payment application vendors: Zeal adds loyalty and customer identification to your product without rebuilding it. Integrate the Zeal SDK into your payment application, or embed Zeal directly into your ePOS or terminal software.
The World's #1 VAS Solution on Payment Terminals
Path one: the Zeal SDK for payment applications
If you build the payment application, integrate the Zeal SDK and your terminals gain customer identification and loyalty natively. Zeal sits alongside your payment app, identifies the customer when the card is presented, and never interferes with the payment flow, so your certification stays untouched. Full documentation at docs.getzeal.io.
.avif)
Path two: embedded iframes for ePOS and terminal apps
If you run an ePOS or an application that triggers the terminal, embed Zeal iframes inside your own software. Your interface stays yours; loyalty, rewards and customer recognition appear inside it, powered by Zeal behind the scenes.
Built to leave your payment flow alone
Zeal gathers what it needs when the payment method is presented, before the transaction, and the payment then processes exactly as it does today. No recertification, no added scheme fees, no change to how you process. Talk to sales for the integration guide and we will walk you through the technical flow.
What integrating Zeal actually involves
If you build a payment application, you integrate the Zeal SDK directly into it. You get a sandbox, a full integration guide at docs.getzeal.io and a reference implementation to build against, and the SDK is held to a strict processing budget so the checkout experience never slows. Your application keeps its certification; Zeal works alongside the payment, not inside it.
If you build an ePOS or an app that triggers the terminal, you embed Zeal iframes inside your own software instead. Loyalty, customer identification and reporting appear as native parts of your product, without your team building or maintaining any of it.
Either way, the commercial logic is the same: software with loyalty inside is stickier than software beside a loyalty app, and stickier software churns less and commands more. Your customers get a capability their competitors' vendors do not offer, and you share in the subscription revenue it creates.
We are honest about effort: a typical SDK integration is a scoped engineering project with a pilot phase, not an afternoon's work, and the iframe route is considerably lighter. Talk to us with your stack and we will tell you which path fits and how long it should take.
What does the Communicator SDK hook into?
The Communicator SDK gives your Android payment application direct app-to-app hooks into the payment flow: manifest-driven receivers handle discounts, rewards, eReceipts and refunds at fixed points in the transaction. In the beforeAmountEntry example shown here, the amount goes to Zeal before entry, any voucher or loyalty discount is applied, and the possibly discounted amount is handed back to the terminal so the sale continues as normal.
After a customer taps their card, Zeal identifies them by Card Token, and the acquirer still processes the payment as it always has; Zeal awards points once the payment is approved. The Zeal Developer Hub documents every receiver with request and response models and Kotlin examples, keeps a changelog, and publishes a status page for zms.getzealapi.com. SDK packages install from maven.pkg.github.com/zeal-io.
Read the docs at docs.getzeal.ioHow do Zeal iframes sit inside an ePOS?
Your ePOS window embeds Zeal's merchant modules directly, so customers, loyalty and campaigns appear inside the software your merchants already use. There is no separate app to open and no new login to learn: the Zeal screens render in a panel of your product, showing that merchant's own customer and loyalty data.
Because Zeal serves the modules, they stay current without an ePOS release on your side. When Zeal ships a new campaign type or report, it simply appears in the embedded view, and the white-label controls mean the whole thing carries the branding you choose.
Embedded Zeal moduleWhat can partners automate over the Acquirer API?
The Acquirer REST API is the estate-management surface: partners onboard merchants as branches, provision payment terminals, and archive, reassign or look up any device programmatically. It keeps a live estate in sync with Zeal without anyone touching a dashboard, and the status page for zms.getzealapi.com shows platform health at any time.
What is app-to-app integration on a payment terminal?
App-to-app integration means two applications on the same Android terminal talking to each other directly: here, your payment application and the Zeal app. Receivers declared in the manifest let the payment app hand a transaction to Zeal at fixed points in the flow (before amount entry, after approval, on refund) and get a response back before the flow continues, without routing the sale through any other device.
Where the SDK route is not the right fit
The Communicator SDK is for Android payment applications, so estates on other platforms take the iframe or Acquirer API routes instead. Zeal does not replace your payment application or your acquiring, and certification of the payment application itself stays with its owner. Zeal identifies the customer when the card is presented, before the transaction; payment processes exactly as today; no recertification, no second authorisation, no added scheme fees; redemption follows card scheme rules with one settled transaction.
ISV FAQs
Do we need to recertify our payment application?
No. Zeal sits alongside your payment application rather than inside the certified payment path, so the certification you already hold is untouched. The acquirer processes the payment as normal and Zeal awards points once it is approved.
How long does an SDK integration take?
It depends on your payment application and your release cycle, so we do not quote a fixed number. The pattern is a scoping session with our integrations team, a sandbox integration against the documented receivers on the Developer Hub, then a pilot before rolling out across your estate.
Can we white-label what merchants see?
Yes. Branded terminal screens, branded receipts and a white-label merchant dashboard all carry your identity, and campaigns run under the same branding. Your merchants experience your product, with Zeal supplying the machinery behind it.
What events can our ECR receive?
The Android ECR SDK triggers transactions on Zeal-integrated terminals and streams real-time Pusher events back as each one progresses, with ready-made dialogs included. Your till software can show live transaction state instead of polling for a result.
Around 5,000 merchants already run on Zeal-connected estates, live with Elavon, Worldpay, NMI (gateway) and Lloyds Cardnet, with 95k+ customer profiles created and restaurants seeing 15% more repeat visits. If you want those rails under your own software, the next step is a short technical scoping call.
Talk to our integrations teamActivating 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 runs on supported Android and Linux payment terminals. Compatibility depends on the terminal model, firmware, payment application, payment provider and acquirer route. We confirm the supported setup and any required approvals before scheduling a rollout.
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.