Meal vouchers in Europe Order a meal voucher card programme
Order a meal voucher card programme
Order a meal benefit programme for your team in three steps. Virtual cards issue in minutes and land in Apple Pay and Google Pay. Spending is restricted to food at the moment of authorisation, and the ceiling that applies in your market is applied to your card lines while you configure them.
Where does this programme run?
Cards are issued in euro, so the list covers the euro area. The market you pick sets the daily cap and the tax-exempt ceiling, and we apply them to your card lines automatically.
Card design
Cards are virtual. They land in Apple Pay and Google Pay the moment the employee accepts, so there is no delivery cost and nothing to wait for by post.
What can the card pay for?
Every authorisation carries the merchant category and merchant id. Your rules decide before the transaction is approved, so the scope below is enforced at the payment itself, not reconciled afterwards.
Define your cards
Add a line per group of employees. The monthly load is what each employee receives.
| Group name (optional) | Employees | Monthly load per person | Line total | Remove |
|---|
Who is the employer?
We run know your business checks on this entity. Nothing is issued before it clears.
How the programme is funded
You transfer the monthly load to your programme account. Cards carry a balance only after the funds land, so no employee can spend money that is not there.
Your programme
Check it over. Anything here can still be changed.
What happens after you submit
What it costs, before you fill anything in
The numbers are on the site rather than behind this form. 500 EUR to set the programme up, once. 1.50 EUR per card per month. Nothing per transaction, whatever your staff spend and however often. Physical cards carry the cost of plastic and delivery, and anything outside a standard build is priced separately. Pricing has the detail.
The absence of transaction fees is the part worth pausing on. A meal card gets used on most working days, so a programme priced per transaction bills you roughly twenty times a month per person and costs more the better it works. Priced per card, next year's cost follows from headcount alone.
What happens after you send it
We answer with your market first. Whether acceptance can be restricted by merchant category alone, or whether the law there requires a contract with every accepting merchant. That single answer shapes the build, and it differs between Germany and Italy. It is also the answer that decides whether a card can carry the benefit at all.
Then the checks on your company. We verify the employer and the beneficial owners before any card is issued. This is the step most likely to set your real start date, so the sooner the registered company details are with us, the sooner the rest moves.
Then the build. Your acceptance rules and caps are loaded, the funding account is opened, and your first cycle is funded. Cards sit at a zero balance until that transfer settles, then employees are invited. Launching covers the sequence in full, including the week it takes from decision to the first card.
What we do, and what we do not
We issue cards and process transactions with licensed partners. We do not hold our own electronic money or payment institution licence, we do not do acquiring, and we are on Mastercard rather than every network. If your programme needs something we do not have, it is faster for both of us if you know that on the first call.
Where we are useful is narrower and more specific: programmes where the acceptance decision has to consult your own merchant list rather than a category code, and programmes moving off an issuing partner that is no longer reliable. Both are covered in the guides.
If you are still working things out, start with the pages instead. Open loop or closed loop answers the question that determines the architecture, how to launch a programme covers the sequence, and migrating to a new issuer covers the case where the timetable is not yours. None of them requires talking to anyone.
Issuer or employer, the form is the same
The form above serves both. An employer orders cards for its own staff and the ceiling in its market is applied to every card line as it configures them. A voucher issuer or benefit platform orders the same way, with its own brand on the card and its own acceptance list behind the authorisation. The card programme page covers the issuer side in full.
Seventeen markets have a rules page here, and it is worth reading the one for your market before you order: Austria, Belgium, Bulgaria, Croatia, Czechia, Finland, France, Germany, Greece, Hungary, Italy, Luxembourg, Poland, Portugal, Romania, Slovakia and Spain. Each one tells you the ceiling that applies, what the benefit is worth against paying the same amount as salary, and what disqualifies the exemption. If yours is missing, it may be one of the countries with no scheme at all.
One thing worth knowing before you fill it in. Cards are issued in euro, which is why the market list in the form covers the euro area. A programme in Czechia, Hungary, Poland or Romania is priced in the local currency, and a card denominated in euro converts on every purchase, which the employee sees on the statement. For those four markets, send the order anyway and we come back with the local currency route. Bulgaria joined the euro area in January 2026 and is outside the issuing footprint for now, so it is missing from the list on purpose.
What happens to what you send
We use the details to answer the order. There is no newsletter attached to this form, no mailing list, and no third party analytics reading what you type into it. The form asks for a funding account so that the programme account can be prepared, and that field is optional: leave it empty and we pick it up during onboarding instead. If you would rather not use a form at all, an email works just as well.
The glossary is worth a look before a first conversation, mostly so that nobody spends ten minutes discovering that they were using the same word for two different things.