Who Voucherify is
Voucherify is a promotion and loyalty engine founded in Katowice, Poland, in 2013. The company behind it, Voucherify PSA, has its registered office there and a second office in New York, and describes itself as independent. It calls its product an API-first incentive optimization engine: coupons, automatic discounts, gift cards, product bundles, referral programmes and loyalty programmes run from one set of rules, through a REST API or a dashboard. It names fintech among the industries it is built for, and is a member of the MACH Alliance.
Its current loyalty model, Loyalty v2, builds a programme from parts: point wallets that hold each member's points on a loyalty card, earning rules, tier structures, rewards and benefits, set up in the dashboard's Loyalty hub or through the API under /v2/loyalties. Voucherify runs shared API regions in Europe, the default, the United States and Asia (Singapore), hosts its service on Amazon Web Services, and is ISO 27001 certified. It works out who earned what from the orders and events it is sent, while the money stays in your ledger, which is why it is one of the loyalty and promotions connectors of our Rewards & referrals module.
What it does in your platform
Rewards & referrals
Works out points, cashback and tiers on settled card spend from the earning rules your team builds in its Loyalty hub, keeps each member's points on a loyalty card, and tells the platform what was earned, spent or taken back through signed webhooks. The platform decides which payments count, sends them from its server, and pays any money reward through the ledger.
How the connection works
The apps never call Voucherify. It has a client-side API and its own Android and iOS libraries, but none for Flutter, and in your platform every call goes from the server: customers through /v1/customers, settled payments through /v1/orders, members and balances through the Loyalty v2 endpoints under /v2/loyalties, with application keys that never leave the server. Voucherify reports back with signed webhooks.
A customer joins the programme
In the app, the customer joins your rewards programme. The platform checks that they have passed KYC and that the programme is switched on for their country and product, then creates them in Voucherify with the platform's random ID as their source ID, and no name, email address or phone number. A Create program member call enrols them, and Voucherify answers with a member ID and a loyalty card for each point wallet.
They pay by card, and it settles
An authorisation earns nothing. When the ledger shows the card payment as settled, the platform's server sends it to Voucherify as an order with the status PAID: a random reference, the amount, the customer's source ID and the metadata your rules need, such as the merchant category. Card numbers, account numbers and balances are never part of it.
Earning rules add the points
The order starts the earning rules your team built in Voucherify's Loyalty hub, through their Order paid trigger: say one point for each euro, double in one merchant category, within the earning limits of the point wallet. The points arrive as pending points and become spendable after the waiting period your team sets, long enough to cover most refunds.
A tier is reached
With this payment the customer has earned enough points in the tracking period to move from Silver to Gold in your tier structure. Voucherify records an UPGRADED tier transaction, and a Workflow, its tool for sending Loyalty v2 events to other systems, posts it to the platform as a webhook signed in the x-voucherify-signature header. The platform shows the new tier in the app, and our Notifications module tells the customer.
The platform books it
If your programme runs on points, the balance stays on the customer's loyalty card in Voucherify, and the platform reads it, with pending points and tier progress, through Get program membership to show it in the app. If it pays cashback, the platform books each earning Voucherify reports as a credit in the ledger, from your marketing budget account, so the money is never held in Voucherify.
A refund takes it back
When the payment is refunded or charged back, the platform reports it on the order, and the point wallet's return policy, set to deduct points, removes what the payment earned, from pending points or from the active balance, as a POINTS_REFUNDED transaction. Voucherify's documentation says refunds by item or by amount are not supported yet, so for a part refund the platform works out the difference and removes it with a negative Adjust card points call. A cashback credit is reversed in the ledger.
Next to other providers
Voucherify sits between the modules that know what happened and the ones that act on it. Card issuing and the Ledger say when a payment has settled, KYC / AML says who may join, and Fraud & risk checks devices and duplicate accounts: Voucherify's own documentation says identity fraud has to be prevented on your side, while its limits guard the programme itself. When a customer spends points on a reward, Voucherify records the purchase and the platform delivers it, as a credit through the Ledger or as a gift card through Runa, the module's reward delivery connector. Voucherify also has referral campaigns of its own, next to the module's referral connectors, and documents integrations with Braze, Customer.io and CleverTap, which are connectors of our Analytics & monitoring module.
Voucherify is one of the module's loyalty and promotions connectors, next to Talon.One, which presents itself as enterprise loyalty management with personalised promotions, and Open Loyalty, an API-first loyalty engine with gamification such as badges, challenges and leaderboards. Customer IDs, the record of settled payments, ledger entries, KYC and abuse checks and the per-country switch live in your platform, so a move between them swaps a connector and leaves your apps and your books as they are. Point wallets, earning rules, tier structures and rewards are built in Voucherify and would be built again in the new tool, and members' balances and tiers would be carried over to it.
When Voucherify fits best
A strong fit when
- Your team wants to build and change earning rules, tiers and point expiry in a dashboard, without a release of the apps or the platform.
- You want more than loyalty from one engine: discount coupons, gift cards and a referral programme next to your points and tiers.
- You want a company based in the EU as your data processor, with your project in its Europe region.
Also worth a look
- Talon.One or Open Loyalty, the module's other loyalty and promotions connectors.
- A tool your team already runs: its account becomes a connector too.
How we get you live
The contract
We help you get your Voucherify account and contract in place, with its data processing agreement, your project in the region you need and Loyalty v2 enabled on it. We build on Loyalty v2, because Voucherify keeps its earlier loyalty campaigns in maintenance only.
The data
We open your project in Voucherify's Europe region, whose API address is api.voucherify.io, unless you need the United States or Asia: a project's region cannot be edited later, so we settle it first. Each customer is created with a random platform ID as their source ID, which Voucherify also fixes at creation, and the profile's fields for a name, email address, phone number, address and birth date stay empty. With your team we agree the order metadata the rules may use. Voucherify's documentation puts one programme at up to 100,000 members, so for a larger customer base we plan the structure with Voucherify before launch.
The keys
The application keys, sent as X-App-Id and X-App-Token, go into your platform's secrets. Voucherify's separate client-side keys are not used, so the apps carry no Voucherify key at all. A secret generated in Voucherify's project settings signs every webhook with HMAC SHA-256: the platform rejects any call without a valid x-voucherify-signature, and accepts webhooks only from the IP addresses Voucherify publishes for your region.
A full test run
The whole programme is built first in Voucherify's Sandbox project, which has its own keys and shares no records with production. That matters, because once a programme is active its point wallets cannot be edited and no tier structure can be added. We run the full case there: a member joins, a PAID order earns pending points, a tier is reached, a refund takes the points back. Voucherify does not copy a Sandbox set-up across, so we rebuild it in your production project and repeat the run with a test member before your first real customer.
