DESC:FIELD OF THE INVENTION

The present disclosure relates to Electric Vehicle (EV) charging terminals and more particularly, relates to systems and methods for accessing electric vehicle (EV) charging terminals.

BACKGROUND

Electrical Vehicles (EVs) have gained widespread popularity in the last few years and significant growth and development are still being witnessed in their realm. As is already known, such EVs are required to be frequently charged, for example, at charging terminals for continuous operation. At a charging terminal, a user is required to plug the EV into a charging terminal and pay for the services thereafter. In particular, the user may connect to the charging terminal through a communication device. The user is then authenticated and registered for being able to avail facilities of the charging terminal. However, prior to availing the facilities, the user needs to pay a specific amount to an administrator/owner of such charging terminal.

Currently, the administrator/owner needs to be available at a location of the charging terminal in order to provide payment information to the user, to monitor/confirm whether the payment is received from such user, and to enable charging from the charging terminal upon receiving the payment. However, if there are multiple charging terminals at a charging station, then it might be cumbersome and difficult for the administrator to manage each of the charging terminals simultaneously for multiple users. Further, if the administrator is not present at the charging station on any given day, then the user might not able to get access to the charging terminal.

SUMMARY

This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the invention. This summary is neither intended to identify key or essential inventive concepts of the invention and nor is it intended for determining the scope of the invention.

In an embodiment of the present disclosure, a method for accessing an Electric Vehicle (EV) charging terminal is disclosed. The method includes retrieving, at a guest terminal in communication with the EV charging terminal, a set of payment information associated with an administrator of the EV charging terminal. Further, the method comprises sending, from the guest terminal, a payment request to a payment gateway to initiate a payment based on the set of payment information. The method comprises generating, at each of the guest terminal and an administrator terminal, a notification indicating information associated with payment transaction received from the payment gateway. Further, the method comprises determining information associated with the guest terminal, the EV charging terminal in communication with the guest terminal, and payment transaction. The method comprises generating a key to enable charging from the EV charging terminal based on the determined information.

In an embodiment, the payment request comprises data associated with at least a transaction amount to be paid for accessing the EV charging terminal.

In an embodiment, determining information associated with the guest terminal, the EV charging terminal in communication with the guest terminal, and payment transaction comprises:
receiving, from the guest terminal, a request indicative of initiating charging from the EV charging terminal,
determining, at the administrator terminal, a status of payment transaction and information associated with payment transaction based on the generated notification. The status of payment transaction indicates one of a successful transaction and an unsuccessful transaction, and
retrieving, at the administrator terminal, a guest ID associated with the guest terminal and an outlet ID associated with the EV charging terminal in communication with the guest terminal.

In an embodiment, the information associated with the payment transaction is indicative of a name of payer, a transaction ID, a date of transaction, a time of transaction, an amount of transaction, and information associated with the payment gateway.

In an embodiment, the method comprises displaying a notification on a user interface of an application installed in the administrator terminal based on the determined information associated with payment transaction. The notification is indicative of the status of payment transaction.

In an embodiment, generating the key to enable charging from the EV charging terminal comprises:
determining whether the status of payment transaction is indicative of successful transaction;
generating a notification indicative of successful transaction based on the determined status of payment transaction;
displaying, at the administrator terminal, a user-selectable button on a user interface for enabling charging at the EV charging terminal if the status of payment transaction is indicative of successful transaction;
receiving, from the administrator terminal, an input indicative of enabling charging at the EV charging terminal via the user-selectable button; and
generating the key to enable charging from the EV charging terminal based on the received input. The key comprises an instruction to enable charging from the EV charging terminal for a predetermined time based on the information associated with payment transaction.

In an embodiment, generating the key to enable charging from the EV charging terminal comprises:
determining whether the status of payment transaction is indicative of successful transaction; and
generating the key to enable charging from the EV charging terminal if the status of payment transaction is indicative of successful transaction. The key comprises an instruction to enable charging from the EV charging terminal for a predetermined time based on the information associated with payment transaction.

In an embodiment, the method comprises sending the key to the EV charging terminal which is in communication with the guest terminal.

In another embodiment of the present disclosure, a system for accessing an Electric Vehicle (EV) charging terminal is disclosed. The system comprises at least one processor configured to retrieve a set of payment information associated with an administrator of the EV charging terminal. The at least one processor is configured to send a payment request to a payment gateway to initiate a payment based on the set of payment information. Further, the at least one processor is configured to generate a notification indicating information associated with payment transaction received from the payment gateway. The at least one processor is configured to determine information associated with the guest terminal, the EV charging terminal in communication with the guest terminal, and payment transaction. Further, the at least one processor is configured to generate a key to enable charging from the EV charging terminal based on the determined information.

In an embodiment, the payment request comprises data associated with at least a transaction amount to be paid for accessing the EV charging terminal.

In an embodiment, to determine information associated with the guest terminal, the EV charging terminal, and payment transaction, the at least one processor is configured to:
receive, from the guest terminal, a request indicative of initiating charging from the EV charging terminal;
determine, at an administrator terminal, a status of payment transaction and information associated with payment transaction based on the generated notification. The status of payment transaction indicates one of a successful transaction and an unsuccessful transaction; and
retrieve, at the administrator terminal, a guest ID associated with the guest terminal and an outlet ID associated with the EV charging terminal in communication with the guest terminal.

In an embodiment, the information associated with the payment transaction is indicative of a transaction ID, a date of transaction, a time of transaction, an amount of transaction, and information associated with the payment gateway sever.

In an embodiment, the at least one processor is configured to display a notification on a user interface of an application installed in the administrator terminal based on the determined information associated with payment transaction. The notification is indicative of the status of payment transaction.

In an embodiment, to generate the key to enable charging from the EV charging terminal, the at least one processor is configured to:
determine whether the status of payment transaction is indicative of successful transaction;
generate a notification indicative of successful transaction based on the determined status of payment transaction;
display, at the administrator terminal, a user-selectable button on a user interface for enabling charging at the EV charging terminal if the status of payment transaction is indicative of successful transaction;
receive, from the administrator terminal, an input indicative of enabling charging at the EV charging terminal via the user-selectable button; and
generate the key to enable charging from the EV charging terminal based on the received input. The key comprises an instruction to enable charging from the EV charging terminal for a predetermined time based on the information associated with payment transaction.

In an embodiment, to generate the key to enable charging from the EV charging terminal, the at least one processor is configured to:
determine whether the status of payment transaction is indicative of successful transaction; and
generate the key to enable charging from the EV charging terminal if the status of payment transaction is indicative of successful transaction. The key comprises an instruction to enable charging from the EV charging terminal for a predetermined time based on the information associated with payment transaction.

In an embodiment, the at least one processor is configured to send the key to the EV charging terminal which is in communication with the guest terminal.

In an embodiment, the system comprises an application adapted to be installed in the administrator terminal and the guest terminal. Functionalities of the system are accessed through the application.

In yet another embodiment of the present disclosure, a method for accessing an Electric Vehicle (EV) charging terminal. The method comprises retrieving, at a guest terminal in communication with the EV charging terminal, a set of payment information associated with an administrator of the EV charging terminal. Further, the method comprises initiating, from the guest terminal, a payment request based on the set of payment information. The method comprises determining, at the administrator terminal, a status of payment transaction based on a notification indicative of information associated with payment transaction. Further, the method comprises generating a key to enable charging from the EV charging terminal based on the status of the payment.

In an embodiment, initiating the payment request comprises initiating the payment request via one of third-party applications, installed in the guest terminal, based on the set of payment information.

In an embodiment, determining the status of payment transaction comprises determining, at the administrator terminal, the status of payment transaction based on the notification indicative of information associated with payment transaction received from one of the third-party applications installed in the administrator terminal.

In an embodiment, the method comprises:
receiving a request, from the guest terminal, indicative of initiating charging from the EV charging terminal;
determining a guest ID associated with the guest terminal and an outlet ID associated with the EV charging terminal based on the received request;
generating a notification, at the administrator terminal, indicating the guest ID and the outlet ID; and
verifying, by an administrator, the status of payment transaction and whether the payment transaction is completed by the guest terminal associated with the guest ID as indicated by the generated notification; and
generating the key for enabling the charging from the EV charging terminal if the status of payment indicates a successful transaction.

To further clarify the advantages and features of the present invention, a more particular description of the invention will be rendered by reference to specific embodiments thereof, which is illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:

Figure 1a illustrates an environment depicting a system in communication with at least one Electric Vehicle (EV) charging terminal, a guest terminal, and an administrator terminal, according to an embodiment of the present disclosure;

Figure 1b illustrates an environment depicting the system in communication with at least one Electric Vehicle (EV) charging terminal, the guest terminal, and the administrator terminal, according to another embodiment of the present disclosure;

Figure 1c illustrates an environment depicting the system in communication with at least one Electric Vehicle (EV) charging terminal, the guest terminal, and the administrator terminal, according to yet another embodiment of the present disclosure;

Figure 1d illustrates an environment depicting the system in communication with at least one Electric Vehicle (EV) charging terminal, the guest terminal, and the administrator terminal, according to yet another embodiment of the present disclosure;

Figure 2 illustrates a schematic view of the system for accessing the EV charging terminal, according to an embodiment of the present disclosure;

Figure 3 illustrates a flowchart depicting an implementation of the system for accessing the EV charging terminal, according to an embodiment of the present disclosure;

Figure 4 illustrates a flowchart depicting an implementation of the system for accessing the EV charging terminal, according to another embodiment of the present disclosure;

Figure 5 illustrates a flowchart depicting an implementation of the system for accessing the EV charging terminal, according to yet another embodiment of the present disclosure;

Figures 6a and 6b illustrate exemplary user interfaces of the guest terminal for accessing the EV charging terminal, according to an embodiment of the present disclosure;

Figures 7a and 7b illustrate exemplary user interfaces of the administrator terminal for allowing a guest to access the EV charging terminal, according to an embodiment of the present disclosure; and

Figure 8 illustrates a flowchart depicting a method for accessing the EV charging terminal, according to an embodiment of the present disclosure; and

Figure 9 illustrates a flowchart depicting a method for accessing the charging terminal, according to another embodiment of the present disclosure.

Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have been necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.

DETAILED DESCRIPTION OF FIGURES

For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the embodiment illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the invention as illustrated therein being contemplated as would normally occur to one skilled in the art to which the invention relates. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skilled in the art to which this invention belongs. The system, methods, and examples provided herein are illustrative only and not intended to be limiting.

The term “some” as used herein is defined as “none, or one, or more than one, or all.” Accordingly, the terms “none,” “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” The term “some embodiments” may refer to no embodiments or to one embodiment or to several embodiments or to all embodiments. Accordingly, the term “some embodiments” is defined as meaning “no embodiment, or one embodiment, or more than one embodiment, or all embodiments.”

The terminology and structure employed herein is for describing, teaching and illuminating some embodiments and their specific features and elements and does not limit, restrict or reduce the spirit and scope of the claims or their equivalents.

More specifically, any terms used herein such as but not limited to “includes,” “comprises,” “has,” “consists,” and grammatical variants thereof do NOT specify an exact limitation or restriction and certainly do NOT exclude the possible addition of one or more features or elements, unless otherwise stated, and furthermore must NOT be taken to exclude the possible removal of one or more of the listed features and elements, unless otherwise stated with the limiting language “MUST comprise” or “NEEDS TO include.”

Whether or not a certain feature or element was limited to being used only once, either way, it may still be referred to as “one or more features” or “one or more elements” or “at least one feature” or “at least one element.” Furthermore, the use of the terms “one or more” or “at least one” feature or element do NOT preclude there being none of that feature or element, unless otherwise specified by limiting language such as “there NEEDS to be one or more . . . ” or “one or more element is REQUIRED.”

Unless otherwise defined, all terms, and especially any technical and/or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skills in the art.

Reference is made herein to some “embodiments.” It should be understood that an embodiment is an example of a possible implementation of any features and/or elements presented in the attached claims. Some embodiments have been described for the purpose of illuminating one or more of the potential ways in which the specific features and/or elements of the attached claims fulfil the requirements of uniqueness, utility and non-obviousness.

Use of the phrases and/or terms such as but not limited to “a first embodiment,” “a further embodiment,” “an alternate embodiment,” “one embodiment,” “an embodiment,” “multiple embodiments,” “some embodiments,” “other embodiments,” “further embodiment”, “furthermore embodiment”, “additional embodiment” or variants thereof do NOT necessarily refer to the same embodiments. Unless otherwise specified, one or more particular features and/or elements described in connection with one or more embodiments may be found in one embodiment, or may be found in more than one embodiment, or may be found in all embodiments, or may be found in no embodiments. Although one or more features and/or elements may be described herein in the context of only a single embodiment, or alternatively in the context of more than one embodiment, or further alternatively in the context of all embodiments, the features and/or elements may instead be provided separately or in any appropriate combination or not at all. Conversely, any features and/or elements described in the context of separate embodiments may alternatively be realized as existing together in the context of a single embodiment.

Any particular and all details set forth herein are used in the context of some embodiments and therefore should NOT be necessarily taken as limiting factors to the attached claims. The attached claims and their legal equivalents can be realized in the context of embodiments other than the ones used as illustrative examples in the description below.

Embodiments of the present invention will be described below in detail with reference to the accompanying drawings.

Figure 1a illustrates an environment depicting a system in communication with at least one Electric Vehicle (EV) charging terminal, a guest terminal, and an administrator terminal, according to an embodiment of the present disclosure. For the sake of readability, the EV charging terminal 102 may hereinafter interchangeably be referred to as the charging terminal 102. In an embodiment, the charging terminal 102 is a standalone unit and is therefore not connected to any cloud server or a backend server for performing the functionalities. The charging terminal 102 may be deployed with a system 100 for enabling a user to access the charging terminal 102 to charge an electric vehicle.

Referring to Figure 1a, in the illustrated embodiment, the system 100 may be implemented as a part of the charging terminal 102, without departing from the scope of the present disclosure. In the present embodiment, the system 100 and the EV charging terminal 102 may be in communication with a guest terminal 104 and an administrator terminal 106. In an exemplary implementation, the guest terminal 104 and the administrator terminal 106 may be in communication with the system 100 and the EV charging terminal 102 via a Bluetooth Low Energy (BLE) network. Further, in the present embodiment, the guest terminal 104 and the administrator terminal 106 may be in communication with a payment gateway server 110 and an EV server 112 via a network 108.

Figure 1b illustrates an environment depicting the system 100 in communication with at least one Electric Vehicle (EV) charging terminal 102, the guest terminal 104, and the administrator terminal 106, according to another embodiment of the present disclosure. Referring to Figure 1b, in the illustrated embodiment, the system 100 may be implemented externally with respect to the EV charging terminal 102. In the present embodiment, the guest terminal 104 and the administrator terminal 106 may be in communication with the system 100 via a BLE network. Further, the guest terminal 104 and the administrator terminal 106 may be in communication with the payment gateway server 110 and the EV server 112 via the network 108.

Figure 1c illustrates an environment depicting the system 100 in communication with at least one Electric Vehicle (EV) charging terminal 102, the guest terminal 104, and the administrator terminal 106, according to yet another embodiment of the present disclosure. Referring to Figure 1c, in the illustrated embodiment, the system 100 may be implemented as a part of the EV charging terminal 102. In the present embodiment, the EV charging terminal 102 may be provided with functional capabilities to establish communication via the network 108. Referring to Figure 1c, the system 100 and the EV charging terminal 102 may be in communication with the payment gateway server 110 and the EV server 112 via the network 108.

In the illustrated embodiment, the guest terminal 104 and the administrator terminal 106 may be in communication with the EV charging terminal 102 and the system 100 via the network 108. Alternatively, a communication may be established between the system 100 and each of the guest terminal 104 and the administrator terminal 106 via a BLE network. Therefore, in the present embodiment, the guest terminal 104, the administrator terminal 106, the system 100, the payment gateway server 110, and the EV server 112 may communicate with each other via the network 108.

Figure 1d illustrates an environment depicting the system 100 in communication with at least one Electric Vehicle (EV) charging terminal 102, the guest terminal 104, and the administrator terminal 106, according to yet another embodiment of the present disclosure. Referring to Figure 1d, in the illustrated embodiment, the system 100 may be implemented externally with respect to the EV charging terminal 102. In the present embodiment, the system 100 may be provided with functional capabilities to establish communication via the network 108. Referring to Figure 1d, the system 100 may be in communication with the payment gateway server 110 and the EV server 112 via the network 108.

In the illustrated embodiment, the guest terminal 104 and the administrator terminal 106 may be in communication with the system 100 via the network 108. Alternatively, a communication may be established between the system 100 and each of the guest terminal 104 and the administrator terminal 106 via a BLE network. Therefore, in the present embodiment, the guest terminal 104, the administrator terminal 106, the system 100, the payment gateway server 110, and the EV server 112 may communicate with each other via the network 108.

The present disclosure is explained with respect to the environment as depicted in Figure 1a. However, it should be appreciated by a person skilled in the art that it should not be construed as limiting, and details of the present disclosure can also be implemented for the environments as depicted in Figures 1b-1d, without departing from the scope of the present disclosure.

In the illustrated embodiments, the network 108 may be a wired network or a wireless network. The network 108 may include, but is not limited to, a mobile network, a broadband network, a Wide Area Network (WAN), a Local Area Network (LAN), and a Personal Area Network. Further, each of the guest terminal 104 and an administrator terminal 106 may be embodied as one of a smartphone, a laptop, a tablet, a PDA, and a voice assistant device, without departing from the scope of the present disclosure.

Further, an application 202 (as shown in Figure 2) may be installed in the guest terminal 104 and the administrator terminal 106. The guest terminal 104 may be operated by a user to access the charging terminal 102 for charging the electric vehicle. In an embodiment, the user may be embodied as a registered user and an unregistered user, without departing from the scope of the present disclosure. The administrator terminal 106 may be operated by an administrator for allowing the user to access the charging terminal 102. The administrator and the user may access the functionalities of the charging terminal 102 and the system 100 through the application 202 installed in their respective communication terminals 104, 106. The administrator and the user may require respective unique credentials for logging into the application 202 for accessing the charging terminal 102. In an embodiment, rights and privileges of the administrator for accessing the EV charging terminal 102 may be more than that of the user.

As explained earlier, the charging terminal 102 may be deployed with the system 100 for allowing the administrator and the user to access the functionalities of the charging terminal 102 through the application 202 installed in their respective communication terminals 104, 106. In particular, the system 100 may allow the user to initiate and complete a payment transaction to access the charging terminal 102. Further, the system 100 may allow the administrator to monitor information associated with the payment transaction completed by the user and subsequently, allow the administrator to enable charging functionality of the charging terminal 102 for charging an electric vehicle of the user.

The payment gateway server 110 may be configured to initiate and complete payment transactions for accessing the charging terminal 102. In an embodiment, the payment gateway server 110 may be embodied as a remote server, such as a cloud server, without departing from the scope of the present disclosure. The guest terminal 104 may be operated to access the application 202 which provides a platform for accessing the payment gateway server 110 to initiate and complete payment transactions.

In an embodiment, the EV server 112 may be embodied as a remote server, such as a cloud server, without departing from the scope of the present disclosure. The EV server 112 may be configured to be accessed to obtain payment information associated with the administrator assigned to the charging terminal 102 and to authenticate unique credentials for logging into the application 202 installed in the terminals 104, 106 for accessing the charging terminal 102. In an embodiment, data communication between the EV server 112, the payment gateway server 110, the guest terminal 104, and the administrator terminal 106 may be encrypted using standard high-security encryption protocols.

For the sake of simplicity, one user and the associated the guest terminal 104 are illustrated in Figures 1a-1d. However, as would be appreciated by a person skilled in the art, the number of users may vary depending on the requirements of usage of the charging terminal 102. Accordingly, in other embodiments, the number of administrators may also vary, for example, based on the number of users, without departing from the scope of the present disclosure.

Constructional and operational details of the system 100 are explained at least in the description of Figure 2.

Figure 2 illustrates a schematic view of the system 100 for accessing the charging terminal 102, according to an embodiment of the present disclosure. Referring to Figure 2, in the illustrated embodiment, the system 100 may include, but is not limited to, at least one processor 204, memory 206, module(s) 208, and data 210. The module(s) 208 and the memory 206 are coupled to the processor 204. The processor 204 can be a single processing unit or a number of units, all of which could include multiple computing units. The processor 204 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor 204 is configured to fetch and execute computer-readable instructions and data stored in the memory.

The memory 206 may include any non-transitory computer-readable medium known in the art including, for example, volatile memory, such as static random-access memory (SRAM) and dynamic random-access memory (DRAM), and/or non-volatile memory, such as read-only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.

The module(s) 208, amongst other things, include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement data types. The module(s) 208 may also be implemented as, signal processor(s), state machine(s), logic circuitries, and/or any other device or component that manipulates signals based on operational instructions.

Further, the module(s) 208 may be implemented in hardware, instructions executed by at least one processing unit, for e.g., the processor, or by a combination thereof. The processing unit may comprise a computer, a processor, a state machine, a logic array and/or any other suitable devices capable of processing instructions. The processing unit may be a general-purpose processor which executes instructions to cause the general-purpose processor to perform operations or, the processing unit may be dedicated to performing the required functions. In some example embodiments, the module(s) 208 may be machine-readable instructions (software, such as web application, mobile application, program, etc.) which, when executed by a processor/processing unit, perform any of the described functionalities.

In an embodiment, the modules 208 may include a pairing module 212, a determining module 216, a receiving module 218, a generating module 220, and a communication module 222. The pairing module 212, the determining module 216, the receiving module 218, the generating module 220, and the communication module 222 may be in communication with each other. The data 210 serves, amongst other things, as a repository for storing data processed, received, and generated by one or more of the modules 208.

The processor 204 may be configured to receive a pairing request from the guest terminal 104. In an embodiment, the pairing module 212 may be adapted to receive the pairing request when the charging terminal 102 is available for the pairing, i.e., in a pairing mode. Upon completion of pairing with the guest terminal 104, the processor 204 may retrieve an outlet ID of the charging terminal 104 paired with the guest terminal 104. The processor 204 may be configured to communicate the retrieved outlet ID to the guest terminal 104 which is configured to display the outlet ID on a graphical user interface, interchangeably referred to as the user interface, of the application 202.

As explained earlier, the user may be embodied as the registered user and the unregistered user, without departing from the scope of the present disclosure. The EV server 112 may be configured to store unique credentials corresponding to the registered user. If the user is a registered user, the processor 204 may be configured to receive unique credentials from the guest terminal 104 via the application 202 installed in such terminal 104. The processor 204 may be configured to authenticate the unique credentials with respect to a set of pre-stored credentials stored in the EV server 112. Based on the authentication, the processor 204 may be configured to allow the guest terminal 104 to interact with the system 100 via the application 202. If the user is an unregistered user, the processor 204 may be configured to generate a guest ID corresponding to the guest terminal 104. The guest ID may be stored in the EV server 112 which can be retrieved for further processing via the applications 202. Subsequently, the processor 204 may be configured to allow the guest terminal 104 of such unregistered user to interact with the system 100 via the application 202.

The processor 204 may be configured to retrieve information associated with an administrator of the charging terminal 102 based on the outlet ID of such paired charging terminal 102. In an embodiment, the receiving module 218 may be configured to retrieve a set of payment information associated with the administrator of the charging terminal 102 from the EV server 112 via the application 202 of the guest terminal 106. In an embodiment, the set of payment information may include, but is not limited to, an account number, a recipient name, a name of banking authority, and a Unified Payment Interface (UPI) ID.

Further, the receiving module 218 may communicate the set of payment information to the communication module 222 of the system 100. The communication module 220 may be configured to communicate the set of payment information to the guest terminal 104. In an embodiment, the guest terminal 104 may be configured to display the set of payment information on a user interface of the application 202. Further, the communication module 222 may be configured to communicate information associated with a set of payment options to the guest terminal 104. The guest terminal 104 may be operated to select a payment option from among the set of payment options, via a user interface of the application 202.

In an embodiment, the set of payment options may include, but is not limited to, payment via the application 202 and payment via third-party applications, without departing from the scope of the present disclosure. In the present embodiment, functionalities of the system 100 may be explained with respect to the payment option, i.e., payment via the application 202. However, the functionality of the system 100 is explained with respect to other payment options in the description with respect to Figure 5 of the present disclosure.

Further, the processor 204 may be configured to send a payment request, from the guest terminal 104, to the payment gateway server 110 to initiate a payment based on the set of payment information. In an embodiment, the guest terminal 104 may be operated to generate a payment request via the application 202 based on the selected payment option. The payment request may include, but is not limited to, data associated with at least a transaction amount to be paid for accessing the charging terminal 102. Further, the receiving module 218 may receive the payment request from the guest terminal 104 and subsequently communicate the payment request to the communication module 222.

The communication module 222 may be configured to send the payment request to the payment gateway server 110 based on the set of payment information. Further, the communication module 222 may be configured to send the set of payment information to the payment gateway server 110. Based on the payment request and the set of payment information, the payment gateway server 110 may initiate a payment transaction and subsequently, send information associated with the payment transaction to the system 100.

The receiving module 218 may be configured to receive the information from the payment gateway server 110. In an embodiment, the information associated with the payment transaction received from the payment gateway server 110 may be stored in the EV server 112. Further, based on the received information, the generating module 222 may be configured to generate a notification indicating information associated with the payment transaction received from the payment gateway server 110.

The information associated with the payment transaction may be indicative of a name of payer, i.e., the user, a transaction ID, a date of transaction, a time of transaction, an amount of transaction, and information associated with the payment gateway server 110. The communication module 222 may be configured to communicate the notification indicating information associated with payment transaction to the guest terminal 104 and the administrator terminal 106. In an embodiment, each of the guest terminal 104 and the administrator terminal 106 may be operated to access the received notification via the application 202. In an embodiment,

The processor 204 may be configured to determine an information associated with the guest terminal 104, the charging terminal 102 in communication with the guest terminal 104, and the payment transaction. As mentioned earlier, the guest terminal 104 may be initially paired with the charging terminal 102 via the application 202 installed in the guest terminal 104. Upon pairing, the receiving module 218 may be configured to retrieve a guest ID associated with the guest terminal 104 and the outlet ID associated with the charging terminal 102 in communication with the guest terminal 104. In an embodiment, the receiving module 218 may be configured to retrieve the guest ID and the outlet ID stored in the EV server 112. The communication module 222 may be configured to display, at the administrator terminal 106, the guest ID of the guest terminal 104 and the outlet ID of the charging terminal 102 on a user interface of the application 202.

Further, the determining module 216 may be configured to determine, at the administrator terminal 106, a status of payment transaction and the information associated with payment transaction based on the generated notification. The status of payment transaction may indicate one of a successful transaction and an unsuccessful transaction. In an embodiment, the communication module 222 may be configured to display a notification on a user interface of an application installed in the administrator terminal 106 based on the determined information associated with payment transaction. The notification may be indicative of the status of payment transaction, i.e., successful transaction or unsuccessful transaction.

In an embodiment, the communication module 222 may be configured to display the guest ID associated with the guest terminal 104, the outlet ID of the charging terminal 102 in communication with the guest terminal 104, the status of payment transaction, and the information associated with the payment transaction on a user interface of the application 202 at the administrator terminal 106.

Further, the processor 204 may be configured to generate a key to enable charging from the charging terminal 102 based on the determined information, i.e., information associated with payment transaction, the status of payment, the outlet ID, and the guest ID. In an embodiment, upon completion of the payment transaction, the receiving module 218 may be configured to receive, from the guest terminal 104, a request indicative of initiating charging from the charging terminal 102. The guest terminal 104 may be operated by the user to generate the request via the application 202 installed in the guest terminal 104.

In such an embodiment, to generate the key to enable charging from the charging terminal 102, the determining module 216 may be configured to determine whether the status of payment transaction is indicative of successful transaction. As explained earlier, the communication module 222 may be configured to display the status of payment transaction on a user interface of the application 202 at the administrator terminal 106. In an embodiment, the generating module 220 may be configured to generate a notification indicative of successful transaction based on the determined status of payment transaction. The communication module 222 may be configured to display, at the administrator terminal 106, the notification indicative of the status of payment transaction, such as successful transaction or unsuccessful transaction.

Further, the communication module 222 may be configured to display, at the administrator terminal 106, a user-selectable button on the user interface of the application 202 for enabling charging at the charging terminal, if the status of payment transaction is indicative of successful transaction. The receiving module 218 may be configured to receive, by the administrator terminal 106, an input indicative of enabling charging at the charging terminal 102 via the user-selectable button displayed on the user interface of the application 202. In the present embodiment, the administrator terminal 106 may be operated by the administrator to provide the input via the user-selectable button on the user interface of the application 202.

The generating module 220 may generate the key to enable charging from the charging terminal 102 based on the received input. In an embodiment, the key comprises an instruction to enable charging from the charging terminal 102 for a predetermined time based on the information associated with payment transaction. The communication module 222 may communicate the key to the guest terminal 104 which further sends the key to the paired charging terminal 102 for initiating charging operation. Alternatively, the administrator terminal 106 may be operated by the administrator to provide an input indicative of disabling charging at the charging terminal 102 via the user interface of the application 202. Based on the input, the generating module 220 may generate an output to disable charging from the charging terminal 102.

In another embodiment, to generate the key to enable charging from the charging terminal 102, the determining module 216 may be configured to determine whether the status of payment transaction is indicative of successful transaction. Further, in the present embodiment, the generating module 220 may be configured to generate the key to enable charging from the charging terminal 102 without requiring any input from the administrator, if the status of payment transaction is indicative of successful transaction. The key may include an instruction to enable charging from the charging terminal 102 for a predetermined time based on the information associated with payment transaction. The communication module 222 may communicate the key to the guest terminal 104 which further sends the key to the paired charging terminal 102 for initiating charging operation.

In yet another embodiment, if a payment option, i.e., payment via third-party applications, may be opted by the user via the application 202 installed in the guest terminal 104, then the administrator may manually verify the status of payment transaction and information associated with the payment transaction. Upon confirming that the status of payment transaction is successful, the administrator terminal 106 may be operated, by the administrator, to access the application 202 for enabling access to the charging terminal 102. In the present embodiment, the receiving module 218 may be configured to receive, by the administrator terminal 106, an input, via the user interface of the application 202, indicative of enabling charging at the charging terminal 102. The input may be indicative of an amount received from the user via the guest terminal 104.

In such an embodiment, subsequently, the generating module 220 may generate the key to enable charging from the charging terminal 102 based on the received input. In an embodiment, the key comprises an instruction to enable charging from the charging terminal 102 for a predetermined time based on the amount received from the user. The communication module 222 may communicate the key to the guest terminal 104 which further sends the key to the paired charging terminal 102 for initiating charging operation. Alternatively, the administrator terminal 106 may be operated by the administrator to provide an input indicative of disabling charging at the charging terminal 102 via the user interface of the application 202. Based on the input, the generating module 220 may generate an output to disable charging from the charging terminal 102.

Figure 3 illustrates a flowchart depicting an implementation of the system 100 for accessing the charging terminal 102, according to an embodiment of the present disclosure. For the sake of brevity, details of the present disclosure that are explained in detail in the description of Figure 1 and Figure 2 are not explained in detail in the description of Figure 3. Referring to Figure 3, at step 302, the guest terminal 104 may establish communication with the charging terminal 102 and subsequently receive the outlet ID associated with the charging terminal 102. Further, the guest terminal 104 may receive the set of payment information for accessing the charging terminal 102. At step 304, the system 100 may communicate the payment request from the guest terminal 104 to the payment gateway server 110.

Upon completion of the payment transaction, the system 100 may communicate the notification indicating information associated with payment transaction received from the payment gateway server 110 to each of the guest terminal 104 and the administrator terminal 106. Further, at step 306, the system 100 may receive the request, from the guest terminal 104, indicative of initiating charging from the charging terminal 102. Upon receiving the request, the system 100 may determine the status of payment transaction, information associated with payment transaction, the guest ID, and the outlet ID.

Subsequently, the system 100 may generate the notification indicating the status of payment transaction and display, at the administrator terminal 106, the information associated with payment transaction, the guest ID, and the outlet ID. Based on the status of payment transaction, the system 100 may display the user-selectable button on a user interface of the application installed in the administrator terminal 106. The administrator may provide the input, via the user-selectable button, to generate the key for enabling the charging from the charging terminal 102.

Figure 4 illustrates a flowchart depicting an implementation of the system 100 for accessing the charging terminal 102, according to another embodiment of the present disclosure. For the sake of brevity, details of the present disclosure that are explained in detail in the description of Figure 1, Figure 2, and Figure 3 are not explained in detail in the description of Figure 4. Referring to Figure 4, at step 402, the guest terminal 104 may establish communication with the charging terminal 102 and subsequently, receive the outlet ID associated with the charging terminal 102. Further, the guest terminal 104 may receive the set of payment information for accessing the charging terminal 102. At step 404, the system 100 may communicate the payment request from the guest terminal 104 to the payment gateway server 110.

Upon completion of the payment transaction, the system 100 may communicate the notification indicating information associated with payment transaction received from the payment gateway server 110 to each of the guest terminal 104 and the administrator terminal 106. Further, at step 406, the system 100 may receive the request, from the guest terminal 104, indicative of initiating charging from the charging terminal 102. Upon receiving the request, the system 100 may determine the status of payment transaction, information associated with payment transaction, the guest ID, and the outlet ID.

Subsequently, the system 100 may generate the notification indicating the status of payment transaction and display, at the administrator terminal 106, the information associated with payment transaction, the guest ID, and the outlet ID. Based on the status of payment transaction, the system 100 may generate the key for enabling the charging from the charging terminal 102 and subsequently, send the key to the charging terminal 102 for enabling charging of the electric vehicle.

Figure 5 illustrates a flowchart depicting an implementation of the system 100 for accessing the charging terminal 102, according to yet another embodiment of the present disclosure. For the sake of brevity, details of the present disclosure that are explained in detail in the description of Figure 1, Figure 2, Figure 3, and Figure 4 are not explained in detail in the description of Figure 5. Referring to Figure 5, at step 502, the guest terminal 104 may establish communication with the charging terminal 102 and subsequently, receive the outlet ID associated with the charging terminal 102. Further, the guest terminal 104 may receive the set of payment information for accessing the charging terminal 102. At step 504, the guest terminal 104 may communicate the payment request via one of the third-party applications based on the set of payment information.

Upon completion of the payment transaction, the administrator can determine, at the administrator terminal 106, the status of payment based on a notification indicative of information associated with payment transaction received from one of the third-party applications. Further, at step 506, the system 100 may receive the request, from the guest terminal 104, indicative of initiating charging from the charging terminal 102. Upon receiving the request, the system 100 may determine the guest ID and the outlet ID based on the received request. Subsequently, the system 100 may generate the notification, at the administrator terminal 106, indicating the guest ID and the outlet ID. The administrator may manually verify the status of payment transaction and whether the payment transaction is completed by the guest terminal associated with the guest ID as indicated by the generated notification. Based on manual verification regarding the status of payment transaction, the administrator may provide the input, via the user interface of the application 202, to generate the key for enabling the charging from the charging terminal 102.

Figures 6a and 6b illustrate exemplary user interfaces of the guest terminal 104 for accessing the charging terminal 102, according to an embodiment of the present disclosure. For the sake of brevity, details of the present disclosure that are explained in detail in the description of Figure 1, Figure 2, Figure 3, Figure 4, and Figure 5 are not explained in detail in the description of Figures 6a-6b. Referring to Figure 6a, a user interface 602-1 of the application 202 installed in the user terminal 104 depicts a list 604 of the charging terminals 102 available to be paired with the user terminal 104. The user may select one of the charging terminals 102 from the list 604 to initiate pairing and subsequently, to provide a request for charging the electric vehicle.

Referring to Figure 6b, the user may select the charging terminal 102, such as the EV charging terminal-1 from the list 604 depicted in the user interface 602-1 of Figure 6a. Based on the selection, a user interface 602-2 of the application 202 may display details 606, such as the outlet ID of the selected charging terminal 102 and payment information associated with the selected charging terminal 102. Further, the user interface 602-2 may also display a user interactable field, “Enter Amount”, for providing information associated with an amount to be paid for accessing the charging terminal 102. The user interface 602-2 may display a list 608 of the payment options which can be selected by the user to initiate the payment transactions. Upon selection of one of the payment options, the transaction may be initiated and subsequently, a notification may be displayed on the user interface to indicate information associated with the payment transaction.

Figures 7a and 7b illustrate exemplary user interfaces of the administrator terminal 106 for allowing the guest to access the charging terminal 102, according to an embodiment of the present disclosure. For the sake of brevity, details of the present disclosure that are explained in detail in the description of Figure 1, Figure 2, Figure 3, Figure 4, Figure 5, and Figures 6a-6b are not explained in detail in the description of Figures 7a-7b.

Referring to Figure 7a, upon completion of the payment transaction, a user interface 702-1 of the application 202 installed in the administrator terminal 106 may display details 704 of the transaction, such as transaction ID, date of transaction, time of transaction, payee, and amount of transaction. Referring to Figure 7b, based on the status of payment transaction, a user interface 702-2 may display a user-selectable button 706 for generating the key to enable charging from the charging terminal 102, such as EV charging terminal-1. Further, the user interface 702-2 may also display information 708, such as the guest ID, the outlet ID, amount paid, charging time, and charging capacity.

Figure 8 illustrates a flowchart depicting a method 800 for accessing the charging terminal 102, according to an embodiment of the present disclosure. For the sake of brevity, details of the present disclosure that are explained in detail in the description of Figure 1, Figure 2, Figure 3, Figure 4, Figure 5, Figures 6a-6b, and Figures 7a-7b are not explained in detail in the description of Figure 8.

At step 802, the method 800 includes retrieving, at the guest terminal 104 in communication with the charging terminal 102, the set of payment information associated with an administrator of the charging terminal 102. At step 804, the method 800 includes sending, from the guest terminal 104, the payment request to the payment gateway server 110 to initiate the payment based on the set of payment information. In an embodiment, the payment request may include data associated with at least a transaction amount to be paid for accessing the charging terminal 102.

At step 806, the method 800 includes identifying, at each of the guest terminal 104 and the administrator terminal 106, the notification indicating information associated with payment transaction received from the payment gateway server 110. At step 808, the method 800 includes determining, at the administrator terminal 106, information associated with the guest terminal 104, the charging terminal 102 in communication with the guest terminal 104, and payment transaction. In an embodiment, the method may include receiving, from the guest terminal 104, a request indicative of initiating charging from the charging terminal 102. The method 800 may include determining, at the administrator terminal 106, the status of payment transaction and information associated with payment transaction based on the generated notification.

The status of payment transaction may indicate one of a successful transaction and an unsuccessful transaction. Further, the method 800 may include retrieving, at the administrator terminal 106, a guest ID associated with the guest terminal 104 and an outlet ID associated with the charging terminal 102 in communication with the guest terminal 104. In an embodiment, the information associated with the payment transaction may be indicative of a name of payer, a transaction ID, a date of transaction, a time of transaction, an amount of transaction, and information associated with the payment gateway server 110.

At step 810, the method 800 includes generating the key to enable charging from the charging terminal 102 based on the determined information. In one embodiment, the method 800 includes determining whether the status of payment transaction is indicative of successful transaction. Further, the method 800 includes generating the notification indicative of successful transaction based on the determined status of payment transaction. The method 800 includes displaying, at the administrator terminal 106, the user-selectable button on the user interface for enabling charging at the charging terminal 102 if the status of payment transaction is indicative of successful transaction.

Further, in such an embodiment, the method 800 includes receiving, by the administrator terminal 106, an input indicative of enabling charging at the charging terminal 102 via the user-selectable button. The method 800 includes generating the key to enable charging from the charging terminal 102 based on the received input. The key comprises the instruction to enable charging from the charging terminal 102 for the predetermined time based on the information associated with payment transaction.

In another embodiment, the method 800 includes determining whether the status of payment transaction is indicative of successful transaction. Further, the method 800 includes generating the key to enable charging from the charging terminal 102 if the status of payment transaction is indicative of successful transaction.

Figure 9 illustrates a flowchart depicting a method 900 for accessing the charging terminal 102, according to another embodiment of the present disclosure. For the sake of brevity, details of the present disclosure that are explained in detail in the description of Figure 1, Figure 2, Figure 3, Figure 4, Figure 5, Figures 6a-6b, Figures 7a-7b, and Figure 8 are not explained in detail in the description of Figure 9.

At step 902, the method 900 includes retrieving, at the guest terminal 104 in communication with the EV charging terminal 102, the set of payment information associated with an administrator of the EV charging terminal 102.

At step 904, the method 900 includes initiating, from the guest terminal 104, the payment request based on the set of payment information.

At step 906, the method 900 includes determining, at the administrator terminal 106, the status of payment transaction based on the notification indicative of information associated with payment transaction.

At step 908, the method 900 includes generating the key to enable charging from the EV charging terminal 102 based on the status of the payment.

As would be gathered, the present disclosure offers the system 100 and the method 800 for accessing the charging terminal 102. Firstly, the system 100 and the method 800 allow the administrator to remotely monitor the payment transaction received from the registered or unregistered users for availing facilities of the charging terminal 102. Accordingly, the administrator can remotely confirm the receipt of payment and subsequently, enable charging from the charging terminal 102. As explained earlier, the administrator can remotely enable or disable charging from the charging terminal 102 based on the payment transaction from the user. This eliminates the requirement of physical presence of the administrator at the charging terminal 102 for enabling the charging and confirming the payment transaction.

Further, as explained earlier, the system 100 can enable both registered and unregistered users to perform payment transaction for availing facilities of the charging terminal 102. The unregistered user can simply perform payment transaction via the application 202 without registering themselves as registered users. This substantially enhances the overall user experience for availing facilities of the charging terminal 102. Further, the system 100 and the method 800 allows the administrator to remotely monitor payment transaction performed by the unregistered user and accordingly, enable charging from the charging terminal 102 for such unregistered user. Further, this eliminates the requirement of physically visiting the charging terminal 102 by the administrator for enabling the unregistered user to connect with the charging terminal 102 for initiating the payment transaction.

Therefore, the system 100 and the method 800 of the present disclosure are flexible in implementation, less complex, cost-effective, convenient, operation-effective, secure in operation, and offer significant convenience to the administrator and the users.

While specific language has been used to describe the present subject matter, any limitations arising on account thereto, are not intended. As would be apparent to a person in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein. The drawings and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. ,CLAIMS:We Claim:
1. A method for accessing an Electric Vehicle (EV) charging terminal (102), the method comprising:
retrieving, at a guest terminal (104) in communication with the EV charging terminal (102), a set of payment information associated with an administrator of the EV charging terminal (102);
sending, from the guest terminal (104), a payment request to a payment gateway server (110) to initiate a payment based on the set of payment information;
generating, at each of the guest terminal (104) and an administrator terminal (106), a notification indicating information associated with payment transaction received from the payment gateway server (110);
determining information associated with the guest terminal (104), the EV charging terminal (102) in communication with the guest terminal (104), and payment transaction; and
generating a key to enable charging from the EV charging terminal (102) based on the determined information.

2. The method as claimed in claim 1, wherein the payment request comprises data associated with at least a transaction amount to be paid for accessing the EV charging terminal (102).

3. The method as claimed in claim 1, wherein determining information associated with the guest terminal (104), the EV charging terminal (102) in communication with the guest terminal (104), and payment transaction comprises:
receiving, from the guest terminal (104), a request indicative of initiating charging from the EV charging terminal (102);
determining, at the administrator terminal (106), a status of payment transaction and information associated with payment transaction based on the generated notification, wherein the status of payment transaction indicates one of a successful transaction and an unsuccessful transaction; and
retrieving, at the administrator terminal (106), a guest ID associated with the guest terminal (104) and an outlet ID associated with the EV charging terminal (102) in communication with the guest terminal (104).

4. The method as claimed in claim 3, wherein the information associated with the payment transaction is indicative of a name of payer, a transaction ID, a date of transaction, a time of transaction, an amount of transaction, and information associated with the payment gateway (110).

5. The method as claimed in claim 3 comprising displaying a notification on a user interface of an application installed in the administrator terminal (106) based on the determined information associated with payment transaction, wherein the notification is indicative of the status of payment transaction.

6. The method as claimed in any of claims 2 to 5, wherein generating the key to enable charging from the EV charging terminal (102) comprises:
determining whether the status of payment transaction is indicative of successful transaction;
generating a notification indicative of successful transaction based on the determined status of payment transaction;
displaying, at the administrator terminal (106), a user-selectable button on a user interface for enabling charging at the EV charging terminal (102) if the status of payment transaction is indicative of successful transaction;
receiving, from the administrator terminal (106), an input indicative of enabling charging at the EV charging terminal (102) via the user-selectable button; and
generating the key to enable charging from the EV charging terminal (102) based on the received input, wherein the key comprises an instruction to enable charging from the EV charging terminal (102) for a predetermined time based on the information associated with payment transaction.

7. The method as claimed in any of claims 2 to 5, wherein generating the key to enable charging from the EV charging terminal (102) comprises:
determining whether the status of payment transaction is indicative of successful transaction; and
generating the key to enable charging from the EV charging terminal (102) if the status of payment transaction is indicative of successful transaction, wherein the key comprises an instruction to enable charging from the EV charging terminal (102) for a predetermined time based on the information associated with payment transaction.

8. The method as claimed in any of claims 6 and 7 comprising sending the key to the EV charging terminal (102) which is in communication with the guest terminal (104).

9. A system (100) for accessing an Electric Vehicle (EV) charging terminal (102), the system (100) comprising:
at least one processor (204) configured to:
retrieve a set of payment information associated with an administrator of the EV charging terminal (102);
send a payment request to a payment gateway server (100) to initiate a payment based on the set of payment information;
generate a notification indicating information associated with payment transaction received from the payment gateway server (100);
determine information associated with a guest terminal (104), the EV charging terminal (102) in communication with the guest terminal (104), and payment transaction; and
generate a key to enable charging from the EV charging terminal (102) based on the determined information.

10. The system as claimed in claim 9, wherein the payment request comprises data associated with at least a transaction amount to be paid for accessing the EV charging terminal (102).

11. The system as claimed in claim 9, wherein to determine information associated with the guest terminal (104), the EV charging terminal (102), and payment transaction, the at least one processor (204) is configured to:
receive, from the guest terminal (104), a request indicative of initiating charging from the EV charging terminal (102);
determine, at an administrator terminal (106), a status of payment transaction and information associated with payment transaction based on the generated notification, wherein the status of payment transaction indicates one of a successful transaction and an unsuccessful transaction; and
retrieve, at the administrator terminal (106), a guest ID associated with the guest terminal (104) and an outlet ID associated with the EV charging terminal (102) in communication with the guest terminal (104).

12. The system as claimed in claim 11, wherein the information associated with the payment transaction is indicative of a transaction ID, a date of transaction, a time of transaction, an amount of transaction, and information associated with the payment gateway sever (100).

13. The system as claimed in claim 11, wherein the at least one processor (204) is configured to display a notification on a user interface of an application installed in the administrator terminal (106) based on the determined information associated with payment transaction, wherein the notification is indicative of the status of payment transaction.

14. The system as claimed in any of claims 11 to 13, wherein to generate the key to enable charging from the EV charging terminal (102), the at least one processor (204) is configured to:
determine whether the status of payment transaction is indicative of successful transaction;
generate a notification indicative of successful transaction based on the determined status of payment transaction;
display, at the administrator terminal (106), a user-selectable button on a user interface for enabling charging at the EV charging terminal (102) if the status of payment transaction is indicative of successful transaction;
receive, from the administrator terminal (106), an input indicative of enabling charging at the EV charging terminal (102) via the user-selectable button; and
generate the key to enable charging from the EV charging terminal (102) based on the received input, wherein the key comprises an instruction to enable charging from the EV charging terminal (102) for a predetermined time based on the information associated with payment transaction.

15. The system as claimed in any of claims 11 to 13, wherein to generate the key to enable charging from the EV charging terminal (102), the at least one processor (204) is configured to:
determine whether the status of payment transaction is indicative of successful transaction; and
generate the key to enable charging from the EV charging terminal (102) if the status of payment transaction is indicative of successful transaction, wherein the key comprises an instruction to enable charging from the EV charging terminal (102) for a predetermined time based on the information associated with payment transaction.

16. The system as claimed in any of claims 14 or 15, wherein the at least one processor (204) is configured to send the key to the EV charging terminal (102) which is in communication with the guest terminal (104).

17. The system as claimed in any of claims 9 to 16 comprising an application adapted to be installed in the administrator terminal (106) and the guest terminal (104), wherein functionalities of the system (100) are accessed through the application.

18. A method for accessing an Electric Vehicle (EV) charging terminal (102), the method comprising:
retrieving, at a guest terminal (104) in communication with the EV charging terminal (102), a set of payment information associated with an administrator of the EV charging terminal (102);
initiating, from the guest terminal (104), a payment request based on the set of payment information;
determining, at the administrator terminal (106), a status of payment transaction based on a notification indicative of information associated with payment transaction; and
generating a key to enable charging from the EV charging terminal (102) based on the status of the payment.

19. The method as claimed in claim 18, wherein initiating the payment request comprises:
initiating the payment request via one of third-party applications, installed in the guest terminal (104), based on the set of payment information.

20. The method as claimed in claim 18, wherein determining the status of payment transaction comprises:
determining, at the administrator terminal (106), the status of payment transaction based on the notification indicative of information associated with payment transaction received from one of the third-party applications installed in the administrator terminal (106).

21. The method as claimed in claim 18 further comprising:
receiving a request, from the guest terminal (104), indicative of initiating charging from the EV charging terminal (102);
determining a guest ID associated with the guest terminal (104) and an outlet ID associated with the EV charging terminal (102) based on the received request;
generating a notification, at the administrator terminal (106), indicating the guest ID and the outlet ID; and
verifying, by an administrator, the status of payment transaction and whether the payment transaction is completed by the guest terminal (104) associated with the guest ID as indicated by the generated notification; and
generating the key for enabling the charging from the EV charging terminal (102) if the status of payment indicates a successful transaction.