Description:FIELD OF DISCLOSURE
[0001] The present disclosure relates to automated cashless fare deduction for public transport systems. In particular, the present disclosure relates to a system for automated cashless fare deduction, in a contactless manner, in public transport systems.

BACKGROUND OF THE DISCLOSURE
[0002] The background description includes information that may be useful in understanding the present invention. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed invention, or that any publication specifically or implicitly referenced is prior art.
[0003] Online transactions and internet banking has played a major role for making the cashless transactions during the COVID-19 pandemic. The cashless financial transactions may reduce the spread of contagious diseases since it involves no direct contacts among humans. The cashless online payment system has been adopted almost in every sector; however the public transport such as public bus transport, roadways, etc. still lags cashless financial transaction facility. For example, a commuter/passenger, travelling by a bus or taxi, may be issued a ticket by an authorized person, such as conductor, against a fee/fare. The payment of bus fare is done through cash payment, which increases the risk of contagious diseases.
[0004] This lack of flexibility in payment options and manual issuing of a ticket may discourage a passenger from using the public transport system, especially during a time of pandemic or other contagious diseases as manual exchange may enhance risk of contamination. Moreover, passengers may be required to wait in long queues in order to carry out cash based transactions for purchasing the ticket, resulting in a loss of valuable time and effort.
[0005] Hence, there is a need in the art for an efficient, safe and flexible system that should be able to overcome aforementioned problems. The system should make it convenient for a passenger to purchase a ticket using a cashless transaction mechanism. The system should also be able to support a contact-less exchange to reduce the risk of contagious diseases.

OBJECTS OF THE INVENTION
[0006] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.
[0007] A general object of the present disclosure is to provide a cashless transport fare deduction system which obviates the above mentioned limitations.
[0008] It is an object of the present disclosure to provide a system and method to facilitate automated cashless transport fare deduction in a public transport system.
[0009] It is an object of the present disclosure to provide a system and method to enable cashless payment of transport fare to reduce the risk of contagious diseases by avoiding any direct/indirect contact among human beings.
[00010] It is an object of the present disclosure to provide an automated cashless transport fare deduction system for enhancing ease, safety and transparency of payments/transactions.

SUMMARY
[00011] The present disclosure pertains to a system for automated transaction for use in public transport. In particular, the present disclosure pertains to a system that allows a user to perform digital or cashless transactions such as purchasing a ticket for a ride.
[00012] This summary is provided to introduce simplified concepts of an automated transaction system including a card reader device, a database, and an output device. The card reader device (e.g., a payment card swipe/scan machine or any other scanning or reader machine, such as optical reader devices, and the like) may use a digital payment instrument (e.g., a credit card, a debit card or any other physical card which may be used as a cashless payment instrument) for executing a transaction (e.g., purchase of a ticket for a ride in a public transport) over a network (e.g., Internet). The card reader device may automatically read data stored in a memory of the digital payment instrument without having any physical contact with the digital payment instrument. In order to execute the transaction, the card reader device may transmit a portion of the read data along with any other information necessary for executing the transaction, to another computing device (e.g, a remote server or cloud) over the network. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended for use in determining/limiting the scope of the claimed subject matter.
[00013] This summary is provided to introduce simplified concepts of an automated transaction system. The automated transaction system may include a database associated with the card reader device. The database may be stored within a memory of the card reader device or a memory detachably coupled to the card reader device. The database may also be stored within a separate computing device such that the device may be physically or wirelessly connected to the card reader. The database may also be stored within a system-on-chip where the system-on-chip may be an internal or external component of the card reader device. The database may include one or more modules to dynamically determine a transaction value (e.g., ride fare and/or a combination of fare and other costs, such as transport tax or convenience charge) based on one or more factors or a combination of factors. One of the exemplary factors may be travel distance from a source to a destination. Another exemplary factor may be actual or expected travel time from a source to a destination. The transaction value may be provided to the card reader device for processing a transaction. The card reader device may send the transaction value along with any other necessary information, such as data fetched from a digital payment instrument, to an external device (e.g., a server) processing the transaction. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended for use in determining/limiting the scope of the claimed subject matter.
[00014] This summary is provided to introduce simplified concepts of an automated transaction system. The automated transaction system may include an output device (e.g., a display device or a printer) for outputting a copy of a ticket where the ticket may be a printed or a digital voucher that indicates entitlement or right to travel on a public transport. The ticket may also serve as proof of reservation. The ticket may be valid for any seat/berth or for a specific one. The output device may be associated with a card reader device, where the output device may be an internal or external component of the card reader device or the output device may be a standalone device detachably coupled to the card reader device. The output device may produce the ticket upon successful execution a transaction, where the output device may display the ticket, or the output device may print the ticket, or both. Further, the ticket may include various details such as information related to the transaction (e.g., transaction timestamp, approving authority, transaction gateway, transaction identifier(s), or any other information related to a financial authority or payment instrument involved in the transaction), information related to the transaction value (e.g., breakup of the ride fare including fee type and cost), travel distance, actual or expected travel time, source related details (e.g., ZIP/PIN code, city/street/stop name, and the like), destination related details (e.g., ZIP/PIN code, city/street/stop name, and the like), and details associated with the digital payment instrument (e.g., information printed on the payment instrument, information stored within a memory of the payment instrument, or any other information external to the payment instrument such as credentials or PIN). This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended for use in determining/limiting the scope of the claimed subject matter.
[00015] Within the scope of this application it is expressly envisaged that the various aspects, embodiments, examples and alternatives set out in the preceding paragraphs, in the claims and/or in the following description and drawings, and in particular the individual features thereof, may be taken independently or in any combination. Features described in connection with one embodiment are applicable to all embodiments, unless such features are incompatible.
[00016] Various objects, features, aspects and advantages of the present disclosure will become more apparent from the following detailed description of preferred embodiments, along with the accompanying drawing figures in which like numerals represent like features.

BRIEF DESCRIPTION OF DRAWINGS
[00017] The accompanying drawings are included to provide a further understanding of the present disclosure, and are incorporated in and constitute a part of this specification. The drawings illustrate exemplary embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure. The diagrams are for illustration only, which thus is not a limitation of the present disclosure, and wherein:
[00018] FIG. 1 illustrates overall architecture of the proposed system, in accordance with an exemplary embodiment of the present disclosure.
[00019] FIG. 2 illustrates various components of a card reader device in accordance with an exemplary embodiment of the present disclosure.

DETAILED DESCRIPTION
[00020] The following is a detailed description of embodiments of the disclosure depicted in the accompanying drawings. The embodiments are in such detail as to clearly communicate the disclosure. However, the amount of detail offered is not intended to limit the anticipated variations of embodiments; on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure as defined by the appended claims.
[00021] In the following description, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present invention. It will be apparent to one skilled in the art that embodiments of the present invention may be practiced without some of these specific details.
[00022] Embodiments of the present invention include various steps, which will be described below. The steps may be performed by hardware components or may be embodied in machine-executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps. Alternatively, steps may be performed by a combination of hardware, software, and firmware and/or by human operators.
[00023] Various methods described herein may be practiced by combining one or more machine-readable storage media containing the code according to the present invention with appropriate standard computer hardware to execute the code contained therein. An apparatus for practicing various embodiments of the present invention may involve one or more computers (or one or more processors within a single computer) and storage systems containing or having network access to computer program(s) coded in accordance with various methods described herein, and the method steps of the invention could be accomplished by modules, routines, subroutines, or subparts of a computer program product.
[00024] Exemplary embodiments will now be described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments are shown. These exemplary embodiments are provided only for illustrative purposes and so that this disclosure will be thorough and complete and will fully convey the scope of the invention to those of ordinary skill in the art. The invention disclosed may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Various modifications will be readily apparent to persons skilled in the art. The general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the invention. Moreover, all statements herein reciting embodiments of the invention, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future (i.e., any elements developed that perform the same function, regardless of structure). Also, the terminology and phraseology used is for the purpose of describing exemplary embodiments and should not be considered limiting. Thus, the present invention is to be accorded the widest scope encompassing numerous alternatives, modifications and equivalents consistent with the principles and features disclosed. For purpose of clarity, details relating to technical material that is known in the technical fields related to the invention have not been described in detail so as not to unnecessarily obscure the present invention.
[00025] Thus, for example, it will be appreciated by those of ordinary skill in the art that the diagrams, schematics, illustrations, and the like represent conceptual views or processes illustrating systems and methods embodying this invention. The functions of the various elements shown in the figures may be provided through the use of dedicated hardware as well as hardware capable of executing associated software. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the entity implementing this invention. Those of ordinary skill in the art further understand that the exemplary hardware, software, processes, methods, and/or operating systems described herein are for illustrative purposes and, thus, are not intended to be limited to any particular named element.
[00026] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth in the appended claims.
[00027] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, systems, networks, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known elements, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[00028] Embodiments of the present invention may be provided as a computer program product, which may include a machine-readable storage medium tangibly embodying thereon instructions, which may be used to program a computer (or other electronic devices) to perform a process. The term “machine-readable storage medium” or “computer-readable storage medium” includes, but is not limited to, fixed (hard) drives, magnetic tape, floppy diskettes, optical disks, compact disc read-only memories (CD-ROMs), and magneto-optical disks, semiconductor memories, such as ROMs, PROMs, random access memories (RAMs), programmable read-only memories (PROMs), erasable PROMs (EPROMs), electrically erasable PROMs (EEPROMs), flash memory, magnetic or optical cards, or other type of media/machine-readable medium suitable for storing electronic instructions (e.g., computer programming code, such as software or firmware).A machine-readable medium may include a non-transitory medium in which data can be stored and that does not include carrier waves and/or transitory electronic signals propagating wirelessly or over wired connections. Examples of a non-transitory medium may include, but are not limited to, a magnetic disk or tape, optical storage media such as compact disk (CD) or digital versatile disk (DVD), flash memory, memory or memory devices. A computer-program product may include code and/or machine-executable instructions that may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.
[00029] Furthermore, embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks (e.g., a computer-program product) may be stored in a machine-readable medium. A processor(s) may perform the necessary tasks.
[00030] Systems depicted in some of the figures may be provided in various configurations. In some embodiments, the systems may be configured as a distributed system where one or more components of the system are distributed across one or more networks in a cloud computing system.
[00031] Each of the appended claims defines a separate invention, which for infringement purposes is recognized as including equivalents to the various elements or limitations specified in the claims. Depending on the context, all references below to the "invention" may in some cases refer to certain specific embodiments only. In other cases it will be recognized that references to the "invention" will refer to subject matter recited in one or more, but not necessarily all, of the claims.
[00032] Various terms as used herein are shown below. To the extent a term used in a claim is not defined below, it should be given the broadest definition persons in the pertinent art have given that term as reflected in printed publications and issued patents at the time of filing.
[00033] In an aspect, present disclosure elaborates upon a system for automated transaction for use in public transport, the system includes a card reader device for using a physical card for executing a transaction over a network, wherein the card reader device may be configured to fetch data stored within the physical card without having any physical contact with the physical card, wherein said card reader device may transmit one or more data packets to a server over the network; a database, associated with the card reader device, configured to dynamically determine a transaction value based on any or a combination of distance from a source point to a destination point, and actual or expected time to reach a destination point from a source point, wherein the one or more data packets comprise a first set of data bits corresponding to said transaction value received by the card reader device from the database, and a second set of data bits corresponding to the data fetched by the card reader device from the physical card; and an output device, associated with the card reader device, for providing a ticket upon successful execution of the transaction, wherein the ticket comprises information corresponding to any or a combination of the transaction, the transaction value, the dynamically determined distance, the source point, the destination point, and the data fetched by the card reader device from the physical card.
[00034] In another aspect, the ticket may either a physical ticket or a virtual ticket (e.g., digital ticket).
[00035] In yet another aspect, the output device may be a printer device, a system-on-chip (SOC), a software module, an external device, an on-device display, or an external display device, or a combination thereof.
[00036] In an aspect, the network over which the transaction processing is performed may be Internet, Intranet, Public network, Private network, or a group of networks.
[00037] In another aspect, card reader device may include a set of actuable keys, one or more sensors (e.g., biometric sensor, magnetic sensor, optical/imaging sensor, proximity sensor, and the like) to fetch said data stored within said physical card, and a network hardware.
[00038] In yet another aspect, the set of actuable keys are used to provide one or more inputs to the card reader device, wherein said one or more inputs being any or a combination of the source point (e.g., source location, source coordinates, source city, source country, and the like), said destination point (e.g., destination location, destination coordinates, destination city, destination country, and the like), information associated with said physical card, and information related to a user.
[00039] In an aspect, the set of actuable keys are either a set of physical keys (e.g., physical keys/buttons) or a set of virtual keys (e.g., soft keys/buttons).
[00040] In an aspect, in order to fetch data stored within the physical card without having any physical contact or touch with the physical card requires the physical card to be in a close proximity (e.g., within a distance of 25-50 centimeters) of the card reader.
[00041] In another aspect, the network hardware may be capable of facilitating one or more of a radio frequency communication, cellular communication, infrared communication, near-field communication, or bluetooth communication.
[00042] In yet another aspect, card reader device may be configured to determine and display a route from the source point to the destination point using on a screen.
[00043] In another aspect, public transportation systems may include a variety of transit options (e.g., taxi, bus, rail, metro rail, subways, and the like).
[00044] In yet another aspect, an automated transaction system including a card reader device, a database, and an output device. The card reader device (e.g., a payment card swipe/scan machine, RFID-enabled reader, scanning machine, mobile/hand held device, point-of-sale device, and the like) may use a digital payment instrument (e.g., a credit card, a debit card, or any other physical or virtual card which may be used as a cashless payment instrument) for executing a transaction (e.g., purchase of a ticket for a ride in a public transport) over a network (e.g., Internet). The card reader device may automatically read data (e.g., credit or debit account details) stored in a memory of the digital payment instrument without having any physical contact (e.g., contactless transaction processing) with the digital payment instrument. In order to execute the transaction, the card reader device may transmit a portion of the read data along with any other information necessary for executing the transaction, to another computing device (e.g., a remote server, gateway or cloud) over the network.
[00045] In another aspect, an automated transaction system may include a database associated with the card reader device. The database may be stored within a memory of the card reader device or a memory detachably coupled to the card reader device. The database may also be stored within a separate computing device such that the device may be physically or wirelessly connected to the card reader. The database may also be stored within a system-on-chip where the system-on-chip may be an internal or external component of the card reader device. The database may also be a distributed database having one or more components where the one or more components may be distributed across various computing devices such that the computing devices may be operably connected to each other using a network (e.g., Internet). In an exemplary embodiment, the term “database” may mean a portion or a component of a database management system. In yet another exemplary embodiment, the term “database” may also mean a portion or a component of a file system. The database may include one or more modules (e.g., hardware, software, driver or firmware components) to dynamically determine a transaction value (e.g., ride fare and/or a combination of fare and other costs, such as transport tax or convenience charge) based on one or more factors or a combination of factors. The database may also include one or more modules to determine one or more routes from source to destination based on pre-stored route information. One of the exemplary factors may be travel distance from a source to a destination. Another exemplary factor may be actual or expected travel time from a source to a destination. The transaction value may be provided to the card reader device for processing a transaction. The card reader device may send the transaction value along with any other necessary information, such as data fetched from a digital payment instrument, to an external device (e.g., a merchant/bank server or gateway) for processing the transaction.
[00046] In another aspect, the automated transaction system may include an output device (e.g., a display device or a printer) for outputting a copy of a ticket where the ticket may be a printed or a digital voucher that indicates entitlement or right to travel on a public transport. The ticket may also serve as proof of reservation. The ticket may be valid for any seat/berth or for a specific one. The output device may be associated with a card reader device, where the output device may be an internal or external component of the card reader device or the output device may be a standalone device detachably coupled to the card reader device. The output device may produce the ticket upon successful execution a transaction, where the output device may display the ticket, or the output device may print the ticket, or both. Further, the ticket may include various details such as information related to the transaction (e.g., transaction timestamp, approving authority, transaction gateway, transaction identifier(s), or any other information related to a financial authority or payment instrument involved in the transaction, etc.), information related to the transaction value (e.g., breakup of the ride fare including fee type and cost), travel distance, actual or expected travel time, source related details (e.g., ZIP/PIN code, city/street/stop name, and the like), destination related details (e.g., ZIP/PIN code, city/street/stop name, and the like), and details associated with the digital payment instrument (e.g., information printed on the payment instrument, information stored within a memory of the payment instrument, or any other information external to the payment instrument such as credentials or PIN). The ticket may be pay-per-ride ticket, maximum number of rides per ticket, or unlimited ride ticket for a time period.
[00047] In an implementation aspect, customers may set-up and register pre-funded travel accounts, which are linked to the customer’s payment instrument. In practice, a customer may present, hover, or tap his card at the card reader device to gain access to the transit system. The card reader device may be a mobile device or mounted on another machine/terminal.
[00048] The proposed system 100 may be either a standalone system or integrated across several transit systems (e.g., taxis, subways, buses, railroads, etc.) and also may be integrated with other electronic payment solutions. The system 100 may also be configured to provide offers or discount to the customers based on various factors such as make/model of the card, travel history, user profile (e.g., age, gender, and the like), registration, etc.
[00049] In another aspect, the system 100 may associate a virtual ticket to the physical card such that the customer may show or present his physical card to a ticket inspector as a ticket. The ticket inspector may use the card, in a contactless manner, to obtain the details of the associated virtual ticket on his card reader device. Alternatively, upon successful contactless payment of the fare, a virtual copy of the ticket may be sent to the user online using various mediums such as email, short messaging service (sms), social media service, and the like. The user may also show the received virtual copy of the ticket on his device to the inspector for inspection.
[00050] Various objects, features, aspects and advantages of the present disclosure will become more apparent from the following detailed description of preferred embodiments, along with the accompanying drawing figures in which like numerals represent like features.
[00051] In an aspect, a card reader device may be an information input device for reading data from a physical payment instrument. The card reader device may also be an electronic device that can read plastic cards embedded with either a computer chip, barcode, magnetic strip or another storage structure. The card reader device may also be used for communicating with a physical card. The card reader device may further be used to scan, fetch (e.g., read), and/or save information stored within the physical payment instrument. After obtaining data from the physical payment instrument, the card reader may be configured to decode the obtained information. In an exemplary embodiment, information stored in the memory of the physical payment instrument may include account details (e.g., account number, issue date, instrument validity date, CVV, and the like), instrument holder information (e.g., user details such as holder name, date or birth, and the like), security related information, financial details, and/or authorization code(s). In another exemplary embodiment, information stored within the physical payment instrument may be contained either in a magnetic strip, or a microchip, or both, where the magnetic strip and/or the microchip may be embedded in the physical payment instrument.
[00052] FIG. 1 illustrates overall architecture of the proposed system, in accordance with an exemplary embodiment of the present disclosure.
[00053] As illustrated, proposed system 100 is an exemplary architecture and various components and structures as depicted herein may also be arranged in various other ways to achieve various described objectives. The system 100 depicts an exemplary architecture or arrangement in which all the components within 110 may be included in a single device or may be distributed across various devices. In another exemplary embodiment, all the components within 110 may depict functionality performed as client-side or local processing. In the same way, in another exemplary embodiment, all the components within 160 may depict functionality performed as server-side or remote processing.
[00054] In an exemplary embodiment, the proposed system 100 includes a card reader device 130 which may be configured to read data stored in an internal memory of a physical card 120 in a contactless manner. The physical card 120 may be an ATM/Debit card or Credit card. In an aspect, other type of cards such as gift cards or virtual cards may also be used in place of physical card 120. The card reader device 130 may also be configured to write data into the internal memory of the physical card 120. The physical card 120 may also be a smart card such that it may include one or more processors where the one or more processors may be configured to perform various computing tasks for manipulating data stored in the internal memory of the card 120.
[00055] In an aspect, the reader device 130 may be associated with a ticket print module 140. The print module 140 may be a printer device, a system-on-chip (SOC), a software component of the reader device 130, a hardware device, a hardware component, an on-device display, or an external display device, or a combination thereof. The print module 140 may be configured to output a ticket such as a printed ticket or a virtual ticket. The reader device 130 and/or the print module 140 may also be configured to transmit the ticket to a user device over a network. The card reader device 130 may store ticket history, past transaction information, and/or information related to card 120 in an internal and/or external memory device. The card reader device 130 may also store information related to the user such as user name, address, travel history, online account(s), user profile(s), social media account(s), email address, phone number(s), etc. in an internal and/or external memory device. The card reader device 130 may receive as input travel information (e.g., source and/or destination information) entered by an operator. The card reader device 130 may be associated with a database 150. The card reader device 130 may provide the travel information to the database 150 for processing. The database 150 may determine a travel fare amount in real-time. The database 150 may determine distance between source and destination based on the received travel information. The database 150 may also determine actual or expected travel time for reaching to the destination from the source. The database 150 may dynamically calculate the travel fare based on the determined travel distance and/or the determined actual or expected travel time. The database 150 may use pre-stored information (e.g., base fare, fare per unit distance, fare per unit travel time, surcharge, tax, other costs, and the like) and/or the received travel information for determining the travel fare. The database 150 may provide the pre-stored information to the card reader device.
[00056] In another aspect, the card reader device 130 may receive information related to dynamically determined travel fare from the database 150. The card reader device 130 may be configured to communicate with an online banking portal/platform/gateway 160 over a network 170. The card reader device 130 may transmit payment information including information associated with the card 120 and the dynamically determined travel fare to the online banking portal 160 for payment/transaction processing. The online banking portal 160 may include a web/application server for acting as a remote endpoint to manage receiving and processing of the payment information. Upon successful processing of the payment information, the online banking portal 160 may provide a confirmation to the card reader device 130 over the network 170. After receiving the confirmation, the card reader device 130 may employ the print module 140 to output a new ticket. The ticket may include information obtained from the card 120, information stored in the memory of the card reader device 130, information received from the database 150, information associated with the confirmation, or a combination thereof.
[00057] FIG. 2 illustrates various components of a card reader device in accordance with an exemplary embodiment of the present disclosure.
[00058] As illustrated, proposed card reader device 200 may have (or be operatively connected to) various components. As illustrated, display/printer device 210 may output (e.g., print or display) a ticket upon receiving a confirmation of successful payment processing by the card reader device. A keyboard 200 may be a hardware or software component which may enable an operator to provide travel input(s) using one or more keyboard keys. The keyboard 200 may also include a trackpad for receiving touch and/or gesture based inputs(s). The card reader device 200 may also include network hardware 230 which may include radio frequency unit, cellular unit, infrared unit, near-field communication unit, Bluetooth unit, or a combination thereof. Although not explicitly illustrated in Fig. 2, the card reader device 200 may also include a set of different type of sensors such as biometric sensor, magnetic sensor, optical/imaging sensor, proximity sensor, etc. The sensor(s) may be used to fetch data from a physical card.
[00059] It can be appreciated that proposed system can be configured in a computing device or across a plurality of computing devices operatively connected with each other, wherein the computing devices can be any of a computer, a laptop, a smart phone, an Internet enabled mobile device and the like. Therefore, all possible modifications, implementations and embodiments of where and how the proposed system is configured are well within the scope of the present invention.
[00060] In an aspect, the proposed system can be operatively connected using an Internet based application such as a web application to any Internet enabled computing device, and can as well have a mobile application that can be downloaded on a mobile device that can connect to Internet for such connection. In such manner, the proposed system can be available 24*7 to its users (different entities as elaborated above). Any other manner of implementation of the proposed system or a part thereof is well within the scope of the present disclosure/invention. The computing device can be a PC, a tablet, a smart phone and other like devices.
[00061] As used herein, and unless the context dictates otherwise, the term “coupled to” is intended to include both direct coupling (in which two elements that are coupled to each other or in contact with each other) and indirect coupling (in which at least one additional element is located between the two elements). Therefore, the terms “coupled to” and “coupled with” are used synonymously. Within the context of this document terms “coupled to” and “coupled with” are also used euphemistically to mean “communicatively coupled with” over a network, where two or more devices are able to exchange data with each other over the network, possibly via one or more intermediary device.
[00062] Moreover, in interpreting both the specification and the claims, all terms should be interpreted in the broadest possible manner consistent with the context. In particular, the terms “comprises” and “comprising” should be interpreted as referring to elements, components, or steps in a non-exclusive manner, indicating that the referenced elements, components, or steps may be present, or utilized, or combined with other elements, components, or steps that are not expressly referenced.
[00063] In a preferred embodiment proposed system may be enabled using Internet. However, it can be readily understood that other communication methods such as those where the system is configured at a server and various computing devices connect to it using LAN, WAN etc. may as well be deployed.
[00064] While some embodiments of the present disclosure have been illustrated and described, those are completely exemplary in nature. The disclosure is not limited to the embodiments as elaborated herein only and it would be apparent to those skilled in the art that numerous modifications besides those already described are possible without departing from the inventive concepts herein. For instance, the system as disclosed can as well be used for grading different services as provided by different service providers such as transporters etc. All such modifications, changes, variations, substitutions, and equivalents are completely within the scope of the present disclosure. The inventive subject matter, therefore, is not to be restricted except in the spirit of the appended claims.

ADVANTAGES OF THE INVENTION
[00065] The present disclosure provides a cashless transport fare deduction system which obviates the above mentioned limitations.
[00066] The present disclosure provides a system to facilitate automated cashless transport fare deduction in a public transport system.
[00067] The present disclosure provides a system to enable cashless payment of transport fare to reduce the risk of contagious diseases by avoiding any direct/indirect contact among human beings.
[00068] The present disclosure provides an automated cashless transport fare deduction system for enhancing ease, safety and transparency of payments/transactions.

We Claims:

1. An automated transaction system for use in public transport, said system comprising:
a card reader device configured to fetch data stored in a memory of a physical card, wherein said card reader device fetches the data without having any physical contact with said physical card, wherein said card reader device transmits one or more data packets to a server over a network for processing a transaction;
a database, associated with said card reader device, for dynamically determining a transaction value based at least in part on any or a combination of a distance from a source point to a destination point, and actual or expected time to reach the destination point from the source point, wherein said database provides one or more of the transaction value, and pre-stored information to said card reader device, wherein the one or more data packets comprise a first set of data bits corresponding to the transaction value, and a second set of data bits corresponding to the data fetched by said card reader device; and
an output device, associated with said card reader device, for providing a ticket upon successful execution of the transaction, wherein the ticket comprises information corresponding to any or a combination of the transaction, the transaction value, the distance, the actual or expected time, the source point, the destination point, the pre-stored information, and the data fetched by said card reader device.
2. The automated transaction system as claimed in claim 1, wherein said ticket is either a physical ticket or a virtual ticket.
3. The automated transaction system as claimed in claim 1, wherein said output device is either a printer device or a display device.
4. The automated transaction system as claimed in claim 1, wherein said network is Internet.
5. The automated transaction system as claimed in claim 1, wherein said card reader device comprises a set of actuable keys, one or more sensors to fetch said data stored within said physical card, and a network hardware.
6. The automated transaction system as claimed in claim 5, wherein fetching the data stored in said memory of said physical card without having any physical contact with said physical card requires said physical card to be in a close proximity of said card reader device.
7. The automated transaction system as claimed in claim 5, wherein said set of actuable keys are used to provide one or more inputs to said card reader device, wherein said one or more inputs comprising any or a combination of said source point, said destination point, information associated with said physical card, and information related to a user.
8. The automated transaction system as claimed in claim 7, wherein said card reader device provides said one or more inputs to said database.
9. The automated transaction system as claimed in claim 5, wherein said set of actuable keys are either a set of physical keys or a set of virtual keys.
10. The automated transaction system as claimed in claim 5, wherein said network hardware is capable of facilitating one or more of a radio frequency communication, cellular communication, infrared communication, near-field communication, and bluetooth communication.
11. The automated transaction system as claimed in claim 1, wherein said database is configured to determine a route from the source point to the destination point based on the pre-stored information.
12. The automated transaction system as claimed in claim 11, wherein said output device is configured to show the determined route.