Skip to main content

Enforcement Export

Introduction

entervo infinite provides ticketless free-flow parking solutions. It supplies information that enables operators to enforce unpaid exit transactions. The enforcement process itself is carried out by a third-party enforcement agency/application. entervo acts solely as an enforcement data supplier. For this purpose, entervo infinite provides a file export interface, which is described in this document. The document contains:

  • General information about the interface
  • Explanations of the data contained in the exported files

The interface operates in automated mode: all unpaid customer transactions are collected and exported together in a single cyclic (nightly) export.

With each cyclic export, the following files are exported for each car park:

/Enforcement detailsEnforcement images
Enforcement file name20251110000000_CP9763070_enfo.zip20251110000000_CP9763070_pict.zip
Naming conventionYYYYMMDDHHMMSS_CARPARKID_Filetype.zipYYYYMMDDHHMMSS_CARPARKID_Filetype.zip

Within the ZIP file the following files are included per car park:

/Enforcement detailsEnforcement images
Enforcement file nameENFO-CP9763070-20251110000000.xml

c5c500c3-8231-41a2-874d-ca8d86fc479b_77adc2e4-b9e0-33b0-a1bf-94201ff94902_2025-21-10T11-20-12.8Z.jpg
c5c500c3-8231-41a2-874d-ca8d86fc479b_545eb93a-537d-3135-bc90-e7bd80b7ca50_2025-09-11T12-34-18.8Z.jpg
...

Naming conventionENFO-CARPARKID-YYYYMMDDHHMMSS.xmlSensor ID_BTID_Date/Time stamp

Enforcement File Interface

The export files are transfered via SFTP push from entervo infinite to the 3rd party enforcement agency/ application.


Supported Product Types

The enforcement interface supports the following type of product:

  • Short-term parker

Data Description

Each enforcement record consists of the following information:

  • General
  • Entry
  • Payment
  • Exit
important

Nested areas are not supported!


Structure of XML

The XML is described in the following chapters. The head of the XML file begins with:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

The whole body is enclosed in:

<parkingTransaction>                      
<transaction>
<generalData>
</generalData>
<entryData>
</entryData>
<paymentData>
</paymentData>
<exitData>
</exitData>
</transaction>
<transaction>
<generalData>
</generalData>
<entryData>
</entryData>
<paymentData>
</paymentData>
<exitData>
</exitData>
</transaction>
</parkingTransaction>

Every single parking transaction is enclosed in a transaction tag.


General Data

Example Request Body (XML)

<generalData>
<recordExportId>12345</recordExportID>
<exportDate>2025-11-10T00:00:00</exportDate>
<instanceID>CP9763070</instanceID>
<facilityID>FC3439563</facilityID>
<operatorID>premiumparking</operatorID>
<taxID>DE47113265</taxID>
<currency>EUR</currency>
</generalData>

Variables

VariableShort descriptionFormatPossible valuesRequired
recordExportIDUnique export ID per export recordMandatory
exportDateDate/timeISO 8601 format (e.g. YYYY-MM-DDThh:mm:ss)Mandatory
instanceIDConfigured car park IDstringe.g. CP9763070Mandatory
facilityIDConfigured facility IDstringe.g. FC3439563Mandatory
operatorIDConfigured Tenant namestringe.g. premiumparkingMandatory
taxIDTax or VAT ID of the operator (if configured in entervo; optional; country-specific)Optional
currencyentervo system configured currency (ISO 4217)stringe.g. EUR, GBP, NOKMandatory

Entry-specific Data

Example Request Body (XML)

<entryData>
<dateTime>2025-10-21T11:20:13</dateTime>
<device>lane-device-bi-directional-entry</device>
<epan>SC_0000000000000002981</epan>
<customerType>PP000075</customerType>
<companyID/>
<participantID/>
<lpnCountryID>DEU</lpnCountryID>
<lpnStateID/>
<lpnRegionID></lpnRegionID>
<lpnType>LICENSEPLATE</lpnType>
<lpnString>VEN2</lpnString>
<lpnStringSep/>
<image1>
<imageData/>
<imageFileName>c5c500c3-8231-41a2-874d-ca8d86fc479b_77adc2e4-b9e0-33b0-a1bf-94201ff94902_2025-21-10T11-20-12.8Z.jpg</imageFileName>
</image1>
<image2/>
<image3/>
<carType/>
<carColour>
<red/>
<green/>
<blue/>
</carColour>
</entryData>

Variables

VariableShort descriptionFormatPossible valuesRequired
dateTimeDate/timeISO 8601e.g. 2018-01-01T12:00:00Mandatory
deviceConfigured device namestringlane-device-bi-directional-entryMandatory
epanUnique cart IDstringe.g. SC_0000000000000002981Mandatory
customerTypeAssigned Product IDstringe.g. PP000075Mandatory
companyIDAssigned company ID of registered user stringe.g. C2024CxUd9H9Optional
participantIDAssigned consumer ID of registered user stringe.g. N2024BLlNrz4IOptional
lpnCountryIDCountry information provided by the LPR system; format may vary based on chosen LPR vendorstring
ISO 3166-1 ALPHA-3 format
e.g. DEU - Germany, NLD - NetherlandsMandatory
lpnStateIDState information in case provided by the LPR system, format may vary based on chosen LPR vendorstringSamples: Switzerland LPN "BE" (Bern) Austrian LPN "W" (Vienna)Optional
lpnRegionIDRegion information in case provided by the LPR system; format may vary based on chosen LPR vendorstringOptional
lpnTypeLPN type information in case provided by the LPR systemstringe.g. DIPLOMATIC, MILITARY, POLICE, etc.Optional
lpnStringComplete LPN string provided by LPR camera; normalized without separatorstringe.g. "MGSB1872"Mandatory
lpnStringSepLPN string with separatorsstringSamples:
LPR system provided fpr Germany MG_SB_1872,
LPR provided for Switzerland BE_124872
Optional
image1Full view image from LPR cameraimageTypeMandatory
image2Detailed view of number plateimageTypeMandatory
image3Full view from second camera in case the lane is equipped with two camerasimageTypeMandatory
imageDataNot supportedstring (Base64 decoded)Optional
imageFileNameFile name of license plate image providedstringe.g. c5c500c3-8231-41a2-874d-ca8d86fc479b_77adc2e4-b9e0-33b0-a1bf-94201ff94902_2025-21-10T11-20-12.8Z.jpg
Format: businessTransactionId_sensorId_datetime.jpg
Optional
carTypeIn case 3rd party LPR system provides car typestringe.g. CAR, BUS, CAR WITH TRAILER, MOTORCYCLE, etc.Optional
carColourTag for carColour
In case 3rd party provides car colour
Colour TypeOptional
redIntensity of red colourinteger0–255Optional
greenIntensity of green colourinteger0–255Optional
blueIntensity of blue colourinteger0–255Optional
tip

The content of the "image…" tags can be "(-)". This means that the tag is empty. This is the case if the picture is generated as file or if there is no picture of LPN stored in database.


Payment-specific Data

Example Request Body (XML)

<paymentData>
<paymentCount>0</paymentCount>
<dateTime>1970-01-01T00:00:00</dateTime>
<device>0</device>
<epan>SC_0000000000000002981</epan>
<amountGross>0</amountGross>
<amountNet>0</amountNet>
<vatAmount>0</vatAmount>
<vatAmount2>0</vatAmount2>
<paidTime>1970-01-01T00:00:00</paidTime>
</paymentData>
Multiples Payments

For each payment a <paymentData>...</paymentData> element is provided.

Variables


VariableShort descriptionFormatPossible valuesRequired
paymentCountSequential counter for payment transaction made by a customer; per payment a customer made during his stay one payment specific data blocknumber0-...Mandatory
dateTimeDate/time

dateTime
Format based on ISO 8601, e.g. YYYY-MM-DDThh:mm:ss

No payment: 1970-01-01T00:00:00Mandatory
device'location of payment';
Note: customer can do payment via several devices
stringNo payment: 0
Payment: Configured device name
Mandatory
epanUnique cart IDstringe.g. SC_00000000000000002981Mandatory
amountGrossAmount (gross value) paid by customernumberMandatory
amountNetAmount (net value) paid by customernumberMandatory
vatAmountVAT / TAX amountnumberMandatory
vatAmount2VAT / TAX amount, e.g. second TAX amount for CanadanumberOptional
paidTimePayment relevant time till when the paid ticket had been encoded to be paid.

dateTime
Format based on ISO 8601, e.g. YYYY-MM-DDThh:mm:ss

No payment: 1970-01-01T00:00:00Mandatory

tip

The content of the "image…" tags can be "(-)". This means that the tag is empty. This is the case if the picture is generated as file or if there is no picture of LPN stored in database.

Exit-specific Data

Example Request Body (XML)

<exitData>
<dateTime>2025-11-09T12:34:18</dateTime>
<device>exit-free-flow</device>
<epan>SC_0000000000000002981</epan>
<customerType>PP000075</customerType>
<companyID/>
<participantID/>
<lpnCountryID>DEU</lpnCountryID>
<lpnStateID/>
<lpnRegionID></lpnRegionID>
<lpnType>LICENSEPLATE</lpnType>
<lpnString>VEN2</lpnString>
<lpnStringSep/>
<image1>
<imageData/>
<imageFileName>c5c500c3-8231-41a2-874d-ca8d86fc479b_545eb93a-537d-3135-bc90-e7bd80b7ca50_2025-09-11T12-34-18.8Z.jpg</imageFileName>
</image1>
<image2/>
<image3/>
<amountGross>762</amountGross>
<amountNet>630</amountNet>
<vatAmount>132</vatAmount>
<vatAmount2>0</vatAmount2>
<carType/>
<carColour>
<red/>
<green/>
<blue/>
</carColour>
<nonPaidTimePeriod>1646045</nonPaidTimePeriod>
<commentCode/>
<commentText/>
</exitData>

Variables

VariableShort descriptionFormatPossible valuesRequired
dateTimeDate/timeISO 8601, e.g. YYYY-MM-DDThh:mm:sse.g. 2025-11-09T12:34:18Mandatory
deviceConfigured device namestringexit-free-flowMandatory
epanUnique card IDstringe.g. SC_0000000000000002981Mandatory
customerTypeAssigned Prduct IDstringe.g. PP000075Mandatory
companyIDAssigned company ID of registered userstringe.g. C2024CxUd9H9Optional
participantIDAssigned consumer ID of registered user stringe.g. N2024BLlNrz4IOptional
lpnCountryIDCountry information provided by the LPR system;
Format may vary based on chosen LPR vendor
string
ISO 3166-1 ALPHA-3 format
e.g. DEU-Germany, NLD-NetherlandsMandatory
lpnStateIDState information provided by the LPR system;
Format may vary based on chosen LPR vendor
stringe.g.
Switzerland LPN “BE” (Bern)
Austria LPN “W” (Vienna)
Optional
lpnRegionIDRegion information provided by the LPR system;
Format may vary based on chosen LPR vendor
stringOptional
lpnTypeLPN type information provided by the LPR systemstringe.g. DIPLOMATIC, MILITARY, POLICE, etc.Optional
lpnStringComplete LPN string provided by LPR camera; normalized without separatorstringe.g. for Germany “MGSB1872”Mandatory
lpnStringSepIn case the LPR system provides a LPN string with separators, first part of LPN stringstringSamples:
LPR system provides for Germany “MG_SB_1872”
LPR system provides for Switzerland “BE_124872”
Optional
image1Tag for image 1
Full view image provided by LPR camera
imageTypeMandatory
image2Tag for image 2
Detailed view of number plate
imageTypeMandatory
image3Tag for image 3
Full view image of second camera in case the lane is equipped with two cameras
imageTypeMandatory
imageData- Not supported -string (Base64 decoded)Optional
imageFileNameFile name of license plate image providedstring e.g. c5c500c3-8231-41a2-874d-ca8d86fc479b_545eb93a-537d-3135-bc90-e7bd80b7ca50_2025-09-11T12-34-18.8Z.jpg
Format: businessTransactionId_sensorId_datetime.jpg
Optional
amountGrossAmount (gross value) due;
Parking fee based on calculation that took place at the exit taking into account previous payment a customer potentially did before;
Amount that needs to be enforced
numberMandatory
amountNetAmount (net value) due,net amount to be enforcednumberMandatory
vatAmountVAT / TAX amount duenumberMandatory
vatAmount2Second TAX amount, e.g. second TAX amount for CanadanumberOptional
carTypeIn case 3rd party LPR system pprovides car typestringe.g. CAR, BUS, CAR WITH TRAILER, MOTORCYCLE, etc.Optional
carColourTag for carColour
In case 3rd party LPR system provides car type
ColourTypeOptional
redIntensity of red colourinteger0–255Optional
greenIntensity of green colourinteger0–255Optional
blueIntensity of blue colourinteger0–255Optional
nonPaidTimeperiodTime which had not been paid
Remark: GraceTime for non enforced time has to be separately defined in the grace time table in entervo (ID100)
For Transacions w/o any Payment calculation rule is: ExitTime-EntryTime-GraceEnforcement
For Transactions which have partial payment rule is: ExitTime-PaidTime
TIME in seconds
numberCalculation rules applyMandatory
commentCodeCode for special evaluations and messages between entervo and enforcementstringOptional
commentTextDefaultText for comment based on codestringOptional
Note

The content of the "image…" tags can be "(-)". This means that the tag is empty. This is the case if the picture is generate as file or if there is no pic-ture of LPN stored in database.

Example

XML file "ENFO-CP9763070-20251110000000.xml"

<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<parkingTransaction>
<transaction>
<generalData>
<recordExportID>19</recordExportID>
<exportDate>2025-12-08T09:32:35</exportDate>
<instanceID>CP5802558</instanceID>
<facilityID>FC5802558</facilityID>
<operatorID>premiumparking</operatorID>
<taxID/>
<currency>EUR</currency>
</generalData>
<entryData>
<dateTime>2025-10-21T11:20:13</dateTime>
<device>lane-device-bi-directional-entry</device>
<epan>SC_0000000000000002981</epan>
<customerType>PP000075</customerType>
<companyID/>
<participantID/>
<lpnCountryID>DEU</lpnCountryID>
<lpnStateID/>
<lpnRegionID></lpnRegionID>
<lpnType>LICENSEPLATE</lpnType>
<lpnString>VEN2</lpnString>
<lpnStringSep/>
<image1>
<imageData/>
<imageFileName>c5c500c3-8231-41a2-874d-ca8d86fc479b_77adc2e4-b9e0-33b0-a1bf-94201ff94902_2025-21-10T11-20-12.8Z.jpg</imageFileName>
</image1>
<image2/>
<image3/>
<carType/>
<carColour>
<red/>
<green/>
<blue/>
</carColour>
</entryData>
<paymentData>
<paymentCount>0</paymentCount>
<dateTime>1970-01-01T00:00:00</dateTime>
<device>0</device>
<epan>SC_0000000000000002981</epan>
<amountGross>0</amountGross>
<amountNet>0</amountNet>
<vatAmount>0</vatAmount>
<vatAmount2>0</vatAmount2>
<paidTime>1970-01-01T00:00:00</paidTime>
</paymentData>
<exitData>
<dateTime>2025-11-09T12:34:18</dateTime>
<device>exit-free-flow</device>
<epan>SC_0000000000000002981</epan>
<customerType>PP000075</customerType>
<companyID/>
<participantID/>
<lpnCountryID>DEU</lpnCountryID>
<lpnStateID/>
<lpnRegionID></lpnRegionID>
<lpnType>LICENSEPLATE</lpnType>
<lpnString>VEN2</lpnString>
<lpnStringSep/>
<image1>
<imageData/>
<imageFileName>c5c500c3-8231-41a2-874d-ca8d86fc479b_545eb93a-537d-3135-bc90-e7bd80b7ca50_2025-09-11T12-34-18.8Z.jpg</imageFileName>
</image1>
<image2/>
<image3/>
<amountGross>762</amountGross>
<amountNet>630</amountNet>
<vatAmount>132</vatAmount>
<vatAmount2>0</vatAmount2>
<carType/>
<carColour>
<red/>
<green/>
<blue/>
</carColour>
<nonPaidTimePeriod>1646045</nonPaidTimePeriod>
<commentCode/>
<commentText/>
</exitData>
</transaction>

</parkingTransaction>