Claims:CLAIMS:
I/We claim:

1. A computer-implemented method for performing a payment transaction, the method comprising:
electronically facilitating, by a server system associated with a payment network, a pay-by-friend option on a merchant interface in a user interface of a user for making the payment transaction;
receiving, by the server system, a selection of one or more member users provided by the user upon selection of the pay-by-friend option by the user, the one or more member users associated with the pay-by-friend option;
sending, by the server system, a notification signal to the one or more member users for performing the payment transaction, the notification signal comprising at least a user name data of each member user, a payment transaction amount data and a merchant data; and
notifying, by the server system, a payment settlement to the user upon successful completion of the payment transaction by the one or more member users.

2. The method as claimed in claim 1, wherein sending the notification signal comprises:
receiving, by the server system, a confirmation from each of the one or more member users for performing the payment transaction, each confirmation comprising a contribution amount to be contributed by each member user;
transmitting, by the server system, a confirmation signal to the user; and
processing, by the server system, the payment transaction based on the confirmation signal.

3. The method as claimed in claim 1, further comprising:
creating a user account of the user upon registration of the user in an application interface associated with the server system; and
upon creation of the user account, creating a group by the user corresponding to the pay-by-friend option by the user at the application interface, the group comprising the user and one or more friends of the user.

4. The method as claimed in claim 3, wherein the one or more friends are selected from at least one of a contact list of the user and a friend list in a social media account of the user.

5. The method as claimed in claim 4, further comprising:
facilitating, by the server system, creating of a group fund for the group via the application interface, the group fund comprising a fund amount contributed by the user and each friend in the group; and
upon creation of the group fund, notifying, by the server system, the fund amount to the user and the group via the application interface.

6. The method as claimed in claim 5, wherein creating the group fund comprises:
receiving, by the server system, a contribution request provided by the user via the application interface for the group fund, the contribution request includes a contribution amount to be contributed by the user;
sending, by the server system, the contribution request to each friend in the group;
receiving, by the server system, a response provided by each friend upon receipt of the contribution request, the response comprising the contribution amount of each friend to be contributed for the group fund; and
processing, by the server system, deduction of each contribution amount from corresponding payment account of the user and the friends of the group for the group fund upon agreement on each contribution amount by the group.

7. The method as claimed in claim 6, further comprising:
facilitating, by the server system, setting of a minimum limit and a maximum limit on the contribution amount for the group fund by the group, the minimum limit and the maximum limit associated with a minimum amount and a maximum amount respectively permitted for contributing to the group fund; and
processing, by the server system, deduction of the contribution amount from the corresponding payment accounts upon agreement on the minimum limit and the maximum limit by the group.

8. The method as claimed in claim 7, further comprising:
receiving, by the server system, a rejection from at least one or more friends of the group for a contribution to the group fund;
facilitating, by the server system, a modification of the contribution amount by the at least one or more friends via the application interface based on the rejection; and
sending, by the server system, a notification for a modified contribution amount to the group.

9. The method as claimed in claim 8, further comprising:
facilitating, by the server system, updating of the minimum limit and the maximum limit based on the modified contribution amount; and
processing, by the server system, deduction of the modified contribution amount from the corresponding payment accounts upon agreement on an updated minimum limit and an updated maximum limit by the group.

10. The method as claimed in claim 6, further comprising:
receiving, by the server system, a withdrawal request from at least one of the user or a friend from the group for withdrawing from the group fund, the withdrawal request comprising a withdrawal amount;
determining, by the server system, whether the withdrawal amount is within a corresponding contribution amount contributed by the at least one of the user and the group; and
deducting, by the server system, the withdrawal amount from the group fund based on the determination.

11. The method as claimed in claim 10, further comprising:
determining, by the server system, a pending amount for the withdrawal based on the deduction;
sending, by the server system, a notification to the group for approving a withdrawal of the pending amount;
receiving, by the server system, an approval from one or more friends in the group for the withdrawal; and
completing, by the server system, deduction of the pending amount from the group fund based on the approval.

12. A server system for performing a payment transaction, the server system comprising:
a memory comprising stored instructions; and
a processor configured to execute the stored instructions to cause the server system to perform at least in part to:
electronically facilitate a pay-by-friend option on a merchant interface in a user device for making the payment transaction;
receive facilitate a selection of one or more member users provided by the user upon selection of the pay-by-friend option by the user, the one or more member users associated with the pay-by-friend option;
send a notification signal for performing the payment transaction to the one or more member users, the notification signal comprising at least user name data of each member user, a payment transaction amount data and a merchant data; and
notify a payment settlement to the user upon successful completion of the payment transaction by the one or more member users.

13. The server system as claimed in claim 12, wherein for sending the notification signal, the server system is caused to perform at least in part to:
receive a confirmation from each of the one or more member users for performing the payment transaction, each confirmation comprising a contribution amount to be contributed by each member user;
transmit a confirmation signal to the user; and
process the payment transaction based on the confirmation signal.

14. The server system as claimed in claim 12, wherein the server system is caused to perform at least in part to:
creating a user account of the user upon registration of the user in an application interface associated with the server system; and
upon creation of the user account, creating a group corresponding to the pay-by-friend option by the user at the application interface, the group comprising the user and one or more friends of the user selected from at least one of a contact list of the user and a friend list in a social media account of the user.

15. The server system as claimed in claim 14, wherein the server system is caused to perform at least in part to:
facilitate creating of a group fund for the group via the application interface, the group fund comprising a fund amount contributed by the user and each friend in the group; and
upon creation of the group fund, notify the fund amount to the group via the application interface.

16. The server system as claimed in claim 15, wherein for creating the group fund, the server system is further caused to perform at least in part to:
receive a contribution request provided by the user via the application interface for the group fund, the contribution request comprising a contribution amount to be contributed by the user;
send the contribution request to each friend in the group;
receive a response provided by each friend upon receipt of the contribution request, the response comprising the contribution amount of each friend to be contributed for the group fund; and
process deduction of each contribution amount from corresponding payment account of the user and the friends of the group for the group fund upon agreement on each contribution amount by the group.

17. The server system as claimed in claim 16, wherein the server system is further caused to perform at least in part to:
facilitate setting of a minimum limit and a maximum limit on the contribution amount for by the group, the minimum limit and the maximum limit associated with a minimum amount and a maximum amount respectively permitted for contributing to the group fund; and
process deduction of the contribution amount from the corresponding payment accounts upon agreement on the minimum limit and the maximum limit by the group.

18. The server system as claimed in claim 17, wherein the server system is further caused to perform at least in part to:
receive a rejection from at least one or more friends of the group for a contribution amount to be contributed for the group fund;
facilitate a modification of the contribution amount by the at least one or more friends via the application interface based on the rejection; and
send a notification for a modified contribution amount to the group.

19. The server system as claimed in claim 18, wherein the server system is further caused to perform at least in part to:
facilitate updating of the minimum limit and the maximum limit based on the modified contribution amount; and
process deduction of the modified contribution amount upon agreement on an updated minimum limit and an updated maximum limit by the group.

20. The server system as claimed in claim 16, wherein the server system is further caused to perform at least in part to:
receive a withdrawal request from at least one of the user and a friend from the group for withdrawing from the group fund, the withdrawal request comprising a withdrawal amount;
determine whether the withdrawal amount is within a corresponding contribution amount contributed by the at least one of the user and the friend;
deduct the withdrawal amount from the group fund based on the determination;
determine a pending amount for the withdrawal based on the deduction;
send a notification to the group for approving a withdrawal of the pending amount;
receive an approval from one or more friends in the group for the withdrawal; and
complete deduction of the pending amount from the group fund based on the approval. , Description:FORM 2
THE PATENTS ACT 1970
(39 of 1970)
&
The Patent Rules 2003
COMPLETE SPECIFICATION
(refer section 10 & rule 13)

1. TITLE OF THE INVENTION:
METHODS AND SYSTEMS FOR PERFORMING A PAY BY FRIEND PAYMENT TRANSACTION FOR USERS

2. APPLICANT(S):

(a) Name:

(b) Nationality:

(c) Address:

MASTERCARD INTERNATIONAL INCORPORATED

United States of America

2000 Purchase Street, Purchase, NY 10577, United States of America

3. PREAMBLE TO THE DESCRIPTION

The following specification particularly describes the invention and the manner in which it is to be performed.

4. DESCRIPTION
(See next page)

METHODS AND SYSTEMS FOR PERFORMING A PAY BY FRIEND PAYMENT TRANSACTION FOR USERS

TECHNICAL FIELD

[0001] The present disclosure generally relates to a payment technology and, more particularly to, methods and systems for performing a payment transaction of a user by friends, family members or others known to the user.
BACKGROUND
[0002] Nowadays, digital payment transactions for goods/services are popular among many users. Generally, the payment transactions are performed using payment cards, such as bank cards, debit cards, credit cards, or the like. For instance, a user provides information of a payment card on an e-commerce website for making a payment transaction of an online purchase. When the user is not having sufficient balance in his payment account, the user may seek help from his near and dear ones. The user may use a payment card belonging to a family member. In some cases, a single payment card may be shared among family members. For instance, a father’s payment card may be shared to a son with a permission of the father. The user may also request a friend to share his payment card for the payment transaction. The family member or the friend may be required to share confidential information, such as password, PIN, card number or any other information corresponding to the payment card to the user for making the payment transaction.
[0003] However, sharing of the confidential information entails high security risks and vulnerability to thefts or frauds. During a payment transaction process, the confidential information may be shared to different parties, which increases security risks. In case the user is not able to provide certain information for identification, then the payment card may be blocked. There may also be chances of closing a bank account of a person, in case a bank or a credit card company finds out that the person is sharing his payment card with others. It may be a tedious and complicated process for a card owner to unblock the card or the account. It may also happen that a person may not be comfortable sharing the payment card with others due to the risk and vulnerability. When a bank (that issued the payment card) finds out that a card is being shared to others, then it may be counted as a violation according to terms and conditions of the bank. There may be consequences that those who shared the payment card may face charges or legal penalties.
[0004] Therefore, there exists a need to provide a technological solution to perform a payment transaction for a user by others in a safe and secure manner, without violating privacy and security concerns. It would be advantageous to perform the payment transaction, without sharing any confidential information.

SUMMARY

[0005] Various embodiments of the present disclosure provide systems and methods for performing a payment transaction of a user by others, such as a friend, a family member or a relative.
[0006] In an embodiment, a computer-implemented method for performing a payment transaction is disclosed. The method includes electronically facilitating, by a server system associated with a payment network, a pay-by-friend option on a merchant interface in a user device of a user for making the payment transaction. The method includes receiving, by the server system, a selection of one or more member users provided by the user upon selection of the pay-by-friend option by the user, the one or more member users associated with the pay-by-friend option. The method includes sending, by the server system, a notification signal to the one or more member users for performing the payment transaction. The notification includes at least a user name data of each member user, a payment transaction amount data and a merchant data. The method further includes notifying, by the server system, a payment settlement to the user upon successful completion of the payment transaction by the one or more member users.
[0007] In another embodiment, a server system for performing the payment transaction is disclosed. The server system includes a memory and a processor. The memory includes stored instructions. The processor is configured to execute the stored instructions to cause the server system to perform at least in part to electronically facilitate a pay-by-friend option on a merchant interface in a user device of a user for making the payment transaction. The server system is caused to receive a selection of one or more member users provided by the user upon selection of the pay-by-friend option by the user. The one or more member users are associated with the pay-by-friend option. The server system is caused to send a notification signal to the one or more member users for performing the payment transaction. The notification signal includes at least user name data of each member user, a payment transaction amount data and a merchant data. The server system is further caused to notify a payment settlement to the user upon successful completion of the payment transaction by the one or more member users.
[0008] Other aspects and example embodiments are provided in the drawings and the detailed description that follows.

BRIEF DESCRIPTION OF THE FIGURES

[0009] For a more complete understanding of example embodiments of the present technology, reference is now made to the following descriptions taken in connection with the accompanying drawings in which:

[0010] FIG. 1 illustrates an example representation of an environment related to at least some example embodiments of the present disclosure;
[0011] FIG. 2 illustrates a sequence flow diagram depicting a process flow of performing a payment transaction for a user using a pay-by-friend option, in accordance with an example embodiment of the present disclosure;
[0012] FIG. 3 represents a sequence flow diagram for performing a payment transaction of the user by one or more friends in a group created by the user, in accordance with another example embodiment of the present disclosure;
[0013] FIG. 4A represents a sequence flow diagram for creating a group fund of the group, in accordance with an example embodiment of the present disclosure;
[0014] FIG. 4B represents a sequence flow diagram for creating a group fund of the group, in accordance with another example embodiment of the present disclosure;
[0015] FIG. 5 represents a sequence flow diagram for withdrawing from the group fund, in accordance with another example embodiment of the present disclosure;
[0016] FIG. 6A shows an example representation of a user interface (UI) displayed to a user on a display screen of a user device displaying a pay-by-friend option for performing a payment transaction of the user, in accordance with an example embodiment of the present disclosure;
[0017] FIG. 6B shows an example representation of a UI displayed to the user on the display screen displaying one or more member users associated with the pay-by-friend option, in accordance with an example embodiment of the present disclosure;
[0018] FIG. 6C shows an example representation of a UI displayed to the user on the display screen displaying a notification on a payment settlement for the payment transaction performed by the one or more users, in accordance with an example embodiment of the present disclosure;
[0019] FIG. 7A shows an example representation of a UI displayed to the user on the display screen of the user device depicting a creation of a user account of the user upon registration of the user in an application interface, in accordance with an example embodiment of the present disclosure;
[0020] FIG. 7B shows an example representation of a UI displayed to the user on the display screen depicting the user account, in accordance with an example embodiment of the present disclosure;
[0021] FIG. 7C shows an example representation of a UI displayed to the user on the display screen depicting selection of one or more friends for the group from at least a contact list of the user and a friend list in a social media account of the user, in accordance with an example embodiment of the present disclosure;
[0022] FIG. 7D shows an example representation of a UI displayed to the user on the display screen depicting the contact list, in accordance with an example embodiment of the present disclosure;
[0023] FIG. 7E shows an example representation of a UI displayed to the user on the display screen depicting the friend list, in accordance with an example embodiment of the present disclosure;
[0024] FIG. 7F shows an example representation of a UI displayed to the user on the display screen displaying the group created by the user, in accordance with an example embodiment of the present disclosure;
[0025] FIG. 8A shows an example representation of a UI displayed to the user on the display screen depicting a creation of a group fund for the group, in accordance with an example embodiment of the present disclosure;
[0026] FIG. 8B shows an example representation of a UI displayed to the user on the display screen depicting receipt of each response and a contribution amount to be contributed by each friend of the group for the group fund, in accordance with an example embodiment of the present disclosure;
[0027] FIG. 8C shows an example representation of a UI displayed to the user on the display screen displaying the group fund to the user and the group, in accordance with an example embodiment of the present disclosure;
[0028] FIG. 9A shows an example representation of a UI displayed to the user on the display screen depicting sending of a withdrawal request for withdrawing from the group fund, in accordance with an example embodiment of the present disclosure;
[0029] FIG. 9B shows an example representation of a UI displayed to the user on the display screen displaying deduction of the withdrawal amount from the group fund, in accordance with an example embodiment of the present disclosure;
[0030] FIG. 9C shows an example representation of a UI displayed to the user on the display screen depicting deduction of a withdrawal amount from the group fund, in accordance with an example embodiment of the present disclosure;
[0031] FIG. 10 illustrates a flow diagram depicting a method for performing a payment transaction, in accordance with an example embodiment of the present disclosure;
[0032] FIG. 11 is a simplified block diagram of a server system for performing the payment transaction, in accordance with an embodiment of the present disclosure;
[0033] FIG. 12 is a simplified block diagram of a payment server for performing the payment transaction, in accordance with an embodiment of the present disclosure;
[0034] FIG. 13 is a simplified block diagram of an issuer server, in accordance with an embodiment of the present disclosure;
[0035] FIG. 14 is a simplified block diagram of an acquirer server, in accordance with an embodiment of the present disclosure; and
[0036] FIG. 15 shows a simplified block diagram of a user device capable of implementing the various embodiments of the present disclosure.
[0037] The drawings referred to in this description are not to be understood as being drawn to scale except if specifically noted, and such drawings are only exemplary in nature.

DETAILED DESCRIPTION

[0038] In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be apparent, however, to one skilled in the art that the present disclosure can be practiced without these specific details.
[0039] Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. The appearance of the phrase “in an embodiment” in various places in the specification is not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not for other embodiments.
[0040] Moreover, although the following description contains many specifics for the purposes of illustration, anyone skilled in the art will appreciate that many variations and/or alterations to said details are within the scope of the present disclosure. Similarly, although many of the features of the present disclosure are described in terms of each other, or in conjunction with each other, one skilled in the art will appreciate that many of these features can be provided independently of other features. Accordingly, this description of the present disclosure is set forth without any loss of generality to, and without imposing limitations upon, the present disclosure.
[0041] The term "payment account" used throughout the description refers to a financial account that is used to fund the financial transaction (interchangeably referred to as "payment transaction"). Examples of the payment account include, but are not limited to a savings account, a credit account, a checking account and a virtual payment account. The payment account may be associated with an entity such as an individual person, a family, a commercial entity, a company, a corporation, a governmental entity, a non-profit organization and the like. In some scenarios, a payment account may be a virtual or temporary payment account that can be mapped or linked to a primary payment account, such as those accounts managed by PayPal®, and the like.
[0042] The term "payment card", used throughout the description, refers to a physical or virtual card linked with a financial or payment account that may be presented to a merchant or any such facility in order to fund a financial transaction via the associated payment account. Examples of the payment card include, but are not limited to, debit cards, credit cards, prepaid cards, virtual payment numbers, virtual card numbers, forex cards, charge cards, e-wallet cards, and stored-value cards. A payment card may be a physical card that may be presented to the merchant for funding the payment. Alternatively or additionally, the payment card may be embodied in form of data stored in a user device, where the data is associated with payment account such that the data can be used to process the financial transaction between the payment account and a merchant's financial account.
[0043] The term "payment network", used throughout the description, refers to a network or collection of systems used for transfer of funds through use of cash-substitutes. Payment networks may use a variety of different protocols and procedures in order to process the transfer of money for various types of transactions. Transactions that may be performed via a payment network may include product or service purchases, credit purchases, debit transactions, fund transfers, account withdrawals, etc. Payment networks may be configured to perform transactions via cash-substitutes, which may include payment cards, letters of credit, checks, financial accounts, etc. Examples of networks or systems configured to perform as payment networks include those operated by Mastercard®, VISA®, Discover®, American Express®, etc.
OVERVIEW
[0044] Various example embodiments of the present disclosure provide systems and methods for performing a payment transaction that overcome above-mentioned obstacles and provide additional advantages. More specifically, techniques disclosed herein enable performing of the payment transaction of a user by other users known to the user through a pay-by-friend option.
[0045] In an illustrative example scenario, the user is purchasing goods/services on a merchant interface using a user device of the user. At the time of payment, a pay-by-friend option is displayed to the user via the merchant interface. The user selects the pay-by-friend option for making the payment transaction. After selecting the pay-by-friend option, the user is directed to a link that displays member users that are associated with the pay-by-friend option. The user selects one or more member users for the payment transaction. A notification is sent to each selected member user for performing the payment transaction. The notification includes a user name of each member user, a payment transaction amount, a merchant information and other information corresponding to the payment transaction. The user receives a confirmation signal for performing the payment transaction from each selected member user. The payment transaction is processed based on the confirmation. Further, a payment settlement is notified to the user upon successful completion of the payment transaction by the one or more member users.
[0046] The payment transaction may also be performed by a group of friends of the user. In at least one example embodiment, the user creates a user account upon registration of the user in an application interface. After the user account creation, the user creates a group corresponding to the pay-by-friend option. The group includes the user and one or more friends of the user. The one or more friends are selected from a contact list of the user such as friends, family member, co-workers, or contacts in a social media account of the user. Further, the user creates a group fund for the group via the application interface. The group fund includes a fund amount contributed by the user and each friend in the group. In an example, the user may provide a contribution request for the group fund at the application interface. The contribution request is sent to each friend in the group. The contribution request includes a contribution amount to be contributed by the user. The contribution amount is notified to the friends upon receipt of the contribution request. Each friend provides a response to the contribution request. Each response includes a contribution amount to be contributed for the group fund. The responses and the contribution amounts are notified to the user as well as the group. When the user and the group have same agreement on the contribution amounts, each contribution amount is processed for deduction from corresponding account of each friend.
[0047] In one example embodiment, the user may set a minimum limit and a maximum limit on a contribution amount. The minimum limit and the maximum limit are associated with a minimum amount and a maximum amount respectively permitted for the contribution. After the setting, the minimum limit and the maximum limit are notified to each friend of the group. In some cases, one or more friends may desire to update or modify their contribution amount. In such cases, the one or more friends may reject their contribution amounts and modify their contribution amounts via their application interface. The modified contribution amount is notified to remaining friends in the group. Further, the minimum limit and the maximum limit are updated based on the modified contribution amount. The updated minimum limit and the updated maximum limit are notified to each friend of the group.
[0048] The fund amount of the group fund may be used by the user and the group based on a requirement. In an example embodiment, the user sends a withdrawal request for withdrawing a withdrawal amount from the group fund. The withdrawal amount is deducted from the group fund based on determining whether the withdrawal amount is within a contribution amount contributed by the user. For example, the user sends the withdrawal request for withdrawing an amount of $100 from the group fund with a fund amount of $1000. In such case, if the withdrawal amount, i.e., $100 is within a contribution amount contributed by the user, then $100 is deducted from $1000. There may be cases that the withdrawal amount is less than the contribution amount. For example, the contribution amount contributed by the user is $50, then withdrawal of $50 is permitted to the user. Here, there is a pending amount, such as $50 left for completing the withdrawal of $100. A notification is sent to the group for approving a withdrawal of the pending amount. The pending amount is then deducted from the group fund based on the approval. For example, one of the friends in the group approves deduction of the pending amount from the group fund and completes the withdrawal of the user.
[0049] Thus, the payment transaction performed by one or more users for the user, is further explained in detail with reference to FIGS. 1 to 15.
[0050] FIG. 1 illustrates an example representation of an environment 100 related to at least some example embodiments of the present disclosure. The environment 100 is depicted to include a user 102 associated with a user device 104. The user device 104 may be a smartphone, a tablet, a laptop, a computer system or any computing device. In an illustrative example scenario, the user 102 purchases online goods/services through a merchant interface (not shown in FIG.1) using the user device 104. At a payment checkout time, the user 102 selects a pay-by-friend option on a merchant interface for making a payment transaction of the purchased goods/services. After the selection of the pay-by-friend option, the user 102 may be directed to a page that displays member users, such as member user 106a, member user 106b and member user 106c. The member users 106a-106c are associated with the pay-by-friend option. Moreover, the member users 106a-106c may include friends, family members, work colleagues or any other users known to the user 102. The user 102 selects the member users 106a-106c for performing the payment transaction.
[0051] In an example embodiment, the user device 104 includes an application interface 120 that provides the pay-by-friend option on the merchant interface. The application interface 120 is interchangeably referred to hereinafter as application 120. The application 120 is associated with a payment server 110. More specifically, instances of the application 120 hosted by the payment server 110 may be downloaded and installed in the user device 104. The user device 104 may communicate with the payment server 110 via a network, such as a network 112. The network 112 may include wired networks, wireless networks and combinations thereof. Some non-limiting examples of the wired networks may include Ethernet, local area networks (LANs), fiber-optic networks, and the like. Some non-limiting examples of the wireless networks may include cellular networks like GSM/3G/4G/5G/LTE/CDMA networks, wireless LANs, Bluetooth, Wi-Fi or Zigbee networks, and the like. An example of the combination of wired and wireless networks may include the Internet.
[0052] The payment server 110 sends a notification for performing the payment transaction to the member users 106a-106c. The notification includes at least a user name of each member user, a payment transaction amount, a merchant information and information corresponding to the payment transaction. The payment server 110 receives a confirmation signal and a contribution amount from each of the member user, such as the member user 106a, the member user 106b and the member user 106c for performing the payment transaction. The confirmation signal and the contribution amount of each of the member user are notified to the user 102 and the member users 106a-106c. For instance, the confirmation and contribution amount of member user 106a are notified to the user 102, the member user 106b and the member user 106c.
[0053] Further, the payment server 110 processes the payment transaction upon agreement of the contribution amounts by the user 102 and the member users 106a-106c. For instance, the payment server 110 sends a payment transaction request for the payment transaction to an issuer, such as an issuer 114. In one example embodiment, each payment account of each member user (i.e., the member users 106a-106c) may belong to same issuer, such as the issuer 114. In another example embodiment, each payment account of each member user may belong to different issuers like the issuer 114. The issuer 114 validates the payment transaction upon receipt of the payment transaction request. After the validation, the issuer 114 debits corresponding contribution amount of each of the member users from their payment account. The issuer 114 transfers each corresponding contribution amount to the payment server 110. The payment server 110 receives each corresponding contribution amount and settles the payment transaction amount to an acquirer, such as an acquirer 116. The acquirer 116 disclosed herein is an acquirer bank of the merchant interface. Further, the payment server 110 notifies the payment settlement to the user 102 upon successful completion of the payment transaction by the member users 106a-106c.
[0054] The payment transaction may be performed by one or more friends in a group, such as group 106 created by the user 102. In one example embodiment, the user 102 creates a user account upon registration in the application 120. After the user account creation, the user 102 creates the group 106 corresponding to the pay-by-friend option. The group 106 includes the user 102 and one or more friends of the user 102 selected from a contact list of the user 102 or a friend list in a social media account of the user 102. For instance, the group 106 includes the user 102, a friend 106a, a friend 106b and a friend 106c. Each friend uses the application 120 installed in their respective user devices (not shown in FIG. 1). It is noted that the description of the group 106 is provided with respect to the friends (e.g., the friends 106a-106c) of the user 102 and this shall not limit the scope of the present disclosure as the group 106 may include family members, work colleagues, roommates, or any other users known to and trusted by the user 102. Moreover, number of members in the group 106 may range from a small number to a large number depending on agreement between its users. Herein, the number of members in the group, disclosed throughout the present description, is kept to the small number, such as 3 members for explanation purpose.
[0055] Further, the user 102 creates a group fund for the group 106 at application 120. The group fund includes a fund amount, such as $5000 contributed by the user 102 and each friend in the group 106. The group fund may be stored in a cloud storage, such as database 108. In one example embodiment, the database 108 may be associated with the payment server 110. In another example embodiment, the database 108 may be embodied in the payment server 110. The group fund is displayed to the user 102 and the group 106 via the application interface 120. The group fund may be used for payments of a bill that are shared among the user 102 and the friends 106a-106c.
[0056] In an illustrative example scenario, the user 102 may be sharing a rented apartment with friends, such as friend 106a, friend 106b and friend 106c. The user 102 may create a group fund for paying a rent of the apartment. For the group fund creation, the user 102 provides a contribution request to the payment server 110 via the application interface 120. The contribution request includes a contribution amount to be contributed by the user 102. For instance, the user 102 states a contribution amount of $1000 for the group fund. The payment server 110 receives the contribution request and sends the contribution request to each friend in the group 106. When the friends 106a-106c receive the contribution request, the contribution amount of $1000 is notified to the friends 106a-106c. Each friend provides a response and a contribution amount to be contributed for the group fund to the payment server 110 via the application 120.
[0057] The payment server 110 notifies the responses and the contribution amounts of each friend to the group 106. For instance, the friend 106a provides a confirmation to the contribution along with a contribution amount of $500. The friend 106b provides a confirmation along with a contribution amount of $800. The friend 106c provides a confirmation along with a contribution amount of $200. When each individual in the group 106 has agreed to the contribution amounts, each contribution amount is deducted from their corresponding payment accounts of the individuals. The agreement may be provided in the application interface 120. The payment server 110 processes the deduction of each contribution amount from a payment account of the user 102, a payment account of the friend 106a, a payment account of the friend 106b and a payment account of the friend 106c.
[0058] In an example embodiment, the user 102 sets a minimum limit and a maximum limit on a contribution amount for the group fund. The minimum limit is a minimum amount and the maximum limit is a maximum amount permitted for contributing to the group fund. For instance, the user 102 sets a minimum limit of $500 and a maximum limit of $1000 for the contribution. The minimum limit and the maximum limit are notified to the group 106. Each contribution amount is deducted from their corresponding payment accounts upon agreement on the minimum limit and the maximum limit by the group 106. The agreement is provided to the payment server 110 via the application 120. The payment server 110 processes the deduction of each contribution amount from the corresponding payment accounts. The fund amount based on the contribution amounts creates the group fund. For example, the user 102 contributes $1000, the friend 106a contributes $500, the friend 106b contributes $900 and the friend 106c contributes $600. Each contribution amount is not less than the minimum limit (i.e., $500) and is not more than the maximum limit (i.e., $1000). The fund amount obtained is $(1000+500+900+600) = $3000, which is the group fund.
[0059] In some cases, one or more friends may reject a contribution amount to be contributed for the group fund. For example, the user 102, the friend 106a and the friend 106b may agree to a contribution amount of $2000. The friend 106c rejects the contribution amount of $2000. The friend 106c provides a rejection for the contribution amount, i.e., $2000 to the payment server 110. The friend 106c modifies the contribution amount via the application 120. For instance, the friend 106c modifies the contribution amount, such as $1000. The payment server 110 sends a notification for the modified contribution amount to the user 102, the friend 106a and the friend 106b. Further, the minimum limit and the maximum limit are updated based on modified contribution amount. The updated minimum limit and the updated maximum limit are notified to the group 106.
[0060] Further, the group fund can be used by any individual of the group 106. In an example embodiment, the payment server 110 receives a withdrawal request from the user 102 for withdrawing from the group fund. The withdrawal request includes a withdrawal amount and information corresponding to the withdrawal. In an illustrative example scenario, the user 102 sends the withdrawal request for a withdrawal amount of $500 to the payment server 110 via the application interface 120. The payment server 110 determines whether the withdrawal amount, i.e., $500 is within the contribution amount contributed by the user 102. For instance, the payment server 110 checks if the withdrawal amount $500 is less than the contribution amount, such as $1000 (i.e., $500<$1000). The withdrawal amount is deducted from the group fund based on the determination, i.e., the withdrawal amount $500 is deducted from the group fund with the fund amount of $3000. In case, the withdrawal amount exceeds the contribution amount, then amount equivalent to the contribution amount is deducted from the group fund and a pending amount for the withdrawal is notified to the group 106. The deduction of the pending amount is completed based on approval from one or more friends in the group 106.
[0061] Some non-exhaustive example embodiments of performing the payment transaction for the user 102 by the one or more members users 106a-106c or the group 106 through the pay-by-friend option, are described with reference to FIGS. 2 to 15. It shall be understood that the group 106 shown in FIGS. 2 to 5 is a collective representation of the one or more member users 106a-106c or the friends 106a-106c.
[0062] FIG. 2 illustrates a sequence flow diagram 200 depicting a process flow of performing a payment transaction for the user 102 using a pay-by-friend option, in accordance with an example embodiment of the present disclosure. In an illustrative example scenario, the user 102 is purchasing from a merchant interface using the user device 104. The pay-by-friend option is displayed in the merchant interface at the time of payment checkout. The pay-by-friend option enables the payment transaction to be performed by friends, family members or colleagues of the user 102.
[0063] At 202, the user 102 selects the pay-by-friend option in the merchant interface. When the pay-by-friend option is selected, the user 102 is directed to the application interface 120 that displays one or more member users 106a-106c associated with the pay-by-friend option. At 204, the user 102 selects the one or more member users, such as the member users 106a-106c of FIG. 1.
[0064] At 206, the selected member users 106a-106c are notified to the payment server 110 via the application interface 120. The application interface 120 communicates with the payment server 110 through application program interface (API) calls.
[0065] At 208, the payment server 110 sends a notification for performing the payment transaction to the member users 106a-106c. The notification includes a user name of each member user, a payment transaction amount, a merchant information and information corresponding to the payment transaction. In one embodiment, the notification is provided to each member user via the application interface 120 in respective user devices of the member users 106a-106c. In an alternate embodiment, the payment server 110 sends the notification using a registered contact number of the member users 106a-106c.
[0066] At 210, each member user provides their confirmation and their contribution amount to be contributed for the payment transaction to the payment server 110. At 212, the payment server 110 processes the payment transaction based on the confirmation and the contribution amounts. At 214, the payment server 110 notifies a payment settlement to the user 102 upon successful completion of the payment transaction by the member users 106a-106c.
[0067] In an example embodiment, the payment transaction may be performed by one or more friends in a group, such as the group 106 created by the user 102 via the application 120. The payment transaction performed by the one or more friends in the group 106 is described further with reference to FIG. 3.
[0068] Referring now to FIG. 3, a sequence flow diagram 300 for performing the payment transaction of the user 102 by the one or more friends in the group 106, is represented in accordance with an example embodiment of the present disclosure. At 302, the user 102 creates a user account at the application 120. For instance, the user account may be created using a contact number, a user name or an email ID of the user 102. At 304, the user 102 creates a group, such as the group 106 at the application interface 120. The group 106 is created based on selecting one or more friends (such as friends 106a-106c of FIG. 1) from a contact list in the user device 104. The user 102 may also select the friends from a friend list in a social media account of the user 102. The group 106 is used by the user 102 for performing a payment transaction for a purchase of goods/services via a merchant interface. For instance, the pay-by-friend option is displayed in payment options at the merchant interface.
[0069] At 306, the user 102 selects the pay-by-friend option. At 308, the user 102 is directed to a link that displays the group 106. At 310, the user 102 selects the friends 106a-106c from the group 106. At 312, a payment transaction request is sent to the payment server 110. The payment transaction request is sent along with the selected friends 106a-106c.
[0070] At 314, the payment server 110 sends a notification for performing the payment transaction to each friend in the group 106. The notification includes a payment transaction amount, a merchant information and information corresponding to the payment transaction. For example, the payment transaction amount, such as $1500 for purchase items from a merchant, such as ‘MERCHANT_ABC’, information of the user 102, or the like are notified to each friend. In one embodiment, the notification is provided to each friend via the application 120 in respective user devices of the friends 106a-106c. In an alternate embodiment, the payment server 110 sends the notification using a registered contact number of the friends 106a-106c.
[0071] At 316, each friend provides their confirmation and their contribution amount to be contributed for the payment transaction (i.e., $1500) to the payment server 110. In some cases, the friends 106a-106c may contribute equally for the payment transaction. For instance, the friend 106a confirms to contribute $500, the friend 106b confirms to contribute $500 and the friend 106c confirms to contribute $500. In some other cases, the friends 106a-106c may contribute different contribution amounts. For instance, the friend 106a confirms to contribute $400, the friend 106b confirms to contribute $500 and the friend 106c confirms to contribute $600. This contribution may be based on a minimum limit and a maximum limit set on the contribution amount, which is explained further in FIG. 4B. Further, each friend may provide information, such as a payment account information, a payment card information or a digital wallet information of each friend along with the confirmation.
[0072] At 318, the payment server 110 processes the payment transaction based on the confirmation and the contribution amounts. For instance, the payment server 110 uses the information, i.e., the payment account or the payment card information for processing the payment transaction. The payment server 110 sends the payment transaction request to issuers (such as the issuer 114) using the information. The issuer 114 performs a validation and provides the contribution amounts. The contribution amounts deducted from each payment account are provided to the payment server 110. The payment server 110 transfers the contribution amounts to the acquirer 116.
[0073] At 320, the payment server 110 notifies a payment settlement to the user 102 upon successful completion of the payment transaction by the friends 106a-106c.
[0074] In an example embodiment, the user 102 creates a group fund for the group 106. It shall be noted that the creation of the group fund is described with respect to the user 102 for explanation purposes and that the group fund can be created by one of the friends in the group 106. The creation of the group fund is further explained next with reference to FIGS. 4A and 4B.
[0075] Referring now to FIG. 4A, a sequence flow diagram 400 for creating the group fund of the group 106, is illustrated in accordance with an example embodiment of the present disclosure. In an illustrative example scenario, the user 102 initiates the group fund creation at the application 120 for a monthly rental payment of an apartment. The apartment is shared by the user 102 and the friends 106a-106c in the group 106.
[0076] At 402, the user 102 sends a contribution request to the payment server 110 via the application 120. The contribution request may include a contribution amount to be contributed by the user 102, and a contact list including identifiers (IDs) of users who can be added for the group fund. For instance, the user 102 states a contribution amount of $500 for the group fund. At 404, the payment server 110 further sends the contribution request to each friend in the group 106. Each friend receives the contribution request and acknowledges the contribution amount (i.e., $500) to be contributed by the user 102. Further, the friends 106a-106c provide their responses and their contribution amounts to be contributed for the group fund in the application interface 120 in their respective user devices.
[0077] At 406, the payment server 110 receives each response and each contribution amount to be contributed for the group fund from the friends 106a-106c via the application 120. At 408, the payment server 110 notifies the responses and the contribution amounts of each friend to the user 102. For instance, the response (i.e., a confirmation) and the contribution amount (i.e., $600) of a friend, such as the friend 106a are notified to the user 102 and other friends, such as the friend 106b and the friend 106c.
[0078] At 410, the payment server 110 processes a deduction of each contribution amount for creating the group fund. In an example embodiment, payment server 110 sends a payment transaction request to each issuer (e.g., the issuer 114) for the deduction. The contribution amount is deducted from a payment account of the user 102 and corresponding payment accounts of each friend upon agreement on each contribution amount by the user 102 and the group 106.
[0079] At 412, the group fund is stored in a database, such as the database 108 of FIG. 1. At 414, the payment server 110 notifies the creation of the group fund. In a similar manner, the group fund is notified to each friend of the group 106. The group fund is displayed to the friends 106a-106c via the application 120.
[0080] Further, the user 102 may set the minimum limit and the maximum limit on the contribution amount to be contributed by each friend for the group fund. The setting of the minimum limit and the maximum limit is described next with reference to FIG. 4B.
[0081] Referring now to FIG. 4B, a sequence flow diagram 420 for creating the group fund of the group 106, is illustrated in accordance with another example embodiment of the present disclosure. In an illustrative example scenario, the user 102 initiates the setting of the minimum limit and the maximum limit after receiving the responses and the contribution amounts to be contributed by the friends 106a-106c of the group 106.
[0082] At 422, the user 102 sets the minimum limit and the maximum limit on the contribution amount via the application 120. For instance, the user 102 sets the minimum limit as $500 and the maximum limit as $1000. It is noted that the minimum limit and the maximum limit can be set by any user in the group 106.
[0083] At 424, the minimum limit and the maximum limit are sent to the payment server 110 via the application interface 120. At 426, the payment server 110 notifies the minimum limit and the maximum limit to each friend of the group 106. Each friend may provide an agreement on the minimum limit and the maximum limit at the application interface 120. Each friend provides a contribution amount based on the minimum limit and the maximum limit. For instance, the friend 106a agrees to contribute $500, the friend 106b agrees to contribute $800 and the friend 106c agrees to contribute $1000.
[0084] At 428, the agreement is notified to the payment server 110 via the application interface 120. At 430, the payment server 110 processes the deduction of each contribution amount. The group fund is created based on the deduction. At 432, the group fund is stored in the database 108. At 434, the group fund is notified to the user 102. In a similar manner, the group fund is also notified and displayed to the group 106 via the application 120.
[0085] In some cases, one of the friends, such as the friend 106b may disagree to contribute for the group fund. The friend 106b sends a rejection to the payment server 110 via the application 120. The payment server 110 notifies the rejection to the user 102 and remaining friends 106a and 106c. The user 102 or the remaining friends 106a and 106c may modify their contribution amount upon receiving the rejection. The modification is notified to the group 106. Further, the minimum limit and the maximum limit are also updated based on the modified contribution amount. The updated minimum limit and the updated maximum limit are notified to the group 106.
[0086] Furthermore, the group fund is used by the user 102 or by at least one of the friends in the group 106, which is explained next with reference to FIG. 5.
[0087] Referring now to FIG. 5, a sequence flow diagram 500 for withdrawing from the group fund withdrawing from the group fund, is illustrated in accordance with an example embodiment of the present disclosure. In an illustrative example embodiment, the group fund includes a fund amount of $3000 for the group 106.
[0088] At 502, the user 102 accesses the group fund via the application interface 120. The fund amount of $3000 is displayed to the user 102. At 504, the user 102 sends a withdrawal request to the payment server 110 for withdrawing from the group fund. The withdrawal request includes a withdrawal amount of $600 along with information corresponding to the withdrawal, such as purpose of the withdrawal.
[0089] At 506, the payment server 110 determines whether the withdrawal amount is within a contribution amount of the user 102. For example, the user 102 contributed $1000 for the group fund at the time of group fund creation. The payment server 110 checks if the withdrawal amount, i.e., $600 is less than the contribution amount, i.e., $1000. Here, $600 is within the contribution amount.
[0090] At 508, the payment server 110 deducts the withdrawal amount based on the determination. In some cases, the withdrawal amount may be more than the contribution amount. For instance, the user 102 contributed $500 for the group fund and sent a withdrawal request for a withdrawal amount of $600. In such case, the payment server 110 deducts $500 from the group fund. The withdrawal is short by $100, which is a pending amount for the withdrawal.
[0091] At 510, payment server 110 determines the pending amount, i.e., $100 based on the deduction. At 512, the payment server 110 sends a notification to the group 106 for approving a withdrawal of the pending amount. The notification is sent to each friend in the group 106 via the application 120.
[0092] At 514, the payment server 110 receives an approval from one or more friends in the group 106 for the withdrawal. For instance, the friend 106a provides the approval for withdrawal of the pending balance $100 from the group fund. At 516, the payment server 110 deducts the pending amount from the group fund based on the approval. At 518, the user 102 is notified on completion of the withdrawal.
[0093] Various embodiments cause provision of one or more UIs displayed on a user device, such as the user device 104 of the user 102, which are shown and described with reference to FIGS. 6A-6C.
[0094] FIG. 6A shows an example representation of a user interface (UI) 600 displayed to the user 102 on a display screen of the user device 104 displaying a pay-by-friend option for performing a payment transaction of the user 102, in accordance with an example embodiment of the present disclosure. In an illustrative example scenario, the UI 600 is a payment checkout page on a merchant interface for making a payment for purchased online goods/services by the user 102. As shown in FIG. 6A, the UI 600 is depicted to include a title 602 associated with text ‘PAYMENT’. Further, the UI 600 is depicted to include a total amount 604, such as $300 for the purchased goods/services.
[0095] The UI 600 is further depicted to include payment options 606. The payment options 606 includes options, for example, a card on delivery option, a cash on delivery option, a universal payment interface (UPI) option, and a pay-by-friend option, such as pay-by-friend option 608. The pay-by-friend option 608 enables performing the payment transaction by one or more member users associated with the option 608. As shown in FIG. 6A, the user 102 selects the pay-by-friend option 608. After the selection, the user 102 clicks on button 609. The user 102 is directed to a link that displays the one or more member users, which is shown next in FIG. 6B.
[0096] Referring now to FIG. 6B, an example representation of a UI 610 displayed to the user 102 on the display screen displaying the one or more member users associated with the pay-by-friend option 608, is illustrated in accordance with an example embodiment of the present disclosure. The UI 610 is depicted to include a title 612 associated with text ‘PAY-BY-FRIEND’. As shown in FIG. 6B, the member users are displayed as a list, such as a list of member users 614. The user 102 selects the member users from the list of member users 614. In an illustrative example scenario, the user 102 selects member users, such as member user 616a (i.e., ‘SAM’), member user 616b (i.e., ‘TOM’) and member user 616c (i.e., ‘BOB’) by checking corresponding checkboxes, shown in FIG. 6B. After the selection of the member users 616a-616c, the user 102 clicks on button 618.
[0097] The selected member users 616a-616c are notified to the payment server 110. As explained with reference to FIG. 2, the payment server 110 sends a notification for performing the payment transaction to the selected member users 616a-616c. The notification includes user name of each member user (i.e., ‘SAM’, ‘TOM’ and ‘BOB’), a payment transaction amount (i.e., $300), a merchant information and information corresponding to the payment transaction. Each member user may equally contribute $100 for the payment transaction of $300. The member users may contribute different contribution amount for the payment transaction. For example, SAM may contribute $100, TOM may contribute $150 and BOB may contribute $50. The payment server 110 processes deduction of each contribution amount and completes a payment settlement for the issuer 114 and the acquirer 116. The payment server 110 also sends a notification to the user 102 upon successful completion of the payment transaction by the member users 616a-616c. The notification received by the user 102 is shown next in FIG. 6C.18
[0098] FIG. 6C shows an example representation of a UI 620 displayed to the user 102 on the display screen displaying a notification 624 on a payment settlement for the payment transaction performed by the selected member users 616a-616c, in accordance with an example embodiment of the present disclosure. The UI 620 is depicted to include a title 622 associated with text ‘NOTIFICATION’. As shown in FIG. 6C, the notification 624 includes information of the member users 616a-616c and their contribution amounts for the payment transaction. It is noted that the notification 624 is shown herein for explanation purpose and may include more content than those shown in FIG. 6C. The user 102 closes the notification 624 by clicking on button 626.
[0099] Some embodiments cause provision of one or more UIs displayed on the user device 104 via the application interface 120 for creating a user account of the user 102, creating a group 106 by the user 102 and creating a group fund by the user 102, which are shown and described with reference to FIGS. 7A-7F.
[00100] FIG. 7A shows an example representation of a UI 700 displayed to the user 102 on a display screen of the user device 104 depicting a creation of the user account of the user 102 upon registration of the user 102 in the application interface 120, in accordance with an example embodiment of the present disclosure. In an illustrative example scenario, the user 102 accesses the application 120 and performs the user account creation.
[00101] The UI 700 is depicted to include a title 702 associated with text ‘APPLICATION’. As shown in FIG. 7A, the UI 700 includes an input field 704 for entering user ID of the user 102. The user 102 may provide an email ID, a contact number or a user name of the user 102 as the user ID. For instance, the user 102 may provide the user name ‘FRANK’ as the user ID. The user 102 provides a password in an input field 706. After filling the input fields 704 and 706, the user 102 clicks on button 708 and completes the user account creation. Further, the user 102 accesses the user account and creates a group, which is shown in FIG. 7B.
[00102] Referring now to FIG. 7B, an example representation of a UI 710 displayed to the user 102 on the display screen depicting the user account of the user 102, is illustrated in accordance with an example embodiment of the present disclosure. The UI 710 is depicted to include a title 712 associated with a text ‘USER ACCOUNT’. As shown in FIG. 7B, the UI 710 is depicted to include groups, such as ‘COUSINS’, ‘WORK’ and ‘FAMILY’. The groups may be either created by the user 102 or the user 102 may belong to these groups created by someone else. For instance, the group ‘COUSINS’ may be created by a different user, who added the user 102 in the group. The UI 710 is further depicted to include button 714 that enables creating of a group by the user 102. When the user 102 clicks on the create group button 714, the user 102 is directed to a next UI, which is shown in FIG. 7C.
[00103] In FIG. 7C, a UI 720 is depicted to include a title 722 associated with text ‘CREATE GROUP’. As shown in FIG. 7C, the UI 720 is depicted to include options, such as a contact list option 724 and a social media option 726. When the user 102 clicks on the contact list option 722, a contact list 732 of the user 102 in the user device 104 is opened, as shown in UI 730 of FIG. 7D. The user 102 selects friends from the contact list 732 by clicking on button 734 shown in FIG. 7D. After the selection, the user 102 clicks on confirm button 736.
[00104] In some other cases, the user 102 clicks on the social media option 724. When the user 102 clicks on the social media option 724, a friend list 742 in a social media account of the user 102 is displayed, as shown in a UI 740 of FIG. 7E. The user 102 selects the friends from the friend list 742 by clicking on button 744. The user 102 clicks on confirm button 746 and completes the group creation.
[00105] In an illustrative example scenario, the group, such as group 752 is displayed to the user 102, which is displayed in UI 750 of FIG. 7F. The user 102 provides a name, such as ‘FRIENDS’ to the group 752. The group 752 has no fund group that is indicated under column fund group and admin of the group 752 is ‘FRANK’. The group fund of the group 752 is created by clicking on button 754. For instance, the user 102 checks corresponding checkbox 755 of the group 752 and clicks on the button 754. The creation of the group fund for the group 752 is further described with reference to FIGS. 8A-8C.
[00106] Referring now to FIG. 8A, an example representation of a UI 800 displayed to the user 102 on the display screen depicting a creation of a group fund for a group via the application interface 120, such as the group 752 of FIG. 7F, in accordance with an example embodiment of the present disclosure. The UI 800 is depicted to include a title 802 associated with text ‘GROUP FUND CREATION’. The UI 800 is also depicted to include an input field 804 for entering a contribution amount to be contributed by the user 102 for the group fund. For instance, the user 102 enters the contribution amount as $100, as shown in FIG. 8A. Further, a minimum limit and a maximum limit on the contribution amount is set on the contribution by the user 102. In an illustrative example scenario, the user 102 enters the minimum limit in an input field 806 and the maximum limit in an input field 808. As shown in FIG. 8A, the minimum limit is set as ‘$50’ and the maximum limit is set as ‘$100’.
[00107] After providing the contribution amount, or the minimum and the maximum limits, the user 102 clicks on button 809. When the user 102 clicks on the button 809, a contribution request is sent to the payment server 110. The contribution request that includes the contribution amount (i.e., $100) is further sent to each friend in the group 752. Each response of the friends is notified to the user 102, which is shown in FIG. 8B. In a similar manner, a response of one friend is also notified to remaining friends of the group 752 via the application interface 120.
[00108] FIG. 8B shows an example representation of a UI 810 displayed to the user 102 on the display screen depicting receipt of each response and a contribution amount to be contributed by each friend of the group 752 for the group fund, in accordance with an example embodiment of the present disclosure. As shown in FIG. 8B, each response and each contribution amount to be contributed by corresponding friend of the group 752 are displayed in a table 812. For example, the friend ‘RON’ provides a response ‘YES’ with a contribution amount of $100, the friend ‘SEAN’ provides a response ‘YES’ with a contribution amount of $100 and the friend ‘JEAN’ provides a response ‘YES’ with a contribution amount of $100. When the user 102 clicks on a button 814, an agreement of the user 102 is notified to the payment server 110. In a similar manner, the payment server 110 also receives an agreement of each friend. The payment server 110 processes deduction of each contribution amount based on the agreement and creates the group fund for the group 752. The created group fund is shown in UI 820 of FIG. 8C. As shown in FIG. 8C, the group fund includes a fund amount 822, such as $400 for the group 752.
[00109] The user 102 or any friends in the group 752 may use the group fund by sending a withdrawal request. In an illustrative example scenario, the user 102 sends the withdrawal request via the application 120 for withdrawing from the group fund, which is shown and described with reference to FIGS. 9A and 9B.
[00110] FIG. 9A shows an example representation of a UI 900 displayed to the user 102 on the display screen depicting sending of a withdrawal request for withdrawing from a group fund of a group, such as the group 752 of FIG. 7F, in accordance with an example embodiment of the present disclosure. The UI 900 is depicted to a include a title 902 associated with a text ‘WITHDRAWAL’. The UI 900 is depicted to include an input field 904 for entering a withdrawal amount, such as $150 for withdrawing from the group fund of the group 752, as shown in FIG. 9A. In an illustrative example scenario, the user 102, i.e., ‘FRANK’ belonging to the group 752 (i.e., the group ‘FRIENDS’) sends the withdrawal request to the payment server 110. The user 102 clicks on a button 906 to send the withdrawal request to the payment server 110. The withdrawal request is notified to remaining friends in the group 752 via the application 120.
[00111] In an example embodiment, the payment server 110 determines whether the withdrawal amount is within a contribution amount contributed by the user 102, upon receipt of the withdrawal request. The determination is notified to the user 102, which is shown in next FIG. 9B.
[00112] FIG. 9B shows an example representation of a UI 910 displayed to the user 102 on the display screen displaying deduction of a withdrawal amount 912 from a group fund 911, in accordance with an example embodiment of the present disclosure. As shown of FIG. 9B, a UI 910 is depicted to include the group fund 911 with a fund amount of $400. The UI 910 is further depicted to include a contribution amount 914, and a permitted withdrawal amount 916 for the withdrawal. The contribution amount 914, i.e., $100 is amount contributed by the user 102 at the time of the group fund creation for a group, such as the group 752.
[00113] Here, the withdrawal amount 912 exceeds the contribution amount 914, i.e., $150>$100. The permitted withdrawal amount 916, i.e., $100 is amount permitted for deduction from the group fund 911. Therefore, the permitted withdrawal amount 916 is deducted from the group fund 911. Here, the withdrawal is partial as there is a pending amount 918, i.e., $50 to be withdrawn. The pending amount 918 is notified to the user 102, as is shown in FIG. 9B. The user 102 clicks on button 919 and proceeds further.
[00114] The pending amount 918 is notified to remaining friends of the group 752. In an illustrative example scenario, a notification to the group 752 is sent for approving a withdrawal of the pending amount 918. A friend, such as ‘RON’ of the group 752 approves the withdrawal of $50. The pending amount 918 is deducted from the group fund 911 based on the approval. The group fund 911 is updated based on the deduction. The updated group fund and complete deduction of the withdrawal amount 912, are shown in FIG. 9C. As shown in FIG. 9C, UI 920 is depicted to include an updated group fund 922, i.e., $250. Further, information related to complete deduction of the withdrawal amount 912 is displayed in the UI 920. The notification is also sent to remaining friends of the group 752 via the application 120.
[00115] It shall be noted that the UIs described herein are shown for explanation purposes and may include more or less content than contents shown in the UIs of FIGS. 6A-6C, FIGS. 7A-7F, FIGS. 8A-8C and FIGS. 9A-9C.
[00116] FIG. 10 illustrates a flow diagram depicting a method 1000 for performing a payment transaction, in accordance with an example embodiment of the present disclosure. The method 1000 depicted in the flow diagram may be executed by, for example, the payment server 110 of FIG. 1. Operations of the method 1000, and combinations of operation in the method 1000, may be implemented by, for example, hardware, firmware, a processor, circuitry and/or a different device associated with the execution of software that includes one or more computer program instructions. The operations of the method 1000 are described herein may be performed by an application interface (e.g., the application 120 of FIG. 1) in the user device 104 that is hosted and managed with help of the payment server 110. The method 1000 starts at operation 1002.
[00117] At operation 1002, the method 1000 includes electronically facilitating, by a server system associated with a payment network, a pay-by-friend option on a merchant interface in a user device of a user for making the payment transaction. The pay-by-friend option is explained in detail with reference to FIG. 2. In an illustrative example scenario, the pay-by-friend option is displayed to the user as one of payment options on the merchant interface (refer FIG. 6A).
[00118] At operation 1004, the method 1000 includes receiving, by the server system, a selection of one or more member users provided by the user upon selection of the pay-by-friend option by the user. The one or more member users associated with the pay-by-friend option. The one or more member users may include family members, friends, work colleagues of the user. In one example embodiment, the user selects one or more friends in a group created by the user. The group is created after creating a user account of the user. The user account is created upon registration of the user in an application interface associated with the server system. The one or more friends are selected from at least one of a contact list of the user and a friend list in a social media account of the user.
[00119] At operation 1006, the method 1000 includes sending, by the server system, a notification signal to the one or more member users for performing the payment transaction. The notification signal includes at least a user name data of each member user, a payment transaction amount data and a merchant data. In an example embodiment, confirmation from each of the one or more member users for performing the payment transaction is received by the server system. Each confirmation includes a contribution amount to be contributed by each member user. After receiving the confirmation, the server system processes the payment transaction based on the confirmation. In an example embodiment, the payment transaction is performed by using the group fund. In an illustrative example scenario, a group fund of the group is created by the user via the application interface. The group fund includes a fund amount contributed by the user and each friend in the group. In an example embodiment, the user provides a contribution request at the application interface for the group fund (refer FIG. 4A). The contribution request includes a contribution amount to be contributed by the user. A minimum limit and a maximum limit may be set on the contribution amount for the group fund (refer FIG. 4B). The user or any friend in the group may use the group fund by sending a withdrawal request via the application interface (refer FIG. 5).
[00120] At operation 1008, the method 1000 includes notifying, by the server system, a payment settlement to the user upon successful completion of the payment transaction by the one or more member users.
[00121] The sequence of operations of the method 1000 need not necessarily be executed in the same order as they are presented. Further, one or more operations may be grouped together and performed in form of a single step, or one operation may have several sub-steps that may be performed in parallel or sequential manner.
[00122] FIG. 11 is simplified block diagram of a server system 1100 for performing the payment transaction, in accordance with an embodiment of the present disclosure. The server system 1100 is an example of a payment server (e.g., the payment server 110). The server system 1100 includes a computer system 1102 and a database 1104. In an embodiment, the server system 1100 is integrated in the payment server 110.
[00123] The computer system 1102 includes at least one processor 1106 configured to execute executable instructions for providing various features of the present disclosure. The executing instructions are stored in a memory 1108. The components of the computer system 1102 provided herein may not be exhaustive and that the computer system 1102 may include more or fewer components than those depicted in FIG. 11. Further, two or more components may be embodied in one single component, and/or one component may be configured using multiple sub-components to achieve the desired functionalities. Some components of the computer system 1102 may be configured using hardware elements, software elements, firmware elements and/or a combination thereof.
[00124] The processor 1106 is operatively coupled to a communication interface 1110 such that the computer system 1102 is capable of communicating with a remote device 1112 such as a user device 104 or capable of communicating with any entity connected to a network, such as the network 112 (shown in FIG. 1) or any constituents of the payment network. In an embodiment, the processor 1106 is configured to electronically facilitate a pay-by-friend option on a merchant interface for making a payment transaction. The merchant interface is accessed by the user 102 in the user device 104.
[00125] In an embodiment, the communication interface 1110 is configured to receive a selection of the pay-by-friend option provided by the user 102 on the merchant interface. Further, the communication interface 1110 is configured to receive a selection of one or more member users provided by the user 102 upon selection of the pay-by-friend option. The processor 1106 sends a notification signal to the one or more member users for performing the payment transaction, via the communication interface 1110. The notification signal includes a user name data of each member user, a payment transaction amount data and a merchant data. The communication may be achieved through API calls, without loss of generality. The communication interface 1110 also receives a confirmation from each of the one or more member users for performing the payment transaction. Each confirmation includes a contribution amount to be contributed by each member user for the payment transaction. The processor 1106 processes the payment transaction based on the confirmation. In an embodiment, the communication interface 1110 includes an application interface 1114. The application interface 1114 is an example of the application 120 of FIG. 1. The application interface 1114 is configured to facilitate a user account creation, a group creation and creation of a group fund, such as group fund 1116 for the group. The group fund 1116 is stored in the database 1104. The group fund 1116 includes a fund amount contributed by the user and each friend in the group.
[00126] The processor 1106 may also be operatively coupled to the database 1104. The database 1104 is any computer-operated hardware suitable for storing and retrieving data, such as, but not limited to, information of the user 102, information of the group, information of the group fund 1116, transaction data generated as part of sales activities conducted over the bankcard network including data relating to merchants, payees, or customers, and purchases. The database 1104 may include multiple storage units such as hard disks and/or solid-state disks in a redundant array of inexpensive disks (RAID) configuration. The database 1104 may include a storage area network (SAN) and/or a network attached storage (NAS) system.
[00127] In some embodiments, the database 1104 is integrated within computer system 1102. For example, the computer system 1102 may include one or more hard disk drives as the database 1104. In other embodiments, the database 1104 is external to the computer system 1102 and may be accessed by the computer system 1102 using a storage interface 1118. The storage interface 1118 is any component capable of providing the processor 1106 with access to the database 1104. The storage interface 1118 may include, for example, an Advanced Technology Attachment (ATA) adapter, a Serial ATA (SATA) adapter, a Small Computer System Interface (SCSI) adapter, a RAID controller, a SAN adapter, a network adapter, and/or any component providing processor 1106 with access to the database 1104.
[00128] The processor 1106 is configured to deduct a withdrawal amount from the group fund 1116, upon receipt of a withdrawal request via the communication interface 1110. The withdrawal request includes a withdrawal amount provided by at least one of the user 102 and a friend from the group (such as group 752 of FIG. 7F) for withdrawing from the group fund 1116. The processor 1106 determines whether the withdrawal amount is within a contribution amount contributed by the user or the friend. Further, the processor 1106 deducts the withdrawal amount from the group fund 1116 based on the determination.
[00129] FIG. 12 is a simplified block diagram of a payment server 1200 for performing the payment transaction, in accordance with an embodiment of the present disclosure. The payment server 1200 is an example of the payment server 110 of FIG. 1. The network 112 may be used as a payment network by the payment server 1200, an issuer server 1300 and acquirer server 1400 as a payment interchange network. Examples of payment interchange network include, but not limited to, Mastercard® payment system interchange network. The payment server 1200 includes a processing system 1202 configured to extract programming instructions from a memory 1204 to provide various features of the present disclosure. The components of the payment server 1200 provided herein may not be exhaustive and that the payment server 1200 may include more or fewer components than those depicted in FIG. 12. Further, two or more components may be embodied in one single component, and/or one component may be configured using multiple sub-components to achieve the desired functionalities. Some components of the payment server 1200 may be configured using hardware elements, software elements, firmware elements and/or a combination thereof.
[00130] Via a communication interface 1206, a selection of a pay-by-friend option by the user 102 in a remote device 1208, such as the user device 104 is received. The communication interface 1206 also receives notification of one or more member users or friends selected by the user 102 for the payment transaction. Further, the payment server 1200 sends a notification for the payment transaction to each member user via the communication interface 1206. The notification includes a user name of each member user, a payment transaction amount, a merchant information and information corresponding to the payment transaction. The communication interface 1206 receives each confirmation and their contribution amount to be contributed by each member user for the payment transaction. The communication may be achieved through API calls, without loss of generality.
[00131] The processing system 1202 is configured to process the payment transaction based on the confirmation and the contribution amounts. The payment server 1200 sends a payment transaction request to the issuer server 1300 for deducting the contribution amounts, via the communication interface 1206. The deducted contribution amounts are transferred to the acquirer server 1400, upon receipt of the contribution amounts from the issuer server 1300. The processing system 1202 completes a payment settlement between the issuer server 1300 and the acquirer server 1400. A notification on the payment settlement is sent to the user 102 from the payment server 1200 via the communication interface 1206.
[00132] In an example embodiment, the communication interface 1206 is configured to receive a notification of selected one or more friends in a group of the user 102. The communication interface 1206 sends a notification for performing the payment transaction to each friend. Via the communication interface 1206, confirmation and each contribution amount of each friend are received. The processing system 1202 processes the deduction and completes a payment settlement between issuer, such as issuer server 1300 of the friends and the acquirer server 1400.
[00133] In one embodiment, the communication interface 1206 is also configured to receive a contribution request for creating a group fund of the group. The contribution request includes a contribution amount to be contributed by the user 102. The contribution request is further transferred to each friend in the group via the communication interface 1206. The communication interface 1206 further receives responses and contribution amounts to be contributed for the group fund. The processing system 1202 processes a deduction of each contribution amount for creating the group fund by sending a payment transaction request to the issuer server 1300 for the deduction. The group fund includes a fund amount based on the contribution amounts, that is notified to the group via the communication interface 1206. The group fund is stored in a database, such as database 1210.
[00134] FIG. 13 is a simplified block diagram of an issuer server 1300, in accordance with an embodiment of the present disclosure. The issuer server 1300 is an example of the issuer 114 of FIG. 1, or may be embodied in the issuer 114. The issuer server 1300 is associated with an issuer bank/issuer, in which a user (e.g., the user 102 or the member users 106a-106c or the friends in the group 106) may have a payment account, which provides a payment card. The issuer server 1300 includes a processing module 1302 operatively coupled to a storage module 1304 and a communication module 1306. The components of the issuer server 1300 provided herein may not be exhaustive and that the issuer server 1300 may include more or fewer components than that of depicted in FIG. 13. Further, two or more components may be embodied in one single component, and/or one component may be configured using multiple sub-components to achieve the desired functionalities. Some components of the issuer server 1300 may be configured using hardware elements, software elements, firmware elements and/or combination thereof.
[00135] The storage module 1304 is configured to store machine executable instructions to be accessed by the processing module 1302. Additionally, the storage module 1304 stores information related to, contact information of the user 102, bank account number, availability of funds in the account, payment card details, transaction details and/or the like. Further, the storage module 1304 is configured to store information related to successful payment transactions of the user 102 by the one or more member users 106a-106c through a pay-by-friend option.
[00136] The processing module 1302 is configured to communicate with one or more remote devices such as a remote device 1308 using the communication module 1306 over a network, such as the network 112 of FIG. 1. The examples of the remote device 1308 include the payment server 110 or other computing systems of issuer and the network 112 and the like. The communication module 1306 is capable of facilitating such operative communication with the remote devices and cloud servers using API (Application Program Interface) calls. The processing module 1302 receives a payment card information, a payment transaction amount, a customer information and merchant information in remote device 1308 (i.e. the payment server 110).
[00137] FIG. 14 is a simplified block diagram of an acquirer server 1400, in accordance with an embodiment of the present disclosure. The acquirer server 1400 is an example of the acquirer 116 of FIG. 1, or may be embodied in the acquirer 116. The acquirer server 1400 is associated with an acquirer bank/ acquirer, in which a user (e.g., the user 102) may have a payment account, which provides a payment card. The acquirer server 1400 includes a processing module 1402 operatively coupled to a memory 1404 and a communication module 1406. The components of the acquirer server 1400 provided herein may not be exhaustive and that the acquirer server 1400 may include more or fewer components than those depicted in FIG. 14. Further, two or more components may be embodied in one single component, and/or one component may be configured using multiple sub-components to achieve the desired functionalities. Some components of the acquirer server 1400 may be configured using hardware elements, software elements, firmware elements and/or combination thereof.
[00138] The memory 1404 is configured to store machine executable instructions to be accessed by the processing module 1402. Additionally, the memory 1404 stores information related to, contact information of a merchant, an account number of the merchant, availability of funds in the account, payment card details, transaction details and/or the like.
[00139] The processing module 1402 is configured to communicate with one or more remote devices such as a remote device 1408 using the communication module 1406 over a network, such as the network 112 of FIG. 1. The examples of the remote device 1408 include the payment server 110 or other computing systems of acquirer 116 and the network 112 and the like. The communication module 1406 is capable of facilitating such operative communication with the remote devices and cloud servers using API (Application Program Interface) calls. The processing module 1402 receives a payment card information, a payment transaction amount, and a merchant information in remote device 1408.
[00140] FIG. 15 shows a simplified block diagram of a user device 1500 capable of implementing the various embodiments of the present disclosure. The user device 1500 is depicted to include one or more applications 1506. The user device 1500 is an example of the user device 104. It should be understood that the device 1500 as illustrated and hereinafter described is merely illustrative of one type of device and should not be taken to limit the scope of the embodiments. As such, it should be appreciated that at least some of the components described below in connection with the user device 1500 may be optional and thus in an example embodiment may include more, less or different components than those described in connection with the example embodiment of the FIG. 15. As such, among other examples, the user device 1500 could be any of an electronic device, for example, cellular phones, tablet computers, laptops, mobile computers, personal digital assistants (PDAs), mobile televisions, mobile digital assistants, or any combination of the aforementioned, and other types of communication or multimedia devices.
[00141] The illustrated user device 1500 includes a controller or a processor 1502 (e.g., a signal processor, microprocessor, ASIC, or other control and processing logic circuitry) for performing such tasks as signal coding, data processing, image processing, input/output processing, power control, and/or other functions. An operating system 1504 controls the allocation and usage of the components of the user device 1500 and supports for one or more applications programs (see, applications 1506), such as application interface 120 in the user device 104. The application interface 120 in the user device 104 is used for creating a user account upon registration of the user 102, a group and a group fund for the group. In addition to the application interface, the applications 1506 may include common mobile computing applications (e.g., telephony applications, email applications, calendars, contact managers, web browsers, messaging applications such as USSD messaging or SMS messaging or SIM Tool Kit (STK) application) or any other computing application.
[00142] The illustrated user device 1500 includes one or more memory components, for example, a non-removable memory 1508 and/or removable memory 1510. The non-removable memory 1508 and/or removable memory 1510 may be collectively known as database in an embodiment. The non-removable memory 1508 can include RAM, ROM, flash memory, a hard disk, or other well-known memory storage technologies. The removable memory 1510 can include flash memory, smart cards, or a Subscriber Identity Module (SIM). The one or more memory components can be used for storing data and/or code for running the operating system 1504 and the applications 1506. The user device 1500 may further include a user identity module (UIM) 1512. The UIM 1512 may be a memory device having a processor 1502 built in. The UIM 1512 may include, for example, a subscriber identity module (SIM), a universal integrated circuit card (UICC), a universal subscriber identity module (USIM), a removable user identity module (R-UIM), or any other smart card. The UIM 1512 typically stores information elements related to a mobile subscriber. The UIM 1512 in form of the SIM card is well known in Global System for Mobile Communications (GSM) communication systems, Code Division Multiple Access (CDMA) systems, or with third-generation (3G) wireless communication protocols such as Universal Mobile Telecommunications System (UMTS), CDMA7000, wideband CDMA (WCDMA) and time division-synchronous CDMA (TD-SCDMA), or with fourth-generation (4G) wireless communication protocols such as LTE (Long-Term Evolution).
[00143] The user device 1500 can support one or more input devices 1520 and one or more output devices 1530. Examples of the input devices 1520 may include, but are not limited to, a touch screen / a screen 1522 (e.g., capable of capturing finger tap inputs, finger gesture inputs, multi-finger tap inputs, multi-finger gesture inputs, or keystroke inputs from a virtual keyboard or keypad), a microphone 1524 (e.g., capable of capturing voice input), a camera module 1526 (e.g., capable of capturing still picture images and/or video images) and a physical keyboard 1528. Examples of the output devices 1530 may include, but are not limited to a speaker 1532 and a display 1534. Other possible output devices 1530 can include piezoelectric or other haptic output devices. Some devices can serve more than one input/output function. For example, the touch screen 1522 and the display 1534 can be combined into a single input/output device.
[00144] A wireless modem 1540 can be coupled to one or more antennas (not shown in the FIG. 15) and can support two-way communications between the processor 1502 and external devices, as is well understood in the art. The wireless modem 1540 is shown generically and can include, for example, a cellular modem 1542 for communicating at long range with the mobile communication network, a Wi-Fi compatible modem 1544 for communicating at short range with an external Bluetooth-equipped device or a local wireless data network or router, and/or a Bluetooth-compatible modem 1546. The wireless modem 1540 is typically configured for communication with one or more cellular networks, such as a GSM network for data and voice communications within a single cellular network, between cellular networks, or between the user device 1500 and a public switched telephone network (PSTN).
[00145] The user device 1500 can further include one or more input/output ports 1550 for establishing connection with peripheral devices including a power supply 1552, one or more sensors 1554 for example, an accelerometer, a gyroscope, a compass, or an infrared proximity sensor for detecting the orientation or motion of the user device 1500 and biometric sensors for scanning biometric identity of an authorized user, a transceiver 1556 (for wirelessly transmitting analog or digital signals) and/or a physical connector 1560, which can be a USB port, IEEE 1294 (FireWire) port, and/or RS-232 port. The illustrated components are not required or all-inclusive, as any of the components shown can be deleted and other components can be added.
[00146] With the application (see, applications 1506) and/or other software or hardware components, the user device 1500 can implement the technologies described herein. In one example embodiment, the processor 1502 can cause registration of the user, creation of the user account, creation of a group and creation of a group fund for the group via the application interface 120. Moreover, a payment transaction of the user is performed by one or more member users selected by the user through a pay-by-friend option. Further, a payment transaction may be performed using the group fund.
[00147] Without limiting the scope of the present disclosure, the one or more example embodiments disclosed herein provide technical effects such as methods and systems for performing payment transactions of the user by one or more friends of the user through a pay-by-friend option. More specifically, the payment transaction is performed by the friends or any other users known to the user in a safe and secure manner. The payment transaction is performed without having the need to share any confidential information of the friends, which eliminates security risks.
[00148] The disclosed methods with reference to FIGS. 1 to 15, or one or more operations of the method 1000 may be implemented using software including computer-executable instructions stored on one or more computer-readable media (e.g., non-transitory computer-readable media, such as one or more optical media discs, volatile memory components (e.g., DRAM or SRAM), or nonvolatile memory or storage components (e.g., hard drives or solid-state nonvolatile memory components, such as Flash memory components) and executed on a computer (e.g., any suitable computer, such as a laptop computer, net book, Web book, tablet computing device, smart phone, or other mobile computing device). Such software may be executed, for example, on a single local computer or in a network environment (e.g., via the Internet, a wide-area network, a local-area network, a remote web-based server, a client-server network (such as a cloud computing network), or other such network) using one or more network computers. Additionally, any of the intermediate or final data created and used during implementation of the disclosed methods or systems may also be stored on one or more computer-readable media (e.g., non-transitory computer-readable media) and are considered to be within the scope of the disclosed technology. Furthermore, any of the software-based embodiments may be uploaded, downloaded, or remotely accessed through a suitable communication means. Such suitable communication means include, for example, the Internet, the World Wide Web, an intranet, software applications, cable (including fiber optic cable), magnetic communications, electromagnetic communications (including RF, microwave, and infrared communications), electronic communications, or other such communication means.
[00149] Although the disclosure has been described with reference to specific exemplary embodiments, it is noted that various modifications and changes may be made to these embodiments without departing from the broad spirit and scope of the disclosure. For example, the various operations, blocks, etc., described herein may be enabled and operated using hardware circuitry (for example, complementary metal oxide semiconductor (CMOS) based logic circuitry), firmware, software and/or any combination of hardware, firmware, and/or software (for example, embodied in a machine-readable medium). For example, the apparatuses and methods may be embodied using transistors, logic gates, and electrical circuits (for example, application specific integrated circuit (ASIC) circuitry and/or in Digital Signal Processor (DSP) circuitry).
[00150] Particularly, the server system 1100 (e.g., the payment server 110) and its various components such as the computer system 1102 and the database 1104 may be enabled using software and/or using transistors, logic gates, and electrical circuits (for example, integrated circuit circuitry such as ASIC circuitry). Various embodiments of the disclosure may include one or more computer programs stored or otherwise embodied on a computer-readable medium, wherein the computer programs are configured to cause a processor or computer to perform one or more operations. A computer-readable medium storing, embodying, or encoded with a computer program, or similar language, may be embodied as a tangible data storage device storing one or more software programs that are configured to cause a processor or computer to perform one or more operations. Such operations may be, for example, any of the steps or operations described herein. In some embodiments, the computer programs may be stored and provided to a computer using any type of non-transitory computer readable media. Non-transitory computer readable media include any type of tangible storage media. Examples of non-transitory computer readable media include magnetic storage media (such as floppy disks, magnetic tapes, hard disk drives, etc.), optical magnetic storage media (e.g. magneto-optical disks), CD-ROM (compact disc read only memory), CD-R (compact disc recordable), CD-R/W (compact disc rewritable), DVD (Digital Versatile Disc), BD (BLU-RAY® Disc), and semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash memory, RAM (random access memory), etc.). Additionally, a tangible data storage device may be embodied as one or more volatile memory devices, one or more non-volatile memory devices, and/or a combination of one or more volatile memory devices and non-volatile memory devices. In some embodiments, the computer programs may be provided to a computer using any type of transitory computer readable media. Examples of transitory computer readable media include electric signals, optical signals, and electromagnetic waves. Transitory computer readable media can provide the program to a computer via a wired communication line (e.g. electric wires, and optical fibers) or a wireless communication line.
[00151] Various embodiments of the disclosure, as discussed above, may be practiced with steps and/or operations in a different order, and/or with hardware elements in configurations, which are different than those which are disclosed. Therefore, although the disclosure has been described based upon these exemplary embodiments, it is noted that certain modifications, variations, and alternative constructions may be apparent and well within the spirit and scope of the disclosure.
[00152] Although various exemplary embodiments of the disclosure are described herein in a language specific to structural features and/or methodological acts, the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as exemplary forms of implementing the claims.