in English - Maksu- ja Tolliamet

Estonian Tax and Customs BoardElectronic Gambling Reporting System (EHMA) X-road services specification

Version: 1.02 Date: 12.12.2011Document HistoryDate Version Description Author20.06.2011 0.80 Initial document Estonian Tax andCustoms Board16.09.2011 0.90 Changes in the data structure of services1. EHMAOMA: .2. EHMAOML: , .3. EHMAKAM1: .4. EHMATUR1: .5. EHMATUR2: , , ,.6. EHMATUR3 .7. EHMATUR4: , , .8. EHMAOMT1: .9. EHMAOMT2: , .10. EHMAATM1: , , ,.11. EHMAATM2: , , ,, .12. EHMAMLR: , , .Estonian Tax andCustoms Board10.10.2011 1.00 Additions and clarifications1. Compression format changed to Gzip.2. Data fields "use start time" and "use end time" are added toEHMA registries.3. EHMAAUDIT: "service code" parameter is moved to input,service description clarified.4. Attachment rule changed - Content-Transfer-Encoding: binary.5. Added examples for some queries.6. Security class S2K1T2.7. Points 13, 14 and 15 are added to the chapter "Generalrequirements to the gambling operator’s EHMA IT solution".8. EHMAATM1 and EHMAMLR: added rule for ship-basedcasino addresses.9. EHMAKAM1: .10. EHMAKAM2: , .11. EHMAATM2: .12. EHMATUR1: , , , .13. EHMATUR2: , .14. EHMATUR3: .15. EHMATUR411.11.2011 1.01 1. Error in example is fixed.2. Some disparities between EST and ENG version of thedocument are removed. Some other minor clarifications.12.12.2011 1.02 1. EHMAOMT2 explanation is clarified.2. EHMAAUDIT input’s value TURR is removed.3. EHMAKAM2 explanation of data fields is clarified.4. Appendix 4 (The process of EAKS – EHMA integration).Estonian Tax andCustoms BoardEstonian Tax andCustoms BoardEstonian Tax andCustoms Board2

Version: 1.02 Date: 12.12.2011Table of ContentsIntroduction .................................................................................................................... 4EHMA services .............................................................................................................. 4Reference Documents .................................................................................................... 4General requirements to the gambling operator’s IT solution ....................................... 51. EHMAOMA ......................................................................................................... 62. EHMAOML ......................................................................................................... 73. EHMAKAM1 ....................................................................................................... 84. EHMAKAM2 ....................................................................................................... 95. EHMATUR1 ...................................................................................................... 106. EHMATUR2 ...................................................................................................... 117. EHMATUR3 ...................................................................................................... 128. EHMAOMT1 ..................................................................................................... 129. EHMAOMT2 ..................................................................................................... 1310. EHMAATM1 ..................................................................................................... 1411. EHMAATM2 ..................................................................................................... 1512. EHMAATM3 ..................................................................................................... 1613. EHMAMLR ........................................................................................................ 1614. EHMAAUDIT .................................................................................................... 17APPENDIX 1. Examples of XML queries .................................................................. 18APPENDIX 2. Testing of services with Estonian Tax and Customs Board ................ 20APPENDIX 3. The procedure for delivery of services ................................................ 21APPENDIX 4. The process of EAKS – EHMA integration ........................................ 223

Version: 1.02 Date: 12.12.2011IntroductionIn accordance with Gambling Act (HasMS § 58) gambling operator (hereinafteroperator) starting from 01.01.2012 is required to create a system that will allowEstonian Tax and Customs Board to make queries into the Electronic Record-keepingand Audit System (elektrooniline arvestus- ja kontrollisüsteem, EAKS).Estonian Tax and Customs Board’s (hereinafter ETCB) Electronic GamblingReporting System (elektrooniline hasartmängu aruandluse süsteem, EHMA) grantsan access to operator’s EAKS and allows to query gambling data through the use ofX-road data exchange services.Figure 1. General design of the EHMA system architecture.For each gambling operator a database shall be registered in The Management Systemof State Information System (Riigi infosüsteemi haldussüsteem, RIHA). Operator shallintroduce an IT solution which will allow ETCB to use X-road services described inthis document.The name of database shall be in the form of: ehma-regkood („regkood“ is a codeissued by Central Commercial Register or a non-resident code, for example: „ehma-12345678“).EHMA servicesEHMA services enable to perform queries into the EAKS database, therebyconnecting gambler operator’s system with ETCB system. EHMA services thatoperator is required to create depend on games that are actually organized or will beorganized in the near future by this organized.Reference Documents1. Gambling Act (Hasartmänguseadus, HasMS):www.riigiteataja.ee/akt/106012011011?leiaKehtiv2. HasMS regulation draft may be found at: http://eelnoud.valitsus.ee/3. EHMA services specifications and WSDL description 1 that is located on theETCB web page: www.emta.ee/index.php?id=30025.1 WSDL - Web Services Description Language (WSDL) 1.1 http://www.w3.org/TR/wsdl4

Version: 1.02 Date: 12.12.20114. Guide: EAKS registration in RIHA (in Estonian):http://ftp.ria.ee/pub/riha/EAKSi_kirjeldamine_juhend.pdfGeneral requirements to the gambling operator’s IT solution1. The format of the service name is EHMAservice_code,e.g., the name of service for remote gambling data is EHMAKAM1.2. System corresponds to ISKE (www.ria.ee/iske) security class S2K1T2. Operatoris responsible for security, availability 2 and integrity of IT solution.3. The currency is euro and all sums are in euro, fractional numbers are rounded aftertwo decimal numbers. If currency other than euro is used during gambling/betplacing then operator makes a currency conversion in accordance with theexchange rate provided by Bank of Estonia at the date of gambling.4. The format of date and time is "aaaa-kk-ppTtt:mm:ss+00:00" (aaaa-year, kkmonth,pp-day, tt-hour, mm-minute, ss-second). GMT+0:00 is used. The format ofdate is "aaaa-kk-pp".5. All entries in EAKS buffer database should contain information about whenoriginal entry has been created and in case of a later modification entry'smodification date. EAKS buffer database may be used only in case when it istechnically not feasible to allow direct queries to the primary database.6. Entity ID that is used in queries for EHMA registries should be the same as IDthat is used in EAKS internally. IDs are unique.7. Attachment Content-Transfer-Encoding should be of binary type.8. All data fields should be filled unless specified otherwise.9. All numbers are positive.10. The name of PDF document identifies document. Each name is unique, casesensitive, may contain (ISO/IEC 10646 basic Latin alphabet) symbols, numbersand '_'. Spaces are not permitted. The name of the document begins with the dateof file creation (YYYYDDMM) and contains operator's regkood (a code issued byCentral Commercial Register or a non-resident code) and a file name extension'.pdf'. Example: '20121224_12345678_… .pdf'.11. In case when service uses XML attachments it is necessary to compressattachment in GZIP format. Compression of PDF attachments is not required.Naming convention of compressed file is the same as described in p.10. Example:'20121224_12345678_… .gz'.12. In case of a EHMA registries data field 'use start time' is the time when gamblinghardware or software was connected to the EAKS network, data field 'use endtime' is the time when gambling hardware or software was disconnected from theEAKS network. A new database entry is created for each change.13. Ship name is an address of a ship-based casino.14. Estonian operator is a gambling operator that complies with Estonian GamblingAct (possesses Estonian operation permit).15. Gambler is a natural person who is participating in a gambling through the webpage or software of Estonian operator.2 Precise availability requirements are defined by the operator - ETCB Service Level Agreement.5

Version: 1.02 Date: 12.12.2011EHMA SERVICES GROUPSEHMA services are divided into groups in accordance with service’s designation:The summarized data about games played during a queried period:- Gambling machine games (EHMAOMA)- Gambling table games (EHMAOML)- Remote gambling (EHMAKAM1)- Tournament games of chance (EHMATUR1)- Tournament games of chance (EHMATUR3, ring games)- Additional game of chance (EHMAOMT1)The registry of gambling inventory:- The registry of gambling machines (EHMAATM1)- The registry of software used in gambling machines (EHMAATM2)- Document (EHMAATM3)- The registry of gambling tables (EHMAMLR)The detailed data about games played during a queried period:- Remote gambling funds transfers (EHMAKAM2)- Tournament games of chance (EHMATUR2)- Additional game of chance (EHMAOMT2)- Modified data (EHMAAUDIT)EHMA services description along with the data structure of input and output queriesis presented in chapters below.1. EHMAOMAThe service „Gambling machine games“ (EHMAOMA) enables to query gamblingmachines data summarized for the query’s input period.InputData field XML tag Data type CommentPerioodi alguse kuupäev /Start date of the period date Alates kasiinopäeva kellaajastaaaa-kk-ppT00:00:00+00:00Perioodi lõpu kuupäev /End date of the period date Kuni kasiinopäeva kellaajaniaaaa-kk-ppT23:59:59+00:00OutputData field XML tag Data type CommentAutomaadi ID /Slot ID stringvarchar2 (25)Identifikaator e. korraldaja pooltmänguinventarile määratudnumber.Mängitud mängude arv /Games playedAutomaati sisestatud summa /DropnonNegativeIntegernumber (10,0)decimalnumber (12,2)Mängitud mängude arv.Sisestatud raha või sedaasendavate vahendite (näiteksžetoonid, tšekid) kogusumma.Tehtud panuste summa /Coin indecimalnumber (12,2)Mängudes tehtud panuste (credits)kogusumma.Saadud võitude summa /Coin outdecimalnumber (12,2)Mängudes saadud võitudekogusumma.6

Version: 1.02 Date: 12.12.20112. EHMAOMLThe service „Gambling table games“ (EHMAOML) enables to query gambling tablesdata summarized for the query’s input period.InputData field XML tag Data type CommentPerioodi alguse kuupäev /Start date of the period date Alates kasiinopäeva kellaajastaaaa-kk-ppT00:00:00+00:00Perioodi lõpu kuupäev /End date of the period date Kuni kasiinopäeva kellaajaniaaaa-kk-ppT23:59:59+00:00OutputData field XML tag Data type CommentLaua ID / stringIdentifikaator e. korraldaja pooltGame table IDvarchar2 (25) mänguinventarile määratudŽetoonide algväärtus /Opening floatŽetoonide lõppväärtus /Closing floatŽetoonide suurenemine /FillŽetoonide vähenemine /CreditŽetoonide ostmine kliendi poolt /DropSaadud võitude netosumma /Net windecimalnumber (12,2)decimalnumber (12,2)decimalnumber (12,2)decimalnumber (12,2)decimalnumber (12,2)decimalnumber (12,2)number. 3Mängulaual kasutamiseks olevatežetoonide väärtus mängukohaavamisel (opening float).Mängulaual kasutamiseks olevatežetoonide väärtus mängukohasulgemisel (closing float).Mängulaua andmed žetoonidekoguväärtuse suurendamise kohtamängukoha lahtiolekuaja jooksulkassas (fill).Mängulaua andmed žetoonidekoguväärtuse vähendamise kohtamängukoha lahtiolekuaja jooksulkassas (credit).Mängulaual sularahas võisularahata žetoonide ostukoondsumma (drop).Mängulaua mängudes saadudvõitude netosumma.3 The data of all gambling tables located at some address is considered as the data of a single entity incase when casino chips are being exchanged in a centralized manner at the single cash register or atable. The identifier of this cash register or a table shall contain information about it's physical locationor address.7

Version: 1.02 Date: 12.12.20113. EHMAKAM1The service “Remote gambling” (EHMAKAM1) enables to query “versus the house”remote gambling games data. The result of the query is the summary of the inputperiod grouped by the game type. Additional games of chance are not part of thisservice.InputData field XML tag Data type CommentPerioodi alguse kuupäev /Start date of the period date Alates kasiinopäeva kellaajastaaaa-kk-ppT00:00:00+00:00Perioodi lõpu kuupäev /End date of the period date Kuni kasiinopäeva kellaajaniaaaa-kk-ppT23:59:59+00:00OutputData field XML tag Data type CommentLiik ja nimetus /Gaming class and type stringvarchar2 (10)Hasartmängu klassifikatsioon:1) KOMATM - õnnemängmänguautomaadil;2) KOMLAU - õnnemängmängulaual;3) KOMLOT - õnnemäng loterii;4) KTOKIV - toto kihlvedu;5) KTOTOS - toto totalisaator;6) KOSOVM - osavusmäng;7) KLOKLL - klassikaline loterii;8) KLOKRL - kiirloterii.Tehtud panuste summa /Total bets decimalnumber (12,2)Mängudes tehtud panuste(credits) kogusumma.Saadud võitude summa / decimalMängudes saadud võitudeTotal winsMängijate arv /Players numbernumber (12,2)nonNegativeIntegernumber (10,0)kogusumma.Mängijate arv.8

Version: 1.02 Date: 12.12.20114. EHMAKAM2The service “Remote gambling funds transfers” (EHMAKAM2) enables to query thedata for funds transfers that has taken place between operator and gambler during theinput period. The result is returned in the form of XML attachment and is sorted bydate and time. The result should contain only data of successfully completedtransactions.InputData field XML tag Data type CommentPerioodi alguse kuupäev /Start date of the period date Alates kasiinopäeva kellaajastaaaa-kk-ppT00:00:00+00:00Perioodi lõpu kuupäev /End date of the period date Kuni kasiinopäeva kellaajaniaaaa-kk-ppT23:59:59+00:00Output as zipped XML attachmentData field XML tag Data type CommentKorraldaja arveldusarvele rahaliste datetime Ülekande aeg.vahendite laekumise aeg /Deposit timeKorraldaja arvele kantud summa /Deposit amount decimalnumber (12,2)Mängija poolthasartmängukorraldajaMängija arveldusarvele korraldajapoolne ülekande teostamise aeg /Withdraw timeMängija arvele kantud summa /Withdraw amountarveldusarvele kantud summa. datetime Mängija taotlusel temaarveldusarvele tagasikantudülekande toimumise aeg.decimalnumber (12,2)Mängija taotlusel temaarveldusarvele tagasikantudsumma.9

Version: 1.02 Date: 12.12.20115. EHMATUR1The result of the “Tournament games of chance 1” (EHMATUR1) query is the datafor tournaments (player vs house) that were organized during query’s input period andsummarized for the said period.InputData field XML tag Data type CommentPerioodi alguse kuupäev /Start date of the period date Alates kasiinopäeva kellaajastaaaa-kk-ppT00:00:00+00:00Perioodi lõpu kuupäev /End date of the period date Kuni kasiinopäeva kellaajaniaaaa-kk-ppT23:59:59+00:00OutputData field XML tag Data type CommentOsalustasust võidufondi mineva osasumma / Amount deposited intopool decimalnumber (12,2)Eesti korraldaja mängijate käestkogutud kogusumma, mis lähebturniiri võidufondi.Osalustasust korraldajateenustasuks mineva osa summa /Total rakedecimalnumber (12,2)Eesti korraldaja mängijate panustealusel kogutud korraldajateenustasu summa.Väljamakstud summa /Total payoutsdecimalnumber (12,2)Eesti korraldaja mängijavõitudena väljamakstudkogusumma.10

Version: 1.02 Date: 12.12.20116. EHMATUR2The service “Tournament games of chance 2” (EHMATUR2) enables to query thedata for tournaments (player vs house) that ended during query’s input period. Thequery’s result is sorted by tournament end date, the output is provided as XMLattachment.InputData field XML tag Data type CommentPerioodi alguse kuupäev /Start date of the period date Alates kasiinopäeva kellaajastaaaa-kk-ppT00:00:00+00:00Perioodi lõpu kuupäev /End date of the period date Kuni kasiinopäeva kellaajaniaaaa-kk-ppT23:59:59+00:00Output as zipped XML attachmentData field XML tag Data type CommentTurniiri ID /Tournament ID stringvarchar2 (25)Õnnemänguturniiri identifikaatorkorraldaja IS-s nt. “236300C”.Turniiri nimetus / stringNimetus.Tournament namevarchar2 (250)Korraldamise viis /Form of organisation stringvarchar2 (3)Korraldamise viis:a) klassikaline (KLA),b) kaughasartmäng (KAM).Turniiri alguse aeg / datetime Alguse ja lõpu aeg.Tournament start timeTurniiri lõpu aeg / datetime Alguse ja lõpu aeg.Tournament end timeVõidu selgitamise koht /Tournament locationEesti korraldaja osavõtjate arv /Participants numberOsalustasust võidufondi minevaosa summa /Amount deposited into poolstringvarchar2 (250)nonNegativeIntegernumber (10,0)decimalnumber (12,2)Võidu selgitamise koht.KLA puhul füüsiline aadress,KAM puhul URL, mille kauduisik pääses mängima.Eesti korraldaja osavõtjate arv.Eesti korraldaja mängijate käestkogutud kogusumma, mis lähebturniiri võidufondi.Osalustasust korraldajateenustasuks mineva osa summa/ Total rakedecimalnumber (12,2)Eesti korraldaja mängijatepanuste alusel kogutudkorraldaja teenustasu summa.Võidufondi summa /PricepoolVäljamakstud summa /Total payoutsdecimalnumber (12,2)decimalnumber (12,2)Turniiri võidufondi kogusumma.Eesti korraldaja mängijatelevõitudena väljamakstud summa.11

Version: 1.02 Date: 12.12.20117. EHMATUR3The result of the “Tournament games of chance 3” (EHMATUR3) query is the datafor tournaments (player vs player ring game) that were organized during query’s inputperiod and summarized for the said period.InputData field XML tag Data type CommentPerioodi alguse kuupäev /Start date of the period date Alates kasiinopäeva kellaajastaaaa-kk-ppT00:00:00+00:00Perioodi lõpu kuupäev /End date of the period date Kuni kasiinopäeva kellaajaniaaaa-kk-ppT23:59:59+00:00OutputData field XML tag Data type CommentKorraldamise viis /Form of organisation stringvarchar2 (3)Õnnemänguturniiri korraldamiseviis:a) klassikaline (KLA),Tehtud panuste summa /Total betsdecimalnumber (12,2)b) kaughasartmäng (KAM).Kaughasartmängu (KAM) korral:Eesti korraldaja mängijate käestkogutud panuste bruto (panus +teenustasu) kogusumma.Osalustasust korraldajateenustasuks mineva osa summa /Total rakeVäljamakstud summa /Total payoutsdecimalnumber (12,2)decimalnumber (12,2)KLA korral on täitmata.Eesti korraldaja mängijate panustealusel kogutud korraldajateenustasu summa.Kaughasartmängu (KAM) korral:Eesti korraldaja mängijatelevõitudena väljamakstud summa.KLA korral on täitmata.8. EHMAOMT1The service “Additional game of chance 1” (EHMAOMT1) enables to queryadditional game of chance data summarized for the query’s input period.InputData field XML tag Data type CommentPerioodi alguse kuupäev /Start date of the period date Alates kasiinopäeva kellaajastaaaa-kk-ppT00:00:00+00:00Perioodi lõpu kuupäev /End date of the period date Kuni kasiinopäeva kellaajaniaaaa-kk-ppT23:59:59+00:00OutputData field XML tag Data type CommentVäljamakstud võidud / decimalTäiendavas õnnemängus saadudRaffle payoutsnumber (12,2) võitude kogusumma.12

Version: 1.02 Date: 12.12.20119. EHMAOMT2The service “Additional game of chance 2” (EHMAOMT2) enables to query the datafor additional games of chance that have been completed during the input period.Theresult is returned in the form of XML attachment and is sorted by the time and date ofthe winnings. Additional game of chance allows gambler to win two or more differentprizes simultaneously. It is possible that a pool for additional game of chance isgathered either from a single source (i.e. gambling machine) or multiple sources. Thedata for remote additional game of chance shall be gathered if a gambler of Estonianoperator has won a prize.InputData field XML tag Data type CommentPerioodi alguse kuupäev /Start date of the period date Alates kasiinopäeva kellaajastaaaa-kk-ppT00:00:00+00:00Perioodi lõpu kuupäev /End date of the period date Kuni kasiinopäeva kellaajaniaaaa-kk-ppT23:59:59+00:00Output as zipped XML attachmentData field XML tag Data type CommentTäiendava õnnemängu ID /Raffle ID stringvarchar2 (25)Täiendava õnnemänguidentifikaator korraldaja IS-s nt.“96312MY”.Täiendava õnnemängu nimetus / stringTäiendava õnnemängu nimetus.Name of rafflevarchar2 (250)Mängitud õnnemängu nimetus /Name of played game stringvarchar2 (250)Õnnemäng, mille mängiminetäiendava võidu kaasa tõi.Võidu selgumise aeg / datetime Täiendava õnnemängu võiduRaffle timeVäljamakstud võidud /Raffle payoutsdecimalnumber (12,2)selgitamise kuupäev ja kellaaegTäiendavas õnnemängus saadudvõitude kogusumma.13

Version: 1.02 Date: 12.12.201110. EHMAATM1The service “The registry of gambling machines” (EHMAATM1) enables to retrievethe list of gambling machines that were in use in operator’s casino halls during casinobusiness day specified by the input query.InputData field XML tag Data type CommentKasiinopäev / date Korraldaja poolt defineeritavCasino business daykasiinopäev.OutputData field XML tag Data type CommentAutomaadi ID / stringIdentifikaator.Slot IDvarchar2 (25)Automaadi seerianumber / stringSeerianumber.Slot serial numbervarchar2 (100)Automaadi mudeli number / stringMudeli number.Slot model numbervarchar2 (100)Automaadi valmistamise aeg / date Valmistamise aeg.Slot manufacture dateAutomaadi tootja / stringTootja nimi.Slot manufacturervarchar2 (100)Automaadi dokumendi PDF failinimi (ID) / stringvarchar2 (100)Mänguautomaadi kasutusõigusttõendava dokumendi ärakiri.Evidence of slot ownership PDFfile name (ID)Automaadi aadress 4 – linn / stringAsukoha aadress.Slot address-cityvarchar2 (100)Automaadi aadress – tänav /Slot address-street stringvarchar2 (100)Automaadi aadress – maja nr / stringSlot address-nouse numberKasutuse alguse aeg /Use start timeKasutuse lõpu aeg 5 /Use end timevarchar2 (100) datetime Kasutuse alguse kuupäev jakellaaeg.aaaa-kk-ppTtt:mm:ss+00:00 datetime Kasutuse lõpu kuupäev jakellaaeg.aaaa-kk-ppTtt:mm:ss+00:004 A ship's name shall be the address of a machine case when it is physically located on a ship-basedcasino. A ship's name is entered instead of a city; street and house number should be left empty.5 "Use end time" data field is not required if machine is still in use.14

Version: 1.02 Date: 12.12.201111. EHMAATM2The service “The registry of software used in gambling machines” (EHMAATM2)enables to retrieve the list of software that was in use in operator’s casino halls duringcasino business day specified by the input query.InputData field XML tag Data type CommentKasiinopäev / date Korraldaja poolt defineeritavCasino business daykasiinopäev.OutputData field XML tag Data type CommentMängu ID / stringIdentifikaator.Game IDvarchar2 (25)Mängu nimi /Game name stringvarchar2 (100)Mängu nimi, mis sisaldab katarkvara numbrit.Mängu versiooni number / stringVersiooni number.Game version / software numbervarchar2 (100)Mängu soetamise aeg 6 / date Mängu soetamise aeg.Game purchase dateMängu tootja / stringTootja nimi.Game manufacturervarchar2 (100)Vastavussertifikaadi number /Certificate of compliance number stringvarchar2 (100)Sõltumatu eksperdi hinnangunumber.Vastavussertifikaadi kuupäev /Certificate of compliance date date Sõltumatu eksperdi hinnanguväljastamise kuupäev.Sõltumatu eksperdi nimi / stringSõltumatu eksperdi nimi.Name of independent expertvarchar2 (100)Vastavussertifikaadi PDF faili nimi(ID) /Assessment of independent expertPDF file name (ID) stringvarchar2 (100)Sõltumatu eksperdihinnangu ärakiri.Mängu dokumendi PDF faili nimi(ID) /Evidence of game ownership PDFfile name (ID)Kasutuse alguse aeg /Use start timeKasutuse lõpu aeg 7 /Use end timestringvarchar2 (100)Kasutusõigust tõendavadokumendi ärakiri. datetime Kasutuse alguse kuupäev jakellaaeg.aaaa-kk-ppTtt:mm:ss+00:00 datetime Kasutuse lõpu kuupäev jakellaaeg.aaaa-kk-ppTtt:mm:ss+00:006 The data field was known as "Manufacture date" in the previous version of HasMS draft law.7 "Use end time" data field is not required if software is still in use.15

Version: 1.02 Date: 12.12.201112. EHMAATM3The service “Document” (EHMAATM3) by providing document name in input queryenables to retrieve said PDF document from “The registry of gambling machines” or“The registry of software used in gambling machines”.InputData field XML tag Data type CommentDokumendi PDF faili nimi (ID) /Document PDF file name (ID) stringvarchar2 (100)Dokumendi PDF faili nimi /identifikaator (;; )OutputData field XML tag Data type CommentDokument /Document MIME 8 Manusena edastatav fail võib ollamänguautomaadi soetamist võirentimist tõendava dokumendi ärakirivõi mängu dokument võivastavussertufikaat. Fail peab olemaPDF vormingus. Faili suurus ei tohiületada 10 MB, samas tuleb tagadadokumendi loetavus.Content-Type: application/pdfContent-Transfer-Encoding: binary13. EHMAMLRThe service “The registry of gambling tables” (EHMAMLR) enables to retrieve thelist of mechanical gambling tables that were in use in operator’s casino halls duringcasino business day specified by input query.InputData field XML tag Data type CommentKasiinopäev / date Korraldaja poolt defineeritavCasino Business Daykasiinopäev.OutputData field XML tag Data type CommentLaua ID / stringIdentifikaator.Game table IDvarchar2 (25)Laua aadress 9 – linn / stringMängulaua asukoha aadress.Game table address-Cityvarchar2 (100)Laua aadress – tänav /Game table address-Street stringvarchar2 (100)Laua aadress – maja nr /Game table address-House No stringvarchar2 (100)Kasutuse alguse aeg /Use start time datetime Kasutuse alguse kuupäev jakellaaeg.Kasutuse lõpu aeg 10 /Use end timeaaaa-kk-ppTtt:mm:ss+00:00 datetime Kasutuse lõpu kuupäev jakellaaeg.aaaa-kk-ppTtt:mm:ss+00:008 Multipart Internet Mail Extensions9 A ship's name shall be the address of a game table in case when it is physically located on a shipbasedcasino. A ship's name is entered instead of a city; street and house number should be left empty.10 "Use end time" data field is not required if game table is still in use.16

Version: 1.02 Date: 12.12.201114. EHMAAUDITThe service “Modified data” (EHMAAUDIT) enables to retrieve information aboutdata modifications that have taken place in EAKS buffer database after initial creationof the data. The input query parameters are period and service code.Operator may use EAKS buffer database in case when it is technically not feasible orrisky to allow a direct communication between EHMA and EAKS "in production"database. All entries in buffer database should contain information about whenoriginal entry has been created and in case of a later modification entry's modificationdate.InputData field XML tag Data type CommentPerioodi alguse kuupäev /Start date of the period Date Alates kasiinopäeva kellaajastaaaa-kk-ppT00:00:00+00:00Perioodi lõpu kuupäev /End date of the period Date Kuni kasiinopäeva kellaajaniaaaa-kk-ppT23:59:59+00:00Teenuse kood /Sevice code Stringvarchar2 (10)Teenuse kood viitab teenusele, mis kasutabEAKS puhvrit. Teenuste koodid on:OMA - “Mängud automaatidel”,OML - “Mängud laudadel”,TURT - “Õnnemänguturniirid”,OMT - “Täiendavad õnnemängud”,KAM - “Kaughasartmängud”.Output as zipped XML attachmentData field XML tag Data type CommentKasiinopäev / Date Korraldaja poolt defineeritav kasiinopäev.Casino Business DayObjekti ID /Object ID Stringvarchar2 (250)Andmed, mille järgi on võimalik objektiüheselt identifitseerida.1. TUR puhul ühe kaupa nende kirjete osasmida on muudetud, objekti ID on 2. OMA puhul ühe automaadi kaupa,objekti ID on 3. OML puhul ühe automaadi kaupa,objekti ID on 4. OMT puhul ühe mängu kaupa, objektiID on 5. KAM puhul objekti ID on Andmete loomise aeg / datetime Kuupäev ja kellaaeg.Created timeAndmete muutmise aeg /Modified timeaaaa-kk-ppTtt:mm:ss+00:00 datetime Kuupäev ja kellaaeg.aaaa-kk-ppTtt:mm:ss+00:0017

Version: 1.02 Date: 12.12.2011APPENDIX 1. Examples of XML queriesBelow are some examples of XML query inputs and outputs. 12345678 is a code ofservice provider, 33333333333 is a personal identification number (isikukood) of aperson who has performed a query.1. Example of EHMAOMA service query70000349ehma-1234567833333333333EE33333333333411d673578411773365ad8aa77210be07613daehma-12345678.EHMAOMA.v12011-09-012011-09-192. Example of EHMAOMA service outputThe output is located in SOAP body.70000349ehma-1234567833333333333EE33333333333411d673578411773365ad8aa77210be07613daehma-12345678.EHMAOMA.v12011-09-012011-09-191003124980.00239.002257.0010363114305.001190.00412.0010383424784.001041.00644.0010491323938.001527.002922.0010592389394.002678.004944.0010603374175.001190.002586.0010721972128.001596.002834.001083

Version: 1.02 Date: 12.12.2011xsi:type="xsd:nonNegativeInteger">7856450.001886.004455.002103006718436.002344.004368.003. Example of EHMAKAM2 service outputThe output is compressed XML attachment.--=_133927a23f0000013e74fabcb9cbbd24Content-Type: text/xml; charset=UTF-8Content-Transfer-Encoding: 8bit70000349ehma-1234567833333333333EE33333333333411d673578411773365ad8aa77210be07613daehma-12345678.EHMAKAM2.v1toimik1112011-11-012011-11-10171691--=_133927a23f0000013e74fabcb9cbbd24Content-Type: application/octet-streamContent-Disposition: attachment; filename="20111111_ehma-12345678_EHMAKAM2.xml.gz"Content-ID: Content-Transfer-Encoding: binary[...attatchment...]--=_133927a23f0000013e74fabcb9cbbd24--4. Example of EHMAATM3 service outputThe output is PDF attachment.--=_1339289663000001715a4c354fb7e3caContent-Type: text/xml; charset=UTF-8Content-Transfer-Encoding: 8bit70000349ehma-1234567833333333333EE33333333333411d673578411773365ad8aa77210be07613daehma-12345678.EHMAATM3.v1toimik111c1.pdfc1.pdf--=_1339289663000001715a4c354fb7e3caContent-Type: application/pdfContent-Disposition: attachment; filename="c1.pdf"Content-ID: Content-Transfer-Encoding: binary[...attatchment...]--=_1339289663000001715a4c354fb7e3ca--19

Version: 1.02 Date: 12.12.2011APPENDIX 2. Testing of services with Estonian Tax andCustoms Board1. Gambling operator submits an electronic free form application to ehma@emta.ee e-mail. Application shall contain the following information:a. Confirmation that operator has tested it’s system and that operator’sservices are opened to MTA (https://testmisp.mta/x/devmta/index.php).b. Period, when operator is ready to perform a bilateral testing sessionwith ETCB.c. The surname, the family name, the position, telephone and e-mail of aperson responsible for bilateral testing.d. The list of services to be tested.e. The initial data of EAKS that will be forwarded by the means of X-road services during a test session (as an attachment to e-mail, either as.csv or .xls).f. Any other information that might be relevant to the planned testing.2. ETCB electronically answers within five working days counting from the day ofapplication. ETCB marks in a reply a testing period of a bilateral testing taking intoaccount, if possible, a period that was marked in operator’s application.3. In case when serious defects in X-road services, EAKS or EAKS data are found(incl. X-road services, EAKS or data is not in accordance with specifications) and it isnot feasible to fix and re-test the system within the previously agreed testing period,then operator will need to submit a new testing application after defects are fixed.4. If tests concluded in test environment confirm that the data exchange betweenEAKS and EHMA is performed properly and stably then operator has a right tosubmit an application requesting an integration of EAKS and EHMA systems(application form is located at www.emta.ee, under “organization of gambling”column). Application shall be signed by a person with the right to represent gamblingoperator. Digitally signed application must be sent to ehma@emta.ee. Non-digitallysigned application shall be sent by post to: Maksu- ja Tolliamet, Narva mnt 9j, 15176Tallinn.20

Version: 1.02 Date: 12.12.2011APPENDIX 3. The procedure for delivery of servicestäiendatakse21

Version: 1.02 Date: 12.12.2011APPENDIX 4. The process of EAKS – EHMA integration22