WO2020095150A1

WO2020095150A1 - Payment notification and collection method and system, in particular for fines in violation of the rules of the road

Info

Publication number: WO2020095150A1
Application number: PCT/IB2019/059254
Authority: WO
Inventors: Antonino TYSSERAND
Original assignee: Paycity S.R.L.
Priority date: 2018-11-05
Filing date: 2019-10-29
Publication date: 2020-05-14
Also published as: EP3877931A1; IT201800010024A1

Abstract

Payment notification and collection method, in particular for fines in violation of the rules of the road, the method providing the following steps: registering the users, owning one or more vehicles univocally identified with at least one registration plate univocally associated with the owner thereof, with a management body of the collection activities, said management and collection body being in communication with the institution responsible for generating and issuing the fine notifications and being in communication with each of the registered users; said user or said vehicle being univocally associated with a navigator that tracks the routes done, the start and end times and the execution date and the navigator being provided with a communication unit to communicate with said management and collection body for tracking the route done; the method providing for detecting the vehicle for which the fine was issued and/or its owner; receiving or downloading the data of the route done from the navigator of the identified user or vehicle; comparing the route data with the data related to the place, date and time of the violation notification and checking correspondence with the data of the tracked route; initiating an error reporting and/or checking procedure if the comparison indicates non- compliance between the navigator data and the data of the violation notification upstream of the fine provision notification to the user.

Description

PAYCITY SRL

"Payment notification and collection method and system, in particular for fines in violation of the rules of the road"

TEXT OF THE DESCRIPTION

Object of the present invention is a payment notification and collection method and system, in particular for fines in violation of the rules of the road.

The present method and system for implementing thereof aim to reduce the notification times and costs and to facilitate and speed up the payments and other conciliation operations of the fines provided by the norms by exploiting the typical digital communication means of IT systems, such as emails or the like.

The present method provides for registering the users, owning one or more vehicles univocally identified with at least one registration plate univocally associated with the owner thereof, with a management body of the collection activities,

said management and collection body being in communication with the institution responsible for generating and issuing the fine notifications;

said management and collection body being in communication with each of the registered users;

said user or said vehicle being univocally associated with a navigator that tracks the routes done, the start and end times and the execution date;

said navigator being provided with a communication unit to communicate with said management and collection body for the transmission of the tracking data of the route done and indicated in the preceding step;

said method providing for detecting the vehicle for which the fine was issued and/or its owner;

scanning the user registration database to determine if the user or contact person of said vehicle is registered;

receiving or downloading the data of the route done from the navigator of the identified user or vehicle ;

comparing the route data with the data related to the place, date and time of the violation notification and checking correspondence with the data of the tracked route;

initiating an error reporting and/or checking procedure if the comparison indicates non-compliance between the navigator data and the data of the violation notification upstream of the fine provision notification to the user;

transmitting, through a digital communication such as an email for example, the fine provision to the address by means of the digital communication method the user is registered for;

receiving the payment in digital form from the user according to the digital payment methods provided and/or possible attachments of collateral payment activities related to the fine and/or payment receipts of the fine when carried out in a form different from the digital one;

transmitting the payment details and/or documents attached thereto to the fine provision issuing body;

the individual transmission and/or reception and/or transaction steps being recorded in digitally certified log files univocally associated with the users , bodies and personnel that executed said transactions and/or transmissions and/or receptions.

According to a first embodiment, the certifications occur by means of digital timestamps (time marks) associated with communication and/or transaction files.

Preferably the timestamps are extended up to a second.

In an embodiment, the timestamps are also provided for the log files.

Further forms of certification can be provided by Blockchains, such as digital signatures associated with the timestamps and/or registration of the most significant transaction steps for example.

A system according to the present invention comprises a transaction management processor comprising

At least one data storage to store a database registering the users and vehicles associated therewith, and the data for the notification and communication with said management processor;

at least one communication unit configured to receive and transmit information and messages from and to a processor provided at a fine provision issuing body;

at least one communication unit to communicate with the communication unit of each user, for example with a management processor of a digital email account of the user;

at least one communication unit to communicate with a navigator univocally associated with a user and/or vehicle in order to transmit the data related to the route tracked by the navigator, such as the data related to the places crossed on the route and/or to the start and/or end times and to the execution date of each route, for example;

the management processor comprising a recording unit to record the communication steps between the fine provision issuing body, the fine provision management and notification body and the registered users

the management processor comprising a communication unit to communicate with said navigators and an acquisition unit to acquire the data related to the user or vehicle univocally associated with the navigator and the data related to the routes done at the execution date thereof and to the start and/or end times of each route;

the processor further comprising or being associated with a comparator that compares the route data acquired from the navigator with the data related to the place, date and time at which the violation was notified with respect to a user or vehicle associated with said navigator;

and the management processor comprising a digital certification unit of the communications and transmitting and receiving subjects, as well as of the transmission and reception times and dates and of the log files wherein the flow of the aforesaid communication steps are recorded.

Still according to a further characteristic, the system provides a communication interface to communicate with a digital payment system of the fines . Thanks to the method and system according to the present invention, it is possible to register the vehicles, both owned or rented, that are used by the users, so that whenever a user should be fined, the fine that will arrive will not have:

• the management costs that are usually added to the initial amount of the fine by the rental and car sharing companies ;

• the notification costs, which are also added by the body sending the fine.

Moreover, the possibility of univocally registering, for each user and/or each vehicle, a navigator device that tracks the routes and associates the geographical data thereof with the data related to the execution times and date, allows to check if the violation notifications blamed to a vehicle or user, on the basis of a detected image and of plate recognition algorithms, are correct, thus avoiding errors due to wrong readings or interpretations of the data detected by the images or by the responsible personnel and intervening upstream of the notification provision. This allows to considerably save on challenges with respect to the correctness of the provisions and to the respective preliminary investigation and/or legal expenses, thus also making the system more user-friendly and correct for the users struck by provisions.

This way, the user will receive a fine with a much lower total amount, which is believed to push users to register to the portal.

Further characteristics of the invention are object of the dependent claims.

These and further characteristics and advantages of the present invention will become clearer in the following description of some exemplary embodiments depicted in the accompanying drawings, in which the figures show:

Figure 1 - State Machine

Figure 2 - Summary of the customer's fines

Figure 3 - Fine details

Figure 4 - popup for selecting the attachments to be inserted

Figure 5 - Inserting customer's data

Figure 6 - Initial generic operator control panel

Figure 7 - Initial operator control panel by city and period

Figure 8 - Flow monitor for the operator: in read only

Figure 9 - Operator info monitor

Figure 10 - Flow monitor for the operator: to be processed

Figure 11 - Fine to be processed by the operator

Figure 12 - List of the fines to be processed for the fleet service providers Figure 13 - Fine details to insert the data of transgressors for the fleet service providers

Figure 14 - a high-level block scheme of the system according to the present invention.

A preferred embodiment of the present invention is depicted in the figures. This embodiment provides different specific implementation choices which can be considered non-limiting with respect to the most general concepts to which they refer.

In specific, the players provided for the example of the system described below and shown in the figures consist of the following figures:

1. the company managing the notifications and collecting the payments and which has a management system to manage the fines in order to create the interface between two systems;

2. the Public Administration issuing the violation provisions, i.e. the fines;

3. the Citizens for which the fines are detected;

4. the Service Providers of large fleets (i.e. car rentals, private companies with car fleet, car sharing companies) ;

5. Companies with which to integrate the system in order to make the online payment.

The terms defined hereunder will be used in the following description:

• Customer = transgressor end user of the system according to the present invention;

• Operator = who operates in the fine management system for a city;

• Fine management system = system for supporting the management of fines.

Initial configuration of the system

A folder, in which the various messages sent from and to the township and the various emails sent to the customers or service providers of large fleets in pdf format will be saved in xml or txt format, will be created for each city and for each month. Each file will be named according to the sending/receiving timestamp up to one second; for emails, the timestamp will be completed by an *_E . * to show it is an email.

Moreover, the folder in which the system logs are to be inserted is indicated: it is in fact necessary to keep the logs of those who carried out all the various operations with the respective timestamp and detail .

Records

The following will be herein defined in a centralized way:

• the operators and the respective cities for which they are enabled;

• the service providers of large fleets with all the respective plates ;

• the articles of the C.d.S. (Rules of the Road) with the respective descriptions;

• the mapping of the information copy "City - Web Service address to invoke," so that the Web Service (WS) of the proper management system can be invoked according to the city to which the fine belongs ;

• all durations for the deadlines found in the rest of the document that have to be configurable. Such durations must also be diversified depending on whether dealing with car rentals (to which the law usually grants longer times) or other.

Other customers can also register to the service. According to an option, these are not managed at a centralized level, but each time a subject is inserted a record of the data thereof is recorded .

Receiving data from the fine management system

Downstream of the insertion of minutes in the fine management DB, a Web Service of the system, to which the information summarized in the following table will be provided, will be recalled:

At this point, the system that creates the item that is put in the "Received" status is created, just to show that the flow was properly received. Subsequently, an ACK is sent to the management system that sent it to communicate its proper reception.

An example of such ACK receipt is shown in the foilowing table :

Any picture sent to the system and which is transferred in an appropriate network share can also be managed. In fact, it is possible that the same management system or different management systems can use a same file name at different times, thus the system manages such files so that to avoid confusing conditions .

The Checksum field is used to univocally certify what was sent with the xml flow, such as no complaints can be made on the issue.

Checking the data on MF and customer communications

The item now passes in the "Data Check" and the system scans the user registrations DataBase to see if it already contains that plate:

• if it finds it and there is an associated email address, it sends an email containing some header information of the fine and the link to access the portal of the system itself to this address and puts the item in "Customer Communication"; • if it does not find it, it puts it in the "Completed" status.

The emails referring to persons whose data was provided by fleet Service Providers will contain the information that their data was provided by that Service Provider.

When in "Customer Communication," according to the normal procedure (thus excluding the re-heading and challenge) , it may happen that:

1. the customer pays and thus immediately passes in the "Completed" status;

2. the customer allows N days to go by (wherein N is configurable as previously shown) without paying, after which the system changes the status, by putting the item in "Completed" to restart the normal fine notification procedure in the source management system.

Before N days go by, a reminder must also be sent to the customer to remind him to pay the fine.

Once the payment has occurred, the pdf and receipt of payment are kept in the portal , in addition to being sent via email to the customer. This pdf must always be able to be consulted, also by the customer, by accessing the "Fine Summary" section .

Completed status

When an object changes to the "Completed" status, the system sends a communication to the management system and indicates various possibilities :

1. the flow of the management system can restart with the normal notification procedure because:

a. the plate was not found; b. the customer let N days go by since he received the communication from the MF;

c. the plate was found, but does not have any associated email address;

d. the fine was challenged, but the challenge was rejected by the operator.

2. the management system must not restart the procedure, but must close the file because:

a. the fine was paid;

b. the challenge was accepted by the operator.

Downstream of all these cases, the system no longer makes it possible to pay the fine from the portal .

Sending data to the fine management system

Whenever a fine changes to the "Completed" status, the Web Service of the management system from which the flow originated (data present in the Records) is recalled, by sending it the information listed in the following table:

The sending of the xml file from the system to the Web Service of the source management system will constitute the trigger that warns the management system to carry out the following activities:

• restarting the fine flow that was interrupted because it was put in standby status;

• blocking it.

Downstream of the reception of this information, the management system sends an ACK receipt signal to the system.

The figure 1 shows the workflow of the system described above through a representation thereof in the form of state machine.

The following figures 2 to 5 show some embodiments of the user interface, named customer control panel .

Customer control panel

After authentication via user name and password on the access portal, the customer will, in addition to modifying his data, also be able to carry out all the other operations specified below thanks to the interfaces described with reference to figures 2 to 5.

The Fine Summary interface in the figure shows a summary list of the fines of the user, ordered in decreasing order by taking the "Communication date" as reference.

It is possible to order the results in the fine summary table by clicking on the name of the column.

The fine detail will open by clicking on any row of the table.

Figure 3 shows an example of a screen related to the fine detail. The interface, in the form of a table, shows the "Transgressor" and "Violation Data" sections which cannot be modified by the customer, while the others, i.e. "Notes," "Challenge" and "Point deductions statement," can.

The customer must be able to insert notes (for example to notify that he does not consider the violation valid) . Each time this occurs, the symbol in the Notes column of the respective fine in Figure 2 will be shown and an email will be sent to the operator with the text of the message and the link to open that specific fine.

According to a further improvement not shown, the fine detail table can also provide information on the payments in a similar way as that provided for the fine themselves.

The following signals will be shown in the corresponding cases in the fine detail:

• If the payment was not made, a red light will appear and

o if within the N days from the notification, then the payment section will also be active;

o if beyond those, no action will be allowed;

• If payment was made, a green light will appear and the system will show the details of the payments carried out.

Challenge

It must be possible to challenge the fine in this step. Thus, the following steps and actions will be carried out by the system and/or user by opening the fine detail and by ticking the check box "Challenge" :

1. a popup will open with a message saying that he is making a self-certification in accordance with the law and there must be a checkbox at the bottom, not selected by default, to be ticked in order to accept what is reported and continue;

2. the user will write the reason for the challenge in the "Notes" field and, by clicking on the "Attachments" icon, a popup window will open with the list of all Documents inserted in the personal profile, thus to be able to select and attach them to the file (the possibility to insert further documents not present in the initial profile will be given, also directly from this window) . The popup interface of the respective attachments is shown in figure 4.

3. he will save the fine detail;

4. the operator will receive an email, with the challenge well-specified in the object and what is reported in the Notes field and the link to open that fine in the text;

5. the customer will receive an email with all the data referred to in the preceding point, but also with all the legal indications of what he has accepted in the popup referred to in point 1. ;

6. it passes to the "Operator Check" status.

When a document is inserted in one of these communications and an attempt to delete from the customer's control panel is made, the system will not allow the operation by warning that such document has already been attached to a communication, specifying which .

Re-heading

A fine re-heading procedure can be provided and according to an embodiment, the access to such procedure can only be granted to expressly authorized users, such as for example "Large fleet service providers" .

With reference to the specific point deductions procedures provided in some legislation, the system can provide a procedure for these activities.

The system can further provide an interface for the point deduction statement Module.

In case of fines containing articles that provide for point deductions (this information is given by the source management system) , the "Point deductions statement" function will be enabled in the detail of the fine, a checkbox that would not otherwise be able to be selected.

By ticking it, a new section with such writing will automatically open under this writing and allow to :

1. state who was driving by filling out the various fields and by then printing the pre-filled out module, which will be available here, signing and scanning it, and by adding any attachments (also beyond those inserted in the "Inserting customer's data" section)

The system provides to send both a summary email to the user (if possible a certified electronic mail) and an email (better a certified electronic mail, but need to understand how to proceed with foreign authorities such as in Spain) to the authority, saying that the self-certification was inserted for the point deductions, thus by reporting all the data inserted therein, including the attachments.

If the customer still does not have all the data of the new driver, he can however decide to pay the fine and, at that point, the times defined in the records in order to give him time to insert the data of the new customer start. In this case, the system can provide to generate and send at least one reminder ;

2. choose not to state who is driving. In this second case, there must be a page that warns the user of the future issuance of minutes against him. The system thus provides to communicate to the authority, i.e. the body that generated the fine, that the user has voluntarily decided not to state who was driving.

In this case, the customer cannot save the fine without first ticking the checkbox of this field. Once saved, the fine will pass to the "Operator check" status.

If the customer does not access the system, after a certain amount of time (set in a configuration file) , the fine automatically changes to the "Completed" status to be able to resume the normal procedure in the management system.

Still according to a further functionality, shown in figure 5, the system allows to insert and modify customer data.

Both citizens and rental companies will be able to, via an appropriate template, register their cars in the web portal of the system. This information is recorded in the Database for subsequent comparisons.

The registered users can store their documents, such as the driver's license, handicap pass... in the system so that, whenever needed for a communication, they are already in the system and can be more easily attached to the communication.

Before being able to insert data, each user that will register for the first time must accept, in a specific page that will appear, a Privacy approval module .

As can be seen in figure 5, customers can also register hourly plates, for the cars rented. When trying to register a plate belonging to the group of plates of the large fleets that are registered in the system, a warning popup, in which it will be specified to the customer that it will not be possible to register that plate because it is among the plates already registered in the database and thus associated, will open.

The following figures 6 to 13 show different screens of an interface example for the user operator, said interface being named operator control panel .

Figure 6 shows a first screen of the Operator control Panel .

A few interface screens, in which he can see the progress of all flows of the cities for which he is enabled, are available to the operator who interacts with the fine management system.

By inserting the city (if an operator is enabled for more cities) and the period of interest, a screen, such as the one of the example of figure 7, will open.

By clicking on any row of the table shown in the screen of figure 7, only the results in that status are shown. Thus, the screen will open like in Figure 8 with already set filters for the city and status selected; it will be possible to remove such filters via the drop-down menu in the top part of the screen, in order to see the records of all statuses. It will also be possible to order the results by clicking on the name of the column .

It will be possible to click on a row to open the fine detail (similarly to that shown in figure 3) , but only in read only mode, without thus being able to modify anything.

By clicking on of the Info column of the table in figure 8, a popup window containing all the communications concerning that fine, i.e. the xml of data exchanges with the WebServices and any email sent to the customer, will open, as shown in figure 9.

By clicking on any row of Figure 9, a popup window will open to display the file.

In the Notes column, whenever the symbol "..." is present, then it means that the customer has inserted notes (or general or in the challenge box) for that fine, which will be displayed both via the tooltip by going over it with the pointer and by entering the fine detail.

By instead clicking in the top row of Figure 6 or Figure 7, a screen such as in Figure 8 will open, but only with the fines in the "operator Check" status, in which the fines challenged and with point deductions that must still be processed by the operator are reported, as shown in figure 10.

Thus, by clicking on one of these fines, the detail thereof, in which buttons will appear to change the status, will open, as shown in figure 11.

The example of Figure 11 reports a Re-heading case .

The operator must thus consult the attachments and decide whether to Accept or Refuse the challenge via the buttons at the bottom of the page. Both in case of Acceptance and Refusal, an email must be sent to the customer with the reason in one way or another .

In particular:

• point deductions :

o if the operator accepts, the system will communicate to the new references of the transgressor to the management system, so that it can issue a new fine, vice-versa, if it refuses, the data inserted by the customer will not be transferred to the management system. In both cases, the fine changes to the "Completed" status;

• challenge:

o whether the operator accepts or refuses , the fine passes in the "Completed" status, but in one case, the system will communicate not to proceed with the procedure to the management system, while in the other, the procedure will be carried out and a fine will be sent to the customer.

An object will be removed from this list from the moment it will be processed by the operator and will thus change status.

A particular advantage is given by the present system in case of large fleet management.

Procedure related to the Service Providers of large fleets

Inserting the fleet's plates

The large fleets that will draw up an affiliation contract with the system by registering the vehicles they manage in the Database, will have to periodically provide the list of their plates, so that to allow the system to:

1. block the registration of these plates by customers (by hourly assignments) ;

2. address all the system communications (re heading, challenge...) to them.

The system provides a procedure for inserting data manually

From the moment a fine is sent by the management system of the supplier company, the system will first see if some customer has registered that plate for that time on his behalf in his DataBase, otherwise it must send a certified electronic mail (if the counterparty is in Italy) or simple email to the fleet service provider to communicate that there are some new plates for which information is required (changing to the "customer communication" status) . The link to a web page will be directly available in the email in order to connect to the portal of the system, wherein this third party can access, subject to inserting the user name and password, and only see its transport means for which information is required.

The list of the reports is found here, with the detail of the date-time-place of the violation of the cars for which it was consulted so that to be able to insert, for each of these, the data of the person who was using the vehicle at that time or generic notes.

Figure 12 shows an interface in which the fines to be processed and concerning the service providers of large fleets are listed. By clicking on any point of a row of the table of the interface mentioned above, a page, such as the one shown in figure 13, where the third party must insert the data, will open .

At the end of the day, all data inserted in the system by the third party will be summarized in an email (whenever possible via certified electronic mail) that will be sent, in addition to the TT and operator of the City defined in the records in Cc, to certify that which has been stated.

However, they may also want to directly pay some of these fines (because, for example, taken by their employees) instead of re-heading them and the same functionalities and screens shown above for other customers will be used to do this.

Still according to a further embodiment, the system allows to execute an automatic data retrieval procedure .

If the Service Provider of large fleets gives his consent, it is also possible to automatically access the DataBase of the company to automatically access all the information of the lessees/users. A support table with connection parameters and credentials for each service provider must be provided to do this.

A further functionality can be related to the search page for the history.

In this case, the system creates a page, such as that of Figure 8, containing all information on the fines made only to the plates managed by that Service Provider .

Here, it will be possible, with the fields in the upper part of the window, to also search through the entire history.

Still according to a further characteristic, the method and system have the technological advantage of allowing to cross-check the data related to the position of the driver of the vehicle with the data related to the recording of the minutes .

In fact, the fine detecting tools, usually provided with OCR software for the plate recognition, can record the plate incorrectly, thus sending a fine to the wrong recipient.

According to an advantageous embodiment of the present system and method according to which it operates, it is possible to avoid this inconvenient.

According to this embodiment, a driver of a vehicle provided with a portable processing device provided with a GPS position detector or satellite navigator can run an app thereon and thanks to which his trip is stored and such route is univocally associated to the date on which it was done. This way, since the violation detected has as base data a certain place, date and time, it is possible to warn both the issuing Authority and the driver that a plate reading error was certainly made since he was taking another route on that given date.

This certainly allows everyone to save time and money, also all the OCR errors that cannot be avoided by the tools currently available on the market are canceled.

The use of the phone's GPS is always authorized by the driver who can activate this function only on his own initiative. Instead, as far as privacy is concerned, we can ensure that no data will be registered in the system since the route exclusively remains on the user's device. This comparison is in fact carried out at the level of the app in the device. In fact, only the latter communicates to the central system that there could be a plate reading error without giving any information on the route effectively done by the vehicle.

Figure 14 shows a high-level block scheme of the system according to the present invention.

With regard to the embodiment of the system, this can be constituted by processing hardware, such as microcomputers, PCs, smartphones, tablets and the like, which execute software containing the instructions to configure the generic hardware so that to carry out the functions provided for the system, or the hardware is at least partly dedicated and stably configured to carry out given functions or the functionalities are fixedly implemented in the hardware configuration.

The system has a central processing unit 140 that executes managing software according to one or more of the embodiments and embodiment variants described previously. The central processing unit has several peripherals, which are not shown in detail and which comprise interfacing means for receiving and transmitting and for displaying and inputting information from and in the processor 140 and which can be provided in any combination or sub-combination between them and constituted by a unit or combinations of different units that carry out the communication, data input and data output functions.

The software executed in combination with said communication units generates access portals denoted by 141, 142 with different types of users such as for example private users 143, users constituted by fleet service providers 144 and institutional users 145, i.e. the users who provide to manage and emit the violation provisions, such as for example the fines, access the central processing unit 140 to carry out one or more of the activities described above.

A registration server, which can be constituted by the same processing unit 140 that executes dedicated software or by a separate unit that is connected to said processing unit, provides the functions of generating a registration database of users registered to the service, denoted by 146, thanks to a portal 147.

As explicitly set forth, the processing unit 140 comprises a transmitting unit to transmit the fines 149 to the users 143 and 144 that are registered in the database and a communication unit related to the payments, which is denoted by 150, and with which the processor transmits the payment information to the institutional user 145.

The information present in the database is the one essentially set forth in the description of the preceding functional example and which, in the most general form, provides the univocal association of a plate or other identification data of a vehicle or user, including the personal data thereof and at least one email address.

When, as denoted by 151, the vehicle or user are provided with a GPS navigator or other tracking system for tracking the position, also comprising a communication unit, for example wireless, such as access to wifi networks or to a telephone network, the system can comprise a communication unit 152 for communicating with said navigator or route tracking device, which allows a route data acquisition unit 153 to receive the route done by the vehicle or user and the corresponding date and time and to store it.

The acquisition unit, controlled by the processing unit 140, carries out a check by comparing any fine issued for the user and/or vehicle and notified on a certain date and at a certain time in a certain place with the route registered by the navigator, the execution time of the route and the date on which it was done in order to identify any recognition error of the vehicle's plates. If the information is compatible, the notification is confirmed and the fine is thus issued. However, if a non-compliance is detected between the data specified in the provision and the data acquired by the navigation or tracking unit, an error warning is issued.

It is also possible to provide a registration with the system by means of an identification code of navigators or route tracking units, said code being registered in the database by univocally associating it with a user and/or vehicle.

Thanks to this functionality, errors that generally lead to long and costly challenges of the fines issued are quickly and securely avoided.

Claims

1. Payment notification and collection method, in particular for fines in violation of the rules of the road, the method providing the following steps: registering the users, owning one or more vehicles univocally identified with at least one registration plate univocally associated with the owner thereof, with a management body of the collection activities,

said user or said vehicle being univocally associated with a navigator that tracks the routes done, the start and end times and the execution date; said navigator being provided with a communication unit to communicate with said management and collection body for the transmission of the tracking data of the route done and indicated in the preceding step;

the method providing for detecting the vehicle for which the fine was issued and/or its owner;

2. Method according to claim 1 , wherein the certifications occur by means of digital timestamps associated with communication and/or transaction files .

3. Method according to claim 2 , wherein the timestamps are extended up to the second.

4. Method according to one or more of the preceding claims, wherein the timestamps are also provided for the log files.

5. Method according to one or more of the preceding claims, wherein further forms of certifications can be provided by Blockchains, such as digital signatures associated with the timestamps and/or registration of the most significant transaction steps for example.

5. A payment notification and collection system, in particular for fines in violation of the rules of the road, for the execution of the method according to one or more of the preceding claims, which system comprises

a transaction management processor comprising at least one data storage to store a database registering the users and vehicles associated therewith, and the data for the notification and communication with said management processor;

6. System according to claim 5, wherein said system comprises a certification unit of at least some communication and/or transmission steps.

7. System according to claim 6, wherein the system comprises, in alternative or in combination, a certified timestamps generator and an association unit to associate said timestamps with communication files and/or a data files and/or a log files describing the communication and/or transaction activities and/or a Blockchain.

8. System according to one or more of preceding claims 5 to 7 characterized by comprising a communication interface to communicate with the digital payment system of the fines.