[001] The present invention relates to the domain of transportation services and in particular provides efficient systems and methods for implementing electronic payments towards software application based taxi aggregation and dispatcher services.
Background
[002] Software application based taxi dispatcher systems have become increasingly popular across the world. Such systems are configured to automate the dispatching of taxis to rider locations, the determining of routes between a rider pick-up location and a rider drop destination, the billing for the tide, and the receiving of electronic payments from riders upon completion of rides.
[003] Typically, a system of this type receives a rider request for a taxi from a network communication enabled terminal associated with a rider (for example a smartphone), and obtain the rider pick-up location (for example a GPS location) from a locator device installed in the requesting terminal. The system simultaneously collects taxi locations of available taxis using locator devices (e.g. a GPS locator device) installed in taxis, and stores this information in a database. To dispatch a taxi to a specific rider, the system searches its database for a taxi with a location close to a rider location using a matching algorithm.
[004] The rider’s GPS location is translated to a street address using a digital map database and is transmitted to a communication terminal (for example a smartphone) inside the taxi so that the taxi operator can reach the pick-up location. Once a ride commences, the system records the route taken, as well as one or more ride parameters (including for example, speed, distance, idling time etc.) and upon termination of the ride (for example, once the rider reaches her / his desired destination) calculates the fare for the ride based on these parameters. The calculated fare is communicated to the rider, who then requires to pay the calculated fare.
[005] While such systems are automatic, efficient and flexible, it has been found that implementing a post-ride billing system is susceptible to certain jurisdiction specific limitations.
3
[006] Ordinarily, software application based taxi dispatcher systems require an onboarding process, wherein a new rider requires to create an electronic account with the system, and as part of this process to register one or more payment accounts with the system – which payment accounts can be automatically debited by the system once a ride has been completed.
[007] It has however been found that the ability to automatically debit payment accounts is often regulated in a jurisdiction specific manner, with applicable laws preventing debit of payment accounts without express authentication from the holder of the payment account - for example, by requiring the holder to input a personal identification number (PIN), password, passcode, one-time-password or other form of express authentication either at a payor terminal or at a payee terminal before authorizing the requested debit.
[008] This requirement for prior authorization by a payment account holder has been found to offer opportunities for deliberate misuse and/or inadvertent default on payment that fall due, on the part of riders – who deliberately or inadvertently omit to provide such authorization, thereby causing a financial loss to the software application based taxi dispatcher service provider.
[009] There is accordingly a need for a system for electronic payments in software application based taxi dispatcher systems, which ensures that the taxi dispatcher service provider receives payment for a completed ride.
Summary
[0010] The present invention provides systems and methods for implementing electronic payments towards taxi rides initiated through a software application based taxi aggregator or dispatcher service.
[0011] The invention provides a method for electronic payment towards software application based taxi dispatcher services. An embodiment of the method comprises (i) receiving a request for a taxi ride, comprising a ride commencement location and a ride termination location, identifying a trip route from the ride commencement location to the ride termination location, (iii) determining one or more estimated route parameters corresponding to the identified trip route, (iv) determining an estimated ride fare associated with the identified trip route, wherein the estimated ride fare is determined based on the determined one or more estimated route parameters,
4
(v) receiving an authorization confirming that the estimated ride fare may be debited from an identified payor payment account, (vi) debiting the estimated ride fare from the identified payor payment account for crediting to a payee payment account corresponding to the software application based taxi dispatch service provider (vii) recording within a duration between initiation of the requested taxi ride and completion of the requested taxi ride, one or more ride parameters, (viii) determining an actual ride fare associated with the completed taxi ride, wherein the actual ride fare is determined based on the recorded one or more ride parameters, and (ix) initiating an electronic transfer of an identified difference amount between the estimated ride fare and the actual ride fare from one of the payor payment account and the payee payment account.
[0012] In an embodiment of the method, responsive to the estimated ride fare being greater than the actual ride fare, the identified difference amount between the estimated ride fare and the actual ride fare is transferred from the payee payment account to the payor payment account.
[0013] Responsive to the estimated ride fare being less than the actual ride fare, the identified difference amount between the estimated ride fare and the actual ride fare may be transferred from the payor payment account to the payee payment account.
[0014] The estimated ride fare associated with the identified trip route may be determined based on one or more of estimated distance and estimated time corresponding to the identified trip route.
[0015] In a particular embodiment of the method, the recorded one or more ride parameters comprise one or more of distance and time corresponding to completion of the requested taxi ride.
[0016] The invention additionally provides a system for implementing electronic payments towards software application based taxi dispatcher services. In an embodiment, the system comprises a processor implemented dispatcher network server configured to (i) receive a request for a taxi ride, comprising a ride commencement location and a ride termination location, (ii) identify a trip route from the ride commencement location to the ride termination location, (iii) determine one or more estimated route parameters corresponding to the identified trip route, (iv) determine an estimated ride fare associated with the identified trip route, wherein the estimated ride fare is determined based on the determined one or more estimated route parameters, (v)
5
receive an authorization confirming that the estimated ride fare may be debited from an identified payor payment account, (vi) debit the estimated ride fare from the identified payor payment account for crediting to a payee payment account corresponding to the software application based taxi dispatch service provider, (vii) record within a duration between initiation of the requested taxi ride and completion of the requested taxi ride, one or more ride parameters, (viii) determine an actual ride fare associated with the completed taxi ride, wherein the actual ride fare is determined based on the recorded one or more ride parameters, and (ix) initiate an electronic transfer of an identified difference amount between the estimated ride fare and the actual ride fare from one of the payor payment account and the payee payment account.
[0017] In an embodiment of the system, responsive to the estimated ride fare being greater than the actual ride fare, the identified difference amount between the estimated ride fare and the actual ride fare is transferred from the payee payment account to the payor payment account.
[0018] Responsive to the estimated ride fare being less than the actual ride fare, the identified difference amount between the estimated ride fare and the actual ride fare may be transferred from the payor payment account to the payee payment account.
[0019] The system may estimate the ride fare associated with the identified trip route based on one or more of estimated distance and estimated time corresponding to the identified trip route.
[0020] In a particular embodiment, the recorded one or more ride parameters comprise one or more of distance and time corresponding to completion of the requested taxi ride.
[0021] The invention additionally provides a computer program product for electronic payment towards software application based taxi dispatcher services. The computer program product comprises a non-transitory computer usable medium having a computer readable program code embodied therein, the computer readable program code comprising instructions for implementing within a processor based computing system, the steps of (i) receiving a request for a taxi ride, comprising a ride commencement location and a ride termination location, (ii) identifying a trip route from the ride commencement location to the ride termination location, (iii) determining one or more estimated route parameters corresponding to the identified trip route, (iv) determining an estimated ride fare associated with the identified trip route, wherein the estimated ride fare is determined based on the determined one or more estimated route parameters,
6
(v) receiving an authorization confirming that the estimated ride fare may be debited from an identified payor payment account, (vi) debiting the estimated ride fare from the identified payor payment account for crediting to a payee payment account corresponding to the software application based taxi dispatch service provider, (vii) recording within a duration between initiation of the requested taxi ride and completion of the requested taxi ride, one or more ride parameters, (viii) determining an actual ride fare associated with the completed taxi ride, wherein the actual ride fare is determined based on the recorded one or more ride parameters, and (ix) initiating an electronic transfer of an identified difference amount between the estimated ride fare and the actual ride fare from one of the payor payment account and the payee payment account.
Brief Description of the Accompanying Drawings
[0022] Figure 1 illustrates a system environment for implementing a software application based taxi dispatcher service.
[0023] Figure 2 illustrates a system environment for implementing electronic payments within a system for software application based taxi dispatcher services.
[0024] Figure 3 illustrates a representation of an exemplary route map of a type that may be presented to a rider at the time of ride commencement.
[0025] Figure 4 illustrates a method for effecting an electronic payment corresponding to a taxi ride availed through a software application based taxi dispatcher service, in accordance with the present invention.
[0026] Figure 5 illustrates a method for settling any balance payment due from a rider to the taxi dispatcher service upon completion of a ride.
[0027] Figure 6 illustrates a method for settling any balance payment due from the taxi dispatcher service to a rider upon completion of a ride.
[0028] Figure 7 illustrates an exemplary configuration for a dispatcher network server configured in accordance with the teachings of the present invention.
7
[0029] Figure 8 illustrates an exemplary computer system that may be configured to implement the teachings of the present invention.
Detailed Description
[0030] The present invention provides methods, systems and computer programs for implementing electronic payments towards software application based taxi aggregator services and/or taxi dispatcher services.
[0031] For the purposes of the present invention, the following terms shall be understood to have the corresponding meanings provided below:
[0032] “Acquirer” shall mean a business (e.g., a financial institution or a merchant bank) that contracts with a merchant or service provider to coordinate with the issuer network of a customers’ payment card or payment account.
[0033] “Acquirer network” shall refer to a communication network, including hardware, software and other equipment used by an acquirer to transmit and process card based transactions and information related to merchants, customers, payment cards and transactions.
[0034] “Payor”, “Card holder” or “Customer” shall mean an authorized payment card or payment account user who is making a purchase or effecting an electronic transaction with a payment card or payment account.
[0035] “Payment network” shall refer to the intermediary between the merchant’s acquirer and the customer’s issuer (for example, Mastercard® or Visa®). The payment network primarily coordinates payment card or payment account transactions between acquirers and issuers, and additionally coordinates clearing and settlement services to transfer payments from issuers to merchants.
[0036] “Issuer” shall mean a financial institution that issues payment cards or payment accounts and maintains a contract with a customer or account holder for repayment or settlement of purchases made on the payment card or payment account.
8
[0037] “Issuer network” shall refer to a communication network, including hardware, software and other equipment used by an issuer to transmit and process payment card transactions or payment account transactions and information related to customers, payment cards/payment accounts and transactions.
[0038] “Merchant” or “Payee” shall mean an authorized acceptor of payment towards goods or services provided.
[0039] “Payment card” shall mean a card or data associated with a payment account that may be provided to a merchant in order to fund a financial transaction via the associated payment account. Payment cards may include credit cards, debit cards, charge cards, stored-value cards, prepaid cards, fleet cards, virtual payment numbers, virtual card numbers, controlled payment numbers, etc. A payment card may be a physical card that may be provided to a merchant, or may be data representing the associated payment account (e.g., as stored in a communication device, such as a smart phone or computer). For example, in some instances, data including a payment account number may be considered a payment card for the processing of a transaction funded by the associated payment account. In some instances, a check may be considered a payment card where applicable.
[0040] “Payment account” shall mean any account that may be used for the purposes of effecting an electronic payment or electronic transaction, and shall include any electronic transaction account, payment card account, bank account or electronic wallet account.
[0041] Figure 1 illustrates a system environment 100 for implementing a software application based taxi dispatcher service.
[0042] As illustrated, system environment 100 includes one or more riders 102 having access to a network communication enabled terminal 104 (such as a smartphone) and one or more taxis 106. Each terminal 104 and taxi 106 is respectively connected to dispatcher network 110 through network 108 (for example through a wireless communication network or through the internet). Dispatcher network 110 may include at least one server configured for network communication with terminals 104 and / or taxis 106.
9
[0043] In operation, the dispatcher network 110 receives a rider request for a taxi from terminal 104 associated with a rider 102, and obtains the rider location (for example a GPS location) from a locator device installed in the terminal 104 that is in wireless communication with one or more Global Positioning System (GPS) satellites 112’.
[0044] The dispatcher network 110 simultaneously obtains and parses taxi locations of available taxis using a locator device (e.g. a GPS locator device) installed in each taxi 106, and which locator device is in wireless communication with one or more GPS satellites 112, and stores this information in a database. To dispatch a taxi 106 to a specific rider 102, the system searches its database for a taxi 106 with a location close to a rider’s 102 location using a matching algorithm and assigns the ride to a specific taxi identified by the matching algorithm.
[0045] The rider’s GPS location is translated to a street address using a digital map database and is communicated to a communication terminal (for example a smartphone) inside the taxi. The taxi 106 then meets the rider 102 and subsequent to commencement of the ride, the dispatcher network 110 records the route taken, as well as one or more ride parameters (including for example, speed, distance, idling time etc.). Upon termination of the ride (for example, once the rider 102 reaches her / his desired destination) the dispatcher network 110 calculates the fare for the ride based on these parameters. The calculated fare is communicated to the rider 102 through terminal 104, and rider 102 would thereafter require to pay the calculated fare.
[0046] Figure 2 illustrates a system environment 200 for electronic payments in connection with a software application based taxi dispatcher service – which system environment may be used to implement the features of the present invention.
[0047] As in the case of Figure 1, system environment 200 includes one or more riders 202 each having access to a network communication enabled terminal 204 (such as a smartphone) and one or more taxis 206. Each terminal 204 and taxi 206 is respectively connected to dispatcher network 210 through data network 208 (for example through a wireless communication network or through the internet). Dispatcher network 210 may include at least one dispatcher network server configured for network communication with terminals 204 and / or taxis 206. Also coupled to data network 208 are payment network 212, issuer network 214 and acquirer network 216.
10
[0048] As discussed in connection with Figure 1, in operation, the dispatcher network 210 receives a rider request for a taxi from terminal 204 associated with a rider 202, matches the rider 202 to a conveniently located taxi 206, and dispatches the taxi 206 to a requesting rider 202. Responsive to receiving a request for a taxi from a rider 202, the system searches its database for a taxi 206 with a location close to a rider’s 202 location and assigns the ride to a specific taxi identified by a matching algorithm. The rider’s street address is communicated to a communication terminal inside the taxi and the taxi 206 meets the rider 202. Upon termination of the ride (for example, once the rider reaches her / his desired destination) the dispatcher network 210 calculates the fare for the ride based on these parameters, and the calculated fare is communicated to the rider 202 through terminal 204.
[0049] Upon intimation of the calculated fare, the rider may initiate payment of the fare amount through a payment account that has been previously registered, on-boarded or otherwise linked with a rider’s account that has been previously created with the software application based taxi dispatcher service. Said payment may be initiated by the rider through the taxi service’s software application that is installed on terminal 204 – which software application will transmit both the rider’s / payor’s payment account information, and the service provider’s / payee’s payment account information, along with the transaction amount to payment network 212. Said payment network 212 thereafter manages settlement of the transaction amount from the rider’s payment account maintained with issuer network 214 to the service provider’s payment account maintained with the acquirer network 216 – which settlement may be achieved in accordance with standard electronic payment techniques that are known and would be apparent to the skilled person. Upon completion of the electronic payment, one or more of rider 202, a taxi operator driving taxi 206 and dispatcher network 210 may receive intimation that the payment transaction has been successfully completed.
[0050] Figure 4 illustrates a method for ensuring settlement of electronic payment(s) for a taxi ride obtained through a software application based taxi dispatcher service in accordance with the present invention.
[0051] Step 402 comprises receiving a ride request (i.e. a request for the dispatcher service to dispatch a taxi to the requesting rider’s location) along with a ride commencement location A (i.e. the location at which the taxi is to be dispatched) and a ride termination location B (i.e. the rider’s intended destination). The ride request may in an embodiment be input by rider 202 through a
11
software application implemented on a terminal 204 (for example, a smartphone) operated by rider 202 – and may be transmitted by terminal 204 onward to dispatcher network 210 through network 208.
[0052] At step 404, dispatcher network 210 identifies one or more available route(s) between location A and location B using a routing algorithm and may display the identified route(s) to rider 202 on a display of terminal 204. In an embodiment, the one or more identified routes may be overlaid over a digital map displayed on terminal 204 – so that rider 202 may view the proposed route.
[0053] Figure 3 illustrates a representation of an exemplary route map of a type that that may be presented to a rider 202. As illustrated in Figure 3, the illustrated route map may show a plurality of available / recommended routes. In the event a rider 202 is presented with a plurality of available / recommended routes, input may additionally be received from rider 202 through terminal 204 selecting a specific route to be followed for the taxi ride.
[0054] At step 406, responsive to selection of a route for the taxi ride, dispatcher network applies one or more estimation algorithms to estimate route parameters associated with a selected route between location A and location B. Said route parameters may include estimations of at least one or more of distance, traffic and time involved in case the selected route is followed. The route parameters may in an embodiment be estimated using estimation algorithms implemented within dispatcher network 210 – and said estimation algorithms may use as inputs, one or more items of real time information received by the dispatcher network 210 from multiple sources – including one or more of traffic information, road condition information and information regarding routing decisions taken by traffic signals and / or traffic regulation agencies such as the traffic police or the municipal works department.
[0055] At step 408, dispatcher network 210 determines an estimated ride fare associated with a selected route for a taxi ride. The estimated ride fare may be determined based on one or more fare algorithms implemented within dispatcher network 210 – and said fare algorithms may use as inputs, the estimations of at least one of distance, traffic and time that have been determined at step 406. The estimated ride fare may thereafter be displayed to rider 202 through a display within terminal 204.
12
[0056] At step 410, dispatcher network 210 receives from rider 202, consent to pay the estimated ride fare. Said consent may be provided by input(s) received from rider 202 through a user interface within terminal 204 – and the received consent may be transmitted to dispatcher network 210 from terminal 204 through data network 208. It would be understood that for the purposes of the method of Figure 4, the rider’s consent to the estimated ride fare is communicated to dispatcher network 210 prior to commencement of the taxi ride (for example, when rider 202 enters the taxi 206 and prior to initiation of ride metering by the taxi 206 or the taxi driver.
[0057] At step 412, dispatcher network 210 retrieves payment account information associated with rider 202, or with a rider account maintained with the dispatcher network 210 that has been used to request a taxi ride. The retrieved payment account information may include information representing a payment card or payment account that has been previously registered, on-boarded or otherwise linked with the rider’s account with the software application based taxi dispatcher service. In an embodiment of the invention, payment account information retrieved at step 412 includes at least a payment account identifier, and an issuer bank identifier or issuer network identifier associated with a payment account. Said payment account information may in certain embodiments be retrieved from a payment account database that is maintained by or accessible to dispatcher network 210.
[0058] At step 414, a payment account identified based on the payment account information retrieved at step 412, is debited for the estimated ride fare that has been determined at step 408 and to which debit the rider has consented at step 410. Said debit is in an embodiment implemented by payment network 212, and may be implemented subsequent to obtaining from the user, all necessary inputs, authorizations and consents that may be required under applicable local regulations. The debited amount is subsequently credited into a payment account corresponding to the taxi dispatcher service. The debit / credit of the estimated ride fare is notified to one or more of rider 202, a taxi operator for taxi 206 (for example through a communication terminal located within taxi 206) and / or dispatcher network 210. Pursuant to receiving a notification of successful payment, the taxi ride may be commenced by the taxi operator.
[0059] Step 416 comprises completing the requested taxi ride from location A to location B - whereafter dispatcher network 210 receives confirmation of ride completion from one or both of terminal 204 and a communication terminal within taxi 206.
13
[0060] At step 418, subsequent to receiving confirmation of completion of the ride from location A to location B, dispatcher network 210 determines an actual ride fare based on one or more fare algorithms implemented within dispatcher network 210 – wherein said fare algorithm(s) receive as inputs, one or more ride parameters corresponding to the completed ride. Said one or more ride parameters corresponding to the completed ride may include at least one of distance covered between commencement of the ride and termination of the ride, and time between commencement of the ride and termination of the ride.
[0061] At step 420 dispatcher network 420 initiates electronic transfer of any payment necessary to rectify or balance a difference between the actual ride fare calculated at step 418 and the estimated ride fare that has been debited from the rider’s payment account at step 414.
[0062] Figures 5 and 6 discuss in more detail the electronic transfer of payment initiated at step 420 of Figure 4.
[0063] Figure 5 illustrates a method for settling any balance payment due from a rider to the taxi dispatcher service upon completion of a ride. As shown in Figure 5, step 502 comprises determining a difference between the actual ride fare (that has been determined in accordance with step 418 of Figure 4) and the estimated ride fare (that has been debited from a payment account at step 404 of Figure 4). In the event it is found that the actual ride fare determined at step 418 is greater than the estimated ride fare that has been debited from a payment account at step 414, step 504 comprises initiating transfer of the difference amount from a payment account that has been identified by the payment account information retrieved at step 412, to a payment account corresponding to the taxi dispatcher service.
[0064] Figure 6 illustrates a method for settling any balance payments due from the taxi dispatcher service to a rider upon completion of a ride. As shown in Figure 6, step 602 comprises determining a difference between the actual ride fare (determined at step 418 of Figure 4) and the estimated ride fare. In the event it is found that the actual ride fare determined at step 418 is less than the estimated ride fare that has been debited from a payment account at step 414, step 604 comprises initiating transfer of the difference amount from a payment account corresponding to the taxi dispatcher service, to a payment account identified by the payment account information retrieved at step 412.
14
[0065] As a result of the above discussed methods, the taxi dispatcher service provider is at all times assured of receiving at least the estimated ride fare, and any loss due to post-ride non-payment by a rider is limited to any difference between the estimated ride fare and the actual ride fare – thereby significantly limiting the potential for loss to the taxi dispatcher service provider, while simultaneously ensuring that the rider receives back any excess payment made in case it is eventually found that the estimated ride fare is greater than the actual ride fare.
[0066] Figure 7 illustrates an exemplary configuration for a dispatcher network server 700 within a dispatcher network 210 of a type previously discussed in connection with Figure 2, and that has been configured in accordance with the teachings of the present invention.
[0067] Dispatcher network server 700 comprises any server having data processing and network communication capabilities. In specific embodiments, dispatcher network server 700 comprises operator interface 702, processor 704, transceiver 706, dispatcher controller 708, route controller 710, route parameter information controller 712, fare estimation controller 714 and memory 716.
[0068] Operator interface 702 is a server interface that enables inputs and server controls to be received from an operator. Processor 704 comprises any one or more data processors implemented within dispatcher network server 700. Transceiver 706 comprises a data transceiver configured to enable the server to receive and transmit data over a communication network.
[0069] Dispatcher controller 708 may comprise a hardware and / or software implemented controller configured to implement one or more matching algorithms for selecting a taxi corresponding to a received ride request, and for dispatching a selected taxi to a rider pickup location.
[0070] Route controller 710 comprises a hardware / software implemented controller configured to determine available routes between a trip start location and a trip end location, and optionally to select one of multiple available routes based on one or more specified selection parameters or based on one or more received user inputs.
15
[0071] Route parameter information controller 712 comprises a hardware / software implemented controller configured to record route parameter information corresponding to trips undertaken by taxis dispatched by the dispatcher network – which information may include one or more of distance information, time information, traffic information and diversion information.
[0072] Fare estimation controller 714 comprises a hardware / software implemented controller configured to estimate a ride fare associated with a selected route for a taxi ride, in advance of initiating the taxi ride. The fare estimation controller 714 may be configured to implement one or more fare algorithms for the purposes of ride fare estimation.
[0073] Memory 716 may include therewithin, (i) an operating system 718 configured for managing device hardware and software resources and that provides common services for software programs implemented within dispatcher network server 700, (ii) a rider account database 720 configured to store records corresponding to riders registered to use the services of the software application based taxi dispatcher service, (iii) a payment account database 722 configured to store payment account information records corresponding to riders registered to use the services of the software application based taxi dispatcher service, (iv) a map database 724 configured to store digital maps of one or more locations or regions, (v) a road condition database 726 configured to receive and store real time information corresponding to roads or routes, including traffic information, mobility information and access information corresponding to such roads, and (vi) a taxi tracking database 728 configured to receive and store in real time, data corresponding to the location of taxis registered and available for services with the dispatcher network.
[0074] It would be understood that dispatcher network server 700 may be configured to implement one or more methods steps discussed in connection with Figures 4 to 6.
[0075] Figure 8 illustrates an exemplary computer system 800 that may be configured to implement the teachings of the present invention.
[0076] System 800 includes computer system 802 which in turn comprises one or more processors 804 and at least one memory 806. Processor 804 is configured to execute program instructions - and may be a real processor or a virtual processor. It will be understood that computer system 802 does not suggest any limitation as to scope of use or functionality of
16
described embodiments. The computer system 802 may include, but is not be limited to, one or more of a general-purpose computer, a programmed microprocessor, a micro-controller, an integrated circuit, and other devices or arrangements of devices that are capable of implementing the steps that constitute the method of the present invention. Exemplary embodiments of a computer system 802 in accordance with the present invention may include one or more servers, desktops, laptops, tablets, smart phones, mobile phones, mobile communication devices, tablets, phablets and personal digital assistants. In an embodiment of the present invention, the memory 806 may store software for implementing various embodiments of the present invention. The computer system 802 may have additional components. For example, the computer system 802 may include one or more communication channels 808, one or more input devices 810, one or more output devices 812, and storage 814. An interconnection mechanism (not shown) such as a bus, controller, or network, interconnects the components of the computer system 802. In various embodiments of the present invention, operating system software (not shown) provides an operating environment for various software(s) executing in the computer system 802 using a processor 804, and manages different functionalities of the components of the computer system 802.
[0077] The communication channel(s) 808 allow communication over a communication medium to various other computing entities. The communication medium provides information such as program instructions, or other data in a communication media. The communication media includes, but is not limited to, wired or wireless methodologies implemented with an electrical, optical, RF, infrared, acoustic, microwave, Bluetooth or other transmission media.
[0078] The input device(s) 810 may include, but is not limited to, a touch screen, a keyboard, mouse, pen, joystick, trackball, a voice device, a scanning device, or any another device that is capable of providing input to the computer system 802. In an embodiment of the present invention, the input device(s) 810 may be a sound card or similar device that accepts audio input in analog or digital form. The output device(s) 812 may include, but not be limited to, a user interface on CRT, LCD, LED display, or any other display associated with any of servers, desktops, laptops, tablets, smart phones, mobile phones, mobile communication devices, tablets, phablets and personal digital assistants, printer, speaker, CD/DVD writer, or any other device that provides output from the computer system 802.
17
[0079] The storage 814 may include, but not be limited to, magnetic disks, magnetic tapes, CD-ROMs, CD-RWs, DVDs, any types of computer memory, magnetic stripes, smart cards, printed barcodes or any other transitory or non-transitory medium which can be used to store information and can be accessed by the computer system 802. In various embodiments of the present invention, the storage 814 may contain program instructions for implementing any of the described embodiments.
[0080] In an embodiment of the present invention, the computer system 802 is part of a distributed network or a part of a set of available cloud resources.
[0081] The present invention may be implemented in numerous ways including as a system, a method, or a computer program product such as a computer readable storage medium or a computer network wherein programming instructions are communicated from a remote location.
[0082] The present invention may suitably be embodied as a computer program product for use with the computer system 802. The method described herein is typically implemented as a computer program product, comprising a set of program instructions that is executed by the computer system 802 or any other similar device. The set of program instructions may be a series of computer readable codes stored on a tangible medium, such as a computer readable storage medium (storage 814), for example, diskette, CD-ROM, ROM, flash drives or hard disk, or transmittable to the computer system 802, via a modem or other interface device, over either a tangible medium, including but not limited to optical or analogue communications channel(s) 808. The implementation of the invention as a computer program product may be in an intangible form using wireless techniques, including but not limited to microwave, infrared, Bluetooth or other transmission techniques. These instructions can be preloaded into a system or recorded on a storage medium such as a CD-ROM, or made available for downloading over a network such as the Internet or a mobile telephone network. The series of computer readable instructions may embody all or part of the functionality previously described herein.
[0083] While the exemplary embodiments of the present invention are described and illustrated herein, it will be appreciated that they are merely illustrative. It will be understood by those skilled in the art that various modifications in form and detail may be made therein without departing from or offending the spirit and scope of the invention as defined by the appended claims. Additionally, the invention illustratively disclosed herein suitably may be practiced in the
18
absence of any element which is not specifically disclosed herein – and in a particular embodiment that is specifically contemplated, the invention is intended to be practiced in the absence of any one or more element which are not specifically disclosed herein.

We Claim:
1. A method for electronic payment towards software application based taxi dispatcher services, comprising:
receiving a request for a taxi ride, comprising a ride commencement location and a ride termination location;
identifying a trip route from the ride commencement location to the ride termination location;
determining one or more estimated route parameters corresponding to the identified trip route;
determining an estimated ride fare associated with the identified trip route, wherein the estimated ride fare is determined based on the determined one or more estimated route parameters;
receiving an authorization confirming that the estimated ride fare may be debited from an identified payor payment account;
debiting the estimated ride fare from the identified payor payment account for crediting to a payee payment account corresponding to the software application based taxi dispatch service provider;
recording within a duration between initiation of the requested taxi ride and completion of the requested taxi ride, one or more ride parameters;
determining an actual ride fare associated with the completed taxi ride, wherein the actual ride fare is determined based on the recorded one or more ride parameters; and
initiating an electronic transfer of an identified difference amount between the estimated ride fare and the actual ride fare from one of the payor payment account and the payee payment account.
20
2. The method for electronic payment as claimed in claim 1, wherein responsive to the estimated ride fare being greater than the actual ride fare, the identified difference amount between the estimated ride fare and the actual ride fare is transferred from the payee payment account to the payor payment account.
3. The method for electronic payment as claimed in claim 1, wherein responsive to the estimated ride fare being less than the actual ride fare, the identified difference amount between the estimated ride fare and the actual ride fare is transferred from the payor payment account to the payee payment account.
4. The method for electronic payment as claimed in claim 1, wherein the estimated ride fare associated with the identified trip route is determined based on one or more of estimated distance and estimated time corresponding to the identified trip route.
5. The method for electronic payment as claimed in claim 1, wherein the recorded one or more ride parameters comprise one or more of distance and time corresponding to completion of the requested taxi ride.
6. A system for implementing electronic payments towards software application based taxi dispatcher services, comprising:
a processor implemented dispatcher network server configured to:
receive a request for a taxi ride, comprising a ride commencement location and a ride termination location;
identify a trip route from the ride commencement location to the ride termination location;
determine one or more estimated route parameters corresponding to the identified trip route;
21
determine an estimated ride fare associated with the identified trip route, wherein the estimated ride fare is determined based on the determined one or more estimated route parameters;
receive an authorization confirming that the estimated ride fare may be debited from an identified payor payment account;
debit the estimated ride fare from the identified payor payment account for crediting to a payee payment account corresponding to the software application based taxi dispatch service provider;
record within a duration between initiation of the requested taxi ride and completion of the requested taxi ride, one or more ride parameters;
determine an actual ride fare associated with the completed taxi ride, wherein the actual ride fare is determined based on the recorded one or more ride parameters; and
initiate an electronic transfer of an identified difference amount between the estimated ride fare and the actual ride fare from one of the payor payment account and the payee payment account.
7. The system for implementing electronic payments as claimed in claim 6, wherein responsive to the estimated ride fare being greater than the actual ride fare, the identified difference amount between the estimated ride fare and the actual ride fare is transferred from the payee payment account to the payor payment account.
8. The system for implementing electronic payments as claimed in claim 6, wherein responsive to the estimated ride fare being less than the actual ride fare, the identified difference amount between the estimated ride fare and the actual ride fare is transferred from the payor payment account to the payee payment account.
22
9. The system for implementing electronic payments as claimed in claim 6, wherein the estimated ride fare associated with the identified trip route is determined based on one or more of estimated distance and estimated time corresponding to the identified trip route.
10. The system for implementing electronic payments as claimed in claim 6, wherein the recorded one or more ride parameters comprise one or more of distance and time corresponding to completion of the requested taxi ride.
11. A computer program product for electronic payment towards software application based taxi dispatcher services, the computer program product comprising a non-transitory computer usable medium having a computer readable program code embodied therein, the computer readable program code comprising instructions for implementing within a processor based computing system, the steps of:
receiving a request for a taxi ride, comprising a ride commencement location and a ride termination location;
identifying a trip route from the ride commencement location to the ride termination location;
determining one or more estimated route parameters corresponding to the identified trip route;
determining an estimated ride fare associated with the identified trip route, wherein the estimated ride fare is determined based on the determined one or more estimated route parameters;
receiving an authorization confirming that the estimated ride fare may be debited from an identified payor payment account;
debiting the estimated ride fare from the identified payor payment account for crediting to a payee payment account corresponding to the software application based taxi dispatch service provider;
23
recording within a duration between initiation of the requested taxi ride and completion of the requested taxi ride, one or more ride parameters;
determining an actual ride fare associated with the completed taxi ride, wherein the actual ride fare is determined based on the recorded one or more ride parameters; and
initiating an electronic transfer of an identified difference amount between the estimated ride fare and the actual ride fare from one of the payor payment account and the payee payment account.