☰

Greece — FAQ: Invoices & Cloud Terminal API


1) How can I issue a Sales Invoice (1.1) that is simultaneously a Delivery Note?

You can find it 1.1 here


2) In the Referenced Credit Note (5.1) I cannot understand from the sample file how to declare the MARK that I am referencing.

Every fiscal document created through Viva Fiscalisation receives a unique reference — the value you set in cbReceiptReference.

To create a Referenced Credit Note (5.1), you do not declare a MARK or any AADE-specific field. Instead, you simply point to the original document’s cbReceiptReference.

Example:

The original document (e.g., a Sales Invoice) has:

{
  "cbReceiptReference": "XYZ-123"
}

In the Credit Note (5.1) that references it, you include:

{
  "cbPreviousReceiptReference": "XYZ-123"
}

That’s all that is needed to correctly link the two documents.


3) ISV API — what role does it play in the payments flow?

The ISV API is strictly used for onboarding new merchants and is not related to payments. In the payment use-case we use the ISV credentials to call the Cloud Terminal REST API.

ISV Sale Request:
See the endpoint here.

Unreferenced Refund:
See the endpoint here.

The Sale Request accepts ISV credentials — inside ISVDetails you place the merchantID of the merchant under you in the field terminalMerchantID. The unreferenced refund does not accept ISV details for now, so the call is performed using the merchant’s credentials.


4) Cloud Terminal API & fiscalisationData

In the Cloud Terminal API we separate:

Everything related to taxation / documents / myDATA must be placed exclusively inside the fiscalisationData object.

Indicatively, inside fiscalisationData you will find:

If fiscalisationData, is missing or incorrect, the payment might succeed on the acquiring layer, but fiscalisation will fail.


5) Cloud Terminal — call flow(Search Devices, Actions, Sales Requests κ.λπ.)

Flow overview::
here

Step-by-step documentation::
here


6) Cash without POS usage — how is fiscalisation performed?

Exactly the same way as with card: in cbPayItems we use ftPayItemCase for cash, and the request still goes through the terminal (as middleware, without user interaction).

{
  "cbPayItems": [
    {
      "amount": 2300,
      "description": "cash",
      "position": 1,
      "currencyCode": "978",
      "moment": "2025-07-17T08:11:06Z",
      "ftPayItemCase": 5139205309155246081
    }
  ],
  "fiscalisationData": {
    "GR": {
      "MerchantVATID": "098000979",
      "Series": "A",
      "AA": 397717,
      "HashAlg": "sha256",
      "HashPayload": "098000979-A-397717-receiptreference1-2025-07-17T08:11:06Z-23.0"
    }
  }
}

7) Where do I find the “cashRegisterId” for a specific merchant?

This is not something the Viva provides. It is your own identifier for the cash register / ePOS / ERP, and you can put whatever you want as long as it makes sense in your system.


8) What is the interappCallback field?

This interface is for all-in-one devices where the ePOS/ECR/ERP app runs on the same Android (and soon iOS) device as the Viva Terminal app. The interappCallback tells the Viva app where to return after the payment and/or fiscalisation completes.


9) Is there a list of supported values for the unit field inside cbChargeItems?

We do not enforce strict validation on this field – it is essentially free text (“unit of measure”).


10) About isvDetails

In the basic scenario, you only care about terminalMerchantId:

terminalMerchantId → the merchant ID of the merchant under you (the ISV).

merchantId, merchantSourceCode → used only in multi-merchant scenarios.

Multi-merchant functionality means the same terminal can switch between different merchants and accept payments on behalf of third parties (e.g., a ticketing agency collecting for many companies).


11) In the sourceCode field, do I need to put the sourceCode defined in my ISV? Or is it optional?

It belongs to the merchant’s account and is not mandatory — only needed if the merchant has multiple wallets (sub-accounts) or wants to tag transactions with different groupings, where the source changes per transaction. But in most cases, the source is assigned to different locations, and usually each location has its own terminal.


12) How do I issue receipts for Order Slip (8.6) — separate or aggregated?

For order-slip type orders (8.6) there are two flows:

1) Immediate fiscal receipt per order (without 8.6)
When the customer pays at the moment of ordering (cash or card), you may issue a direct fiscal receipt, without creating an 8.6.

2) Issuing 8.6 per order & final document(s) at the end
For each order you issue an 8.6, and at the end: - you issue one or more final documents, - with line items from the original 8.6 entries, - and a reference to the respective 8.6. Payments can be made using one or multiple cards/cash.

Are separate receipts allowed for each individual? Yes. You can issue multiple final documents referencing the same 8.6, as long as the total amounts fully match the original order slips.

Example

By law:

To “split” the salad between 3 people, you send 3 line items each with amount / 3, because you cannot split one line item unless you represent it as multiple lines.


13) In documents 11.1 / 11.2, do I always receive Series and AA from the Viva API and my own values are ignored? And must each document type (e.g., 11.1 and 11.2) have a different Series, or is it enough that AA is unique within one Series?

No, it is not mandatory to always receive Series and AA from the Viva API – you may override them with your own values via ftReceiptCaseData. More details: here

Regarding Series:

AA must be unique within a specific Series.

The same Series can be reused for different document types (e.g., 11.1 and 11.2 do not need to have different Series).


14) In case of TRANSMISSION_FAILURE_1 or TRANSMISSION_FAILURE_2 during fiscalisation, will any of the above webhook events (especially the 1802 one) be triggered, or will no event be sent?

We do not send anything to webhooks at this moment, but it is coming soon.


15) Which endpoint and credentials should be used for performing a return/refund with fiscalisation?

Fiscal returns/refunds and refunds of their associated payments are supported through the Unreferenced refunds

Endpoint_Could

Endpoint_Local

Please note that unreferenced refunds are not supported through the ISV flow, therefore they must be executed using the merchant’s credentials. The Bearer token must be generated with the merchant’s client credentials, and the payload must not include any isvDetails object.

At this time, there is no alternative endpoint that supports fiscalisation of a return/refund with optional electronic payment refunds via the ISV credentials

16) Why is a cash return shown as a negative Cash pay item, while card returns use a “refund” flow (11.4 vs 5.1⁄5.2)?

This is expected behavior.

In short: Card returns = refund flow, Cash returns = negative cash amount (cash out).

17) Can I send a SALE with amount = 0 when I only want fiscalisation (0-value data)?

No. For the SALE request, the top-level amount must be greater than zero. If you send amount: 0, the request is rejected with: “Wrong request parameters: Amount value must be greater than zero”.

Important notes:
Even if you intend to send cbReceiptAmount = 0 (and line items with amount = 0) for fiscal data, the SALE endpoint still requires a positive payment amount.
For a valid SALE request, you should keep amounts consisten

- amount (top-level) > 0
- cbReceiptAmount = sum of cbChargeItems[].amount (and should match the paid amount)


18) Is it possible to send the invoice payload in myDATA format, or in something closer to myDATA?

Not at the moment, because our interface is designed to support fiscalisation across Europe through a single interface. Therefore, it is intentionally designed to be as abstracted as possible from local APIs such as myDATA.


19) Can we send AADE/myDATA classifications directly, or are they derived from ftChargeItemCase?

We have the mapping in place so that the classifications of our interface correspond to those of myDATA.

The API does not accept classifications directly from the myDATA spec — classifications are derived from the ftChargeItemCase.


20) Can I declare the customer’s branch/installation (AADE “counterpart”), or is it always sent as 0?

We create and maintain the branches on our side, and then we map each branch to either a Terminal ID (or multiple Terminal IDs) or a Merchant ID, based on what you provide.

If you already have a list, please send it to us in the following format:

21) Can we ignore receptionEmails / ftSignatureFormat / ftSignatureType in the printing?

Yes — you can ignore this. No printing is required.

{"caption":"receptionEmails","data":"receptionEmailsType","ftSignatureFormat":1,"ftSignatureType":5139205309155246096,"ftSignatureItemId":null}

22) Does cbReceiptMoment need to be in UTC (Z) and match HashPayload?

Yes — always send cbReceiptMoment as a UTC timestamp with the Z suffix (e.g. 2026-01-08T11:48:32Z).

The exact same UTC timestamp must also be used in the HashPayload. If cbReceiptMoment and the timestamp inside HashPayload don’t match exactly, the request will fail with a hash mismatch.


23) Do I need Gov.gr authorization and which AADE sales type checkboxes should I select?

To activate Viva Fiscal, the business owner must complete two mandatory steps:
Gov.gr provider authorization and AADE declaration of electronic invoicing.

Step 1 – Gov.gr Provider Authorization

The business owner must authorize Viva Fiscal through Gov.gr (myTAXISnet):

Step 2 – AADE Electronic Invoicing Declaration

In the AADE Bookkeeper application, select
Electronic issuance of documents via Provider (A.1112, Article 6) and configure:

Then: - Select VIVA WALLET S.A. – Viva Fiscal as the software provider. - Fill in the contract date and service start date.

Example:
For car repair shops that issue both B2B and B2C invoices, select
Wholesale and Retail (not the exclusive options).


24) How does Smart Checkout work and how can fiscalisation be automated?

As long as the merchant also has a Viva Terminal, it is possible to accept payments online via Smart Checkout and then automatically proceed with fiscalisation.

Once the payment is completed, the resulting payment’s transactionId can be retrieved (e.g. via webhook) and sent as a payItem in a fiscalisation request, either through the Cloud API or the Local API.

A sample fiscalisation request using a transactionId can be found here.

⚠️ Note: Smart Checkout fiscalisation is not yet natively supported as an out-of-the-box flow and requires implementation logic on the merchant side.


25) How can a store issue an extra receipt after a paid web order without cancelling the full order?

If a customer has already paid for a web order and later requests a product change (e.g. +€0.20), the full order does not need to be cancelled.

A product change should be handled as: - Refund via credit note (return of the original item) - Followed by a new sale on credit for the replacement item

Product changes are therefore treated as a refund and re-sale flow, not as a supplementary charge.

For unreferenced refunds (e.g. when the original transaction cannot be directly linked), see the following example:
Unreferenced refund (AADE 11.4)


  • 26) How should I represent multiple items in a sale with unit quantity and unit price?
  • 26) How should I represent multiple items in a sale with unit quantity and unit price?

    For example, if you have 2 bags of ice weighing 5 kg each, with a unit price of 1 EUR per kg:

    This allows you to correctly calculate the total for multiple items and properly report it in your fiscalisation object.


    27) Can I write free text in the cbPayItems description, or does the string need to follow specific rules?

    You can write free text in the cbPayItems description.

    If the payment or refund is made via bank transfer (for example, using code 0A Bank transfer (SEPA / web banking / professional account)), you do not need to provide the bank transaction details.


    28) Do returns (credit notes) affect the status of embedded delivery notes (e.g. in 1.1 / 11.1 invoices)?

    No. When issuing a credit note (e.g. type 5.1) for an invoice that includes an embedded delivery note (such as 1.1 or 11.1), the return is applied only to the invoice line items.

    The status of the embedded delivery note is not affected and remains unchanged (e.g. REGISTERED). It does not move to CANCELLED and does not participate in the delivery lifecycle for returns.

    This behavior is expected.


    30) How should I handle response signatures and global flags?

    When handling the signatures in the response, you must take into account the global flags (gggg) documented here.

    In particular, please pay attention to the 0020 flag (data contained in this signature object is not intended to be printed on the receipt). Signatures with this flag contain information such as the myDATA XML response payload, which is intended purely for your own record-keeping or debugging and does not constitute content to be printed on the receipt.

    Best Practices for Parsing Signatures: * Avoid Direct Indexing: Do not rely on simple iteration or direct indexing based on the position of the signature objects to find what you need. * Target Specific Signatures: Because signature collections are continuously enriched with new data, relying on fixed indexes means you risk retrieving the wrong data in the future compared to what you are receiving today. You should always target the specific signatures you need by checking their type.


    30) How should I handle prepayments (e.g., table bookings) before the final service?

    When a customer pays a deposit or prepayment (e.g., to reserve a table) but the final receipt will be issued several days later, you can follow one of these two standard workflows:

    Option 1: Partial Payment with Credit

    Option 2: Prepayment Receipt (Type 8.4)

    Best Practices: * Method 1 is ideal if the final price is fixed and known at the time of booking. * Method 2 is preferred in hospitality (restaurants/cafes) where the final consumption (total bill) is unknown until the customer finishes their visit.


    31) Who is responsible for implementing Dispatch Notes (Phase B)?

    The implementation of Dispatch Notes (Phase B) is the responsibility of the merchant’s ERP/POS system.

    Phase B introduces flows related to the management and tracking of goods deliveries (e.g., issuance and updates of delivery notes), which require business logic and operational handling beyond the scope of our services.

    As a result: * The ERP/POS system must handle the creation, management, and lifecycle of dispatch/delivery documents. * It must also support the necessary workflows for updating delivery statuses and transmitting the required data.


    32) How do I send withholding taxes, fees, stamp duty, other taxes and deductions (κρατήσεις)?

    Each charge beyond VAT is sent as an extra charge item in cbChargeItems:

    Amount and base

    The amount is sent to myDATA exactly as you give it (taxAmount). It is not recalculated or checked against a rate or a base, so your system calculates it on whatever base applies.

    Payment amount

    The pay items must equal the sum of all charge items, with the signs above. Otherwise the request is rejected with “The sum of the charge items must be equal to the sum of the pay items.” This sum is myDATA’s totalGrossValue, i.e. the amount actually payable:

    net + VAT − withholding + fees + stamp duty + other taxes − deductions

    Always send the full description

    A description that is not in the tables is rejected with “No withholding tax, fee, stamp duty, or other tax mapping found for description”. However, if there is no exact match, a description that contains a listed text (or is contained in one) is accepted, taking the first match in the order withholding → fees → stamp duty → other taxes. A short, generic text can therefore end up in the wrong category without any error. For example, Κρατήσεις is accepted and transmitted as withholding tax, category 16 (Σ.Α.Δ.Φ.). Always send the full text from the tables.

    Fees that are subject to VAT

    If a fee is itself subject to VAT (e.g. the plastic bag fee), use the VAT slot of its rate instead of 8, e.g. 0x47522000000000F3 for 24 %. It is then sent as a fee line with VAT (recType 2) instead of at document level.

    Deductions (κρατήσεις)

    Deductions (myDATA deductionsAmount) are not supported yet. Support is being added; this answer will be updated when it is available. Until then, do not send a deduction as a withholding description, otherwise myDATA will show it as a withholding tax.

    Registration fee for new vehicles (τέλος ταξινόμησης)

    myDATA (v2.0.2) has no dedicated category for it. It sits outside the VAT base, so send it as Λοιπά τέλη (fees, category 10) with a positive amount. Example 11.1: net 4,699.14 + VAT 1,127.79 + fee 273.07 = 6,100.00:

    {
        "ftReceiptCase": 5139205309155246081,
        "cbReceiptReference": "your-unique-reference",
        "cbReceiptMoment": "2026-11-10T05:30:59Z",
        "cbChargeItems": [
            {
                "Position": 1,
                "Quantity": 1,
                "Description": "ΜΟΤΟΣΙΚΛΕΤΑ YAMAHA XMAX 300 2026",
                "Amount": 5826.93,
                "VATRate": 24,
                "VATAmount": 1127.79,
                "ftChargeItemCase": 5139205309155246099
            },
            {
                "Position": 2,
                "Quantity": 1,
                "Description": "Λοιπά τέλη",
                "Amount": 273.07,
                "VATRate": 0,
                "ftChargeItemCase": 5139205309155246328
            }
        ],
        "cbPayItems": [
            {
                "Description": "Επί πιστώσει",
                "Amount": 6100.0,
                "ftPayItemCase": 5139205309155246089
            }
        ]
    }

    Example: withholding, stamp duty, other taxes and fees on one 1.1

    Net 1,000.00 + VAT 240.00 − 40.00 + 24.00 + 10.00 + 5.00 = 1,239.00:

    {
        "ftReceiptCase": 5139205309155250179,
        "cbReceiptReference": "your-unique-reference",
        "cbReceiptMoment": "2026-11-10T05:30:59Z",
        "cbCustomer": {
            "CustomerVATId": "123456789",
            "CustomerName": "Customer name",
            "CustomerStreet": "Street 1",
            "CustomerZip": "10000",
            "CustomerCity": "Athens",
            "CustomerCountry": "GR"
        },
        "cbChargeItems": [
            {
                "Position": 1,
                "Quantity": 1,
                "Description": "Ανταλλακτικά",
                "Amount": 1240.0,
                "VATRate": 24,
                "VATAmount": 240.0,
                "ftChargeItemCase": 5139205309155246099
            },
            {
                "Position": 2,
                "Quantity": 1,
                "Description": "Λοιπά Αγαθά 4%",
                "Amount": -40.0,
                "VATRate": 0,
                "ftChargeItemCase": 5139205309155246328
            },
            {
                "Position": 3,
                "Quantity": 1,
                "Description": "Συντελεστής 2,4 %",
                "Amount": 24.0,
                "VATRate": 0,
                "ftChargeItemCase": 5139205309155246328
            },
            {
                "Position": 4,
                "Quantity": 1,
                "Description": "Λοιποί Φόροι",
                "Amount": 10.0,
                "VATRate": 0,
                "ftChargeItemCase": 5139205309155246328
            },
            {
                "Position": 5,
                "Quantity": 1,
                "Description": "Λοιπά τέλη",
                "Amount": 5.0,
                "VATRate": 0,
                "ftChargeItemCase": 5139205309155246328
            }
        ],
        "cbPayItems": [
            {
                "Description": "Επί πιστώσει",
                "Amount": 1239.0,
                "ftPayItemCase": 5139205309155246089
            }
        ]
    }

    Supported descriptions

    Click a group to expand it.

    Withholding taxes (Παρακρατούμενοι φόροι), taxType 1 (negative amount)
    CategoryDescription to send (exact text)AADE rate
    1Περιπτ. β’- Τόκοι - 15%15%
    2Περιπτ. γ’ - Δικαιώματα - 20%20%
    3Περιπτ. δ’ - Αμοιβές Συμβουλών Διοίκησης - 20%20%
    4Περιπτ. δ’ - Τεχνικά Έργα - 3%3%
    5Υγρά καύσιμα και προϊόντα καπνοβιομηχανίας 1%1%
    6Λοιπά Αγαθά 4%4%
    7Παροχή Υπηρεσιών 8%8%
    8Προκαταβλητέος Φόρος Αρχιτεκτόνων και Μηχανικών επί Συμβατικών Αμοιβών, για Εκπόνηση Μελετών και Σχεδίων 4%4%
    9Προκαταβλητέος Φόρος Αρχιτεκτόνων και Μηχανικών επί Συμβατικών Αμοιβών, που αφορούν οποιασδήποτε άλλης φύσης έργα 10%10%
    10Προκαταβλητέος Φόρος στις Αμοιβές Δικηγόρων 15%15%
    11Παρακράτηση Φόρου Μισθωτών Υπηρεσιών παρ. 1 αρ. 15 ν. 4172⁄2013amount
    12Παρακράτηση Φόρου Μισθωτών Υπηρεσιών παρ. 2 αρ. 15 ν. 4172⁄2013 - Αξιωματικών Εμπορικού Ναυτικού15%
    13Παρακράτηση Φόρου Μισθωτών Υπηρεσιών παρ. 2 αρ. 15 ν. 4172⁄2013 - Κατώτερο Πλήρωμα Εμπορικού Ναυτικού10%
    14Παρακράτηση Ειδικής Εισφοράς Αλληλεγγύηςamount
    15Παρακράτηση Φόρου Αποζημίωσης λόγω Διακοπής Σχέσης Εργασίας παρ. 3 αρ. 15 ν. 4172⁄2013amount
    16Παρακρατήσεις συναλλαγών αλλοδαπής βάσει συμβάσεων αποφυγής διπλής φορολογίας (Σ.Α.Δ.Φ.)amount
    17Λοιπές Παρακρατήσεις Φόρουamount
    18Παρακράτηση Φόρου Μερίσματα περ.α παρ. 1 αρ. 64 ν. 4172⁄20135%

    Fees (Τέλη), taxType 2 (positive amount)
    CategoryDescription to send (exact text)AADE rate
    1Για μηνιαίο λογαριασμό μέχρι και 50 ευρώ 12%12%
    2Για μηνιαίο λογαριασμό από 50,01 μέχρι και 100 ευρώ 15%15%
    3Για μηνιαίο λογαριασμό από 100,01 μέχρι και 150 ευρώ 18%18%
    4Για μηνιαίο λογαριασμό από 150,01 ευρώ και άνω 20%20%
    5Τέλος καρτοκινητής επί της αξίας του χρόνου ομιλίας (12%)12%
    6Τέλος στη συνδρομητική τηλεόραση 10%10%
    7Τέλος συνδρομητών σταθερής τηλεφωνίας 5%5%
    8Περιβαλλοντικό Τέλος & πλαστικής σακούλας ν. 2339⁄2001 αρ. 6α 0,07 ευρώ ανά τεμάχιοamount
    9Εισφορά δακοκτονίας 2%2%
    10Λοιπά τέληamount
    11Τέλη Λοιπών Φόρωνamount
    12Εισφορά δακοκτονίαςamount
    13Για μηνιαίο λογαριασμό κάθε σύνδεσης (10%)10%
    14Τέλος καρτοκινητής επί της αξίας του χρόνου ομιλίας (10%)10%
    15Τέλος κινητής και καρτοκινητής για φυσικά πρόσωπα ηλικίας 15 έως και 29 ετών (0%)0%
    16Εισφορά προστασίας περιβάλλοντος πλαστικών προϊόντων 0,04 λεπτά ανά τεμάχιο [άρθρο 4 ν. 4736⁄2020]amount
    17Τέλος ανακύκλωσης 0,08 λεπτά ανά τεμάχιο [άρθρο 80 ν. 4819⁄2021]amount
    18Τέλος διαμονής παρεπιδημούντωνamount
    19Τέλος επί των ακαθάριστων εσόδων των εστιατορίων και συναφών καταστημάτωνamount
    20Τέλος επί των ακαθάριστων εσόδων των κέντρων διασκέδασηςamount
    21Τέλος επί των ακαθάριστων εσόδων των καζίνοamount
    22Λοιπά τέλη επί των ακαθάριστων εσόδωνamount

    Stamp duty (Ψηφιακό Τέλος συναλλαγής), taxType 4 (positive amount)
    CategoryDescription to send (exact text)AADE rate
    1Συντελεστής 1,2 %1,2%
    2Συντελεστής 2,4 %2,4%
    3Συντελεστής 3,6 %3,6%
    4Λοιπές περιπτώσεις Χαρτοσήμουamount

    Other taxes (Λοιποί Φόροι), taxType 3 (positive amount)
    CategoryDescription to send (exact text)AADE rate
    1α1) ασφάλιστρα κλάδου πυρός 20%15%
    2α2) ασφάλιστρα κλάδου πυρός 20%5%
    3β) ασφάλιστρα κλάδου ζωής 4%4%
    4γ) ασφάλιστρα λοιπών κλάδων 15%15%
    5δ) απαλλασσόμενα φόρου ασφαλίστρων 0%0%
    6Ξενοδοχεία 1-2 αστέρων 0,50 €amount
    7Ξενοδοχεία 3 αστέρων 1,50 €amount
    8Ξενοδοχεία 4 αστέρων 3,00 €amount
    9Ξενοδοχεία 4 αστέρων 4,00 €amount
    9Ξενοδοχεία 5 αστέρων 4,00 €amount
    10Ενοικιαζόμενα - επιπλωμένα δωμάτια - διαμερίσματα 0,50 €amount
    11Ειδικός Φόρος στις διαφημίσεις που προβάλλονται από την τηλεόραση (ΕΦΤΔ) 5%5%
    123.1 Φόρος πολυτελείας 10% επί της φορολογητέας αξίας για τα ενδοκοινοτικώς αποκτούμενα και εισαγόμενα από τρίτες χώρες 10%10%
    133.2 Φόρος πολυτελείας 10% επί της τιμής πώλησης προ Φ.Π.Α. για τα εγχωρίως παραγόμενα είδη 10%10%
    14Δικαίωμα του Δημοσίου στα εισιτήρια των καζίνο (80% επί του εισιτηρίου)80%
    15ασφάλιστρα κλάδου πυρός 20%20%
    16Λοιποί Τελωνειακοί Δασμοί-Φόροιamount
    17Λοιποί Φόροιamount
    18Επιβαρύνσεις Λοιπών Φόρωνamount
    19ΕΦΚamount
    20Ξενοδοχεία 1-2 αστέρων 1,50€ (ανά Δωμ./Διαμ.)amount
    21Ξενοδοχεία 3 αστέρων 3,00€ (ανά Δωμ./Διαμ.)amount
    22Ξενοδοχεία 4 αστέρων 7,00€ (ανά Δωμ./Διαμ.)amount
    23Ξενοδοχεία 5 αστέρων 10,00€ (ανά Δωμ./Διαμ.)amount
    24Ενοικιαζόμενα επιπλωμένα δωμάτια – διαμερίσματα 1,50€ (ανά Δωμ./Διαμ.)amount
    25Ακίνητα βραχυχρόνιας μίσθωσης 1,50€amount
    26Ακίνητα βραχυχρόνιας μίσθωσης μονοκατοικίες άνω των 80 τ.μ. 10,00€amount
    27Αυτοεξυπηρετούμενα καταλύματα – τουριστικές επιπλωμένες επαύλεις (βίλες) 10,00€amount
    28Ακίνητα βραχυχρόνιας μίσθωσης 0,50€amount
    29Ακίνητα βραχυχρόνιας μίσθωσης μονοκατοικίες άνω των 80 τ.μ. 4,00€amount
    30Αυτοεξυπηρετούμενα καταλύματα – τουριστικές επιπλωμένες επαύλεις (βίλες) 4,00€amount