Restaurant ordering systems and myDATA: issuing through a ΥΠΑΗΕΣ provider, from the order note to the card
You built a system that takes the order. Now every customer asks about the receipt. Your system sends the order to the API and Wrapp does everything else automatically: which document each moment of a shift issues, how the card terminal connects, how you open an account for a new customer in minutes, and what it takes to go live.
Your ordering system takes the order at the table, sends it to the kitchen, keeps the bill open and produces reports. And then comes the question that shows up in every sale: "how do I issue the receipt?"
The answer is short: your system sends the order to the Wrapp API, and from there everything happens automatically. Below is what Wrapp takes care of, which document each moment of a shift issues, how you open an account for every new customer in minutes, and what it takes to go live.
What Wrapp does automatically
Wrapp is a licensed electronic invoicing provider (ΥΠΑΗΕΣ). Your system sends the items, the amounts and the payment method. Wrapp does everything else, with no step in between for you or your customer:
- Issues the document with its ΜΑΡΚ, QR code and issue time.
- Transmits it to myDATA in real time, and resends it on its own if ΑΑΔΕ does not respond.
- Delivers it to the guest, ready to print or by email.
- Sends the amount to the card terminal and completes the receipt once the payment is approved.
- Files the provider declaration with ΑΑΔΕ for each of your customers.
Integrating with the REST API usually takes less than an hour, and then you test every flow on staging before going to production.
A shift, in documents
Every moment your system records maps to one document issued through the API. This is the map you need before writing the first line of code.
| Moment | Document | What your system sends |
|---|---|---|
| Order at the table | 8.6 Catering Order Note | One note per round, with the table |
| The guest pays the table | 11.1 Retail receipt | The order notes' ΜΑΡΚ and the table, then closing the table |
| Counter, take-away, delivery | 11.1 Retail receipt | Directly, with no order note |
| Card payment on the terminal | 11.1 Retail receipt | The terminal with the receipt, which takes its ΜΑΡΚ once the payment is approved |
| Card at the door or on pick-up | 11.1 Retail receipt | The receipt at once, with the charge waiting on the terminal |
| Cash and card on one bill | 11.1 and 8.4 POS Payment Receipt | The receipt for the full amount on credit, and the card part on a POS payment receipt |
| Refund to the card | 8.5 POS Refund Receipt or 11.4 | Depending on which document charged the card |
| Cancelling a receipt | 11.4 Retail credit note | Correlated to the original's ΜΑΡΚ |
| Wrong order note, or a guest who walked out | Cancelling the 8.6 | A new zero-value note on the same table |
| Treat on the house | Zero-value line or 6.1 | Which of the two is the business's accountant's call |
| Staff meal | 6.1 Self-supply document | On its own series, with the reason in the notes |
The complete JSON for every row of the table, ready to send, is in the JSON examples for restaurant ordering.
The order note is the part that costs most when discovered late: it has 24 hours to be correlated with the receipt that settles it, and nothing in the API tells you the correlation is missing. Its full lifecycle, with complete payloads, is in the guide to the Catering Order Note and the 24-hour rule.
Guides by topic
- Split payment and the card at the table: cash and card on one bill, a bill split across receipts.
- Refunds to the card: when one 11.4 is enough and when an 8.5 is needed.
- aade_preloaded: the receipt before the payment, for delivery, pick-up and the table.
- Treats, discounts and tips: and why a discount field raises no error.
- No internet or myDATA down: retrying with external_id and closing the day without a Z report.
The card at the table
Α.1155/2023 requires the card terminal to be interconnected with the system that issues the receipt. When issuing runs through the API, that means the terminal connects to Wrapp.
- One integration. You send the receipt with the terminal, Wrapp sends the amount to the terminal and transmits to myDATA. You never talk to the acquirer separately.
- Over the cloud. The transaction reaches the terminal server to server. Nothing is installed in the venue.
- The result arrives by webhook. The receipt takes its ΜΑΡΚ once the payment is approved, and a failure or cancellation on the terminal reaches you separately.
- A connected terminal from Wrapp Core up. Every plan is on the Wrapp plans page.
How each terminal connects to Wrapp is in the guides for Viva, Worldline Smart POS, epay and NBG Pay.
The receipt before the card: aade_preloaded
In the normal flow the receipt waits for approval on the terminal and takes its ΜΑΡΚ afterwards. But there are moments when the receipt has to exist before the guest pays:
- Delivery with the card at the door. The receipt leaves with the order and the driver charges the card on delivery.
- Payment on pick-up. The order is prepared with its receipt, and the guest pays when they collect it.
- The bill at the table. The receipt is printed and goes to the table together with the terminal.
That is what aade_preloaded is for, with its use cases in detail in the guide to aade_preloaded. You send the 11.1 with the terminal and "aade_preloaded": true:
- The receipt is issued at once, with its ΜΑΡΚ and the payment method "on credit", and the charge waits on the terminal.
- When the guest pays by card on that terminal, Wrapp switches the receipt's payment method to card, with a new payment ΜΑΡΚ. You read the card details with
GET /invoices/{id}, because no second webhook fires. - If they pay cash after all, you cancel the charge on the terminal and the receipt stays "on credit". Nothing else is needed: no credit note, no new receipt.
Cash register: replace it or keep it
Issuing through a provider is a legal alternative to a cash register, under article 12 §10 of law 4308/2014. Your customer can replace the cash register entirely, and that is what we recommend:
- Issuing from the cloud, with real-time transmission to myDATA.
- From the devices they already have, inside your system, with no second device at the till.
- No fiscal device to certify or service, and no Z report at the end of the day.
If they want to keep the cash register, they can: a business may lawfully declare more than one cash register system, so Wrapp also runs alongside it. What changes in neither case is the business's own standing with ΑΑΔΕ and the provider declaration.
What the integration involves
- A REST API for real-time issuing, with documentation and clear myDATA error codes.
- A staging environment to test every document type end to end before you go to production.
- Every document of the shift: the Catering Order Note (8.6), the retail receipt (11.1), the retail credit note (11.4), POS payment and refund receipts (8.4 and 8.5), self-supply (6.1), and invoices for catering and corporate orders.
- Partner Portal and Partners API to open an account for every new customer in minutes.
A new customer, ready in minutes
Every restaurant that signs with you needs its own Wrapp account. You open it, with one button in the Partner Portal or one call to the Partners API, and your customer has nothing to look for:
- The account opens at once and appears in your customer list.
- The customer's API key reaches your webhook at the same moment, so your system is ready to issue for them.
- The customer gets an email with a link to finish setting up their account.
- Wrapp files the provider declaration with ΑΑΔΕ, through myAADE. The customer is notified by e-notification and email, and if they do not respond within 10 days the declaration is presumed accepted.
No paperwork, no appointment, no trip to the accountant to get started. How to create your partner and invite customers, step by step, is in the guide to the Wrapp Partner Portal, and who files the declaration in the guide to the provider declaration.
The timing window
From 2 November 2026 e-invoicing is mandatory for the B2B documents of all businesses, with a transitional period until 31/1/2027 that is conditional on a declaration filed on time. For your customers it covers invoices to businesses: catering, events, corporate accounts. It is the question they will ask now, not at some point. The full timeline and the penalties are in the guide to 2 November 2026.
From staging to production
- Test account. Sign up free at wrapp.ai with your VAT number and press "Try the API". You get a login email and an API key for staging.wrapp.ai, with the billing books already set up.
- Build your flows on staging, one for each moment in the table above. For cards, connect a Viva demo terminal: staging sees demo terminals only.
- Activate a plan on the production account. For a connected terminal, Wrapp Core or above.
- Take the production API key from "API details" on wrapp.ai and switch the base URL from staging.wrapp.ai to wrapp.ai.
- Create the production billing books, one for each type you issue. Staging books do not carry over.
- Register the real terminals on the production account, with their Merchant ID and Terminal ID.
- Set the webhook on the production account.
- Check the first live document: ΜΑΡΚ and print.
The same picture from your customer's side
What connected operation actually means for a hospitality business, from order taking through to the tax document, is described from the owner's point of view in the article on restaurant digitisation. Useful as material for your own sales conversations too: those are the questions your customer will ask you.
How to start
Sign up free at wrapp.ai with your VAT number and open the test account yourself: it gives you a login email and an API key for staging.wrapp.ai, with billing books already set up. Where to find the key, depending on where you are in your account, is in the guide to your test API key. Once your flows work, create your partner and invite your first customer.
Frequently asked questions
What does Wrapp do, and what does my system do?
Your system sends the items, the amounts and the payment method to the API. Wrapp, as a licensed ΥΠΑΗΕΣ provider, does everything else automatically: it issues the document with its ΜΑΡΚ and QR code, transmits it to myDATA in real time and resends it on its own if ΑΑΔΕ does not respond, delivers it to the guest for printing or by email, sends the amount to the card terminal, and files the provider declaration for each of your customers.
Which documents does a restaurant ordering system need?
The Catering Order Note (8.6) for every round at the table, the retail receipt (11.1) that settles it or that is issued directly at the counter and for take-away, the retail credit note (11.4), POS payment and refund receipts (8.4 and 8.5) for mixed payments and refunds to the card, and the self-supply document (6.1). The same API also issues invoices for catering and corporate orders, and every other myDATA type.
How long does the integration take?
Integrating with the REST API is usually completed in less than an hour, with testing in a staging environment before going to production. The timeline depends less on the API and more on how many document types your customers issue.
What happens if an order note is never correlated with a receipt?
The order note has 24 hours from issue to be correlated with the document that settles it. Past that, article 9 of Α.1112/2025 obliges the provider to suspend authentication and transmission of all the business's documents until the open notes are settled. The API does not reject a receipt without a correlation, so the check belongs in your system. The list of open order notes is available from the API.
Does anything need installing in the venue for the card terminal?
No. Your system sends the receipt with the terminal to the API, and Wrapp sends the amount to the terminal over the cloud, server to server. No local app or bridge in the venue, and no separate connection to the acquirer. The receipt takes its ΜΑΡΚ once the payment is approved, and the result reaches you by webhook.
Can the receipt be issued before the guest pays by card?
Yes, with aade_preloaded. The 11.1 is issued at once with its ΜΑΡΚ and the payment method "on credit", and the charge waits on the terminal. When the guest pays by card, the payment method switches to card with a new payment ΜΑΡΚ. If they pay cash, you cancel the charge on the terminal and the receipt stays "on credit", with no credit note and no new receipt. It suits delivery with the card at the door, payment on pick-up, and a bill that goes printed to the table.
Who files the declaration with ΑΑΔΕ for my customers?
The provider does, through myAADE, within 10 days of the contract taking effect. The business is notified through myAADE e-notifications and by email and has 10 days to accept or reject it. If that deadline passes with no action, the declaration is presumed accepted. If the provider fails to file on time, the obligation passes to the business. In practice, it is paperwork you do not carry.
Is there a staging environment, and how do I get access?
What do I need to go live?
An active plan on the production account, the production API key from "API details" on wrapp.ai, one billing book for each type you issue (staging books do not carry over), the real terminals registered with their Merchant ID and Terminal ID, and the production webhook. Then check the first live document: ΜΑΡΚ and print.
My customers have cash registers. What changes for them?
Issuing through a provider is a legal alternative to a cash register, so your customer can replace it entirely, and that is what we recommend: issuing from the cloud with real-time transmission, from the devices they already have, with no fiscal device to service and no daily Z report. If they want to keep it, they can, because a business may lawfully declare more than one cash register system. In neither case do the business's obligations towards ΑΑΔΕ change.
How do my customers get an account?
Need help?
If you have a question about this topic or want to make sure everything is set up correctly, contact us and we will look at it together.