WO2017100151A1 - Systems and methods for authorizing a financial transaction based on a virtual product - Google Patents

Abstract

Embodiments of the disclosure enable a financial transaction to be automatically authorized based on a commonality or similarity of a real-world product with a virtual product. In one aspect, a method is provided for authorizing one or more financial transactions. The method includes receiving a request for authorization of a financial transaction associated with a real-world product, determining whether a cardholder account is associated with a virtual product corresponding to the real- world product, and, on condition that the cardholder account is associated with the virtual product corresponding to the real-world product, approving the request for authorization for the financial transaction. Aspects of the disclosure enable at least some financial transactions to be automatically confirmed and/or verified without prompting a cardholder to confirm and/or verify the financial transaction.

Description

SYSTEMS AND METHODS FOR AUTHORIZING A FINANCIAL TRANSACTION BASED ON A VIRTUAL PRODUCT

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and the benefit of the filing date of U.S. Patent Application Serial No. 14/966,041, filed December 11, 2015, which is hereby incorporated by reference in its entirety.

FIELD OF THE DISCLOSURE

The subject matter described herein relates generally to information processing and, more specifically, to authorizing one or more financial transactions based on a previous interaction at a virtual community.

BACKGROUND

Financial transaction cards have made great gains as a means to attract financial accounts to financial institutions and, in the case of credit cards, as a medium to create small loans and generate interest income for financial institutions. However, fraudulent financial transactions involving credit cards and other similar payment mechanisms may result in huge losses for cardholders, merchants, banks, and other financial institutions. Cardholders may be increasingly bothered, annoyed, and/or inconvenienced with each request to confirm a potentially fraudulent financial transaction as a legitimate financial transaction.

SUMMARY

Embodiments of the disclosure enable a financial transaction to be automatically authorized based on a commonality or similarity of a real-world product with a virtual product In one aspect, a method is provided for authorizing one or more financial transactions. The method includes receiving a request for authorization of a financial transaction associated with a real-world product, determining whether a cardholder account is associated with a virtual product corresponding to the real- world product, and, on condition that the cardholder account is associated with the virtual product corresponding to the real-world product; approving the request for authorization for the financial transaction. In another aspect, a computing device is provided for authorizing one or more financial transactions. Hie computing device includes a memory storing data associated with one or more cardholder accounts and computer-executable instructions, and a processor configured to execute the computer-executable instructions to receive a request for authorization of a financial transaction associated with a real-world product, determine whether a first cardholder account of the one or more cardholder accounts is associated with a virtual product corresponding to the real-world product, and, on condition that the first cardholder account is associated with the virtual product corresponding to the real-world product, approve die request for authorization for the financial transaction.

In yet another aspect, a computer-readable storage device having computer-executable instructions embodied thereon is provided. Upon execution by at least one processor, the computer-executable instructions cause the processor to receive a request for authorization of a financial transaction associated with a real- world product, identify a transaction associated with a virtual product, determine whether the virtual product corresponds to the real-world product, and, on condition that the virtual product corresponds to the real-world product, approve the request for authorization for the financial transaction.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is H intended to be used as an aid in determining the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a block diagram illustrating an example system for authorizing a financial transaction based on a virtual product.

FIG.2 is a block diagram illustrating an example computing device for authorizing a financial transaction based on a virtual product at a system, such as the system shown in FIG. 1.

FIGs. 3 and 4 are flowcharts of an example method of authorizing a financial transaction based on a virtual product using a computing device, such as the computing device shown in FIG.2. FIG. 5 is an example sequence diagram that may be implemented at a system, such as the system shown in FIG. 1.

FIG. 6 is a block diagram illustrating an example operating environment in which a financial transaction may be authorized based on a virtual product.

FIG. 7 is a block diagram illustrating an example environment for processing financial transactions.

Corresponding reference characters indicate corresponding parts throughout the drawings.

DETAILED DESCRIPTION

The subject matter described herein relates to authorizing one or more financial transactions. Embodiments of the disclosure provide the ability to automatically approve one or more financial transactions based on a previous interaction at a virtual community (e.g., a transaction associated with a virtual product), thereby providing at least some opportunity to approve a financial transaction based on previous user actions. That is, the embodiments of the disclosure may utilize data associated with the previous user actions to determine a likelihood of a cardholder performing subsequent user actions (e.g., financial transaction associated with a real-world product). Embodiments described herein enable a computer system to receive a request for authorization of a financial transaction associated with a real- world product, determine whether a cardholder account is associated with a virtual product corresponding to the real-world product, and, on condition that the cardholder account is associated with the virtual product corresponding to the real-world product, approve the request for authorization for the financial transaction.

Aspects of the disclosure provide for a computing system that processes one or more financial transactions in an environment including a plurality of devices coupled to each other via a network (e.g., a local area network, a wide area network, the Internet). For example, a financial transaction processing computing device may receive and/or retrieve data associated with a virtual product, receive a request for authorization of a financial transaction for a real-world product, and approve the request for authorization of the financial transaction based on a comparison of the virtual product with the real-world product. In mis manner, the subsequent financial transaction may be automatically confirmed and/or verified with at least some confidence and/or without prompting a cardholder to confirm and/or verify the financial transaction.

The systems and processes described herein may be implemented using computer programming or engineering techniques including computer software, firmware, hardware or a combination or subset thereof. At least one technical problem with known transaction processing systems is that, with the volume of financial transactions and the diversity of preferences between cardholders, it can be difficult, tedious, and/or time consuming to determine whether a particular financial transaction is legitimate or illegitimate. The embodiments described herein address that technical problem. For example, by processing financial transactions in the manner described in this disclosure, some embodiments improve cardholder confidence in financial institutions by using data (e.g., transaction data associated with a virtual product) that may be indicative of purchasing tendencies of a cardholder. In this manner, the embodiments described herein may facilitate achieving a balance between security from fraud and convenience to the cardholder. Additionally, some embodiments may improve processor security and/or data transmission security by processing one or more financial transactions using one or more updated parameters; improve user efficiency and/or user interaction performance by reducing the number of requests to confirm a potentially fraudulent financial transaction as a legitimate financial transaction; and reduce error rate by automating the analysis and processing of financial transactions. In some embodiments, the subject matter described herein may facilitate increasing processor speed, reducing processor load, improving

communication between systems, reducing network bandwidth usage, and/or improving operating system resource allocation,

The technical effect of the systems and processes described herein is achieved by performing at least one of the following operations: a) subscribing to a notification service associated with a virtual community; b) receiving a notification of a transaction associated with a virtual product; c) identifying a transaction associated with the virtual product; d) identifying a real-world product corresponding to the virtual product; e) generating a promotion associated with the real-world product; f) receiving a request for authorization of a financial transaction associated with the real-world product, g) deterrnining whether a cardholder account is associated with the virtual product corresponding to the real -world product; h) determining whether the virtual product corresponds to the real-world product; i) identifying at least one parameter; j) determining whether the at least one parameter satisfies a predetermined threshold; k) generating a score associated with the financial transaction;

1) determining whether the score satisfies a predetermined threshold; and

m) approving the request for authorization for the financial transaction.

FIG. 1 is a block diagram illustrating an example system 100 for authorizing one or more financial transactions. The system 100 includes a client device 110, a virtual community 120, and a financial transaction processing computing device 130. The client device 110 allows a user 140 (e.g., a cardholder) to enter into a financial transaction associated with a real-world product 150. For example, the client device 110 may be a point-of-sale (POS) terminal configured to generate a request for authorization, and transmit the request for authorization to the financial transaction processing computing device 130. Additionally or alternatively, the client device 110 may be any computing device mat allows a user 140 to enter into a financial transaction including, without limitation, a mobile device, a portable media player, a phablet, a tablet, a nefbook, a laptop, a desktop computer, and the like. For example, the user 140 may utilize the client device 110 to purchase the real-world product 150 in an electronic commerce (e-commerce) environment

The virtual community 120 enables a user (e.g., user 140) to participate in a virtual world or environment. In some embodiments, a virtual community 120 is associated with a social network or other application having access to data associated with the user 140. The user 140 may create an account or profile at the virtual community 120 and, in some embodiments, interact with other users 140 at the virtual community 120. The virtual community 120 includes one or more virtual products 160 that may be purchased or obtained by the user 140. That is, the virtual community 120 allows the user 140 to enter into a transaction associated with the virtual product 160. A virtual product 160 is a virtual good or service that may be obtained, possessed, used, and/or consumed in the virtual environment. In some embodiments, a virtual product 160 may correspond to a real-world product 150. For example, the user 140 may purchase a pair of virtual shoes at the virtual community 120.

The virtual community 120 may be accessible using a computing device (e.g., client device 110). For example, the user 140 may use a client device 110 used to enter into real-world financial transactions to interact with the virtual community 120 and obtain a virtual product 160. Additionally or alternatively, a first client device 110 may be used to enter into real-world financial transactions, and a second client device 110 may be used to interact with the virtual community 120 and obtain the virtual product 160. In some embodiments, the virtual product 160 is obtained using a virtual currency, which may be purchased or obtained by the user 140 using a computing device. That is, the user 140 may obtain a virtual currency, which, in turn, may be used to obtain a virtual product 160. In some embodiments, the virtual currency may be earned or obtained over time and/or by performing one or more activities associated with the virtual community 120. Additionally or alternatively, the virtual product 160 may be obtained using a real-world currency (e.g., United States dollar).

The financial transaction processing computing device 130 is configured to receive the request for authorization (e.g., from the client device 110), and determine whether to approve the request for authorization. In some

embodiments, the financial transaction processing computing device 130 identifies a cardholder account 170 associated with the request for authorization, and determines whether the cardholder account 170 is associated with a virtual product 160 corresponding to the real-world product 150. If the cardholder account 170 is associated with a virtual product 160 corresponding to the real-world product 150, the financial transaction processing computing device 130 is configured to approve the request for authorization.

FIG.2 is a block diagram illustrating an example computing device

200 (e.g., financial transaction processing computing device 130) for authorizing a financial transaction based on a virtual product 160 (shown in FIG. 1). The computing device 200 may include, for example, an interface component 210, an account manager component 220, a transaction score component 230, and/or a memory component 240.

The interface component 210 enables the computing device 200 to receive data from and/or transmit data to another computing device, such as a client device 110 (shown in FIG. 1) and/or a virtual community 120 (shown in FIG. I). For example, the interface component 210 may be configured to receive a request for authorization of a financial transaction. In some embodiments, the interface component 210 receives data from and/or transmits data to another computing device via a network 2S0 (e.g., a local area network, a wide area network, the Internet).

In some embodiments, the interface component 210 is coupled to and/or communicates with the account manager component 220, the transaction score component 230, and/or the memory component 240 to facilitate communication between the computing device 200 and another computing device (e.g., a client device 110, a virtual community 120). For example, the interface component 210 may transmit a request to subscribe to a notification service associated with the virtual community 120, receive a notification of a transaction associated with a virtual product 160, transmit a promotion associated with a real-world product 150 (shown in FIG. 1) to a client device 110, receive a request for authorization of a financial transaction associated with the real-world product 150, and/or transmit an approval of the request for authorization of the financial transaction.

The account manager component 220 enables the computing device

200 to manage one or more cardholder accounts 170 (shown in FIG. 1) and associate a cardholder account 170 with one or more virtual communities 120. For example, the account manager component 220 may determine that a first request for authorization is associated with a virtual community 120 (e.g., the request for authorization may be associated with a purchase of virtual currency at the virtual community 120). Upon determining that the first request for authorization is associated with a virtual community 120, the account manager component 220 may associate or register the virtual community 120 with the cardholder account 170. In some embodiments, the registration of the virtual community 120 with the cardholder account 170 may be stored, for example, at the memory component 240.

In some embodiments, the account manager component 220 may identify a cardholder account 170 associated with a second request for authorization (e.g., a request for authorization not associated with the virtual community 120). Upon identifying the cardholder account 170, the account manager component 220 may identify one or more virtual communities 120 that are registered with the cardholder account 170 such mat one or more virtual products 160 and/or one or more transactions associated with the virtual products 160 may be identified. In some embodiments, data associated with the identification of the virtual products 160 and/or the identification of a transaction associated with the virtual products 160 may be stored, for example, at the memory component 240.

The transaction score component 230 enables the computing device 200 to have confidence in approving, flagging, or declining a request for

authorization. In some embodiments, the transaction score component 230 may calculate or generate a transaction score for a financial transaction that is indicative of a riskiness of authorizing the financial transaction, where a lower score (e.g., 1) is associated with less risk and a higher score (e.g., 10) is associated with more risk (e.g., on a ten-point scale). For example, the transaction score may be calculated based on one or more parameters associated with the cardholder account 170. The parameters may be risk-related parameters that are used to identity or assign a likelihood of fraud. For example, the parameters may set or define one or more boundaries or thresholds of expected user behavior.

In some embodiments, the financial transaction is associated with one or more parameters, such as a product, a merchant, a transaction amount, a transaction time, a geo location, a quantity of products, a product brand, and a product category. The transaction score component 230 may compare one or more factors associated with the financial transaction with one or more parameters associated with the cardholder account 170 to determine whether the financial transaction tails within or outside of expected user behavior and identify or assign a likelihood of fraud. For example, a real-world product 1 SO associated with the financial transaction may be compared with one or more virtual products 160 identified by the account manager component 220 to identify or assign the likelihood of fraud. In such an example, a virtual product 160 corresponding to the real-world product 150 may be indicative of a lower likelihood of fraud. Additionally or alternatively, the transaction score component 230 may be determined based on an amount of virtual currency associated with the virtual community 120 or the cardholder account 170 (e.g., spend amount, current balance), a rate associated with the virtual community 120 (e.g., reload rate, transaction rate, return rate, resale rate), and/or a duration associated with the virtual community 120 (e.g., duration of having an account at the virtual community 120, duration since registering the virtual community 120 with the cardholder account 170, duration of owning a virtual product 160). In some embodiments, data associated with the virtual product 160, for example, may be retrieved from the memory component 240.

A request for authorization may be automatically approved (e.g., approved without prompting a user to confirm and/or verify the financial transaction) when the request is associated with a financial transaction that has a transaction score that satisfies a first predetermined threshold (e.g., the transaction score is less than or equal to the first predetermined threshold). On the other hand, the request for authorization may be automatically declined (e.g., declined without prompting a user to confirm and/or verify the financial transaction) when the request is associated with a financial transaction that has a transaction score that does not satisfy a second predetermined threshold (e.g., the transaction score is greater than or equal to the second predetermined threshold). In some embodiments, the transaction score component 230 is configured to flag the request for authorization when the request is associated with a financial transaction that has a transaction score between the first predetermined threshold and the second predetermined threshold (e.g., the transaction score is greater than the first predetermined threshold and less than the second predetermined threshold). Alternatively, the request for authorization may be flagged when the request is associated with a financial transaction that has a transaction score above the first predetermined threshold (e.g., no request for authorization is automatically declined). A flagged request for authorization is indicative of a potentially fraudulent financial transaction that requires additional analysis or attention to approve and/or decline a request for authorization.

A user may confirm or verify whether the financial transaction is legitimate or illegitimate. For example, the interface component 210 may

automatically communicate with the user via telephone, text message, or electronic mail (email) to confirm a legitimacy or illegitimacy of the financial transaction. If the financial transaction is confirmed or verified as an illegitimate financial transaction, the request for authorization is declined. If the financial transaction is processed (e.g., the request for authorization was approved) and the financial transaction is confirmed or verified as an Ulegitimate financial transaction, a chargeback (e.g., a return of funds associated with the financial transaction) may be processed. If the request for authorization is confirmed or verified as a legitimate financial transaction, the request for authorization is approved.

As described above, the memory component 240 is configured to store data associated with the cardholder account 170. In some embodiments, the cardholder account 170 may be associated with one or more virtual communities 120 and includes data associated with the virtual communities 120. For example, the cardholder account 170 may store data associated with a virtual product 160, a virtual merchant, a virtual transaction amount, a virtual transaction time, a virtual location, a quantity of virtual products 160, a virtual brand, a virtual product category, a purchase or reload of virtual currency, a purchase or reload rate of virtual currency, a balance of virtual currency, a rate of virtual transactions, a rate of virtual returns, a rate of virtual resale, a duration of having an account at the virtual community 120, a duration since registering the virtual community 120 with the cardholder account 170, and a duration of owning the virtual product 160.

FIG. 3 is a flowchart of an example method 300 for authorizing a financial transaction based on a virtual product 160 (shown in FIG. 1) using a computing device 200 (shown in FIG.2). The computing device 200 receives at 310 a request for authorization of a financial transaction associated with a real-world product 150. The request for authorization is associated with a cardholder account 170 and may, for example, access a credit line or an account balance to enable a user 140 to enter into the financial transaction associated with the real-world product 150. In some embodiments, the request for authorization is received from a client device 110.

At 320, the computing device 200 determines whether the cardholder account 170 is associated with a virtual product 160 corresponding to me real-world product 150. For example, the cardholder account 170 may be associated with a virtual community 120 at which there was an interaction or transaction associated with a virtual product 160. On condition that the cardholder account 170 is associated with a virtual product 160 corresponding to the real-world product 150, the request for authorization for the financial transaction is approved at 330. That is, the computing device 200 may determine that the transaction associated with the virtual product 160 is indicative of a user desire to enter into a financial transaction of a real-world product 150 corresponding to the virtual product 160. Alternatively, on condition that the cardholder account 170 is not associated with a virtual product 160 corresponding to the real-world product 150 (e.g., the cardholder account 170 is not associated with a virtual product 160, the virtual product 160 associated whh the cardholder account 170 does not correspond to the real-world product 150), the request for authorization for the financial transaction is declined at 340.

FIG.4 is a detailed flowchart of the method 300. In some embodiments, the user 140 may register for an account at the virtual community 120 and/or obtain virtual currency. The virtual currency may be earned or obtained, for example, over time, by performing one or more activities associated with the virtual community 120 (e.g., completing tasks), and/or by exchanging for real-world currency (e.g., via cardholder account 170). In some embodiments, the virtual currency may be used to purchase a virtual product 160 at the virtual community 120. Additionally or alternatively, real-world currency may be used to purchase the virtual product 160 at the virtual community 120.

In some embodiments, the cardholder account 170 is associated with the virtual community 120 upon identifying a transaction between the cardholder account 170 and the virtual community 120. For example, the user 140 may use the cardholder account 170 to purchase virtual currency and/or the virtual product 160 in exchange for real-world currency (e.g., debit or credit cash from me cardholder account 170). Additionally or alternatively, the user 140 may enroll or register the cardholder account 170 with the account associated with the virtual community 120 and/or the account associated with the virtual community 120 with the cardholder account 170.

In some embodiments, one or more activities and/or interactions (e.g., transactions) at the virtual community 120 may be monitored and/or tracked by the computing device 200. For example, a request to subscribe to a notification service may be generated at 410, and transmitted to a notification system associated with the virtual community 120. The notification system enables the virtual community 120 to provide one or more notifications to the user 140 (e.g., via a client device 110) and/or the computing device 200. For example, a transaction associated with a virtual product 160 may be identified and/or logged by the notification system, and data associated with the virtual transaction may be transmitted to the user 140 (e.g., at the client device 110) and/or the computing device 200.

Upon receiving a notification (e.g., the data associated with the virtual transaction) at 420, the computing device 200 may generate one or more promotions at 430 based on the virtual product 160 associated with the virtual transaction. For example, a coupon, reward, or advertisement for a real-world product 1 SO

corresponding to the virtual product 160 may be generated by the computing device 200 and/or transmitted to the user 140 (e.g., at a client device 110). In some embodiments, a third party (e.g., a merchant) may subscribe to the notification service and be notified when a virtual transaction satisfies one or more predetermined criteria. For example, the third party may elect to be notified when a predetermined virtual product 160 or a predetermined type of virtual product 160 is obtained, possessed, used, and/or consumed for a predetermined period of time. Upon receiving a notification, the third party may provide one or more promotions to a user 140 (e.g., at a client device 110). In some embodiments, the cardholder account 170 may be utilized in a financial transaction to purchase a real-world product 1 SO. Upon receiving a request for authorization associated with the real-world product 150 at 310, the cardholder account 170 associated with the request for authorization is identified, and it may be determined at 320 whether the cardholder account 170 is associated with a virtual product 160 corresponding to the real-world product 150. For example, the computing device 200 may generate a call to determine whether the cardholder account 170 is associated with a virtual product 160 that corresponds to the real-world product 150. In some embodiments, the computing device 200 may transmit a request for transaction data to the virtual community 120, and receive data associated with one or more virtual transactions. One or more transactions associated with a virtual product 160 may be identified at 440, and it may be determined at 4S0 whether at least one of tiie virtual products 160 associated with the transactions correspond to the real-world product 150.

On condition that no virtual product 160 corresponds to the real-world product 150, the computing device 200 may determine whether to approve or decline the request for authorization without the data associated with the one or more virtual transactions. For example, a score may be generated at 460 without the data associated with the one or more virtual transactions, and the score may be compared with a predetermined threshold to determine whether to approve or decline the request for authorization. On the other hand, on condition that a virtual product 160 corresponds to the real-world product 1 SO, data associated with the one or more virtual transactions may be used to determine whether to approve or decline a request for authorization of a financial transaction.

hi some embodiments, the financial transaction and/or the virtual transaction are associated with one or more parameters mat enable the computing device 200 to determine whether to approve or decline the request for authorization. That is, the parameters may be indicative of a likelihood of a user 140 who has obtained a virtual product 160 to purchase a corresponding real-world product 150. For example, the parameter may be associated with the real-world product 150 (e.g., a purchase price of the real-world product 150, a purchase time of the real-world product 150, a brand of the real-world product 150, and a category of the real-world product 1 SO), the virtual product 160 (e.g., a purchase price of the virtual product 160, a purchase time of the virtual product 160, a brand of the virtual product 160, a category of virtual product 160, a duration of the virtual product 160 being associated with the cardholder account 170, a rate of return of the virtual product 160, a rate of resale of the virtual product 160), and/or the virtual currency (e.g., an amount of the virtual currency, a reload rate of the virtual currency, a purchase rate of the virtual currency).

In some embodiments, one or more parameters may be identified at 470, and it may be determined at 480 whether the parameter satisfies a predetermined threshold. For example, the computing device 200 may generate a score associated with the parameter, and compare the score with a predetermined threshold. The request for authorization may be approved at 330 on condition mat the score satisfies the predetermined threshold. On the other hand, the request for authorization may be declined at 340 on condition that the score does not satisfy the predetermined threshold. In some embodiments, the user 140 may be authenticated for a financial transaction associated with a real-world product 150 on condition that the user 140 is associated with a virtual product 160 corresponding to the real-world product 150. For example, the financial transaction and/or the corresponding virtual transaction may be associated with one or more user identity-related parameters and/or risk-related parameters that enable the computing device 200 to authenticate or verify an identity of the user 140. On condition that the user 140 is not seamlessly authenticatable based on the one or more parameters, the user 140 may be challenged to provide another form of authentication.

In some embodiments, the scores and/or parameters may be tracked over time to correlate one or more parameters with successful transactions (e.g., approved requests for authorizations, coupon redemptions, impressions, click- throughs, conversions) and/or with unsuccessful transactions (e.g., declined requests for authorizations, unused coupons, no impressions, no click-through, no conversion) to generate a map based on the correlations. The generated map may be used, for example, to identify parameters that are more inclined to result in successful transactions and/or less inclined to result in unsuccessful transactions, and at least a portion of the virtual transaction and/or financial transaction may be defined based on the identified parameters. For example, terms of purchase of a real-world product 150 associated with a virtual product 160, such as a return policy or a chargeback policy, may be defined based on the identified parameters. FIG. 5 is an example sequence diagram 500 mat may be implemented at a system 100 to authorize one or more financial transactions. As shown in FIG. 5, a virtual community 120 may process a transaction associated with a virtual product 160. For example, a user 140 may obtain the virtual product 160 at the virtual community 120. In some embodiments, the user 140 may use a client device 110 to interface with the virtual community 120. Hie virtual community 120 may transmit data associated with the virtual product 160 to the financial transaction processing computing device 130, and, upon receiving the data associated with the virtual product 160, the financial transaction processing computing device 130 may store the data at a memory device (e.g., memory component 240) associated with the financial transaction processing computing device 130 for later retrieval. Alternatively, the financial transaction processing computing device 130 may transmit a request for data, and, upon receiving the request for data, the virtual community 120 may transmit the requested data to the financial transaction processing computing device 130.

A client device 110 (e.g., a point-of-sale terminal) may generate a request for authorization of a financial transaction for a real-world product 150. In some embodiments, the client device 110 may be the same client device 110 used to interface with the virtual community 120. Alternatively, the client device 110 may be different from the client device 110 used to interface with the virtual community 120. The client device 110 may transmit the request for authorization to the financial transaction processing computing device 130, and, upon receiving the request for authorization, the financial transaction processing computing device 130 may process data associated with the request for authorization to determine whether to approve or decline the request for authorization. For example, the financial transaction processing computing device 130 may determine whether a cardholder account 170 associated with the request for authorization is associated with a virtual product 160

corresponding to the real-world product 150. On condition that the financial transaction processing computing device 130 determines that the cardholder account 170 is associated with the virtual product 160, the financial transaction processing computing device 130 transmits approval of the request for authorization to the client device 110, and the client device 110 receives the approval.

FIG.6 is a block diagram of an example operating environment 600 mat may be used to authorizing a financial transaction based on a virtual product 160 (shown in FIG. 1). The operating environment 600 is only one example of a computing and networking environment and is not intended to suggest any limitation as to the scope of use or functionality of the disclosure. The operating environment 600 should not be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the example operating environment 600.

The disclosure is operational with numerous other computing and networking environments or configurations. While some examples of the disclosure are illustrated and described herein with reference to the operating environment 600 being or including a financial transaction processing computing device 130 (shown in FIG. 1) or a computing device 200 (shown in FIG.2), aspects of the disclosure are operable with any computing device (e.g., client device 110, virtual community 120, interface component 210, account manager component 220, transaction score component 230, memory component 240) that executes instructions to implement the operations and functionality associated with the operating environment 600.

For example, the operating environment 600 may include a mobile device, a mobile telephone, a phablet, a tablet, a portable media player, a netbook, a laptop, a desktop computer, a personal computer, a server computer, a computing pad, a kiosk, atabletop device, an industrial control device, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network computers, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. The operating environment 600 may represent a group of processing units or other computing devices. Additionally, any computing device described herein may be configured to perform any operation described herein including one or more operations described herein as being performed by another computing device.

With reference to FIG. 6, an example system for implementing various aspects of the disclosure may include a general purpose computing device in the form of a computer 610. Components of the computer 610 may include, but are not limited to, a processing unit 620, a system memory 625, and a system bus 630 that couples various system components including the system memory 625 to the processing unit 620. The system bus 630 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus.

The system memory 625 includes any quantity of media associated with or accessible by the processing unit 620. For example, the system memory 625 may include computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 631 and random access memory (RAM) 632. The ROM 631 may store a basic input/output system 633 (BIOS) mat facilitates transferring information between elements within computer 610, such as during startup. The RAM 632 may contain data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 620. For example, the system memory 625 may store computer-executable instructions, communication data, authentication data, application data, and other data.

The processing unit 620 may be programmed to execute the computer- executable instructions for implementing aspects of the disclosure, such as those illustrated in the figures (e.g., FIOs. 3, 4, and 5). By way of example, and not limitation, FIG.6 illustrates operating system 634, application programs 635, other program modules 636, and program data 637. The processing unit 620 includes any quantity of processing units, and the instructions may be performed by the processing unit 620 or by multiple processors within the operating environment 600 or performed by a processor external to the operating environment 600.

The system memory 625 may include computer-executable instructions, cardholder account information (e.g., parameters, preferences, rules, thresholds), message data, security data, enrollment data, and other data. For example, the system memory 625 may include an interface component 210 (shown in FIG.2), an account manager component 220 (shown in FIG.2), a transaction score component 230 (shown in FIG.2), and/or a memory component 240 (shown in FIG.2) for implementing aspects of the disclosure. Upon programming or execution of these components, the operating environment 600 and/or processing unit 620 is transformed into a special purpose microprocessor or machine. For example, the interface component 210, when executed by the processing unit 620, causes the processing unit 620 to receive a request for authorization of a financial transaction associated with a real-world product; the account manager component 220, when executed by the processing unit 620, causes the processing unit 620 to determine whether a cardholder account is associated with a virtual product corresponding to the real-world product; and nie manager component 330, when executed fay the processing unit 620, causes the processing unit 620 to approve the request for authorization for the financial transaction. Although the processing unit 620 is shown separate from the system memory 62S, embodiments of the disclosure contemplate mat the system memory 625 may be onboard the processing unit 620 such as in some embedded systems.

The computer 610 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only, FIG.6 illustrates a hard disk drive 641 that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive 642 that reads from or writes to a removable, nonvolatile magnetic disk 643 (e.g., a floppy disk, a tape cassette), and an optical disk drive 644 that reads from or writes to a removable, nonvolatile optical disk 64S (e.g., a compact disc (CD), a digital versatile disc (DVD)). Other removable/non-removable, volatile/nonvolatile computer storage media mat may be used in the example operating environment include, but are not limited to, flash memory cards, digital video tape, solid state RAM, solid state ROM, and the like. The hard disk drive 641 may be connected to the system bus 630 through a non-removable memory interface such as interface 646, and magnetic disk drive 642 and optical disk drive 644 may be connected to the system bus 630 by a removable memory interface, such as interface 647.

The drives and their associated computer storage media, described above and illustrated in FIG.6, provide storage of computer-readable instructions, data structures, program modules and other data for the computer 610. In FIG.6, for example, hard disk drive 641 is illustrated as storing operating system 654, application programs 655, other program modules 656 and program data 657. Note that these components may either be the same as or different from operating system 634, application programs 635, other program modules 636, and program data 637. Operating system 654, application programs 655, other program modules 656, and program data 657 are given different numbers herein to illustrate that, at a minimum, they are different copies.

The computer 610 includes a variety of computer-readable media. Computer-readable media may be any available media mat may be accessed by the computer 610 and includes bom volatile and nonvolatile media, and removable and non-removable media. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. ROM 631 and RAM 632 are examples of computer storage media. Computer storage media are tangible and mutually exclusive to communication media. Computer storage media for purposes of mis disclosure are not signals per se. Example computer storage media includes, but is not limited to, hard disks, flash drives, solid state memory, RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CDs, DVDs, or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which may be used to store the desired information and which may accessed by the computer 610. Computer storage media are implemented in hardware and exclude carrier waves and propagated signals. Any such computer storage media may be part of computer 610.

Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term "modulated data signal¹' means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

A user may enter commands and information into the computer 610 through one or more input devices, such as a pointing device 661 (e.g., mouse, trackball, touch pad), a keyboard 662, a microphone 663, and/or an electronic digitizer 664 (e.g., tablet). Other input devices not shown in FIG. 6 may include a joystick, a game pad, a controller, a satellite dish, a camera, a scanner, an

accelerometer, or the like. These and other input devices may be coupled to the processing unit 620 through a user input interface 665 that is coupled to the system bus 630, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). Information, such as text, images, audio, video, graphics, alerts, and the like, may be presented to a user via one or more presentation devices, such as a monitor 666, a printer 667, and/or a speaker 668. Other presentation devices not shown in FIG. 6 may include a projector, a vibrating component, or the like. These and other presentation devices may be coupled to the processing unit 620 through a video interface 669 (e.g., for a monitor 666 or a projector) and/or an output peripheral interface 670 (e.g., for a printer 667, a speaker 668, and/or a vibration component) mat are coupled to the system bus 630, but may be connected by other interface and bus structures, such as a parallel port, game port or a USB. In some embodiments, the presentation device is integrated with an input device configured to receive information from the user (e.g., a capacttive touch-screen panel, a controller including a vibrating component). Note that the monitor 666 and/or touch screen panel may be physically coupled to a housing in which the computer 610 is incorporated, such as in a tablet-type personal computer.

The computer 610 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 680. The remote computer 680 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 610, although only a memory storage device 681 has been illustrated in FIG. 6. The logical connections depicted in FIG. 6 include one or more local area networks (LAN) 682 and one or more wide area networks (WAN) 683, but may also include other networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet

When used in a LAN networking environment, the computer 610 is coupled to the LAN 682 through a network interface or adapter 684. When used in a WAN networking environment, the computer 610 may include a modem 685 or other means for establishing communications over the WAN 683, such as the Internet. The modem 685, which may be internal or external, may be connected to the system bus 630 via the user input interface 665 or other appropriate mechanism. A wireless networking component such as comprising an interface and antenna may be coupled through a suitable device such as an access point or peer computer to a LAN 682 or WAN 683. In a networked environment, program modules depicted relative to the computer 610, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation, FIG.6 illustrates remote application programs 686 as residing on memory storage device 681. It may be appreciated that the network connections shown are examples and other means of establishing a communications link between the computers may be used.

The block diagram of FIG. 6 is merely illustrative of an example system that may be used in connection with one or more examples of the disclosure and is not intended to be limiting in any way. Further, peripherals or components of the computing devices known in the art are not shown, but are operable with aspects of the disclosure. At least a portion of the functionality of the various elements in FIG.6 may be performed by other elements in FIG. 6, or an entity (e.g., processor, web service, server, applications, computing device, etc.) not shown in FIG. 6.

FIG.7 is a block diagram illustrating an example system or environment 700 for processing financial transactions. The environment 700 includes a processing network 710, such as the MASTERCARD® brand payment processing network (MASTERCARD® is a registered trademark of MasterCard International Incorporated located in Purchase, NY). The MASTERCARD® brand payment processing network is a propriety network for exchanging financial transaction data between members of the MASTERCARD® brand payment processing network.

The environment 700 includes one or more merchants 720 that accept payment via the processing network 710. To accept payment via the processing network 710, the merchant 720 establishes a financial account with an acquirer 730 that is a member of the processing network 710. The acquirer 730 is a financial institution that maintains a relationship with one or more merchants 720 to enable the merchants 720 to accept payment via the processing network 710. The acquirer 730 may also be known as an acquiring bank, a processing bank, or a merchant bank.

The environment 700 includes one or more issuers 740 mat issue or provide payment cards 750 (e.g., credit card, debit card, prepaid card, and the like) or other payment products to one or more cardholders 760 or, more broadly, account holders ("cardholder" and "account holder" may be used interchangeably herein). The issuer 740 is a financial institution mat maintains a relationship with one or more cardholders 760 to enable the cardholders 760 to make a payment using the payment card 750 via the processing network 710.

A cardholder 760 uses a payment product, such as a payment card 750, to purchase a good or service from a merchant 720. In some embodiments, the payment card 750 is linked or associated with electronic wallet technology or contactless payment technology, such as a radio frequency identification (RFID)- enabled device, a BLUETOOTH® brand wireless technology-enabled device, a ZIGBEE® brand communication-enabled device, a WI-FI® brand local area wireless computing network-enabled device, a near field communication (NFC) wireless communication-enabled device, and/or any other device that enables the payment card 750 to purchase a good or service from a merchant 720. (BLUETOOTH® is a registered trademark of Bluetooth Special Interest Group, ZIGBEE® is a registered trademark of the ZigBee Alliance, and WI-FI® is a registered trademark of the Wi-Fi Alliance). The cardholder 760 may use any payment product that is linked or associated with a corresponding financial account maintained by an issuer 740. As described herein, the term "payment card" includes credit cards, debit cards, prepaid cards, digital cards, smart cards, and any other payment product mat is linked or associated with a corresponding financial account maintained by an issuer 740.

Payment cards 750 may have any shape, size, or configuration mat enables the environment 700 to function as described herein.

A cardholder 760 may present the merchant 720 with a payment card 750 to make a payment to the merchant 720 in exchange for a good or service.

Alternatively, the cardholder 760 may provide the merchant 720 with account information associated with the payment card 750 without physically presenting the payment card 750 (e.g., for remote financial transactions, including e-commerce transactions, card-not-present transactions, or card-on-file transactions). Account information may include a name of the cardholder 760, an account number, an expiration date, a security code (such as a card verification value (CVV), a card verification code (CVC), and the like), and/or a personal identification number (PIN).

The merchant 720 requests authorization from an acquirer 730 for at least the amount of the purchase. The merchant 720 may request authorization using any financial transaction computing device configured to transmit account information of the cardholder 760 to one or more financial transaction processing computing devices of the acquirer 730. For example, the merchant 720 may request authorization through a point-of-sale (POS) terminal, which reads account information of the cardholder 760 from a microchip or magnetic stripe on the payment card 750, and transmits the cardholder's account information to the one or more financial transaction processing computing devices of the acquirer 730. For another example, the POS terminal reads account information of the cardholder 760 from a device configured to communicate with the POS terminal using contactless payment technology, and transmits the cardholder's account information to one or more financial transaction processing computing devices of the acquirer 730.

Using the processing network 710, the financial transaction processing computing devices of the acquirer 730 communicate with one or more financial transaction processing computing devices of an issuer 740 to determine whether the account information of the cardholder 760 matches or corresponds with the account information of the issuer 740, whether the account is in good standing, and/or whether the purchase is covered by (e.g., less than) a credit line or account balance associated with the financial account. Based on these determinations, the financial transaction processing computing devices of the issuer 740 determine whether to approve or decline the request for authorization from the merchant 720.

If the request for authorization is declined, the merchant 720 is notified as such, and may request authorization from the acquirer 730 for a lesser amount or request an alternative form of payment from the cardholder 760. If the request for authorization is approved, an authorization code is issued to the merchant 720, and the cardholder's available credit line or account balance is decreased. The financial transaction is then settled between the merchant 720, the acquirer 730, the issuer 740, and/or the cardholder 760. Settlement typically includes the acquirer 730 reimbursing the merchant 720 for selling the good or service, and the issuer 740 reimbursing the acquirer 730 for reimbursing the merchant 720. When a credit card is used, the issuer 740 may bill the cardholder 760 to settle a financial account associated with the cardholder 760. When a debit or prepaid card is used, the issuer 740 may

automatically withdraw funds from the account.

Although described in connection with an example computing system environment, embodiments of the disclosure are capable of implementation with numerous other general purpose or special purpose computing system environments, configurations, or devices.

Embodiments of well-known computing systems, environments, and/or configurations that may be suitable for use with aspects of the disclosure include, but are not limited to, mobile computing devices, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, gaming consoles,

microprocessor-based systems, set top boxes, programmable consumer electronics, mobile telephones, mobile computing and/or communication devices in wearable or accessory form factors (e.g., watches, glasses, headsets, earphones, and me like), network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. Such systems or devices may accept input from the cardholder in any way, including from input devices such as a keyboard or pointing device, via gesture input, proximity input (such as by hovering), and/or via voice input.

Embodiments of the disclosure may be described in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices in software, firmware, hardware, or a combination thereof. The computer-executable instructions may be organized into one or more computer-executable components or modules. Generally, program modules include, but are not limited to, routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. Aspects of the disclosure may be implemented with any number and organization of such components or modules. For example, aspects of the disclosure are not limited to the specific computer-executable instructions or the specific components or modules illustrated in the figures and described herein. Other embodiments of the disclosure may include different computer-executable instructions or components having more or less functionality than illustrated and described herein.

The embodiments illustrated and described herein as well as embodiments not specifically described herein but within the scope of aspects of the disclosure constitute example means for authorizing one or more financial transactions. For example, the elements illustrated in FIGs. 1, 2, 6, or 7 such as when encoded to perform the operations illustrated in FIGs. 3, 4, or 5 constitute at least an example means for receiving a request for authorization of a financial transaction associated with a real-world product (e.g., interface component 210), an example means for determining whether the cardholder account is associated with a virtual product corresponding to the real-world product (e.g., account manager component 220), and/or an example means for approving the request for authorization for the financial transaction (e.g., transaction score component 230).

The order of execution or performance of the operations in embodiments of the disclosure illustrated and described herein is not essential, unless otherwise specified. That is, the operations may be performed in any order, unless otherwise specified, and embodiments of the disclosure may include additional or fewer operations than those disclosed herein. For example, it is contemplated mat executing or performing a particular operation before, contemporaneously with, or after another operation is within the scope of aspects of the disclosure.

When introducing elements of aspects of the disclosure or the embodiments thereof, the articles "a," "an," "the," and "said" are intended to mean that there are one or more of the elements. Furthermore, references to an

"embodiment" or "example" of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments or examples that also incorporate the recited features. The terms "comprising," "including," and

"having" are intended to be inclusive and mean that mere may be additional elements other than the listed elements. The phrase "one or more of the following: A, B, and C" means "at least one of A and/or at least one of B and/or at least one of C."

Having described aspects of the disclosure in detail, it will be apparent that modifications and variations are possible without departing from the scope of aspects of the disclosure as defined in the appended claims. As various changes could be made in the above constructions, products, and methods without departing from the scope of aspects of the disclosure, it is intended that all matter contained in the above description and shown in the accompanying drawings shall be interpreted as illustrative and not in a limiting sense.

In some embodiments, the operations illustrated in the drawings may be implemented as software instructions encoded on a computer readable medium, in hardware programmed or designed to perform the operations, or both. For example, aspects of the disclosure may be implemented as a system on a chip or other circuitry including a plurality of interconnected, electrically conductive elements.

While the aspects of the disclosure have been described in terms of various embodiments with their associated operations, a person skilled in the art would appreciate that a combination of operations from any number of different embodiments is also whhin scope of the aspects of the disclosure.

Claims

WHAT IS CLAIMED IS:

1. A computer-implemented method for authorizing one or more financial transactions, the computer-implemented method comprising:

receiving, from a client device, a request for authorization of a financial transaction associated with a real-world product, the request for authorization associated with a cardholder account;

determining whether the cardholder account is associated with a virtual product corresponding to the real-world product; and

on condition mat the cardholder account is associated with the virtual product corresponding to the real-world product, approving the request for authorization for the financial transaction.

2. The computer-implemented method of claim 1, wherein (tetermining whether the cardholder account is associated with the virtual product comprises: identifying a transaction associated with the virtual product; and

determining whether the virtual product corresponds to the real-world product

3. The computer-implemented method of claim 1, further comprising: subscribing to a notification service associated with a virtual community; and receiving a notification of a transaction associated with the virtual product

4. The computer-implemented method of claim 1, further comprising: receiving a notification of a transaction associated with the virtual product; in response to receiving the notification, generating a promotion associated with the real-world product.

5. The computer-implemented method of claim 1, wherein approving the request for authorization for the financial transaction comprises, on condition that the cardholder account is associated with the virtual product corresponding to the real- world product, generating a score associated with the financial transaction, the score satisfying a predetermined threshold.

6. The computer-implemented method of claim 1, wherein approving the request for authorization for the financial transaction comprises identifying at least one parameter associated with a virtual currency including at least one of an amount of the virtual currency, a reload rate of the virtual currency, and a purchase rate of the virtual currency, the request for authorization approved on condition that the at least one parameter satisfies a predetermined threshold.

7. Hie computer-implemented method of claim 1, wherein approving the request for authorization for the financial transaction comprises identifying at least one parameter associated with the virtual product including at least one of a duration of the virtual product being associated with the cardholder account, a rate of return of the virtual product, and a rate of resale of the virtual product, the request for authorization approved on condition mat the at least one parameter satisfies a predetermined threshold.

8. The computer-implemented method of claim 1, wherein approving the request for authorization for the financial transaction comprises identifying at least one parameter associated with the real-world product including a purchase price of the real-world product, a purchase time of the real-world product, a brand of the real- world product, and a category of the real-world product, the request for authorization approved on condition that the at least one parameter satisfies a predetermined threshold.

9. A computing device for authorizing one or more financial transactions, the computing device comprising:

a memory device storing data associated with one or more cardholder accounts, and computer-executable instructions; and

a processor configured to execute the computer-executable instructions to: receive a request for authorization of a financial transaction associated with a real-world product, the request for authorization associated with a first cardholder account of the one or more cardholder accounts;

determine whether the first cardholder account is associated with a virtual product corresponding to the real-world product; and

on condition mat the first cardholder account is associated with the virtual product corresponding to the real-world product, approve the request for authorization for the financial transaction.

10. The computing device of claim 9, wherein the processor is further configured to execute the computer-executable instructions to:

identify a transaction associated with the virtual product; and

determine whether the virtual product corresponds to the real-world product

11. The computing device of claim 9, wherein the processor is further configured to execute the computer-executable instructions to:

subscribe to a notification service associated with a virtual community; and receive a notification of a transaction associated with the virtual product

12. The computing device of claim 9, wherein the processor is further configured to execute the computer-executable instructions to generate a promotion associated with the real-world product

13. The computing device of claim 9, wherein the processor is further configured to execute the computer-executable instructions to, on condition that the first cardholder account is associated with the virtual product corresponding to the real-world product, generate a score associated with the financial transaction, the score satisfying a predetermined threshold.

14. The computing device of claim 9, wherein the processor is further configured to execute the computer-executable instructions to identify at least one parameter associated with a virtual currency including at least one of an amount of the virtual currency, a reload rate of the virtual currency, and a purchase rate of the virtual currency, the request for authorization approved on condition that the at least one parameter satisfies a predetermined threshold.

15. The computing device of claim 9, wherein the processor is further configured to execute the computer-executable instructions to identify at least one parameter associated with the virtual product including at least one of a duration of the virtual product being associated with the cardholder account, a rate of return of the virtual product, and a rate of resale of the virtual product the request for authorization approved on condition that the at least one parameter satisfies a predetermined threshold.

16. The computing device of claim 9, wherein the processor is further configured to execute the computer-executable instructions to identify at least one parameter associated with the real-world product including a purchase price of the real-world product a purchase time of the real-world product, a brand of the real- world product, and a category of the real-world product, the request for authorization approved on condition that the at least one parameter satisfies a predetermined threshold..

17. A computer-readable storage device having computer-executable instructions embodied thereon, wherein, upon execution by at least one processor, the computer-executable instructions cause the processor to:

receive a request for authorization of a financial transaction associated with a real-world product the request for authorization associated with a cardholder account; identify a transaction associated with a virtual product, the transaction associated with the cardholder account;

determine whether the virtual product corresponds to the real-world product; and

on condition that the virtual product corresponds to the real-world product, approve the request for authorization for the financial transaction.

18. Hie computer-readable storage device of claim 17, wherein, upon execution by the at least one processor, the computer-executable instructions further cause the processor to:

subscribe to a notification service associated with a virtual community; and receive a notification of a transaction associated with the virtual product.

19. The computer-readable storage device of claim 17, wherein, upon execution by the at least one processor, the computer-executable instructions further cause the processor to generate a promotion associated with the real-world product.

20. The computer-readable storage device of claim 17, wherein, upon execution by the at least one processor, the computer-executable instructions further cause the processor to identify at least one parameter associated with at least one of a virtual currency, the virtual product, and the real-world product, the request for authorization approved on condition that the at least one parameter satisfies a predetermined threshold.