Method and system for automatically transmitting payment mode to merchant
The method automates payment method transfer to merchants by user selection and authentication, addressing user inconvenience and security vulnerabilities in existing payment systems, enabling secure and efficient transactions.
Patent Information
- Application Number
- CN202280102376.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-12-05
- Publication Date
- 2025-07-15
AI Technical Summary
In the prior art, users need to manually enter payment information when changing or using a new credit card, resulting in inconvenience and risk of information leakage. The existing methods increase resistance between users and merchants in the payment life cycle.
The payment processing system provides a list of multiple merchants. The user selects the target merchant and performs authentication. The system automatically transmits user details and payment methods to the relevant payment processor, receives merchant confirmation, and realizes automatic payment method transmission.
It simplifies the payment process of users at different merchants, reduces the risk of information leakage, reduces the cost of merchant authentication, and reduces transaction-related risks.
Smart Images
Figure CN120322787A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to electronic transactions. In particular, but not exclusively, the present disclosure relates to a system and a computer-implemented method for automatically transmitting payment methods to merchants. Background Art
[0002] Currently, when a user obtains a new credit card, the user must manually add the details of the card on the online merchant platform before performing a transaction. This causes inconvenience to the user because the user needs to perform these steps on each merchant platform where the user conducts transactions. Similarly, when the card expires and / or a new card is issued to the user, the user must manually enter these details again. This can lead to resistance between the user and the merchant during the payment lifecycle.
[0003] On the other hand, storing payment details on the merchant platform has a higher possibility of being attacked multiply, such as shoulder surfing and stealing of details. Therefore, the existing methods bring inconvenience to the merchant or the user making the payment. Therefore, a simple and convenient method for automatically transmitting payment methods to merchants is needed.
[0004] The information disclosed in the background art of this part of the present disclosure is only used to enhance the general understanding of the background of the present disclosure, and should not be regarded as an admission or any form of implication that this information constitutes the prior art known to those skilled in the art. Summary of the Invention
[0005] Additional features and advantages are achieved by the techniques of the present disclosure. Other embodiments and aspects of the present disclosure are described in detail herein and are considered part of the claimed present disclosure.
[0006] A computer-implemented method for automatically transmitting payment methods to merchants is disclosed herein. The method may include providing a list of multiple merchants to a user to receive a user selection of at least one merchant from the multiple merchants for performing one or more transactions. In addition, the method may include authenticating the user based on user details provided by the user to authorize the user to set one or more payment methods for the at least one merchant selected by the user from the multiple merchants. Further, the method may include transmitting the user details, user authorization, and one or more payment methods set by the user to a payment processor associated with each merchant selected by the user from the multiple merchants. Finally, the method may include receiving a merchant confirmation of acceptance of one or more payment methods set by the user from at least one merchant selected by the user from the multiple merchants.
[0007] In addition, in an 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 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 of at least one merchant from the multiple merchants to perform one or more transactions. In addition, the instructions may cause the processor to authenticate the user based on user details provided by the user to authorize the user to set one or more payment methods for at least one merchant selected by the user from the multiple merchants. Further, the instructions may cause the processor to transmit the user details, user authorization, and one or more payment methods set by the user to a payment processor associated with each merchant selected by the user from the multiple merchants. Finally, the instructions may cause the processor to receive a merchant confirmation of acceptance of one or more payment methods set by the user from at least one merchant selected by the user from the multiple merchants.
[0008] In addition, in an embodiment, the present disclosure may include a non-transitory computer-readable medium having instructions stored thereon that, when processed by at least one processor, cause a payment processing system to perform operations including: providing a list of multiple merchants to a user to receive a user selection of at least one merchant from the multiple merchants to perform one or more transactions. In addition, the instructions may cause the payment processing system to authenticate the user based on user details provided by the user to authorize the user to set one or more payment methods for at least one merchant selected by the user from the multiple merchants. Further, the instructions may cause the payment processing system to transmit the user details, user authorization, and one or more payment methods set by the user to a payment processor associated with each merchant selected by the user from the multiple merchants. Finally, the instructions may cause the payment processing system to receive a merchant confirmation of acceptance of one or more payment methods set by the user from at least one merchant selected by the user from the multiple merchants.
[0009] Disclosed herein is a computer-implemented method for automatically transmitting payment methods to a merchant, the method may include providing a list of multiple merchants to a user to receive a user selection of at least one merchant from the multiple merchants to delete one or more payment methods set for the multiple merchants. In addition, the method may include authenticating the user based on user details provided by the user to authorize the user to delete one or more payment methods for at least one merchant selected by the user from the multiple merchants. Further, the method may include transmitting the user details, user authorization, and one or more payment methods to be deleted to a payment processor associated with each merchant selected by the user from the multiple merchants. Finally, the method may include receiving a merchant confirmation of deletion of one or more payment methods from at least one merchant selected by the user from the multiple merchants.
[0010] In addition, in an 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 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 of at least one merchant from the multiple merchants to delete one or more payment methods set for the multiple merchants. Further, the instructions may cause the processor to authenticate the user based on user details provided by the user to authorize the user to delete one or more payment methods for at least one merchant selected by the user from the multiple merchants. Furthermore, the instructions may cause the processor to transmit the user details, the user authorization, and the one or more payment methods to be deleted to a payment processor associated with each merchant selected by the user from the multiple merchants. Finally, the instructions may cause the processor to receive a merchant confirmation of the deletion of the one or more payment methods from at least one merchant selected by the user from the multiple merchants.
[0011] In addition, in an embodiment, the present disclosure may include a non-transitory computer-readable medium including instructions stored thereon that, when processed by at least one processor, cause the payment processing system to perform operations including: providing a list of multiple merchants to a user to receive a user selection of at least one merchant from the multiple merchants to delete one or more payment methods set for the multiple merchants. Further, the instructions may cause the payment processing system to authenticate the user based on user details provided by the user to authorize the user to delete one or more payment methods for at least one merchant selected by the user from the multiple merchants. Furthermore, the instructions cause the payment processing system to transmit the user details, the user authorization, and the one or more payment methods to be deleted to a payment processor associated with each merchant selected by the user from the multiple merchants. Finally, the instructions may cause the payment processing system to receive a merchant confirmation of the deletion of the one or more payment methods from at least one merchant selected by the user from the multiple merchants.
[0012] The foregoing summary is illustrative only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments, and features described above, other aspects, embodiments, and features may become apparent by reference to the drawings and the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] The novel features and characteristics of the present disclosure are set forth in the appended claims. However, the present disclosure itself, as well as its preferred mode of use, further objectives, and advantages, will be best understood by reference to the following detailed description of illustrative embodiments when read in conjunction with the accompanying drawings. The accompanying drawings, which are incorporated into and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, serve to explain the disclosed principles. In the figures, the leftmost digit of the reference numeral identifies the figure in which the reference numeral first appears. One or more embodiments are now described by way of example only and with reference to the accompanying drawings, in which like reference numerals represent like elements, and in which:
[0014] Figure 1 illustrates an exemplary environment that depicts a method for automatically transmitting a payment method to a merchant according to some embodiments of the present disclosure;
[0015] Figure 2 shows a detailed block diagram of a payment processing system according to some embodiments of the present disclosure;
[0016] Figure 3A and Figure 3B illustrates a flowchart depicting a method for automatically transmitting a payment method to a merchant according to some embodiments of the present disclosure;
[0017] Figure 4 is an exemplary scenario depicting the authentication of a user according to some embodiments of the present disclosure; and
[0018] Figure 5 is a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.
[0019] Those skilled in the art will appreciate that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the subject matter. Similarly, it will be appreciated that any flowcharts, flow diagrams, state transition diagrams, pseudocode, etc., represent various processes that are substantially represented on a computer-readable medium and can be executed by a computer or processor (whether or not such computer or processor is explicitly shown). DETAILED DESCRIPTION
[0020] In this document, the term "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
[0021] The present disclosure allows for various modifications and alternative forms, and specific embodiments thereof are shown by way of example in the accompanying drawings and may be described in detail below. However, it should be understood that the intention is not to limit the present disclosure to the particular forms disclosed, but on the contrary, the present disclosure will cover all modifications, equivalents, and alternatives falling within the scope of the present disclosure.
[0022] The term "comprising", "including" or any other variation thereof is intended to cover non-exclusive inclusion, such that a set, device or method comprising a list of components or steps is not limited to only those components or steps but may also include other components or steps not expressly listed or inherent to such set, device or method. In other words, one or more elements in a system or apparatus starting with "comprising" or "including" will not, without more constraints, preclude the existence of other elements or additional elements in that system or apparatus.
[0023] The present disclosure relates to a payment processing system and a computer-implemented method for automatically transmitting payment methods to a merchant. In some embodiments, the method includes providing a list of multiple merchants to a user to receive a user selection of at least one merchant from the multiple merchants to perform 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 set one or more payment methods for at least one merchant selected by the user from the multiple merchants. Subsequently, the method includes transmitting the user details, user authorization, and one or more payment methods set by the user to a payment processor associated with each merchant selected by the user from the multiple merchants. Finally, the method includes receiving a merchant confirmation of acceptance of one or more payment methods set by the user from at least one merchant selected by the user from the multiple merchants.
[0024] In some embodiments, the payment processing system and the computer-implemented method of the present disclosure provide a convenient way for a user to perform transactions on a merchant platform. In addition, the present disclosure proposes storing card details on the payment processing system, thereby reducing the workload on the payment processors associated with the merchants. Further, the present disclosure helps the merchants reduce the costs associated with authenticating the users. In addition, according to the present disclosure, storing user details and transaction details at the issuer helps eliminate the risks associated with the transactions.
[0025] In the following detailed description of the embodiments of the present disclosure, reference will be made to the accompanying drawings, which form a part of the present disclosure and illustrate specific embodiments in which the present disclosure may be practiced by way of illustration. These embodiments are described in sufficient detail to enable those skilled in the art to practice the present disclosure, and it should be understood that other embodiments may be utilized and modifications may be made without departing from the scope of the present disclosure. Therefore, the following description should not be construed in a limiting sense.
[0026] Figure 1 An exemplary environment is shown that illustrates a method for automatically transmitting payment methods to a merchant according to some embodiments of the present disclosure.
[0027] In some embodiments, environment 100 may include a plurality of merchants (i.e., merchant A 103 N (collectively referred to as payment processors 109)) associated with one or more payment processors 109 (i.e., payment processor 1 1091,..., payment processor N 109 A , merchant B 103 B ,..., merchant N 103 N (collectively referred to as the plurality of merchants 103), user 105, and payment processing system 101. As an example, user 105 may register with payment processing system 101 and plan to perform one or more transactions with at least one of the plurality of merchants 103. The plurality of merchants 103 may be pre-registered in the payment processing system.
[0028] In some embodiments, payment processing system 101 may be a computing system configured to perform the following technical processes, which include: providing a list of the plurality of merchants 103 to user 105; authenticating user 105; transmitting user details, user authorization, and one or more payment methods set by user 105 to payment processor 109; and receiving merchant confirmation from merchant 103. Here, payment processing system 101 may be an issuer entity, such as, but not limited to, a bank, a payment gateway, and a payment server, etc. In some embodiments, user 105 may use a medium (such as, for example, a web application and / or a mobile application installed on the computing device of user 105) to interact with payment processing system 101. As an example, the computing device may include, but not be limited to, a smart phone, a personal digital assistant (PDA), or a desktop computer.
[0029] In some embodiments, a list of multiple merchants 103 can be provided to a user 105 (as illustrated in step 111) to receive a user selection 107 of at least one merchant from the multiple merchants 103. In some embodiments, the multiple merchants 103 can be displayed to the user 105 on a computing system associated with the user 105. As an example, the computing system associated with the user 105 can include, but is not limited to, a smart phone, a personal digital assistant (PDA), or a desktop computer. In some embodiments, the multiple merchants 103 can be pre-registered at a payment processing system 101 to perform one or more transactions initiated by the user 105 on the merchant platform. In some embodiments, before providing the list of the multiple merchants 103 to the user 105, the multiple merchants 103 can be authenticated by the payment processing system 101. In some embodiments, together with the list of the merchants 103, the payment processing system 101 can also provide information related to the types of payment methods accepted by the merchants 103 to the user 105 along with the merchant details. In some embodiments, the types of payment methods can include, but are not limited to, card-based transactions, Unified Payment Interface (UPI) transactions, and cryptocurrency-based transactions, etc.
[0030] In some embodiments, after receiving the user selection 107, the payment processing system 101 can authenticate the user 105 based on the user details provided by the user 105 to authorize the user 105 to set one or more payment methods for at least one merchant selected by the user 107. In some embodiments, the user details can include pre-registered user credential information, such as, but not limited to, the name of the user 105, the phone number of the user 105, credit card and / or debit card numbers, UPI identifier (ID), cryptocurrency wallet ID, pre-registered email ID at the merchant, and username registered on the merchant platform, etc. As an example, to authenticate the user 105, the payment processing system 101 can send a one-time password (OTP) to the user 105 on the user's registered phone number and / or registered email ID. As an example, when the user 105 selects a card transaction as the payment method, the payment processing system 101 can request the user 105 to provide details of the card, such as the card number, the name on the card, the month and year of the card's expiration date, the card verification value (CVV), and the personal identification number (PIN), etc.
[0031] Subsequently, the payment processing system 101 can verify the one or more payment methods set by the user 103 based on the details related to the one or more payment methods.
[0032] In some embodiments, after authenticating user 105, payment processing system 101 may transmit user details, user authorization, and one or more payment methods set by user 105 to a payment processor 109 associated with each merchant 103 selected by user 107 from among a plurality of merchants 103. In some embodiments, the payment processor 109 associated with each merchant 103 among the plurality of merchants 103 may be a computing system, such as but not limited to, a desktop computer or a server computing system. Here, the payment processor 109 associated with each merchant 103 among the plurality of merchants 103 may be an issuer entity associated with the plurality of merchants 103, such as but not limited to, a bank, a payment gateway, and a payment server, etc. In some embodiments, the user details transmitted to the payment processor 109 may include the details registered by user 105 at merchant 103. In some embodiments, the payment processing system 101 may use a pre-specified technique to generate a token for details related to one or more payment methods set by user 105. Subsequently, the payment processing system 101 may transmit the token to each merchant 103 selected by user 107 from among the plurality of merchants 103.
[0033] In some embodiments, after transmitting user details, user authorization, and one or more payment methods, the payment processing system 101 may receive a merchant confirmation of acceptance of one or more payment methods set by user 105 from at least one merchant selected by user 107 from among the plurality of merchants 103. In some embodiments, the merchant confirmation is received when the user details provided by user 105 match the pre-registered user details stored at at least one merchant selected by user 107 from among the plurality of merchants 103. In some embodiments, the merchant confirmation is generated after successfully authenticating user 105 through a payment processor 109 associated with at least one merchant selected by user 107 from among the plurality of merchants 103. In some embodiments, after receiving the merchant confirmation, user 105 may initiate one or more transactions at at least one merchant selected by user 107 from among the plurality of merchants 103 without repeating the input of details related to one or more payment methods on the merchant platform.
[0034] In some embodiments, when user 105 wants to add a new merchant to a list of multiple merchants 103 previously selected by user 105, a similar process can be performed. In such a case, the payment processing system 101 can dynamically re-verify one or more payment methods when detecting a change in the details related to one or more payment methods. Additionally, as an example, when the card of user 105 expires, the payment processing system 101 can delete the details of the existing card and re-verify the details related to the new card. After verifying the details of the new card, the payment processing system 101 can add and store the details of the new card. In some embodiments, when one or more payment methods set by user 105 are not accepted by at least one of the multiple merchants 103, user 105 can re-attempt to automatically transmit the payment method to at least one of the multiple merchants 103. In some embodiments, when one or more payment methods set by user 105 are not accepted by at least one of the multiple merchants 103, user 105 can repeat the process and select a new payment method at the merchant.
[0035] In some embodiments, user 105 can also delete one or more payment methods set at multiple merchants 103. In some embodiments, the payment processing system 101 can provide the list of multiple merchants 103 to user 105 to receive a user selection 107 for at least one of the multiple merchants 103 to delete one or more payment methods set for the multiple merchants 103.
[0036] In some embodiments, after receiving the user selection 107, the payment processing system 101 can authenticate user 105 based on the user details provided by user 105 before deleting one or more payment methods for at least one of the multiple merchants selected by user selection 107.
[0037] In some embodiments, after authenticating user 105, the payment processing system 101 can transmit the user details, user authorization, and one or more payment methods to be deleted to a payment processor 109 associated with each of the multiple merchants selected by user selection 107.
[0038] Subsequently, the payment processing system 101 can receive a merchant confirmation of the deletion of one or more payment methods from at least one of the multiple merchants selected by user 105. In some embodiments, the payment processor 109 can delete the details related to one or more payment methods set by user 105. In some embodiments, the payment processing system 101 can forward the confirmation to user 105 after successfully deleting one or more payment methods set by user 105.
[0039] Figure 2Shows a detailed block diagram of a payment processing system 101 according to some embodiments of the present disclosure.
[0040] In some embodiments, 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 execute various functions of the payment processing system 101 using the 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 (e.g., the smart phone of user 105) to receive a user selection 107 for at least one of a plurality of merchants 103 in order to perform one or more transactions. In some embodiments, data 207 may be stored in the memory 205 of the payment processing system 101, as Figure 2 shown. As an example, the data 207 may include a list of a plurality of merchants 103, user selections 107, user details 211, payment methods 213, user authorizations 215, and other data 217.
[0041] In some embodiments, the data 207 may be stored in the memory 205 in the form of various data structures. Additionally, a data model (such as a relational data model or a hierarchical data model) may be used to organize and manage the data 207. Other data 215 may store data generated by the module 209 (including temporary data and temporary files) in order to execute various functions of the payment processing system 101.
[0042] In some embodiments, the list of a plurality of merchants 103 may be the names and details of the merchants provided to the user 105 to receive confirmation from the user of the list of a plurality of merchants 103 selected by the user 105. In some embodiments, each of the plurality of merchants 103 in the list may be pre-registered at the payment processing system 101.
[0043] In some embodiments, the user selection 107 may be at least one of the plurality of merchants selected by the user 105 from the list of a plurality of merchants 103. In some embodiments, the user selection 107 may also include the name or identity of the merchant selected by the user 105 for deleting one or more payment methods 213.
[0044] In some embodiments, the user details 211 can be details received from the user 105 and can be used to authorize the user 105 to set one or more payment methods 213 and / or delete one or more payment methods 213 for at least one merchant selected by the user 107 among multiple merchants. In some embodiments, the user details 211 can include, but are not limited to, the name of the user 105, the phone number of the user 105, credit card and / or debit card numbers, Unified Payments Interface (UPI) identifier (ID), encrypted wallet ID, email ID, etc., which are pre-registered at the merchant. In some embodiments, the user details 211 can be transmitted to the payment processor 109 associated with each merchant selected by the user 107 among the multiple merchants.
[0045] In some embodiments, one or more payment methods 213 can be payment means set by the user 105 for performing one or more transactions. In some embodiments, one or more payment methods 213 can include, but are not limited to, card-based transactions, UPI transactions, and crypto-based transactions, etc. In some embodiments, one or more payment methods 213 can be transmitted to the payment processor 109 associated with each merchant selected by the user 107 among the multiple merchants.
[0046] In some embodiments, the user authorization 215 can be an authorization performed by the payment processing system 101 using the user details 211 provided by the user 105. In some embodiments, the user authorization can be transmitted to the payment processor 109 associated with each merchant among the multiple merchants selected by the user 107.
[0047] In some embodiments, each of the data 207 stored in the memory 205 can be processed by the module 209 of the payment processing system 101. The module 209 can be stored within the memory 205. In an example, the module 209 can be communicatively coupled to the processor 203 configured in the payment processing system 101. Alternatively, the module 209 can also be external to the memory 205 as shown in Figure 2 and implemented as a separate hardware component. As used herein, the term module 209 can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or a group thereof) for executing one or more software or firmware programs and memory, combinational logic circuitry, and / or other suitable components that provide the described functionality.
[0048] In some embodiments, module 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. Other modules 227 may be used to perform various functions of the payment processing system 101. It will be appreciated that such module 209 as described above may be represented as a single module or a combination of different modules.
[0049] 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 of at least one merchant among the multiple merchants 103 for performing 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 of at least one merchant among the multiple merchants 103 for deleting one or more payment methods 213 set 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.
[0050] 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 authorize the user 105 to set one or more payment methods 213 and / or delete one or more payment methods 213 for at least one merchant selected by the user 107 among the multiple merchants. In some embodiments, the authentication module 221 may receive user details 211 from the user 105. For example, the authentication module 221 may authenticate the user 105 based on a biometric impression of the pre-registered user 105. In some embodiments, the authentication module 221 may be configured to receive details related to one or more payment methods 213 set by the user 105 from the user 105 and verify the one or more payment methods 213 based on the details 213. In some embodiments, when the user 105 updates details related to 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 related to the one or more payment methods 213.
[0051] In some embodiments, the transmission module 223 may be configured to transmit the user details 211, user authorization, and one or more payment methods 213 set by the user 105 to a payment processor 109 associated with each merchant selected by the user 107 among the multiple merchants. Similarly, the transmission module 223 may be configured to transmit the user details 211, user authorization, and one or more payment methods 213 to be deleted to a payment processor 109 associated with each merchant selected by the user 107 among the multiple merchants.
[0052] In some embodiments, the receiving module 225 may be configured to receive, from at least one merchant selected by the user 107 from among a plurality of merchants, a merchant confirmation of acceptance of one or more payment methods 213 set by the user 105. Similarly, the receiving module 225 may be configured to receive, from at least one merchant selected by the user 107 from among a plurality of merchants, a merchant confirmation of deletion of one or more payment methods 213.
[0053] Figure 3A A flowchart illustrating a method for automatically transmitting payment methods to a merchant according to some embodiments of the present disclosure is shown.
[0054] The order of description of method 300 is not intended to be construed as limiting, and any number of the described method blocks may be combined in any order to implement method 300. Additionally, individual blocks may be deleted from the method without departing from the spirit and scope of the subject matter described herein. Furthermore, method 300 may be implemented in any suitable hardware, software, firmware, or combination thereof.
[0055] At block 301, method 300 may include providing, by a processor 203 of a payment processing system 101, a list of a plurality of merchants 103 to a user 105 to receive a user selection 107 of at least one merchant from among the plurality of merchants 103 for performing one or more transactions.
[0056] At block 303, method 300 may include authenticating the user 105 by the processor 203 based on user details 211 provided by the user 105 to authorize the user 105 to set one or more payment methods 213 for at least one merchant selected by the user 107 from among the plurality of merchants. In some embodiments, authenticating the user 105 includes receiving, from the user 105, details related to one or more payment methods 213 set by the user 105 and validating the one or more payment methods 213 based on the details related to the one or more payment methods 213. In some embodiments, the one or more payment methods 213 are dynamically re-validated upon detection of a change in the details related to the one or more payment methods 213.
[0057] At block 305, method 300 may include transmitting, by the processor 203, the user details 211, user authorization, and one or more payment methods 213 set by the user 105 to a payment processor 109 associated with each merchant selected by the user 107 from among the plurality of merchants.
[0058] At block 307, method 300 may include receiving, by processor 203, a merchant confirmation of acceptance of one or more payment methods 213 set by user 105 from at least one merchant selected 107 by user 105 from among multiple merchants. In some embodiments, the merchant confirmation is received when user details 211 provided by user 105 match pre-registered user details 211 stored at at least one merchant selected 107 by user 105 from among the multiple merchants. In some embodiments, the merchant confirmation is generated after successfully authenticating user 105 by payment processor 109 associated with at least one merchant selected 107 by user 105 from among the multiple merchants. In some embodiments, when one or more payment methods 213 set by user 105 are not accepted by at least one merchant among multiple merchants 103, automatically re-attempting to transmit the payment method(s) to at least one merchant among multiple merchants 103.
[0059] Figure 3B A flowchart illustrating a method for automatically transmitting payment methods to merchants is shown in accordance with some embodiments of the present disclosure.
[0060] The order in which method 310 is described is not intended to be construed as limiting, and any number of the described method blocks may be combined in any order to implement method 310. Additionally, individual blocks may be deleted from the method without departing from the spirit and scope of the subject matter described herein. Furthermore, method 310 may be implemented in any suitable hardware, software, firmware, or combination thereof.
[0061] At block 311, method 310 may include providing, by processor 203 of payment processing system 101, a list of multiple merchants 103 to user 105 to receive a user selection 107 of at least one merchant among multiple merchants 103 for deleting one or more payment methods 213 set for the multiple merchants 103.
[0062] At block 313, method 310 may include authenticating user 105 by processor 203 based on user details 211 provided by user 105 to authorize user 105 to delete one or more payment methods 213 for at least one merchant selected 107 by user 105 from among the multiple merchants.
[0063] At block 315, method 310 may include transmitting, by processor 203, user details 211, user authorization, and one or more payment methods 213 to be deleted to payment processor 109 associated with each merchant selected 107 by user 105 from among the multiple merchants.
[0064] At block 317, method 310 may include receiving, by processor 203, a merchant confirmation of deletion of one or more payment methods 213 from at least one merchant selected 107 by the user from a plurality of merchants.
[0065] Figure 4 FIG. 4 illustrates an exemplary scenario for authenticating user 105 in accordance with some embodiments of the present disclosure. Assume that user 105 selects merchant A from a plurality of merchants 103 to perform one or more transactions. In some embodiments, user details 211 provided by user 105 may include details for registration at merchant A (step 401). User details 211 may match pre-registered user details 211 stored at merchant A. In some embodiments, if user details 211 match, payment processor 1091 associated with merchant A may notify user 105 and request confirmation from user 105 (step 403). In some embodiments, after successfully authenticating user 105 by payment processor 1091 associated with at least one merchant selected 107 by the user from a plurality of merchants, a merchant confirmation is generated. After receiving the confirmation, user 105 may perform one or more transactions at merchant A without providing details related to one or more payment methods 213 to merchant A again.
[0066] In some embodiments, when user 105 wants to delete one or more payment methods 213 set by user 105 at merchant A, user details 211 may be matched with pre-registered user details 211 stored at merchant A. In some implementations, after successfully matching user details 211, payment processor 1091 associated with merchant A may notify user 105 and request confirmation from user 105. In some embodiments, after successfully authenticating user 105 by payment processor 1091 associated with at least one merchant selected 107 by the user from a plurality of merchants, a merchant confirmation is generated. After receiving the confirmation, payment processor 1091 may delete one or more payment details from payment processor 1091.
[0067] Figure 5 FIG. 11 is a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.
[0068] In some embodiments, computer system 500 may be a payment processing system 101 for automatically transmitting payment methods 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 to execute program components for performing user-generated or system-generated business processes. A user may include a person, a person using devices such as those included in the present 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, and the like.
[0069] Processor 502 may be configured to communicate with input device 511 and output device 512 via I / O interface 501. I / O interface 501 may employ communication protocols / methods such as, but not limited to, audio, analog, digital, stereo, IEEE-1394, serial bus, universal serial bus (USB), infrared, PS / 2, BNC, coaxial, component, composite, digital video 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), or WiMax, etc.).
[0070] Using I / O interface 501, computer system 500 may communicate with input device 511 and output device 512.
[0071] In some embodiments, processor 502 may be configured to communicate with communication network 509 via network interface 503. Network interface 503 may communicate with communication network 509. Network interface 503 may employ connection protocols including but not limited to, direct connection, Ethernet (e.g., twisted pair 10 / 100 / 1000 baseband (Base) T), transmission control protocol / internet protocol (TCP / IP), token ring, IEEE 802.11a / b / g / n / x, etc. Using network interface 503 and communication network 509, computer system 500 may interface with devices associated with user 105 and one or more payment processors 1071-107 N associated with each of a plurality of merchants to automatically transmit payment methods to the merchant.
[0072] In some embodiments, the communication network 509 may be implemented as one of different types of networks, such as, for example, an intranet or a local area network (LAN), a closed area network (CAN), and the like. The communication network 509 may be a private network or a shared network, which represents the association of different types of networks that communicate with each other using various protocols (such as, for example, Hypertext Transfer Protocol (HTTP), CAN protocol, Transmission Control Protocol / Internet Protocol (TCP / IP), Wireless Application Protocol (WAP), etc.). In addition, the communication network 509 may include various network devices, including routers, bridges, servers, computing devices, storage devices, etc. In some embodiments, the processor 502 may be configured to communicate with the memory 505 (such as, for example, Figure 5 RAM, ROM, etc. as shown in
[0073] via the storage interface 504. The storage interface 504 may be connected to the memory 505, which includes but is not limited to memory drives, removable disk drives, etc., and employs 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 drums, disk drives, magneto-optical drives, optical disk drives, Redundant Array of Independent Disks (RAID), solid state memory devices, solid state drives, etc.
[0074] The memory 505 may store program sets or database components, including but not limited to, the user interface 506, the operating system 507, the web browser 508, etc. In some embodiments, the computer system 500 may store user data / 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.
[0074] The operating system 507 may facilitate the resource management and operation of the computer system 500. Examples of operating systems include but are not limited to, OS UNIX-like system distributions (such as, for example, BERKELEY SOFTWARE (BSD), OPENBSD, etc.), distributions (such as, for example, RED etc.), ( 10, etc.), GOOGLE TM ANDROID TM or OS, etc. The user interface 506 can prompt the display, execution, interaction, manipulation, or operation of program components through text tools or graphical tools. For example, the user interface can provide computer interaction interface elements, such as a cursor, icons, check boxes, menus, scroll bars, windows, widgets, etc., on a display system operably connected to the computer system 500. A graphical user interface (GUI) can be adopted, including but not limited to, of the operating system (e.g., Aero, Metro, etc.) or web interface libraries (e.g., AJAX, HTML, etc.).
[0075] In some embodiments, the computer system 500 can implement program components stored in a web browser 508. The web browser 508 can be a hypertext viewing application, such as INTERNET GOOGLE TM CHROME TM , etc. Secure hypertext transfer protocol (HTTPS), secure socket layer (SSL), transport layer security (TLS), etc. can be used to provide secure web browsing. The web browser 508 can utilize tools such as AJAX, DHTML, application programming interface (API), etc. In some embodiments, the computer system 500 can implement program components stored in a mail server. The mail server can be an Internet mail server such as Microsoft Exchange. The mail server can utilize tools such as active server pages (ASP), C++ / C#, .NET, CGI scripts, PHP, etc. The mail server can utilize communication protocols such as Internet Message Access Protocol (IMAP), Message Application Programming Interface (MAPI), Exchange, Post Office Protocol (POP), or Simple Mail Transfer Protocol (SMTP), etc. In some embodiments, the computer system 500 can implement program components stored in a mail client. The mail client can be a mail viewing application such as mail, etc.
[0076] In addition, one or more computer-readable storage media may be used to implement embodiments consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor can be stored. Thus, a computer-readable storage medium can store instructions executable by one or more processors, including instructions for causing a 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 to exclude carrier waves and transient signals (i.e., non-transitory signals). Examples include random access memory (RAM), read-only memory (ROM), volatile memory, non-volatile storage, hard disk drives, compact disc (CD) ROMs, digital video discs (DVDs), flash drives, magnetic disks, and any other known physical storage media.
[0077] Unless otherwise expressly specified, the terms "an embodiment", "embodiment", "the embodiments", "the embodiment", "the multiple embodiments", "one or more embodiments", "some embodiments", and "an embodiment" mean "one or more (but not all) embodiments of the present invention".
[0078] Unless otherwise expressly specified, the terms "comprise", "include", "have" and their variants mean "including but not limited to".
[0079] Unless otherwise expressly specified, the listing of items does not imply that any or all of the items are mutually exclusive. Unless otherwise expressly specified, the terms "a" and "the" mean "one or more".
[0080] The description of embodiments with several components communicating with each other does not imply that all these components are required. Instead, various alternative components are described to illustrate the diverse feasible embodiments of the present disclosure.
[0081] When a single device or article is described herein, it is clear that more than one device / article (whether they cooperate or not) can be used in place of the single device / article. Similarly, when more than one device or article (whether they cooperate or not) are described herein, it is clear that a single device / article can be used in place of the more than one device / article, or a different number of devices / articles can be used in place of the indicated number of devices or programs. The functions and / or features of a device can alternatively be embodied by one or more other devices not expressly described as having such functions / features. Thus, other embodiments of the present disclosure do not need to include the device itself.
[0082] Figure 3A and Figure 3BThe illustrated operations show specific events occurring in a specific order. In alternative embodiments, specific operations may be performed, modified, or deleted in a different order. Additionally, steps may be added to the logic described above and still conform to the described embodiments. Further, the operations described herein may occur sequentially, or specific operations may be processed in parallel. Still further, the operations may be performed by a single processing unit or by distributed processing units.
[0083] Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to depict or circumscribe the subject matter of the invention. Accordingly, the scope of the disclosure is not limited by this detailed description, but rather by any claims that issue from this application based hereon. Consequently, the disclosure of embodiments of the present disclosure is intended to be illustrative, and not to limit the scope of the disclosure set forth in the appended claims.
[0084] Although various aspects and embodiments have been disclosed herein, other aspects and embodiments may be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for illustrative purposes only and are not intended to be limiting, and the true scope and spirit are indicated by the appended claims.
Claims
1. A computer-implemented method for automatically transmitting payment methods to merchants, the method 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 to perform one or more transactions; Authenticating the user based on user details provided by the user to authorize the user to set one or more payment methods for at least one of the plurality of merchants selected by the user; Transmitting the user details, user authorization, and the one or more payment methods set 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 at least one of the plurality of merchants selected by the user.
2. The computer-implemented method according to claim 1, wherein The merchant confirmation is received when the user details provided by the user match pre-registered user details stored on at least one of the plurality of merchants selected by the user.
3. The computer-implemented method according to claim 1, wherein The merchant confirmation is generated after the user is successfully authenticated by the payment processor associated with at least one of the plurality of merchants selected by the user.
4. The computer-implemented method according to claim 1, wherein, Authenticating the user comprises: Receiving details related to the one or more payment methods set by the user from the user; and Verifying the one or more payment methods based on the details related to the one or more payment methods.
5. The computer-implemented method according to claim 4, comprising: Dynamically re-verifying the one or more payment methods when a change in the details related to the one or more payment methods is detected.
6. The computer-implemented method according to claim 1, comprising: When the one or more payment methods set by the user are not accepted by at least one of the plurality of merchants, re-attempting to automatically transmit the payment methods to at least one of the plurality of merchants.
7. A computer-implemented method for automatically transmitting payment methods to merchants, the method 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 to delete one or more payment methods set for the plurality of merchants; Authenticating the user based on user details provided by the user to authorize the user to delete the one or more payment methods for at least one of the plurality of merchants selected by the user; 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 plurality of merchants selected by the user; And Receiving a merchant confirmation of deletion of the one or more payment methods from at least one of the plurality of merchants selected by the user.
8. A payment processing system, comprising: A processor; and A memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions that, when executed, cause the processor to: Provide a list of multiple merchants to a user to receive a user selection of at least one merchant from the multiple merchants for performing one or more transactions; Authenticate the user based on user details provided by the user to authorize the user to set one or more payment methods for the at least one merchant selected by the user from the multiple merchants; Transmit the user details, user authorization, and the one or more payment methods set by the user to a payment processor associated with each merchant selected by the user from the multiple merchants; And Receive from the at least one merchant selected by the user from the multiple merchants a merchant confirmation of acceptance of the one or more payment methods set by the user.
9. The payment processing system according to claim 8, wherein The merchant confirmation is received when the user details provided by the user match pre-registered user details stored on the at least one merchant selected by the user from the multiple merchants.
10. The payment processing system according to claim 8, wherein The merchant confirmation is generated after the user is successfully authenticated by the payment processor associated with the at least one merchant selected by the user from the multiple merchants.
11. The payment processing system according to claim 8, wherein, Authenticating the user includes: Receiving from the user details related to the one or more payment methods set by the user; and Verifying the one or more payment methods based on the details related to the one or more payment methods.
12. The payment processing system according to claim 11, comprising: Dynamically re-verifying the one or more payment methods when a change in the details related to the one or more payment methods is detected.
13. The payment processing system according to claim 8, comprising: When the one or more payment methods set by the user are not accepted by the at least one merchant among the multiple merchants, automatically re-attempt to transmit the payment methods to the at least one merchant among the multiple merchants.
14. A payment processing system, comprising: A processor; and A memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions that, when executed, cause the processor to: Provide a list of multiple merchants to a user to receive a user selection of at least one merchant from the multiple merchants for deleting one or more payment methods set for the multiple merchants; Authenticate the user based on user details provided by the user to authorize the user to delete the one or more payment methods for the at least one merchant selected by the user from the multiple merchants; Transmit the user details, user authorization, and the one or more payment methods to be deleted to a payment processor associated with each merchant selected by the user from the plurality of merchants; and Receive a merchant confirmation of the deletion of the one or more payment methods from at least one merchant selected by the user from the plurality of merchants.
15. A non-transitory computer-readable medium comprising instructions stored thereon that, when processed by at least one processor, cause a payment processing system to perform operations comprising: Provide a list of a plurality of merchants to a user to receive a user selection of at least one merchant from the plurality of merchants to perform one or more transactions; Authenticate the user based on user details provided by the user to authorize the user to set one or more payment methods for at least one merchant selected by the user from the plurality of merchants; Transmit the user details, user authorization, and the one or more payment methods set by the user to a payment processor associated with each merchant selected by the user from the plurality of merchants; and Receive a merchant confirmation of the acceptance of the one or more payment methods set by the user from at least one merchant selected by the user from the plurality of merchants.
16. A non-transitory computer-readable medium comprising instructions stored thereon that, when processed by at least one processor, cause a payment processing system to perform operations comprising: Provide a list of a plurality of merchants to a user to receive a user selection of at least one merchant from the plurality of merchants to delete one or more payment methods set for the plurality of merchants; Authenticate the user based on user details provided by the user to authorize the user to delete the one or more payment methods for at least one merchant selected by the user from the plurality of merchants; Transmit the user details, user authorization, and the one or more payment methods to be deleted to a payment processor associated with each merchant selected by the user from the plurality of merchants; and Receive a merchant confirmation of the deletion of the one or more payment methods from at least one merchant selected by the user from the plurality of merchants.