Method and system for automatic payment method transmission to merchants

Abstract

The present disclosure relates to a payment processing system and method for automatic payment method transmission to a merchant. The method includes providing a list of multiple merchants to a user to receive a user selection of at least one of the multiple merchants for conducting one or more transactions. In response to the user selection, the method includes authenticating the user based on user details provided by the user to authorize the user to establish one or more payment methods with at least one of the multiple merchants selected by the user. The method then includes transmitting the user details, user authorization, and the one or more payment methods established by the user to a payment processing device associated with each of the multiple merchants selected by the user. Finally, the method includes receiving a merchant confirmation of acceptance of the one or more payment methods established by the user from at least one of the multiple merchants selected by the user. In some embodiments, the above process may also be used to remove one or more payment methods established with the multiple merchants selected by the user and / or to remove a merchant from the list of the multiple merchants selected by the user.

Description

[Technical Field]

[0001] This disclosure relates to electronic commerce. In particular, but not by way of limitation, this disclosure relates to systems and computer-implemented methods for automatic payment method transmission to merchants. [Background technology]

[0002] Currently, when a user gets a new credit card, the user must manually add the card details on the online merchant platform before conducting a transaction. This creates inconvenience for the user as the user must perform these steps on every merchant platform where the user conducts a transaction. Similarly, when the card expires and / or the user is issued a new card, the user must again manually enter the details. This creates friction between the user and the merchant during the payment lifecycle.

[0003] On the other hand, storing payment details on the merchant platform increases the likelihood of multiple attacks such as shoulder surfing and details being stolen. Therefore, existing approaches cause inconvenience to both the merchant and the paying user. Therefore, there is a need for an easy and convenient method for automatic payment method transmission to merchants.

[0004] The information disclosed in the background section of this disclosure is merely to enhance understanding of the general background of the disclosure and should not be taken as an acknowledgment or any form of suggestion that this information forms prior art already known to those skilled in the art. Summary of the Invention [Means for solving the problem]

[0005] Additional features and advantages are realized through the techniques of the present disclosure.Other embodiments and aspects of the present disclosure are described in detail herein and are considered a part of the claimed disclosure.

[0006] Disclosed herein is a computer-implemented method for automatic payment method transmission to a merchant, the method may include providing a list of multiple merchants to a user to receive a user selection regarding at least one of the multiple merchants for conducting one or more transactions. The method may further include authenticating a user based on user details provided by the user to authorize the user to establish one or more payment methods with at least one of the multiple merchants selected by the user. The method may further include transmitting the user details, user authorization, and the one or more payment methods established by the user to a payment processor associated with each of the multiple merchants selected by the user. Finally, the method may include receiving merchant confirmation regarding acceptance of the one or more payment methods established by the user from at least one of the multiple merchants selected by the user.

[0007] Furthermore, in one embodiment, the present disclosure may include a payment processing system. The payment processing system may include a processor and a memory. The memory may be communicatively coupled to the processor and may store processor-executable instructions that, when executed, cause the processor to provide a list of multiple merchants to a user to receive a user selection regarding at least one of the multiple merchants for conducting one or more transactions. The instructions may further cause the processor to authenticate a user based on user details provided by the user to permit the user to establish one or more payment methods with at least one of the multiple merchants selected by the user. The instructions may further cause the processor to transmit the user details, user authorization, and the one or more payment methods established by the user to a payment processing device associated with each of the multiple merchants selected by the user. Finally, the instructions may cause the processor to receive merchant confirmation regarding acceptance of the one or more payment methods established by the user from at least one of the multiple merchants selected by the user.

[0008] Furthermore, in one embodiment, the present disclosure may include a non-transitory computer-readable medium including instructions stored thereon, which, when processed by at least one processor, cause a payment processing system to perform an action including providing a list of multiple merchants to a user to receive a user selection of at least one of the multiple merchants for conducting one or more transactions. The instructions may further cause the payment processing system to authenticate a user based on user details provided by the user to permit the user to establish one or more payment methods with at least one of the multiple merchants selected by the user. The instructions may further cause the payment processing system to transmit the user details, user authorization, and the one or more payment methods established by the user to a payment processor associated with each of the multiple merchants selected by the user. Finally, the instructions may cause the payment processing system to receive a merchant confirmation regarding acceptance of the one or more payment methods established by the user from at least one of the multiple merchants selected by the user.

[0009] Disclosed herein is a computer-implemented method for automatic payment method transmission to merchants, the method may include providing a list of multiple merchants to a user to receive a user selection for at least one of the multiple merchants for deleting one or more payment methods established at the multiple merchants. The method may further include authenticating a user based on user details provided by the user to authorize the user to delete one or more payment methods for at least one of the multiple merchants selected by the user. The method may further include transmitting the user details, user authorization, and the one or more payment methods to be deleted to a payment processor associated with each of the multiple merchants selected by the user. Finally, the method may include receiving a merchant confirmation of the deletion of the one or more payment methods from at least one of the multiple merchants selected by the user.

[0010] Furthermore, in one embodiment, the present disclosure may include a payment processing system. The payment processing system may include a processor and a memory. The memory may be communicatively coupled to the processor and may store processor-executable instructions that, when executed, cause the processor to provide a list of multiple merchants to a user to receive a user selection for at least one of the multiple merchants for deleting one or more payment methods established at the multiple merchants. The instructions may further cause the processor to authenticate a user based on user details provided by the user to authorize the user to delete one or more payment methods for at least one of the multiple merchants selected by the user. The instructions may further cause the processor to transmit the user details, the user authorization, and the one or more payment methods to be deleted to a payment processing device associated with each of the multiple merchants selected by the user. Finally, the instructions may cause the processor to receive merchant confirmation regarding the deletion of the one or more payment methods from at least one of the multiple merchants selected by the user.

[0011] Furthermore, in one embodiment, the present disclosure may include a non-transitory computer-readable medium including instructions stored thereon, which, when processed by at least one processor, cause a payment processing system to perform an operation including providing a list of multiple merchants to a user to receive a user selection for at least one of the multiple merchants for removing one or more payment methods established with the multiple merchants. The instructions may further cause the payment processing system to authenticate a user based on user details provided by the user to authorize the user to remove one or more payment methods for at least one of the multiple merchants selected by the user. The instructions may further cause the payment processing system to transmit the user details, the user authorization, and the one or more payment methods to be removed to a payment processing device associated with each of the multiple merchants selected by the user. Finally, the instructions may cause the payment processing system to receive a merchant confirmation regarding the removal of the one or more payment methods from at least one of the multiple merchants selected by the user.

[0012] The above summary is merely illustrative and is not intended to be in any way limiting. In addition to the exemplary aspects, embodiments, and features described above, further aspects, embodiments, and features may become apparent by reference to the drawings and the following detailed description.

[0013] The novel features and characteristics of the present disclosure will be set forth in the appended claims. However, the disclosure itself, as well as its preferred modes of use, further objects and advantages, may best be understood by reference to the following detailed description of exemplary embodiments, read in conjunction with the accompanying drawings. The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate illustrative embodiments and, together with the description, serve to explain the principles disclosed. In the drawings, the leftmost digit(s) of a reference number identifies the figure in which the reference number first appears. One or more embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which like reference numerals represent like elements. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 illustrates an exemplary environment illustrating a method for automatic payment method transmission to a merchant according to some embodiments of the present disclosure. [Figure 2] FIG. 1 is a detailed block diagram of a payment processing system according to some embodiments of the present disclosure. [Figure 3A] 1 is a flowchart illustrating a method for automatic payment method transmission to a merchant according to some embodiments of the present disclosure. [Figure 3B] 1 is a flowchart illustrating a method for automatic payment method transmission to a merchant according to some embodiments of the present disclosure. [Figure 4] FIG. 1 shows an illustrative scenario illustrating authentication of a user according to some embodiments of the present disclosure. [Figure 5] FIG. 1 is a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0015] It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it can be appreciated that any flowcharts, flow diagrams, state diagrams, pseudocode, etc., may be substantially represented in a computer-readable medium and represent various processes that may be executed by a computer or processor, whether or not such a computer or processor is explicitly depicted.

[0016] In this document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

[0017] While the present disclosure is susceptible to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the drawings and may be described in detail below. It is to be understood, however, that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is intended to cover all modifications, equivalents, and alternatives falling within the scope of the present disclosure.

[0018] The terms "comprises," "includes," "comprising," "including," or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a configuration, device, or method comprising a series of components or steps includes not only those components or steps, but may also include other components or steps not expressly listed or inherent in such configuration or device or method. In other words, one or more elements in a system or apparatus preceded by "comprises" or "including" does not, without further constraints, exclude the presence of other or additional elements in the system or apparatus.

[0019] The present disclosure relates to a payment processing system and computer-implemented method for automatic payment method transmission to merchants. In some embodiments, the method includes providing a list of multiple merchants to a user to receive a user selection of at least one of the multiple merchants for conducting one or more transactions. In response to the user selection, the method includes authenticating the user based on user details provided by the user to authorize the user to establish one or more payment methods with at least one of the multiple merchants selected by the user. Subsequently, the method includes transmitting the user details, user authorization, and the one or more payment methods established by the user to a payment processing device associated with each of the multiple merchants selected by the user. Finally, the method includes receiving merchant confirmation of acceptance of the one or more payment methods established by the user from at least one of the multiple merchants selected by the user.

[0020] In some embodiments, the disclosed payment processing system and computer-implemented method provide a convenient way for users to conduct transactions on merchant platforms. Moreover, the present disclosure proposes storing card details on the payment processing system, thereby reducing the workload on payment processors associated with merchants. Furthermore, the present disclosure helps merchants reduce costs associated with authenticating users. Also, according to the present disclosure, user details and transaction details are stored at the issuer, helping to eliminate risks associated with transactions.

[0021] In the following detailed description of embodiments of the present disclosure, reference is made to the accompanying drawings which form a part hereof, and in which are shown by way of illustration specific embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it should be understood that other embodiments may be utilized and changes may be made without departing from the scope of the disclosure. The following description, therefore, is not to be taken in a limiting sense.

[0022] FIG. 1 shows an exemplary environment illustrating a method for automatic payment method transmission to a merchant according to some embodiments of the present disclosure.

[0023] In some implementations, environment 100 includes one or more payment processors 109, namely, payment processor 1 1091, ..., payment processor N 109 N (collectively referred to as payment processor 109) associated with a plurality of merchants, namely Merchant A 103 A , Member Store B 103 B ,…, member store N 103 N (collectively referred to as multiple merchants 103), a user 105, and a payment processing system 101. As an example, a user 105 may be registered with the payment processing system 101 and intend to conduct one or more transactions with at least one of the multiple merchants 103. The multiple merchants 103 may be pre-registered with the payment processing system.

[0024] In some embodiments, the payment processing system 101 may be a computing system configured to perform technical processes including providing the user 105 with a list of multiple merchants 103, authenticating the user 105, transmitting user details, user authorization, and one or more payment methods configured by the user 105 to the payment processor 109, and receiving merchant confirmation from the merchant 103. Here, the payment processing system 101 may be an issuer entity such as, without limitation, a bank, a payment gateway, a payment server, etc. In some embodiments, the user 105 may interact with the payment processing system 101 using a medium such as, for example, a mobile application and / or a web application installed on the user's 105 computing device. By way of example, the computing device may include, without limitation, a smartphone, a personal digital assistant (PDA), or a desktop computer.

[0025] In some embodiments, the user 105 may be provided with a list of multiple merchants 103, as shown in step 111, to receive a user selection 107 regarding at least one of the multiple merchants 103. In some embodiments, the multiple merchants 103 may be displayed to the user 105 on a computing system associated with the user 105. By way of example, the computing system associated with the user 105 may include, without limitation, a smartphone, a personal digital assistant (PDA), or a desktop computer. In some embodiments, the multiple merchants 103 may be pre-registered with the payment processing system 101 for conducting one or more transactions initiated by the user 105 on the merchant platform. In some embodiments, the multiple merchants 103 may be authenticated by the payment processing system 101 before providing the user 105 with the list of multiple merchants 103. In some embodiments, along with the list of merchants 103, the payment processing system 101 may also provide the user 105 with merchant details as well as information related to the types of payment methods accepted by the merchant 103. In some embodiments, payment method types may include, without limitation, card-based transactions, Unified Payment Interface (UPI) transactions, cryptocurrency-based transactions, and the like.

[0026] In some embodiments, upon receiving the user selection 107, the payment processing system 101 may authenticate the user 105 based on the user details provided by the user 105 to allow the user 105 to set up one or more payment methods with at least one of the multiple merchants selected by the user 105. In some embodiments, the user details may include pre-registered user authentication information pre-registered with the merchant, such as, without limitation, the user's 105 name, the user's 105 phone number, credit and / or debit card number, UPI identifier (ID), cryptocurrency wallet ID, email ID, username registered with the merchant platform, etc. As an example, to authenticate the user 105, the payment processing system 101 may send a one-time password (OTP) to the user 105 at the user's registered phone number and / or registered email ID. As an example, when a user 105 selects a card transaction as a payment method, the payment processing system 101 may request the user 105 to provide card details such as the card number, the name on the card, the card expiration date, the card verification value (CVV), the personal identification number (PIN), etc.

[0027] The payment processing system 101 may then validate the payment method(s) set by the user 105 based on details associated with the payment method(s).

[0028] In some embodiments, upon authenticating the user 105, the payment processing system 101 may transmit the user details, user authorizations, and one or more payment methods established by the user 105 to a payment processor 109 associated with each of a plurality of merchants 103 selected by the user 105. In some embodiments, the payment processor 109 associated with each of the plurality of merchants 103 may be a computing system such as, without limitation, a desktop computer or a server computing system. Here, the payment processor 109 associated with each of the plurality of merchants 103 may be an issuer entity associated with the plurality of merchants 103, such as, without limitation, a bank, a payment gateway, a payment server, etc. In some embodiments, the user details transmitted to the payment processor 109 may consist of details used by the user 105 to register with the merchant 103. In some embodiments, the payment processing system 101 may generate a token using pre-defined techniques for details associated with the one or more payment methods established by the user 105. The payment processing system 101 may then transmit the token to each of the plurality of merchants 103 selected by the user 105.

[0029] In some embodiments, after submitting the user details, user authorization, and one or more payment methods, the payment processing system 101 may receive a merchant confirmation regarding acceptance of the one or more payment methods set by the user 105 from at least one of the multiple merchants 103 selected by the user 105. In some embodiments, the merchant confirmation is received when the user details provided by the user 105 match pre-registered user details stored at at least one of the multiple merchants 103 selected by the user 105. In some embodiments, the merchant confirmation is generated in response to successful authentication of the user 105 by a payment processor 109 associated with at least one of the multiple merchants 103 selected by the user 105. In some embodiments, upon receiving the merchant confirmation, the user 105 may initiate one or more transactions with at least one of the multiple merchants 103 selected by the user 105 without having to repeatedly enter details related to the one or more payment methods at the merchant platform.

[0030] In some embodiments, a similar process may occur if the user 105 wishes to add a new merchant to a list of multiple merchants 103 previously selected by the user 105. In such cases, the payment processing system 101 may dynamically revalidate one or more payment methods upon detecting a change in details associated with one or more payment methods. Further, as an example, if the user's 105 card expires, the payment processing system 101 may delete the existing card details and revalidate the details associated with the new card. Upon validating the new card details, the payment processing system 101 may add and store the new card details. In some embodiments, if one or more payment methods configured by the user 105 are not accepted by at least one of the multiple merchants 103, the user 105 may retry automatic payment method submission to at least one of the multiple merchants 103. In some embodiments, if one or more payment methods configured by the user 105 are not accepted by at least one of the multiple merchants 103, the user 105 may repeat the process and select a new payment method with the merchant.

[0031] In some embodiments, the user 105 may delete one or more payment methods configured with multiple merchants 103. In some embodiments, the payment processing system 101 may provide the user 105 with a list of multiple merchants 103 to receive a user selection 107 for at least one of the multiple merchants 103 for deleting one or more payment methods configured with the multiple merchants 103.

[0032] In some embodiments, upon receiving the user selection 107, the payment processing system 101 may authenticate the user 105 based on the user details provided by the user 105 before deleting one or more payment methods for at least one of the multiple merchants selected by the user 105.

[0033] In some embodiments, after authenticating the user 105, the payment processing system 101 may transmit the user details, user permissions, and one or more payment methods to be deleted to a payment processor 109 associated with each of multiple merchants selected by the user 105.

[0034] Subsequently, the payment processing system 101 may receive a merchant confirmation regarding the deletion of the one or more payment methods from at least one of the multiple merchants selected by the user 105. In some embodiments, the payment processor 109 may delete details associated with the one or more payment methods established by the user 105. In some embodiments, the payment processing system 101 may send a confirmation to the user 105 upon successful deletion of the one or more payment methods established by the user 105.

[0035] FIG. 2 shows a detailed block diagram of a payment processing system 101 according to some embodiments of the present disclosure.

[0036] In some implementations, the payment processing system 101 may include a processor 203, an I / O interface 201, and a memory 205. The processor 203 may be used to perform various functions of the payment processing system 101 using data and modules stored in the memory 205. The I / O interface 201 may be used to interface the payment processing system 101 with one or more external computing devices, such as a smartphone of a user 105, to receive a user selection 107 regarding at least one of a plurality of merchants 103 for conducting one or more transactions. In some embodiments, the data 207 may be stored in the memory 205 of the payment processing system 101 as illustrated in FIG. 2. As an example, the data 207 may include a list of a plurality of merchants 103, a user selection 107, user details 211, payment methods 213, user permissions 215, and other data 217.

[0037] In some embodiments, the data 207 may be stored in the memory 205 in the form of various data structures. Additionally, the data 207 may be organized using a data model, such as a relational or hierarchical data model. Other data 217 may store data, including temporary data and files, generated by the modules 209 to perform various functions of the payment processing system 101.

[0038] In some embodiments, the list of multiple merchants 103 may be names and details of merchants provided to the user 105 to receive the user's confirmation of the list of multiple merchants 103 selected by the user 105. In some embodiments, each merchant in the list of multiple merchants 103 may be pre-registered with the payment processing system 101.

[0039] In some embodiments, the user selection 107 may be at least one of a plurality of merchants selected by the user 105 from a list of a plurality of merchants 103. In some embodiments, the user selection 107 may also include the name or identity of the merchant from which the user 105 selected to remove one or more payment methods 213.

[0040] In some embodiments, the user details 211 may be details received from the user 105 and may be used to allow the user 105 to set up one or more payment methods 213 and / or delete one or more payment methods 213 for at least one of a plurality of merchants selected by the user 105. In some embodiments, the user details 211 may include, without limitation, the user's 105 name, the user's 105 phone number, credit and / or debit card numbers, Unified Payment Interface (UPI) identifiers (IDs), cryptocurrency wallet IDs, email IDs, etc., pre-registered with the merchant. In some embodiments, the user details 211 may be sent to a payment processor 109 associated with each of a plurality of merchants selected by the user 105.

[0041] In some embodiments, the one or more payment methods 213 may be payment instruments configured by the user 105 to conduct one or more transactions. In some embodiments, the one or more payment methods 213 may include, without limitation, card-based transactions, UPI transactions, cryptocurrency-based transactions, etc. In some embodiments, the one or more payment methods 213 may be transmitted to a payment processor 109 associated with each of multiple merchants selected by the user 105.

[0042] In some embodiments, the user authorization 215 may be authorization made by the payment processing system 101 using the user details 211 provided by the user 105. In some embodiments, the user authorization may be transmitted to a payment processor 109 associated with each of a plurality of merchants selected by the user 105.

[0043] In some embodiments, each of the data 207 stored in memory 205 may be processed by a module 209 of the payment processing system 101. The module 209 may be stored within the memory 205. In one example, the module 209 may be communicatively coupled to a processor 203 configured in the payment processing system 101. Alternatively, the module 209 may reside outside of the memory 205 as illustrated in FIG. 2 and be implemented as a separate hardware component. As used herein, the term module 209 may refer to an application specific integrated circuit (ASIC), electronic circuitry, a processor (shared, dedicated, or group) and memory executing one or more software or firmware programs, combinatorial logic circuitry, and / or other suitable components that provide the described functionality.

[0044] In some embodiments, the modules 209 may include, for example, a display module 219, an authentication module 221, a transmission module 223, a receiving module 225, and other modules 227. The other modules 227 may be used to perform various miscellaneous functions of the payment processing system 101. It will be appreciated that such above-mentioned modules 209 may be represented as a single module or a combination of different modules.

[0045] In some embodiments, the display module 219 may be configured to display a list of multiple merchants 103 to the user 105 to receive a user selection 107 for at least one of the multiple merchants 103 for conducting one or more transactions. Similarly, the display module 219 may be configured to display a list of multiple merchants 103 to the user 105 to receive a user selection 107 for at least one of the multiple merchants 103 for deleting one or more payment methods 213 configured for the multiple merchants 103. As an example, the display module 219 may display a list of multiple merchants 103 on a user device associated with the user 105.

[0046] In some embodiments, the authentication module 221 may be configured to authenticate the user 105 based on user details 211 provided by the user 105 to allow the user 105 to set up one or more payment methods 213 and / or remove one or more payment methods 213 for at least one of a plurality of merchants selected by the user 105. In some embodiments, the authentication module 221 may receive user details 211 from the user 105. As an example, the authentication module 221 may authenticate the user 105 based on a pre-enrolled biometric impression of the user 105. In some embodiments, the authentication module 221 may be configured to receive from the user 105 details associated with one or more payment methods 213 set up by the user 105 and verify the one or more payment methods 213 based on the details. In some embodiments, when the user 105 updates details associated with one or more payment methods 213, the authentication module 221 may be configured to dynamically re-verify the one or more payment methods 213 to update the changes in the details associated with the one or more payment methods 213.

[0047] In some embodiments, the sending module 223 may be configured to send the user details 211, the user authorizations, and one or more payment methods 213 established by the user 105 to the payment processor 109 associated with each of the multiple merchants selected by the user 105. Similarly, the sending module 223 may be configured to send the user details 211, the user authorizations, and one or more payment methods 213 to be deleted to the payment processor 109 associated with each of the multiple merchants selected by the user 105.

[0048] In some embodiments, the receiving module 225 may be configured to receive a merchant confirmation regarding the acceptance of one or more payment methods 213 established by the user 105 from at least one of a plurality of merchants selected by the user 105. Similarly, the receiving module 225 may be configured to receive a merchant confirmation regarding the deletion of one or more payment methods 213 from at least one of a plurality of merchants selected by the user 105.

[0049] FIG. 3A shows a flowchart illustrating a method for automatic payment method transmission to a merchant according to some embodiments of the present disclosure.

[0050] The order in which method 300 is described is not intended to be construed as a limitation, as any number of the described method blocks can be combined in any order to implement method 300. Additionally, individual blocks can be deleted from the method without departing from the spirit and scope of the subject matter described herein. Furthermore, method 300 can be implemented in any suitable hardware, software, firmware, or combination thereof.

[0051] At block 301, the method 300 may include, by the processor 203 of the payment processing system 101, providing a list of multiple merchants 103 to the user 105 to receive a user selection 107 regarding at least one of the multiple merchants 103 for conducting one or more transactions.

[0052] At block 303, the method 300 may include, by the processor 203, authenticating the user 105 based on user details 211 provided by the user 105 to permit the user 105 to establish one or more payment methods 213 with at least one of the plurality of merchants selected by the user 105. In some embodiments, authenticating the user 105 includes receiving from the user 105 details associated with the one or more payment methods 213 established by the user 105 and validating the one or more payment methods 213 based on the details associated with the one or more payment methods 213. In some embodiments, dynamically revalidating the one or more payment methods 213 upon detecting a change in details associated with the one or more payment methods 213.

[0053] At block 305, the method 300 may include transmitting, by the processor 203, the user details 211, the user authorizations, and one or more payment methods 213 established by the user 105 to a payment processing device 109 associated with each of a plurality of merchants selected by the user 105.

[0054] At block 307, the method 300 may include receiving, by the processor 203, a merchant confirmation regarding acceptance of the one or more payment methods 213 established by the user 105 from at least one of the plurality of merchants selected by the user 105. In some embodiments, the merchant confirmation is received when the user details 211 provided by the user 105 match pre-registered user details 211 stored at at least one of the plurality of merchants selected by the user 105. In some embodiments, the merchant confirmation is generated in response to successful authentication of the user 105 by a payment processor 109 associated with at least one of the plurality of merchants selected by the user 105. In some embodiments, if the one or more payment methods 213 established by the user 105 are not accepted by at least one of the plurality of merchants 103, automatic payment method submission is retried for at least one of the plurality of merchants 103.

[0055] FIG. 3B shows a flowchart illustrating a method for automatic payment method transmission to a merchant according to some embodiments of the present disclosure.

[0056] The order in which method 310 is described is not intended to be construed as a limitation, as any number of the described method blocks can be combined in any order to implement method 310. Additionally, individual blocks can be deleted from the method without departing from the spirit and scope of the subject matter described herein. Furthermore, method 310 can be implemented in any suitable hardware, software, firmware, or combination thereof.

[0057] At block 311, the method 310 may include a step by the processor 203 of the payment processing system 101 providing the list of multiple merchants 103 to the user 105 to receive a user selection 107 regarding at least one of the multiple merchants 103 for deleting one or more payment methods 213 configured for the multiple merchants 103.

[0058] At block 313, the method 310 may include, by the processor 203, authenticating the user 105 based on the user details 211 provided by the user 105 to authorize the user 105 to delete one or more payment methods 213 for at least one of the plurality of merchants selected by the user 105.

[0059] At block 315, the method 310 may include transmitting, by the processor 203, the user details 211, the user authorizations, and the one or more payment methods 213 to be deleted to a payment processing device 109 associated with each of the multiple merchants selected by the user 105.

[0060] At block 317, the method 310 may include receiving, by the processor 203, a merchant confirmation regarding the deletion of one or more payment methods 213 from at least one of the plurality of merchants selected by the user 105.

[0061] FIG. 4 illustrates an exemplary scenario for authenticating a user 105, according to some embodiments of the present disclosure. Assume that the user 105 selects Merchant A from a plurality of merchants 103 to conduct one or more transactions. In some embodiments, the user details 211 provided by the user 105 may comprise the details used to register with Merchant A (step 401). The user details 211 may be matched against pre-registered user details 211 stored at Merchant A. In some embodiments, if the user details 211 match, the payment processor 1091 associated with Merchant A may notify the user 105 and request confirmation from the user 105 (step 403). In some embodiments, a merchant confirmation is generated in response to successful authentication of the user 105 by the payment processor 1091 associated with at least one of the plurality of merchants selected by the user 105. Upon receiving the confirmation, the user 105 may conduct one or more transactions with Merchant A without having to again provide details related to one or more payment methods 213 to Merchant A.

[0062] In some embodiments, if the user 105 wishes to delete one or more payment methods 213 configured by the user 105 with Merchant A, the user details 211 may be matched against pre-registered user details 211 stored at Merchant A. In some embodiments, after the user details 211 are successfully matched, the payment processor 1091 associated with Merchant A may notify the user 105 and request confirmation from the user 105. In some embodiments, the merchant confirmation is generated in response to successful authentication of the user 105 by a payment processor 1091 associated with at least one of the multiple merchants selected by the user 105. Upon receiving the confirmation, the payment processor 1091 may delete one or more payment details from the payment processor 1091.

[0063] FIG. 5 is a block diagram of an exemplary computer system for implementing embodiments consistent with this disclosure.

[0064] In some embodiments, computer system 500 may be a payment processing system 101 used for automatic payment method transmission to a merchant. Computer system 500 may include a central processing unit ("CPU" or "processor") 502. Processor 502 may include at least one data processor for executing program components for performing user- or system-generated business processes. A user may include a person, someone using a device such as those included in this disclosure, or such a device itself. Processor 502 may include dedicated processing units such as an integrated system (bus) controller, a memory management control unit, a floating-point unit, a graphics processing unit, a digital signal processing unit, etc.

[0065] The processor 502 may be provided in communication with input devices 511 and output devices 512 via an I / O interface 501. The I / O interface 501 may utilize communication protocols / methods such as, without limitation, audio, analog, digital, stereo, IEEE-1394, serial bus, universal serial bus (USB), infrared, PS / 2, BNC, coaxial, component, composite, digital visual interface (DVI), high-definition multimedia interface (HDMI), radio frequency (RF) antenna, S-video, video graphics array (VGA), IEEE 802.n / b / g / n / x, Bluetooth, cellular (e.g., code division multiple access (CDMA), high speed packet access (HSPA+), global system for mobile communications (GSM), long term evolution (LTE), WiMax, etc.), etc.

[0066] Using the I / O interface 501 , the computer system 500 may communicate with input devices 511 and output devices 512 .

[0067] In some embodiments, processor 502 may be in communication with a communications network 509 via a network interface 503. Network interface 503 may communicate with communications network 509. Network interface 503 may utilize a connection protocol including, without limitation, a direct connection, Ethernet (e.g., twisted pair 10 / 100 / 1000 Base-T), Transmission Control Protocol / Internet Protocol (TCP / IP), Token Ring, IEEE 802.11a / b / g / n / x, etc. Using network interface 503 and communications network 509, computer system 500 communicates with a device associated with user 105 and one or more payment processing devices 1091-109 associated with each of a plurality of merchants for automatic payment method transmission to the merchant. N may interface with

[0068] In some embodiments, communication network 509 may be implemented as one of several different types of networks, such as an intranet or local area network (LAN), a closed area network (CAN), etc. Communication network 509 may be a dedicated network or a shared network, and may represent a combination of several different types of networks that use various protocols to communicate with each other, such as HyperText Transfer Protocol (HTTP), CAN protocol, Transmission Control Protocol / Internet Protocol (TCP / IP), Wireless Application Protocol (WAP), etc. Additionally, communication network 509 may include various network devices, including routers, bridges, servers, computing devices, storage devices, etc. In some embodiments, processor 502 may be in communication with memory 505 (e.g., RAM, ROM, etc., as shown in FIG. 5 ) via storage interface 504. The storage interface 504 may connect to memory 505, including, without limitation, memory drives, removable disk drives, etc., using connection protocols such as Serial Advanced Technology Attachment (SATA), Integrated Drive Electronics (IDE), IEEE-1394, Universal Serial Bus (USB), Fibre Channel, Small Computer System Interface (SCSI), etc. The memory drives may further include drum, magnetic disk drives, magneto-optical drives, optical drives, redundant array of independent disks (RAID), solid state memory devices, solid state drives, etc.

[0069] Memory 505 may store a collection of program or database components, including, without limitation, a user interface 506, an operating system 507, a web browser 508, etc. In some embodiments, computer system 500 may store user / application data, such as data, variables, records, etc., as described in this disclosure. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases, such as Oracle or Sybase.

[0070] Operating system 507 may facilitate resource management and operation of computer system 500. Examples of operating systems include, without limitation, APPLE® MACINTOSH® OS X®, UNIX®, UNIX-like system distributions (e.g., BERKELEY SOFTWARE DISTRIBUTION® (BSD), FREEBSD®, NETBSD®, OPENBSD, etc.), LINUX® distributions (e.g., RED HAT®, UBUNTU®, KUBUNTU®, etc.), IBM® OS / 2®, MICROSOFT® WINDOWS® (XP®, VISTA® / 7 / 8, 10, etc.), APPLE® IOS®, GOOGLE™ ANDROID®, BLACKBERRY® OS, etc. The user interface 506 may facilitate the display, execution, interaction, manipulation, or operation of program components through textual or graphical mechanisms. For example, the user interface may provide computer interaction interface elements on a display system operatively connected to the computer system 500, such as cursors, icons, check boxes, menus, scrollers, windows, widgets, etc. Graphical user interfaces (GUIs) may be utilized, including, without limitation, Apple® Macintosh® operating systems Aqua®, IBM® OS / 2®, Microsoft® Windows® (e.g., Aero, Metro, etc.), web interface libraries (e.g., ActiveX®, Java®, Javascript®, AJAX, HTML, Adobe® Flash®, etc.), etc.

[0071] In some embodiments, the computer system 500 may implement a web browser 508 built-in program component. The web browser 508 may be a hypertext viewing application such as MICROSOFT® INTERNET EXPLORER®, GOOGLE™ CHROME™, MOZILLA® FIREFOX®, APPLE® SAFARI®, etc. Secure web browsing may be provided using Secure Hypertext Transport Protocol (HTTPS), Secure Sockets Layer (SSL), Transport Layer Security (TLS), etc. The web browser 508 may utilize mechanisms such as AJAX, DHTML, ADOBE® FLASH®, JAVASCRIPT®, JAVA®, application programming interfaces (APIs), etc. In some embodiments, the computer system 500 may implement a mail server built-in program component. The mail server may be an Internet mail server such as Microsoft Exchange, etc. The mail server may utilize mechanisms such as Active Server Pages (ASP), ACTIVEX®, ANSI® C++ / C#, MICROSOFT® .NET, CGI scripts, JAVA®, JAVASCRIPT®, PERL®, PHP, PYTHON®, WEBOBJECTS®, etc. The mail server may utilize communication protocols such as Internet Message Access Protocol (IMAP), Messaging Application Programming Interface (MAPI), MICROSOFT® Exchange, Post Office Protocol (POP), Simple Mail Transfer Protocol (SMTP), etc. In some embodiments, computer system 500 may implement a mail client built-in program component.The mail client may be a mail viewing application such as APPLE® Mail, MICROSOFT® ENTOURAGE®, MICROSOFT® OUTLOOK®, MOZILLA® THUNDERBIRD®, or the like.

[0072] Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory in which information or data readable by a processor may be stored. As such, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor to perform steps or stages consistent with the embodiments described herein. The term "computer-readable medium" should be understood to include tangible articles and exclude carrier waves and transient signals, i.e., non-transitory. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, non-volatile memory, hard drives, compact disc (CD) ROMs, digital video discs (DVDs), flash drives, disks, and any other known physical storage medium.

[0073] The terms "one embodiment," "embodiment," "embodiments," "the embodiment," "the embodiments," "one or more embodiments," "some embodiments," and "one embodiment" mean "one or more (but not all) embodiments of the invention," unless expressly stated otherwise.

[0074] The terms "including," "comprising," "having," and variations thereof mean "including, but not limited to," unless expressly stated otherwise.

[0075] An enumerated list of items does not imply that any or all of the items are mutually exclusive unless expressly stated otherwise. The terms "a," "an," and "the" mean "one or more" unless expressly stated otherwise.

[0076] The description of one embodiment in which several components are in communication with each other does not imply that all such components are required, but rather various optional components are described to illustrate the wide variety of possible embodiments of the present disclosure.

[0077] It will be readily apparent that where a single device or article is described herein, two or more devices / articles (whether or not they cooperate) may be used in place of the single device / article. Similarly, where two or more devices or articles (whether or not they cooperate) are described herein, it will be readily apparent that a single device / article may be used in place of the two or more devices or articles, or that a different number of devices / articles may be used in place of the number of devices or programs shown. The functionality and / or features of a device may alternatively be embodied by one or more other devices not explicitly described as having such functionality / features. As such, other embodiments of the present disclosure need not include the device itself.

[0078] The illustrated operations in Figures 3A and 3B show certain events occurring in a certain order. In alternative embodiments, certain operations may occur in a different order, be modified, or removed. Moreover, steps may be added to the logic described above and still be compatible with the described embodiments. Furthermore, operations described herein may occur sequentially, or certain operations may be processed in parallel. Furthermore, operations may be performed by a single processing unit or by distributed processing units.

[0079] Finally, the language used herein has been selected primarily for ease of reading and instructional purposes, and not to limit or restrict the inventive subject matter. Accordingly, it is intended that the scope of the disclosure be limited not by this detailed description, but rather by any claims that issue in an application based thereon. Accordingly, the disclosure of embodiments of the present disclosure is intended to be illustrative, but not limiting, of the scope of the disclosure, which is set forth in the appended claims.

[0080] While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims. [Explanation of symbols]

[0081] 100 Environment 101 Payment Processing System 103 member stores 105 User 107 User Choice 109 Payment Processing Devices 201 I / O Interface 203 processor 205 memory 207 Data 209 Modules 211 User details 213 Payment Method 215 User Permissions 217 Other Data 219 Display Module 221 Authentication Module 223 Transmitting Module 225 Receiver Module 227 other modules 500 Computer Systems 501 I / O interface 502 processor 503 Network Interface 504 Storage Interface 505 memory 506 User Interface 507 Operating Systems 508 Web Browser 509 Communication Network 511 Input Devices 512 output devices

Claims

1. 1. A computer-implemented method for automatic payment method transmission to a merchant, comprising: providing a list of a plurality of merchants to the user to receive a user selection of at least one of the plurality of merchants for conducting one or more transactions; authenticating the user based on user details provided by the user to authorize the user to establish one or more payment methods with the at least one of the plurality of merchants selected by the user; transmitting the user details, user authorizations, and the one or more payment methods configured by the user to a payment processor associated with each of the plurality of merchants selected by the user; and receiving a merchant confirmation of acceptance of the one or more payment methods set by the user from the at least one of the plurality of merchants selected by the user.

2. 2. The computer-implemented method of claim 1, wherein the merchant confirmation is received if the user details provided by the user match pre-registered user details stored at the at least one of the plurality of merchants selected by the user.

3. 2. The computer-implemented method of claim 1, wherein the merchant confirmation is generated upon successful authentication of the user by the payment processing device associated with the at least one of the plurality of merchants selected by the user.

4. The step of authenticating the user includes: receiving from the user details associated with the one or more payment methods established by the user; and validating the one or more payment methods based on the details associated with the one or more payment methods.

5. 5. The computer-implemented method of claim 4, comprising dynamically revalidating the one or more payment methods upon detecting a change in the details associated with the one or more payment methods.

6. 2. The computer-implemented method of claim 1, further comprising: if the one or more payment methods set by the user are not accepted by the at least one of the plurality of merchants, retrying the automatic payment method transmission to the at least one of the plurality of merchants.

7. 1. A computer-implemented method for automatic payment method transmission to a merchant, comprising: providing a list of a plurality of merchants to a user to receive a user selection for at least one of the plurality of merchants for deleting one or more payment methods established with the plurality of merchants; authenticating the user based on user details provided by the user to authorize the user to remove the one or more payment methods for the at least one of the plurality of merchants selected by the user; sending the user details, user authorizations, and the one or more payment methods to be deleted to a payment processor associated with each of the plurality of merchants selected by the user; receiving a merchant confirmation of the deletion of the one or more payment methods from the at least one of the plurality of merchants selected by the user.

8. 1. A payment processing system comprising: a processor; a memory communicatively coupled to the processor, the memory storing processor-executable instructions that, when executed, cause the processor to: providing a list of a plurality of merchants to a user to receive a user selection of at least one of the plurality of merchants for conducting one or more transactions; authenticating the user based on user details provided by the user to permit the user to establish one or more payment methods with the at least one of the plurality of merchants selected by the user; transmitting the user details, user authorizations, and the one or more payment methods configured by the user to a payment processor associated with each of the plurality of merchants selected by the user; receiving a merchant confirmation of acceptance of the one or more payment methods set by the user from the at least one of the plurality of merchants selected by the user;

9. 9. The payment processing system of claim 8, wherein the merchant confirmation is received if the user details provided by the user match pre-registered user details stored at the at least one of the plurality of merchants selected by the user.

10. 9. The payment processing system of claim 8, wherein the merchant confirmation is generated upon successful authentication of the user by the payment processing device associated with the at least one of the plurality of merchants selected by the user.

11. authenticating the user, receiving from the user details associated with the one or more payment methods established by the user; and validating the one or more payment methods based on the details associated with the one or more payment methods.

12. 12. The payment processing system of claim 11, comprising dynamically revalidating the one or more payment methods upon detecting a change in the details associated with the one or more payment methods.

13. 9. The payment processing system of claim 8, further comprising: if the one or more payment methods set by the user are not accepted by the at least one of the plurality of merchants, retrying automatic payment method transmission to the at least one of the plurality of merchants.

14. 1. A payment processing system comprising: a processor; a memory communicatively coupled to the processor, the memory storing processor-executable instructions that, when executed, cause the processor to: providing a list of a plurality of merchants to a user to receive a user selection for at least one of the plurality of merchants for deleting one or more payment methods established with the plurality of merchants; authenticating the user based on user details provided by the user to authorize the user to remove the one or more payment methods for the at least one of the plurality of merchants selected by the user; transmitting the user details, user authorizations, and the one or more payment methods to be deleted to a payment processor associated with each of the plurality of merchants selected by the user; receiving a merchant confirmation regarding the deletion of the one or more payment methods from the at least one of the plurality of merchants selected by the user.

15. A non-transitory computer-readable medium containing stored instructions that, when processed by at least one processor, cause a payment processing system to perform an operation, the operation comprising: providing a list of a plurality of merchants to a user to receive a user selection of at least one of the plurality of merchants for conducting one or more transactions; authenticating the user based on user details provided by the user to authorize the user to establish one or more payment methods with the at least one of the plurality of merchants selected by the user; transmitting the user details, user authorizations, and the one or more payment methods configured by the user to a payment processor associated with each of the plurality of merchants selected by the user; and receiving a merchant confirmation from the at least one of the plurality of merchants selected by the user regarding acceptance of the one or more payment methods set by the user.

16. A non-transitory computer-readable medium containing stored instructions that, when processed by at least one processor, cause a payment processing system to perform an operation, the operation comprising: providing a list of a plurality of merchants to a user to receive a user selection for at least one of the plurality of merchants for deleting one or more payment methods established with the plurality of merchants; authenticating the user based on user details provided by the user to authorize the user to remove the one or more payment methods for the at least one of the plurality of merchants selected by the user; transmitting the user details, user authorizations, and the one or more payment methods to be deleted to a payment processor associated with each of the plurality of merchants selected by the user; and receiving a merchant confirmation regarding the deletion of the one or more payment methods from the at least one of the plurality of merchants selected by the user.

Images