SYSTEM AND METHOD FOR CONFIRMING ELECTRONIC DELIVERY OF DIGITAL INCENTIVES

TECHNICAL FIELD

The present application relates to systems and methods for confirming electronic delivery of digital incentives.

BACKGROUND

Incentives such as digital incentives may be provided for a number of reasons. It is often difficult to confirm electronic delivery of the digital incentives.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are described in detail below, with reference to the following drawings:

FIG. 1 is a schematic operation diagram illustrating an operating environment of an example embodiment;

FIG. 2 is a simplified schematic diagram showing components of a computing device;

FIG. 3 is a high-level schematic diagram of an example computer device;

FIG. 4 shows a simplified organization of software components stored in a memory of the example computer device of FIG. 3;

FIG. 5 is a flowchart showing operations performed by a server computer system in automatically generating a customized incentive interface according to an embodiment;

FIG. 6 shows an example white label incentive interface according to an embodiment;

FIG. 7 shows another example white label incentive interface according to an embodiment;

FIG. 8 shows a digital gift card skin according to an embodiment;

FIG. 9 shows a customized incentive interface generated using the example white label incentive interface of FIG. 6 according to an embodiment;

FIG. 10 is a flowchart showing operations performed by a server computer system for generating recommendations for who should receive the one or more digital incentives according to an embodiment;

FIG. 11 is a flowchart showing operations performed by a server computer system for obtaining the electronic addresses of computing devices associated with the accepted recommendation according to an embodiment;

FIG. 12 is a flowchart showing operations performed by a server computer system for generating a customized incentive interface in a determined digital format according to an embodiment;

FIG. 13 is a flowchart showing operations performed by a server computer system for sending a particular digital incentive according to an embodiment;

FIG. 14 is a flowchart showing operations performed by a server computer system for automatically determining a label for a graphical object according to an embodiment;

FIG. 15 is a flowchart showing operations performed by a server computer system for managing a bulk order of incentives according to an embodiment;

FIG. 16 is a flowchart showing operations performed by a server computer system for managing and tracking bulk orders of incentives according to an embodiment;

FIG. 17 is a flowchart showing operations performed by a server computer system for providing additional information of a particular bulk order of incentives according to an embodiment;

FIG. 18 is a flowchart showing operations performed by a server computer system for cancelling or putting on hold at least one bulk order of incentives according to an embodiment;

FIG. 19 is a flowchart showing operations performed by a server computer system for providing access to an incentive management application;

FIG. 20 is a simplified schematic operation diagram illustrating a computing device provided with a first access level;

FIG. 21 is a simplified schematic operation diagram illustrating a computing device provided with a second access level;

FIG. 22 is a flowchart showing operations performed by a server computer system for fulfilling a bulk order of incentives;

FIG. 23 is an example graphical user interface that includes a list of bulk orders of incentives; and

FIG. 24 is an example graphical user interface that includes a list of incentives and a selectable interface element to upload a digital file.

Like reference numerals are used in the drawings to denote like elements and features.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

Accordingly, in one aspect there is provided a server computer system comprising a communications module; a processor coupled with the communications module; and a memory coupled to the processor and storing processor-executable instructions which, when executed by the processor, configure the processor to obtain a list of incentives associated with a bulk order of incentives and electronic addresses of recipients of the incentives; assign one or more of the incentives to one or more of the electronic addresses; send, via the communications module and to the one or more of the electronic addresses, the incentives; and monitor an error log to confirm successful delivery of the incentives.

In one or more embodiments, the list of the incentives associated with the bulk order of incentives includes at least one of a unique identifier of each incentive or a denomination of each incentive.

In one or more embodiments, the processor-executable instructions, when executed by the processor, further configure the processor to determine, based on the error log, that at least one of the incentives was not successfully delivered; and send, to a computing device, an indication that the at least one of the incentives was not successfully delivered.

In one or more embodiments, the indication that the at least one of the incentives was not successfully delivered includes a selectable interface element to provide an updated electronic address of the recipient.

In one or more embodiments, the indication that the at least one of the incentives was not successfully delivered indicates the electronic address of the recipient that did not successfully receive the incentive.

In one or more embodiments, the processor-executable instructions, when executed by the processor, further configure the processor to confirm successful delivery of at least one of the incentives; and update a fulfillment status of the at least one incentive to fulfilled.

In one or more embodiments, prior to sending the incentives to the one or more of the electronic addresses, the processor-executable instructions, when executed by the processor, further configure the processor to generate a customized incentive interface by populating one or more interface elements of a white label incentive interface according to one or more scopes, the customized incentive interface including a selectable interface element to accept one of the incentives.

In one or more embodiments, sending the incentives includes sending the customized incentive interface.

In one or more embodiments, the incentives include digital gift cards.

According to another aspect there is provided a computer-implemented method executed by a processor of a computer server system, the method comprising obtaining a list of incentives associated with a bulk order of incentives and electronic addresses of recipients of the incentives; assigning one or more of the incentives to one or more of the electronic addresses; sending, via a communications module and to the one or more of the electronic addresses, the incentives; and monitoring an error log to confirm successful delivery of the incentives.

In one or more embodiments, obtaining the list of the incentives associated with the incentive order includes receiving, from a computing device, a digital file that includes the list of the incentives.

In one or more embodiments, the list of the incentives associated with the bulk order of incentives includes at least one of a unique identifier of each incentive or a denomination of each incentive.

In one or more embodiments, the method further comprises determining, based on the error log, that at least one of the incentives was not successfully delivered; and sending, to a computing device, an indication that the at least one of the incentives was not successfully delivered.

In one or more embodiments, the method further comprises confirming successful delivery of at least one of the incentives; and updating a fulfillment status of the at least one incentive to fulfilled.

According to another aspect there is provided a non-transitory computer readable storage medium comprising computer-executable instructions which, when executed, configure a processor to obtain a list of incentives associated with a bulk order of incentives and electronic addresses of recipients of the incentives; assign one or more of the incentives to one or more of the electronic addresses; send, via a communications module and to the one or more of the electronic addresses, the incentives; and monitor an error log to confirm successful delivery of the incentives.

Other aspects and features of the present application will be understood by those of ordinary skill in the art from a review of the following description of examples in conjunction with the accompanying figures.

In the present application, the term “and/or” is intended to cover all possible combinations and sub-combinations of the listed elements, including any one of the listed elements alone, any sub-combination, or all of the elements, and without necessarily excluding additional elements.

In the present application, the phrase “at least one of ...or...” is intended to cover any one or more of the listed elements, including any one of the listed elements alone, any sub-combination, or all of the elements, without necessarily excluding any additional elements, and without necessarily requiring all of the elements.

In the present application, examples involving a general-purpose computer, aspects of the disclosure transform the general-purpose computer into a special-purpose computing device when configured to execute the instructions described herein.

FIG. 1 is a schematic operation diagram illustrating an operating environment of an example embodiment. As shown, the system 100 includes a computing device 110 and a server computer system 120 coupled to one another through a network 130, which may include a public network such as the Internet and/or a private network. The computing device 110 and the server computer system 120 may be in geographically disparate locations. Put differently, the computing device 110 and the server computer system 120 may be located remote from one another.

The computing device 110 may be a laptop computer as shown in FIG. 1. However, the computing device 110 may be a computing device of another type such as for example a smartphone, personal computer, a tablet computer, a notebook computer, a hand-held computer, a personal digital assistant, a portable navigation device, a mobile phone, a wearable computing device (e.g., a smart watch, a wearable activity monitor, wearable smart jewelry, and glasses and other optical devices that include optical head-mounted displays), an embedded computing device (e.g., in communication with a smart textile or electronic fabric), and any other type of computing device that may be configured to store data and software instructions, and execute software instructions to perform operations consistent with disclosed embodiments.

The server computer system 120 is a computer server system. A computer server system may, for example, be a mainframe computer, a minicomputer, or the like. In some implementations thereof, a computer server system may be formed of or may include one or more computing devices. A computer server system may include and/or may communicate with multiple computing devices such as, for example, database servers, computer servers, and the like. Multiple computing devices such as these may be in communication using a computer network and may communicate to act in cooperation as a computer server system. For example, such computing devices may communicate using a local-area network (LAN). In some embodiments, a computer server system may include multiple computing devices organized in a tiered arrangement. For example, a computer server system may include middle tier and back-end computing devices. In some embodiments, a computer server system may be a cluster formed of a plurality of interoperating computing devices.

The network 130 is a computer network. In some embodiments, the network 130 may be an internetwork such as may be formed of one or more interconnected computer networks. For example, the network 130 may be or may include an Ethernet network, an asynchronous transfer mode (ATM) network, a wireless network, a telecommunications network, or the like.

The computing device 110 is associated with a requesting party and may be adapted to send, to the server computer system 120, web requests. As will be described in more detail below, the web requests may include a web request to send one or more incentives. The incentives may include, for example, physical gift cards, digital gift cards, loyalty point multipliers, etc.

The server computer system 120 may be a financial institution server and may maintain a database 140 that includes various data records. At least some of the data records may be associated with customer bank accounts and/or customer credit card accounts. For example, a data record may reflect an amount of value stored in a customer’s bank account. As another example, a data record may store transaction data associated with one or more transactions made on a credit card. The transaction data may include information related to one or more transactions such as for example a transaction location, a transaction date, a transaction amount, etc. At least some of the data records may include additional account data such as for example the name, age, address of the customer, etc. and the account data may be associated with the customer bank accounts and/or customer credit card accounts. The account data may additionally include information relating to incentives or digital incentives previously accepted by a customer. For example, the information may identify the amount of the digital incentive, the type of the digital incentive, and the digital format that was used to send the digital incentive to the customer.

It will be appreciated that the amount of data stored in the database may be referred to as big data. For example, the database 140 may store transaction data for every transaction made by every customer of the financial institution. The amount of data may be too large or complex to be dealt with by traditional data-processing application software. As such, in one or more embodiments, the server computer system 120 may engage a data mining module to analyze the account data to generate at least one recommendation for sending a digital incentive.

The server computer system 120 may communicate with the database 140 directly or through the network 130.

The server computer system 120 may communicate with one or more additional computing devices 150. Specifically, the server computer system 120 may send and receive signals with the additional computing devices 150 and at least some of the signals may include a customized incentive interface that is to be displayed on the one or more additional computing device 150. Although only one additional computing device 150 is shown in FIG. 1, a plurality of additional computing devices 150 may communicate with the server computer system 120 and each additional computing device 150 may be associated with a customer of the financial institution. Each additional computing device 150 may be, for example, a laptop, a smartphone, personal computer, a tablet computer, a notebook computer, a hand-held computer, a personal digital assistant, a portable navigation device, a mobile phone, a wearable computing device (e.g., a smart watch, a wearable activity monitor, wearable smart jewelry, and glasses and other optical devices that include optical head-mounted displays), an embedded computing device (e.g., in communication with a smart textile or electronic fabric), and any other type of computing device that may be configured to store data and software instructions, and execute software instructions to perform operations consistent with disclosed embodiments.

The computing device 110 and/or the one or more additional computing devices 150 may additionally or alternatively include computing devices associated with an administration account, a provider account and/or a purchaser account.

FIG. 2 is a simplified schematic diagram showing components of an exemplary computing device 200. The computing device 110 and the one or more additional computing devices 150 may be of the same type as computing device 200. The computing device 200 may include modules including, as illustrated, for example, one or more displays 210, an image capture module 220, a sensor module 230, and a computer device 240.

The one or more displays 210 are a display module. The one or more displays 210 are used to display screens of a graphical user interface that may be used, for example, to communicate with the server computer system 120 (FIG. 1). The one or more displays 210 may be internal displays of the computing device 200 (e.g., disposed within a body of the computing device).

The image capture module 220 may be or may include a camera. The image capture module 220 may be used to obtain image data, such as images. The image capture module 220 may be or may include a digital image sensor system as, for example, a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) image sensor.

The sensor module 230 may be a sensor that generates sensor data based on a sensed condition. By way of example, the sensor module 230 may be or include a location subsystem which generates location data indicating a location of the computing device 200. The location may be the current geographic location of the computing device 200. The location subsystem may be or include any one or more of a global positioning system (GPS), an inertial navigation system (INS), a wireless (e.g., cellular) triangulation system, a beacon-based location system (such as a Bluetooth low energy beacon system), or a location subsystem of another type.

The computer device 240 is in communication with the one or more displays 210, the image capture module 220, and the sensor module 230. The computer device 240 may be or may include a processor which is coupled to the one or more displays 210, the image capture module 220, and/or the sensor module 230.

Referring now to FIG. 3, a high-level operation diagram of an example computer device 300 is shown. In some embodiments, the computer device 300 may be exemplary of the computer device 240 (FIG. 2) and/or server computer system 120.

The example computer device 300 includes a variety of modules. For example, as illustrated, the example computer device 300 may include a processor 310, a memory 320, a communications module 330, and/or a storage module 340. As illustrated, the foregoing example modules of the example computer device 300 are in communication over a bus 350.

The processor 310 is a hardware processor. The processor 310 may, for example, be one or more ARM, Intel x86, PowerPC processors or the like.

The memory 320 allows data to be stored and retrieved. The memory 320 may include, for example, random access memory, read-only memory, and persistent storage. Persistent storage may be, for example, flash memory, a solid-state drive or the like. Read-only memory and persistent storage are non-transitory computer-readable storage mediums. A computer-readable medium may be organized using a file system such as may be administered by an operating system governing overall operation of the example computer device 300.

The communications module 330 allows the example computer device 300 to communicate with other computer or computing devices and/or various communications networks. For example, the communications module 330 may allow the example computer device 300 to send or receive communications signals. Communications signals may be sent or received according to one or more protocols or according to one or more standards. For example, the communications module 330 may allow the example computer device 300 to communicate via a cellular data network, such as for example, according to one or more standards such as, for example, Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Evolution Data Optimized (EVDO), Long-term Evolution (LTE) or the like. Additionally or alternatively, the communications module 330 may allow the example computer device 300 to communicate using near-field communication (NFC), via Wi-Fi (TM), using Bluetooth (TM) or via some combination of one or more networks or protocols. In some embodiments, all or a portion of the communications module 330 may be integrated into a component of the example computer device 300. For example, the communications module may be integrated into a communications chipset. In some embodiments, the communications module 330 may be omitted such as, for example, if sending and receiving communications is not required in a particular application.

The storage module 340 allows the example computer device 300 to store and retrieve data. In some embodiments, the storage module 340 may be formed as a part of the memory 320 and/or may be used to access all or a portion of the memory 320. Additionally or alternatively, the storage module 340 may be used to store and retrieve data from persisted storage other than the persisted storage (if any) accessible via the memory 320. In some embodiments, the storage module 340 may be used to store and retrieve data in a database. A database may be stored in persisted storage. Additionally or alternatively, the storage module 340 may access data stored remotely such as, for example, as may be accessed using a local area network (LAN), wide area network (WAN), personal area network (PAN), and/or a storage area network (SAN). In some embodiments, the storage module 340 may access data stored remotely using the communications module 330. In some embodiments, the storage module 340 may be omitted and its function may be performed by the memory 320 and/or by the processor 310 in concert with the communications module 330 such as, for example, if data is stored remotely. The storage module may also be referred to as a data store.

Software comprising instructions is executed by the processor 310 from a computer-readable medium. For example, software may be loaded into random-access memory from persistent storage of the memory 320. Additionally or alternatively, instructions may be executed by the processor 310 directly from read-only memory of the memory 320.

FIG. 4 depicts a simplified organization of software components stored in the memory 320 of the example computer device 300 (FIG. 3). As illustrated, these software components include an operating system 400 and an application 410.

The operating system 400 is software. The operating system 400 allows the application 410 to access the processor 310 (FIG. 3), the memory 320, and the communications module 330 of the example computer device 300 (FIG. 3). The operating system 400 may be, for example, Google (TM) Android (TM), Apple (TM) iOS (TM), UNIX (TM), Linux (TM), Microsoft (TM) Windows (TM), Apple OSX (TM) or the like.

The application 410 adapts the example computer device 300, in combination with the operating system 400, to operate as a device performing a particular function. For example, the application 410 may cooperate with the operating system 400 to adapt a suitable embodiment of the example computer device 300 to operate as the computer device 240 (FIG. 2) and/or the server computer system 120.

While a single application 410 is illustrated in FIG. 3, in operation the memory 320 may include more than one application 410 and different applications 410 may perform different operations. For example, in at least some embodiments in which the computer device 300 is functioning as the computing device 110, the applications 410 may include an incentive management application. The incentive management application may be provided as a web application and/or a mobile application. The incentive management application may be configured to present one or more graphical user interfaces on a display of the computing device 110 and may provide various incentive management functions.

The incentive management application may require a requesting party to authenticate. For example, the incentive management application may be accessed on the computing device 110 via an internet web browser and may require the user of the computing device 110 (also referred to as the requesting party) to create an account. Account creation may require the submission of credentials to be used for authentication such as for example a username and a password. The username may include the requesting party’s email address. Additional information may be required to complete account creation such as for example a company name, etc. It will be appreciated that in one or more embodiments the incentive management application may be downloaded or resident on the computing device 110 and thus may be accessed directly thereon.

To access the incentive management application on the computing device 110, the requesting party may be prompted to enter the credentials submitted during the account creation. For example, the requesting party may be prompted to submit a username and a password associated with their account. In response to receiving the credentials, the server computer system 120 may authenticate the computing device 110 (or user) and may identify an account associated therewith.

Within the incentive management application, a graphical user interface may be displayed on a display screen of the computing device 110 that may include one or more selectable interface elements for submitting additional information and/or objects. For example, a selectable interface element for uploading or submitting one or more graphical objects associated with the requesting party may be displayed. The graphical objects may include company logos, digital gift card skins, animated objects, etc. In response to selecting the selectable interface element, a graphical user interface may be displayed that includes one or more selectable interface elements for uploading or submitting the one or more graphical objects. The requesting party may select one of the selectable interface elements which may prompt the user to select a particular file or web address that includes the graphical object. In this manner, graphical objects may be submitted by the requesting party using the computing device 110 and stored in the database 140 by the server computer system 120. As will be described in more detail below, the server computer system 120 may analyze the uploaded graphical objects to label or categorize each uploaded graphical object. Alternatively, the requesting party may be prompted to label or categorize each uploaded graphical object.

As another example, a selectable interface element for uploading or submitting a list of electronic addresses that are to receive the one or more digital incentives may be displayed. The list of electronic addresses may include, for example, email addresses, telephone numbers, unique identifiers of computing devices, etc. In response to selecting the selectable interface element, a graphical user interface may be displayed that includes one or more selectable interface elements for uploading or submitting the list of electronic addresses. The requesting party may select one or more digital files that include the list of electronic addresses and the digital files may be in a standardized format such as for example a comma-separated values (CSV) file format.

The incentive management application may present one or more graphical user interfaces on the computing device 110 that allow a requesting party to submit a request to automatically send one or more digital incentives. In response to receiving the request to send one or more digital incentives, a customized incentive interface may be generated and sent to one or more electronic addresses.

Reference is made to FIG. 5, which illustrates, in flowchart form, a method 500 for generating a customized incentive interface. The method 500 may be implemented by a computing device having suitable processor-executable instructions for causing the computing device to carry out the described operations. The method 500 may be implemented, in whole or in part, by the server computer system 120.

The method 500 includes receiving, from a computing device associated with a requesting party, a signal that includes a web request to send one or more digital incentives and defines one or more scopes for the one or more digital incentives (step 510).

In one or more embodiments, the web request to send one or more digital incentives may include or may define one or more scopes for the one or more digital incentives. The scopes may be defined by the requesting party within the incentive management application. For example, the incentive management application may display, on the computing device 110, a graphical user interface that includes one or more interface elements for defining the scopes for the one or more digital incentives. The interface elements may include, for example, selectable interface elements (selectable buttons, radio buttons, toggle buttons, etc.), input fields, etc. and may be selected or completed by the requesting party using, for example, an input device of the computing device 110.

The one or more scopes may include, for example, a type of each digital incentive. For example, the type of a digital incentive may include a digital gift card, a loyalty point multiplier, etc. The one or more scopes may additionally define an amount of the digital incentive. For example, the digital incentive type may include the digital gift card and the amount of the digital incentive may include, for example, $5, $10, etc. As another example, the digital incentive type may include the loyalty point multiplier and the amount of the digital incentive may include, for example, 2x, 3x, 5x etc. It will be appreciated that the loyalty point multiplier may be an amount of loyalty points earned per dollar spent. For example, the amount of the digital incentive may include 5x and as such for every $1 spent at a particular merchant the digital incentive may allow a recipient of the digital incentive to earn five (5) loyalty points. It will be appreciated that the request to send one or more digital incentives may include a request to send multiple digital incentives and each digital incentive may be of a different type or a different value.

The one or more scopes may include parameters for each digital incentive. For example, the parameters may define where the digital incentive may be used such as for example a particular merchant or category of merchants. As one example, the parameters of a particular digital incentive may define that the digital incentive may be used at a Merchant A and the parameters of another digital incentive may define that the digital incentive may be used at a Merchant B.

It will be appreciated that the requesting party itself may be the merchant where the digital incentive may be used. For example, the requesting party may be a particular grocery store and as such the digital incentives may be used only at the particular grocery store.

The one or more scopes may include one or more text fields that are to be used when sending the one or more digital incentives. The one or more text fields may be customized or entered by the requesting party. Additionally or alternatively, within the incentive management application, the server computer system 120 may cause the computing device 110 to display a number of predefined text fields that may be selected by the requesting party. The predefined text fields may include messages relating to sending digital incentives such as for example “You have received an offer of a digital gift card” and the requesting party may select one or more of the predefined text fields that are to be used.

The one or more scopes may additionally define who is to receive the one or more digital incentives. For example, as mentioned previously, the requesting party may upload a list of electronic addresses that are to receive the one or more digital incentives. In one example, the requesting party may upload a first list defining a first segment that is to receive a first digital incentive and may upload a second list defining a second segment that is to receive a second digital incentive.

The one or more scopes may include a request that the server computer system 120 generate recommendations for who should receive the one or more digital incentives. For example, the requesting party may select a selectable interface element requesting that the server computer system 120 generate recommendations for who should receive the one or more digital incentives. Examples of how the server computer system 120 may generate the recommendations will be described in more detail below.

The requesting party may upload a list of electronic addresses that are to receive the one or more digital incentives and may request that the server computer system 120 generate recommendations for who should receive the one or more digital incentives. For example, the requesting party may upload a first list defining a first segment that is to receive a first digital incentive and may request that the server computer system 120 generate recommendations for who should also receive the first digital incentive or may request that the server computer system 120 generate recommendations for who should receive a second digital incentive.

The one or more scopes may additionally include a selection of one or more graphical objects to be used when sending the one or more digital incentives. For example, as mentioned, within the incentive management application, the user may have previously uploaded or submitted one or more graphical objects associated with the requesting party where the one or more graphical objects may include company logos, digital gift card skins, animated objects etc. As when, when defining the one or more scopes, the computing device 110 may display one or more of the graphical objects and the requesting party may select one or more of the graphical objects to be used.

In one or more embodiments, the server computer system 120 may have automatically labelled each uploaded graphical object and as such the server computer system 120 may cause the computing device 110 to display all uploaded graphical objects that have the same label and may request that the requesting party select one of the graphical objects. For example, the requesting party may have uploaded five (5) different digital gift card skins and the server computer system 120 may cause the computing device 110 to display the five (5) different digital gift card skins and may request that the requesting party select one of the digital gift card skins. Of course, in embodiments where the web request includes a request to send two different gift cards, the server computer system 120 may request that the requesting party select two of the digital gift card skins.

In one or more embodiments, the server computer system 120 may have automatically labelled each uploaded graphical object and as such the server computer system 120 may not require selection of the one or more graphical objects by the requesting party. For example, the requesting party may have uploaded a single digital gift card skin and as such the server computer system 120 may not require the requesting party to select the single digital gift card skin.

The one or more scopes may additionally define a digital format for sending the one or more digital incentives. For example, the digital incentives may be sent via email, text message, or may be sent such that they are displayed as a notification and the digital format may correspond to how the digital incentives are to be sent.

Once the user has completed defining the one or more scopes, the requesting party may select a selectable interface element to submit the web request and in response a signal may be sent to the server computer system 120 that includes the web request.

In response to receiving the web request, the method 500 includes automatically retrieving a white label incentive interface based at least on the one or more scopes for the one or more digital incentives (step 520).

The server computer system 120 receives the web request to send one or more digital incentives and based on the one or more scopes for the one or more digital incentives, may automatically retrieve a white label incentive interface. In one or more embodiments, server computer system 120 may store one or more white label incentive interfaces in the database 140. The white label incentive interfaces may have different digital formats based on whether they are being sent via email, text message, or whether they are to be displayed as a notification.

The one or more scopes may include a request to send a digital incentive in the form of a $5 gift card via email and as such the server computer system 120 may retrieve a white label incentive interface associated with sending a single gift card. As another example, the one or more scopes may include a request to send two digital incentives via email where a first digital incentive is in the form of a $5 gift card for Merchant A and a second digital incentive is in the form of a $10 gift card for Merchant B and as such the server computer system 120 may retrieve a white label incentive interface associated with sending two gift cards.

An example white label incentive interface 600 is shown in FIG. 6. The white label incentive interface 600 may be in a digital format to be sent via email. The white label incentive interface 600 may be a white label incentive interface associated with sending a single digital incentive. The white label incentive interface 600 includes a first interface element 605, a second interface element 610, a third interface element 615 and a fourth interface element 620. The various interface elements are fixed in position relative to one another and this may be defined in metadata of the white label incentive interface 600. Each interface element may include a tag such as for example “logo”, “header”, “title”, “message”, “digital incentive”, “selectable element”, etc. and this may be defined in the metadata. The tag may be used to populate each interface element.

Another example white label incentive interface 700 is shown in FIG. 7. The white label incentive interface 700 may be in a digital format to be sent via email. The white label incentive interface 700 may be a white label incentive interface associated with sending two (2) digital incentives. The white label incentive interface 700 includes a first interface element 705, a second interface element 710, a third interface element 715, a fourth interface element 720, a fifth interface element 725 and a sixth interface element 730. The various interface elements are fixed in position relative to one another and this may be defined in metadata of the white label incentive interface 700. Each interface element may include a tag such as for example “logo”, “header”, “title”, “message”, “digital incentive”, “selectable element”, etc. and this may be defined in the metadata. The tag may be used to populate each interface element.

The method 500 includes, using the white label incentive interface, automatically generating a customized incentive interface by populating one or more interface elements of the white label incentive interface according to the one or more scopes, the customized incentive interface including at least one selectable interface element for accepting the one or more digital incentives (step 530).

The server computer system 120 may populate various interface elements of the retrieved white label incentive interface according to the one or more scopes for the one or more digital incentives to automatically generate the customized incentive interface.

As one example, the white label incentive interface 600 may be used by the server computer system 120 to automatically generate a customized incentive interface. For example, the first interface element 605 may be tagged as “logo” and as such the server computer system 120 may obtain, from the one or more scopes, a graphical object that has been selected by the user and is labelled or tagged as a company logo. The server computer system 120 may automatically populate the first interface element 605 using the graphical object.

In one or more embodiments, the server computer system 120 may determine that no graphical object has been uploaded by the requesting party and as such the server computer system 120 may engage an application programming interface (API) to obtain a graphical object associated with the requesting party. For example, the server computer system 120 may send an API request to an API associated with obtaining images that includes identifying information of the requesting party and may receive, from the API associated with obtaining images, a graphical object associated with the requesting party. The server computer system 120 may use the graphical object to populate the first interface element 605, for example.

The server computer system 120 may obtain, from the one or more scopes, one or more text fields that are to be used. For example, the second interface element 610 may be tagged as “header”, “title” or “message” and as such the server computer system 120 may obtain one or more text fields from the one or more scopes and may automatically populate the second interface element 610 using the one or more text fields.

In one or more embodiments, the server computer system 120 may determine that the one or more scopes do not include any text fields and as such the server computer system 120 may select a default text field that is to be used to populate the second interface element 610.

The server computer system 120 may obtain, from the one or more scopes, a graphical object that has been selected by the user and is labelled or tagged as a digital gift card skin. The third interface element 615 may be tagged as “digital incentive” and as such the digital gift card skin may be used to automatically populate the third interface element 615.

It will be appreciated that the digital gift card skin itself may have an interface element that is to be populated and the server computer system 120 may automatically populate the interface element based on the one or more scopes. An example digital gift card skin 800 is shown in FIG. 8. As can be seen, the digital gift card skin 800 includes an interface element 805 that is to be populated by the server computer system 120 to indicate the value of the digital gift card based on the one or more scopes. In one example, the one or more scopes may define the digital gift card as a $5 digital gift card and as such the server computer system 120 may populate the interface element 805 the digital gift card skin 800 with “$5” and as such, a digital gift card may be automatically generated by the server computer system 120 that indicates the value of the gift card based on the one or more scopes.

In one or more embodiments, the server computer system 120 may determine that no graphical object has been uploaded by the requesting party that has be labelled as “digital incentive” and as such the server computer system 120 may engage an application programming interface (API) to obtain a graphical object associated with the requesting party and may automatically generate a digital incentive skin such as a digital gift card skin. For example, the server computer system 120 may obtain a default digital gift card skin and may populate an interface element with the graphical object associated with the requesting party and in this manner the digital gift card skin may be automatically customized for the requesting party.

The fourth interface element 620 may be tagged as “selectable element” and as such the server computer system 120 may populate the fourth interface element 620 to be a selectable interface element that, when selected, accepts the digital incentive.

A customized incentive interface 900 automatically generated by the server computer system 120 using the white label incentive interface 600 is shown in FIG. 9. As can be seen, the customized incentive interface 900 includes a company logo 905, a message 910, a digital gift card 915 (with a populated interface element indicating that the digital gift card is a $5 gift card), and a selectable interface element 920 that, when selected, accepts the digital incentive.

The method 500 includes sending, to electronic addresses of a plurality of computing devices, a signal that includes the customized incentive interface (step 540).

As mentioned, the one or more scopes may define who is to receive the one or more digital incentives (or the customized incentive interface). For example, the requesting party may upload a list of electronic addresses that are to receive the one or more digital incentives. The electronic addresses may include email addresses, telephone numbers, unique identifiers of computing devices, etc. The server computer system 120 may obtain the electronic addresses from the list and may send, to the electronic addresses, a signal that includes the customized incentive interface.

The one or more scopes may include a request that the server computer system 120 generate recommendations for who should receive the one or more digital incentives. The server computer system 120 may obtain data that is not available to the requesting party, such as for example data from the database 140, to generate the recommendations.

Reference is made to FIG. 10, which illustrates, in flowchart form, a method 1000 for generating recommendations for who should receive the one or more digital incentives. The method 1000 may be implemented by a computing device having suitable processor-executable instructions for causing the computing device to carry out the described operations. The method 1000 may be implemented, in whole or in part, by the server computer system 120.

The method 1000 includes obtaining, from a database, account data (step 1010).

The server computer system 120 obtains account data from the database 140. As mentioned, at least some of the data records may be associated with customer bank accounts and/or customer credit card accounts. The data records may also store transaction data associated with transactions made on a credit card. The transaction data may include information related to one or more transactions such as for example a transaction location, a transaction date, a transaction amount, etc. At least some of the data records may include additional account data such as for example the name, age, address of the customer, etc. and the account data may be associated with the customer bank accounts and/or customer credit card accounts. The account data may additionally include information relating to digital incentives previously accepted by a customer. The information may identify the amount of the digital incentive, the type of the digital incentive, and the digital format that was used to send the digital incentive to the customer.

The method 1000 includes engaging a data mining module to analyze the account data to generate at least one recommendation for sending the signal that includes the customized incentive interface (step 1020).

As mentioned, since the amount of data stored by the database 140 may be too large or complex to be dealt with by traditional data-processing application software, the server computer system 120 may engage a data mining module to analyze the account data to generate at least one recommendation for sending a digital incentive.

The data mining module may analyze the account data to identify at least one segment that is likely to accept the one or more digital incentives. In one or more embodiments, a segment may include a particular group of customers who are likely to accept the one or more digital incentives. The group of customers may share at least one common characteristic. Example characteristics may include location such as for example customers located within a same neighbourhood, city, province, state, country, etc. Example characteristics may include transactions made by the customers such as for example customers who have recently completed a transaction at a particular merchant. Example characteristics may include personal finances such as for example customers who have an annual salary above or below a certain threshold. Example characteristics may include customers who have recently accepted a digital incentive or customers who accepted a digital incentive more than a threshold amount of time ago. For example, customers may have accepted a digital incentive over one year ago. Example characteristics may include customers who have downloaded a particular mobile application. Example characteristics may include a particular demographic such as for example customs of a particular age category, gender, marital status, etc.

The recommendation may include a digital format recommendation. For example, the data mining module may identify a particular segment that is likely to accept a digital incentive sent as a notification within a mobile application. As another example, the data mining module may identify a particular segment that is likely to accept a digital incentive sent as an email. For example, a customer who is twenty (20) years old may be more likely to accept a digital incentive sent as a notification and a customer who is seventy (70) years old may be more likely to accept a digital incentive sent as an email.

The recommendation may include a recommendation for a digital incentive type. For example, the data mining module may identify a particular segment that is likely to accept a loyalty point modifier rather than a digital gift card. As another example, the data mining module may identify a particular segment that is likely to accept a digital gift card but only if it is $10 or more.

The recommendation may include a recommendation for where the digital incentive may be used. For example, the recommendation may include a recommendation to send a $5 digital gift card for a discount grocery store and that this digital gift card be sent to a first segment that has an annual salary below a threshold and may include a recommendation to send a $10 digital gift card for a premium grocery store and that this digital gift card be sent to a second segment that has an annual salary above the threshold.

The at least one recommendation may include a first recommendation that identifies a first segment that is likely to accept the one or more digital incentives and a second recommendation that identifies a second segment that is likely to accept the one or more digital incentives. For example, the first segment may include customers who are known to be college students and the second segment may include customers who are known to be retired.

The at least one recommendation may include a first digital incentive that is likely to be accepted by the first segment and a second digital incentive that is likely to be accepted by the second segment. For example, the recommendation may recommend a first digital incentive such as a digital gift card for the college students and the recommendation may recommend a second digital incentive such as a loyalty point multiplier for airline loyalty points for customers who are known to be retired.

The method 1000 includes sending, to the computing device associated with the requesting party, a signal that includes the at least one recommendation and at least one selectable interface element for accepting the at least one recommendation (step 1030).

The server computer system 120 sends a signal to the computing device 110 that includes the at least one recommendation and at least one selectable interface element for accepting the at least one recommendation. The recommendation may include information that identifies, for example, the one or more segments and may include a count of how many customers within the segment are going to receive the one or more digital incentives. It will be appreciated that multiple recommendations may be generated and as such the server computer system 120 may send a signal that includes the multiple recommendations and a selectable interface element for accepting each particular recommendation.

The requesting party may select one or more of the recommendations by, for example, selecting the selectable interface element associated with the recommendation. In response, the server computer system 120 may perform a method to obtain electronic addresses of computing devices associated with the accepted recommendation.

Reference is made to FIG. 11, which illustrates, in flowchart form, a method 1100 for obtaining the electronic addresses of computing devices associated with the accepted recommendation. The method 1100 may be implemented by a computing device having suitable processor-executable instructions for causing the computing device to carry out the described operations. The method 1100 may be implemented, in whole or in part, by the server computer system 120.

The method 1100 includes receiving, from the computing device associated with the requesting party, a signal indicating selection of the at least one selectable interface element for accepting the at least one recommendation (step 1110).

The server computer system 120 receives the signal from the computing device 110 that indicates selection of a particular selectable interface element for accepting a particular recommendation.

The method 1100 includes obtaining, from the database, the electronic addresses of the plurality of computing devices associated with the accepted recommendation (step 1120).

The particular recommendation may identify a segment of customers that are likely to accept the one or more digital incentives. The server computer system 120 obtains, from the database 140, electronic addresses of computing devices associated with the customers within the segment.

The server computer system 120 may then send the one or more digital incentives to the electronic addresses of the computing devices in accordance with step 540 of the method 500.

In one or more embodiments, the recommendation may identify a digital format that is likely to be accepted and as such the server computer system may generate the customized incentive interface in the digital format that is likely to be accepted.

Reference is made to FIG. 12, which illustrates, in flowchart form, a method 1200 for generating a customized incentive interface in a determined digital format. The method 1200 may be implemented by a computing device having suitable processor-executable instructions for causing the computing device to carry out the described operations. The method 1200 may be implemented, in whole or in part, by the server computer system 120.

The method 1200 includes determining one or more digital formats likely to be accepted (step 1210).

In one or more embodiments, the server computer system 120 may engage the data mining module to determine a digital format that is likely to be accepted by a particular segment. For example, a particular segment may include customers that have a particular mobile application installed on their computing device and as such the data mining module may determine that the digital format that is likely to be accepted by the particular segment may be a notification that is to be displayed within the particular mobile application.

In one or more embodiments, the server computer system 120 may engage the data mining module to determine a digital format that is likely to be accepted by each customer within the segment. For example, the data mining module may analyze historical digital incentive data to determine a digital incentive that has been previously accepted by the customer and may identify that digital format of the previously accepted digital incentive as being the digital format likely to be accepted by the customer.

In one or more embodiments, the data mining module may determine that different customers within a particular segment may be more likely to accept a digital incentive if it is sent in a particular digital format. For example, a segment may include customers within a particular city. The data mining module may determine that customers under the age of forty (40) are more likely to accept a digital incentive sent via text message and customers over the age of forty (40) are more likely to accept a digital incentive sent via email.

The server computer system 120 generates the customized incentive interface in the determined digital format(s) (step 1220). The customized incentive interface may be automatically generated by the server computer system 120 in manners similar to that described herein. The server computer system 120 may generate the customized incentive interface in different digital formats and this may be done based on the digital formats identified during step 1210.

Once the customized incentive interface has been sent to the electronic addresses of the plurality computing devices, the server computer system 120 may receive, from a particular computing device, a signal indicating selection of a selectable interface element for accepting a particular digital incentive and in response the server computer system 120 may generate the digital incentive and send the digital incentive to the particular computing device.

Reference is made to FIG. 13, which illustrates, in flowchart form, a method 1300 for sending a particular digital incentive. The method 1300 may be implemented by a computing device having suitable processor-executable instructions for causing the computing device to carry out the described operations. The method 1300 may be implemented, in whole or in part, by the server computer system 120.

The method 1300 includes receiving, from a particular computing device, a signal indicating selection of the at least one selectable interface element for accepting a particular digital incentive (step 1310).

A recipient of the customized incentive interface may select a particular selectable interface element to accept a particular digital incentive and in response the computing device of the recipient may send the signal to the server computer system 120. The signal may identify the particular digital incentive that is being accepted.

The method 1300 includes generating a unique identifier of the particular digital incentive (step 1320).

In response to receiving the signal indicating selection of the at least one selectable interface element for accepting the particular digital incentive, the server computer system 120 generates a unique identifier of the particular digital incentive.

In one or more embodiments, the unique identifier may be generated using a random number generator. For example, the server computer system 120 may send a signal requesting that a random sixteen (16) digit number be generated. The server computer system 120 may receive the random sixteen (16) digit number.

In one or more embodiments, at least a portion of the unique identifier may be fixed. For example, the first four (4) digits of the sixteen (16) digit number may be fixed and this may be used, for example, to identify the requesting party, that is, the sender of the digital incentive. The remaining twelve (12) digits may be generated using a random number generator.

In one or more embodiments, the unique identifier may follow a sequence of identifiers assigned to digital incentives. For example, a unique identifier may end with one or more digits and the one or more digits may be incremented by a set amount, such as for example one (1) digit, each time a new unique number is to be generated. For example, a unique number may end with 0001 and the next unique number may end with 0002.

The method 1300 includes storing the unique identifier of the particular digital incentive in a database in association with an electronic address of the particular computing device (step 1330).

Once the unique identifier of the particular digital incentive has been generated, the server computer system 120 may send a signal to store the unique identifier in the database 140 in association with the electronic address of the particular computing device 110.

The method 1300 includes sending, to the particular computing device, a signal that includes the particular digital incentive including the unique identifier and a machine-readable indicia (step 1340).

The server computer system 120 may automatically generate the digital incentive to include the unique identifier. For example, a digital gift card skin may include an interface element that is to be populated using the unique identifier and the server computer system 120 may populate the interface element to include the unique identifier. The server computer system 120 may also generate a machine-readable indicia that may be used to redeem or otherwise use the digital incentive. The machine-readable indicia may include a barcode or a Quick Response (QR) code, for example.

The signal that includes the particular digital incentive is sent to the particular computing device. In one or more embodiments, the signal may cause the particular computing device to store the particular digital incentive in a digital wallet. The recipient may access the digital incentive within the digital wallet and this may cause, for example, the machine-readable indicia to be displayed on a display screen of the particular computing device. The machine-readable indicia may be scanned by a merchant and in this manner the digital incentive may be redeemed.

As mentioned previously, the server computer system 120 may analyze uploaded graphical objects to label or categorize each uploaded graphical object. Reference is made to FIG. 14, which illustrates, in flowchart form, a method 1400 for automatically determining a label for a graphical object. The method 1400 may be implemented by a computing device having suitable processor-executable instructions for causing the computing device to carry out the described operations. The method 1400 may be implemented, in whole or in part, by the server computer system 120.

The method 1400 includes analyzing a graphical object to identify at least one parameter thereof (step 1410).

In one or more embodiments, the server computer system 120 may analyze the graphical object to determine a size of the graphical object. The size may include the physical size of the image and/or the resolution of the image measured in pixels. For example, the server computer system 120 may determine, based on the size of a graphical object, that the graphical object is likely to be a digital gift card skin.

In one or more embodiments, the server computer system 120 may analyze the file type of the graphical object. For example, the file type of the graphical object may be an Encapsulated PostScript (EPS) file type and as such the server may determine that the graphical object is likely to be a company logo.

The method 1400 includes determining, based on the identified parameter, a label for the graphical object (step 1420).

Responsive to identifying the at least one parameter of the graphical object, the server computer system 120 may assign a label to the graphical object. For example, the server computer system 120 may determine, based on the size of the graphical object, that the graphical object is likely to be a digital gift card skin and as such the server computer system 120 may assign the label “digital gift card skin” to the graphical object.

It will be appreciated that although the server computer system 120 may label or categorize the graphical object, the requesting party may change or update the label of the graphical object and this may be done within the incentive management application.

The incentive management application may allow the requesting party to sell or otherwise offer incentives to one or more third parties and the server computer system 120 may manage and track purchases of the incentives on behalf of the requesting party. In this embodiment, the requesting party may be referred to as a provider of the incentives and the third party may be referred to as a purchaser of the incentives. The purchase of the incentives may be, for example, a bulk order of incentives.

In one or more embodiments, within the incentive management application, a purchaser may create an account and may select one or more incentives for purchase. As mentioned, the purchase may be a bulk order and thus may include a purchase of a large number of incentives. In the event that the purchaser completes a purchase of a bulk order of one or more incentives offered by the provider, the server computer system 120 may manage and track the bulk order on behalf of the provider.

Reference is made to FIG. 15, which illustrates, in flowchart form, a method 1500 for managing a bulk order of incentives. The method 1500 may be implemented by a computing device having suitable processor-executable instructions for causing the computing device to carry out the described operations. The method 1500 may be implemented, in whole or in part, by the server computer system 120.

The method 1500 includes receiving, from a computing device associated with a purchaser of a bulk order of incentives, a signal that includes a request to purchase the bulk order of incentives (step 1510).

As mentioned, within the incentive management application, a purchaser may select one or more incentives for purchase. In this embodiment, the purchase is for a bulk order of incentives and as such the server computer system 120 receives a signal that includes the request to purchase the bulk order of incentives. The signal may include information identifying the provider of the incentives and one or more scopes relating to the incentives being purchased. For example, the one or more scopes may indicate the quantity of incentives being purchased and what incentives are being purchased. In one example, the bulk purchase may be for five hundred (500) digital gift cards that are valued at $5 each.

The method 1500 includes generating a unique identifier for each incentive in the bulk order of incentives (step 1520).

In this embodiment, after the request to purchase the bulk order of incentives is received, the server computer system 120 generates a unique identifier for each incentive.

The method 1500 includes storing, in a database and in association with a provider of the one or more incentives, data associated with the bulk order of incentives (step 1530).

Once the unique identifiers of the incentives being purchased in the bulk order have been generated, the server computer system 120 may send a signal to store data associated with the bulk order of incentives. In this embodiment, the data associated with the bulk order may include the unique numbers of the incentives and information identifying the purchaser of the incentives. The data is stored in the database in association with the provider. The data may also be stored in the database in association with the purchaser.

The server computer system 120 may provide a customized interface to a computing device associated with the provider that may allow the provider to manage and track bulk purchases of incentives provided thereby.

Reference is made to FIG. 16, which illustrates, in flowchart form, a method 1600 for managing and tracking bulk orders of incentives. The method 1600 may be implemented by a computing device having suitable processor-executable instructions for causing the computing device to carry out the described operations. The method 1600 may be implemented, in whole or in part, by the server computer system 120.

The method 1600 includes storing, in a database and in association with a provider of one or more incentives, data associated with at least one bulk order of incentives (step 1610).

The data associated with the at least one bulk order of incentives may be stored in the database in association with the provider of the one or more incentives in manners similar to that described herein, for example in manners described herein with reference to method 1500.

The method 1600 includes authenticating a computing device associated with the provider of the one or more incentives (step 1620).

In one or more embodiments, to access the incentive management application on the computing device 110 associated with the provider of the one or more incentives, the provider may be prompted to enter credentials submitted during the account creation. For example, the provider may be prompted to submit a username and a password associated with their account. In response to receiving the credentials, the server computer system 120 may authenticate the computing device 110 associated with the provider of the one or more incentives and may identify an account associated therewith.

The method 1600 includes obtaining, from the database, at least one graphical object associated with the provider of the one or more incentives (step 1630).

During account creation, the provider may have uploaded or submitted at least one graphical object associated therewith and the server computer system 120 may have stored the at least one graphical object in the database 140. In this embodiment, the server computer system 120 may obtain the at least one graphical object from the database 140.

As mentioned, one or more graphical objects uploaded may be labelled or tagged (either automatically or manually). As such, the server computer system 120 may obtain the at least one graphical object from the database 140 by selecting one or more graphical objects that were labelled or tagged with “logo”.

The method 1600 includes sending, to the computing device associated with the provider of the one or more incentives, a signal causing the computing device to display an interface that includes the at least one graphical object and a summary of the at least one bulk order of incentives (step 1640).

In one or more embodiments, the interface may be a white label incentive interface that includes one or more interface elements and the server computer system 120 may populate the interface elements prior to sending the interface to the computing device 110 associated with the provider of the one or more incentives. For example, an interface element may be tagged as “logo” and as such the server computer system 120 may populate the interface element using the at least one graphical object obtained during step 1630. In this manner, the server computer system 120 may automatically generate a customized interface that includes the at least one graphical object.

One or more interface elements may be populated using the data associated with the at least one bulk order of incentives. For example, the server computer system 120 may obtain identifying information of one or more purchasers and a count of incentives purchased by each purchaser and this may be used to populate an interface element to generate the summary of the at least one bulk order of incentives.

In this manner, the server computer system 120 may populate the interface such that the incentive management application is customized for the provider and this may be done responsive to successful authentication of the provider. It will be appreciated that different providers may also use the incentive management application and that the server computer system 120 may populate the interface for the different providers responsive to successful authentication thereof.

In one or more embodiments, the interface that includes the at least one graphical object and the summary of the at least one bulk order of incentives may include a selectable interface element for viewing additional information of a particular bulk order of incentives.

Reference is made to FIG. 17, which illustrates, in flowchart form, a method 1700 for providing additional information of a particular bulk order of incentives. The method 1700 may be implemented by a computing device having suitable processor-executable instructions for causing the computing device to carry out the described operations. The method 1700 may be implemented, in whole or in part, by the server computer system 120.

The method 1700 includes receiving, from the computing device associated with the provider of the one or more incentives, a signal indicating selection of the selectable interface element for viewing additional information of a particular bulk order of incentives (step 1710).

As mentioned, the interface may include a selectable interface element for viewing additional information of a particular bulk order of incentives. The selectable interface element may be positioned adjacent to the summary of the particular bulk order of incentives. The selectable interface element may be selected using, for example, an input device associated with the computing device 110. In response to selection of the selectable interface element, the computing device 110 may send a signal to the server computer system 120 indicating selection of the selectable interface element. The signal may identify the particular bulk order of incentives.

The method 1700 includes obtaining, from the database, the additional information of the particular bulk order of incentives (step 1720).

Responsive to receiving the signal indicating selection of the selectable interface element for viewing additional information of the particular bulk order of incentives, the server computer system 120 may obtain the additional information of the particular bulk order of incentives from the database 140. The additional information may include, for example, a list of each incentive purchased within the particular bulk order that includes the unique number of each incentive, an amount of each incentive, a type of each incentive, etc.

In one or more embodiments, the purchaser of the particular bulk order of incentives may provide information identifying the recipient of each incentive. For example, the incentive may include physical gift cards and as such the purchaser of the particular bulk order of incentives may provide a mailing address of the recipients of each incentive. As another example, the incentives may include digital incentives and as such the purchaser of the particular bulk order of incentives may provide electronic addresses of the recipients of each incentive. As such, the additional information may include the identifying information of the recipient of each incentive.

In one or more embodiments, the additional information may include a pickup location for the incentives. For example, the incentives may include physical gift cards and as such the purchaser may have indicated a particular location for picking up the physical gift cards. The physical location may include, for example, a particular retail location of the providers of the incentives.

The additional information may include a status of each incentive. For example, the incentives may include digital incentives and each digital incentive may be sent to an electronic address of a particular recipient. The status may indicate whether each recipient has accepted the incentive. For example, the particular recipient may accept the incentive and as such the status of the incentive may be set to “accepted”. As another example, a particular incentive may have been sent to a recipient but may not have been accepted and as such the status of the incentive may be set to “sent”.

The method 1700 includes sending, to the computing device associated with the provider of the one or more incentives, a signal causing the computing device to display an interface that includes the additional information of the particular bulk order of incentives (step 1730).

The server computer system 120 sends, to the computing device 110, a signal that causes the computing device 110 to display the interface that includes the additional information of the particular bulk order of incentives. The interface may be displayed as a new window within the incentive management application. The interface may include interface elements such as for example a scroll bar that may be used to scroll up or down to view the additional information of the particular bulk order of incentives. The interface may additionally include a graphical object associated with the providers of the incentives, similar to that described herein.

As mentioned, within the incentive management application, a purchaser may create an account and may select one or more incentives for purchase. It will be appreciated that in one or more embodiments, it may be required that the identity of the purchaser be verified and this may be done to fulfill, for example, know your customer (KYC) requirements. It will be appreciated that the identity of the purchaser may be verified by, for example, the financial institution associated with the server computer system 120 and may require the purchaser to provide or upload one or more government issued identity documents.

In one or more embodiments, responsive to the purchaser creating an account, the server computer system 120 may engage an application programming interface (API) associated with identity verification and may provide the purchaser the option to complete verification using the API.

In one or more embodiments, verification may include uploading one or more government issued identity documents and capturing a photo of a person registering as the purchaser. For example, once an image of a government issued identity document has been uploaded, the server computer system 120 may request that the computing device 110 open a camera or imaging device associated therewith and may prompt the user of the computing device 110 to capture a “selfie”. The server computer system 120 may receive the image of the government issued identity document and the image of the user of the computing device 110 and may analyze the two images to verify the identity thereof.

The purchaser may create an account and complete purchases prior to being verified; however, the purchase may not be fulfilled until after the identity of the purchaser has been verified. In one or more embodiments, the provider of the incentives may have the option to allow a purchase prior to the identity of the purchaser being verified and may have the option to cancel or put on hold the purchase until the identity of the purchaser has been verified.

In one or more embodiments, the interface provided to the computing device associated with the provider of the one or more incentives, for example during step 1640 of the method 1600, may additionally include a verification status of the purchaser of the at least one bulk order of incentives. For example, the interface may include the graphical object, the summary of the at least one bulk order of incentives, and the verification status of the purchaser of the at least one bulk order of incentives. It will be appreciated that the verification status may be binary in that the verification status may be one of “verified” or “not verified”.

The verification status of a purchaser may change. For example, the identity of a purchaser may be verified and in response the verification status of the purchaser may change from “not verified” to “verified”. For example, a purchaser may complete a bulk order of incentives and after the purchase has been completed, may engage the API associated with verifying their identity. The purchaser may verify their identity using the API and as such the verification status of the purchaser may change from “not verified” to “verified”. In response, the server computer system 120 may update, in real time, the verification status of the purchaser. In this manner, the provider of the incentives purchased by the purchaser may receive notice, in real-time, that the purchaser verification status has changed.

In one or more embodiments, the interface may additionally include a selectable interface element for flagging the purchaser of the at least one bulk order of incentives as suspicious. For example, a purchaser that is “not verified” may be deemed suspicious and the provider of the incentives may wish to flag the purchaser as suspicious and may want to cancel or put on hold the at least one bulk order of incentives.

Reference is made to FIG. 18, which illustrates, in flowchart form, a method 1800 for cancelling or putting on hold at least one bulk order of incentives. The method 1800 may be implemented by a computing device having suitable processor-executable instructions for causing the computing device to carry out the described operations. The method 1800 may be implemented, in whole or in part, by the server computer system 120.

The method 1800 includes receiving, from the computing device associated with the provider of the one or more incentives, a signal indicating selection of the selectable interface element for flagging the purchaser of the at least one bulk order of incentives as suspicious (step 1810).

As mentioned, the interface may include a selectable interface element for flagging the purchaser of the at least one bulk order of incentives as suspicious. The selectable interface element may be selected using, for example, an input device associated with the computing device 110. In response to selection of the selectable interface element, the computing device 110 may send a signal to the server computer system 120 indicating selection of the selectable interface element. The signal may identify the purchaser being flagged.

The method 1800 includes sending a signal updating the interface to identify the purchaser of the at least one bulk order as suspicious (step 1820).

Responsive to receiving the signal indicating selection of the selectable interface element for flagging the purchaser of the at least one bulk order as suspicious, the server computer system 120 may send a signal updating the interface to identify the purchaser of the at least one bulk order as suspicious. For example, the interface may be updated to change the appearance of any orders completed by the purchaser such that they appear in a red font. As another example, the interface may be updated to include a graphical object positioned adjacent to each order completed by the purchaser that identifies the purchaser as being suspicious.

The method 1800 includes cancelling or putting on hold the at least one bulk order of incentives (step 1830).

Once the purchaser has been flagged as suspicious, the server computer system 120 may automatically cancel or put on hold the at least one bulk order of incentives completed by the purchaser.

In one or more embodiments, the server computer system 120 may prompt the provider of the incentives by sending a signal that causes the computing device 110 to display a selectable interface element for cancelling the bulk order and a selectable interface element for putting on hold the bulk order. In this manner, the provider may have the option to cancel or put on hold the bulk order until the identity of the purchaser is verified.

In one or more embodiments, responsive to the purchaser being flagged as being suspicious, the server computer system 120 may identify one or more additional orders completed by the purchaser. The one or more additional orders may be for incentives provided by the provider or may be one or more additional orders for incentives provided by one or more other providers. The server computer system 120 may cancel or put on hold the one or more additional orders completed by the purchaser and may update interfaces provided to the one or more other providers to identify the purchaser as suspicious. In this manner, the server computer system 120 may cancel or put on hold all orders made by the purchaser and this may reduce or eliminate fraud issues for one or more other providers of incentives that have accounts with the incentive management application.

As mentioned, the purchaser of a bulk order of incentives may provide electronic addresses of a plurality of computing devices associated with recipients of the incentives. The server computer system 120 may send the incentives to the recipients using the electronic addresses. The incentives may include, for example, the unique number of the incentive. The incentive may be sent using a customized incentive interface and/or a customized digital gift card skin and this may be done in manners described herein, for example with reference to FIGS. 5 to 9.

In one or more embodiments, a unique code may be required to redeem a particular incentive. For example, a digital incentive such as a digital gift card may be assigned a unique number and a unique code. The unique code may be required to redeem the digital gift card. In one or more embodiments, the unique code may be generated by the server computer system 120 and provided to the recipient of the incentive. For example, a purchaser may complete a bulk order of digital gift cards and may provide electronic addresses of recipients of the digital gift cards. The purchaser may receive the unique number of each digital gift card but may not be provided the unique code of each digital gift card. The server computer system 120 may generate a unique code for each digital gift card and may send the unique code to the electronic address of the recipient of the digital gift card. The unique code may be sent as a separate communication than the incentive. For example, the recipient may receive a first email that includes the incentive and may receive a second email, different than the first email, that includes the unique code. In this manner, the unique number and the unique code are sent separately and the unique code is only sent to the recipient of the incentive. This may reduce the risk of fraud and may reduce the risk of the incentive being used by someone other than the recipient.

The incentive management application described herein may allow the provider and/or the requester to update and maintain information associated therewith. For example, the incentive management application may allow the provider to update one or more physical retail locations associated therewith.

In one or more embodiments, the incentive management application may have different access levels where each access level may be associated with a particular type of account. Reference is made to FIG. 19, which illustrates, in flowchart form, a method 1900 for providing access to an incentive management application. The method 1900 may be implemented by a computing device having suitable processor-executable instructions for causing the computing device to carry out the described operations. The method 1900 may be implemented, in whole or in part, by the server computer system 120.

The method 1900 includes receiving authentication information to access an incentive management application (step 1910).

The authentication information may be received from a computing device such as for example the computing device 110.

In one or more embodiments, the authentication information may include the credentials submitted during account creation. For example, a user may be prompted to submit a user name and a password associated with their account.

The method 1900 includes determining, based on the authentication information, an access level to access the incentive management application (step 1920).

In response to receiving the authentication information, the server computer system 120 may authenticate the computing device and may identify an account associated therewith. In one or more embodiments, the account may be one of an administration account, a provider account or a purchaser account.

The access levels may provide access to various features, graphical user interfaces, etc. within the incentive management application. The access levels may configure or define what software modules, computer server systems, databases, etc. that an authenticated computing device may communicate with within the incentive management application. For example, a first database may store information such as for example account information for all accounts registered to access the incentive management application. As such, only one of the access levels may be permitted access to communicate with the first database.

The access levels may be hierarchical such that a first access level may have a first type of access to the incentive management application, a second access level may have a second type of access to the incentive management application that includes the first type of access and one or more additional types of access. A third access level may have a third type of access to the incentive management application that includes the first type of access, the second type of access and one or more additional types of access.

The access level may be based on the account identified using the authentication information. For example, the access level may be selected from an administration access level, a provider access level, or a purchaser access level.

The administration access level may be assigned to one or more administration accounts and provides full access to the incentive management application. Put another way, responsive to identifying that the authentication information is associated with an administration account, the server computer system 120 may determine that the access level is the administration access level.

The provider access level may be assigned to one or more provider accounts and may provide access to manage and fulfill incentive orders. Put another way, responsive to identifying that the authentication information is associated with a provider account, the server computer system 120 may determine that the access level is the provider access level.

The purchaser access level may be assigned to one or more purchaser accounts and may provide access to place, track and fulfill incentive orders. Put another way, responsive to identifying that the authentication information is associated with a purchaser account, the server computer system 120 may determine that the access level is the purchaser access level.

The method 1900 includes providing the computing device access to the incentive management application at the determined access level (step 1930).

The server computer system 120 provides the computing device access to the incentive management application at the determined access level.

In one or more embodiments, a particular computer server system may be configured to provide a customized incentive interface similar to that described herein. In this example, only a computing device that has been provided an access level that enables features to generate a customized incentive interface may communicate with the particular computer server system. Put another way, enabling features to generate the customized incentive interface may enable communication between a computing device and the server computer system configured to provide the customized incentive interface.

Examples are shown in FIGS. 20 and 21. In the example shown in FIG. 20, a computing device 2010 is provided a first access level that enables communication between a first server computer system 2020 but does not enable communication between a second server computer system 2030. As such, only features provided by the first server computer system 2020 are available or enabled at the first access level.

In the example shown in FIG. 21, a computing device 2110 is provided a second access level that enables communication between the first server computer system 2020 and the second server computer system 2030. As such, features provided by the first server computer system 2020 and the second server computer system 2030 are available or enabled at the second access level.

In one or more embodiments, the server computer system 120 may determine that the access level is the administration access level and as such may perform operations to provide the computing device access to the incentive management application at the administration access level.

In one or more embodiments, providing the computing device access to the incentive management application at the administration access level may include providing, within the incentive management application, one or more graphical user interfaces to manage the one or more provider accounts and the one or more purchaser accounts.

In one or more embodiments, each time a new provider account and/or purchaser account is requested, the provider account and/or the purchaser account may be sent to an administrator to approve or reject the request. In these embodiments, the administration access level may provide a computing device authenticated with an administration account a graphical user interface that may include selectable interface elements to approve or reject the request. In one or more embodiments, approving or rejecting the request may include reviewing the request to ensure sufficient information is provided to comply with KYC requirements. For example, it may be required that the identity of a user of the provider account and/or the purchaser account be verified to fulfill KYC requirements. As such, the user of the provider account and/or the purchaser account may provide or upload one or more government issued identity documents that may be viewed only within the administration access level accessed by an administration account.

The one or more graphical user interfaces may include, for example, one or more selectable interface elements for flagging one or more of the providers accounts and/or one or more of the purchaser accounts as suspicious and in response the server computer system 120 may perform operations to cancel, delete, or investigate the flagged accounts and this may be done in manners similar to that described herein. In one or more embodiments, the one or more selectable interface elements may be for flagging one or more of the provider account and/or one or more of the purchaser accounts as a trusted account that may not require additional review prior to fulfilling incentive orders.

The server computer system 120 may determine that the access level is the provider access level and as such may perform operations to provide the computing device access to the incentive management application at the provider access level.

In one or more embodiments, providing the computing device access to the incentive management application at the provider access level may include providing, within the incentive management application, one or more graphical user interfaces to fulfill incentive orders completed by one or more of the purchaser accounts. The one or more graphical user interfaces to fulfill incentive orders may include one or more selectable interface elements for assigning incentives to fulfill the incentive orders.

In one or more embodiments, the one or more graphical user interfaces to fulfill incentive orders may include a list of all incentive orders or only those incentive orders that have not yet been fulfilled. The incentive orders may only include incentive orders for incentives offered by the provider. The one or more graphical user interfaces may display information associated with each order such as for example an order number, customer name or purchaser name, organization, email address, telephone number, shipping address, etc. The one or more graphical user interfaces may include selectable interface elements to sort and/or filter the orders. The one or more graphical user interfaces may include a selectable interface element to download, email, print, etc. a list that includes one or more of the orders.

In one or more embodiments, the one or more graphical user interfaces to fulfill incentive orders may include a selectable interface element to upload a digital file that includes a list of incentives that are to be provided to the purchaser to fulfill the order.

In one or more embodiments, the one or more graphical user interfaces to fulfill incentive orders may include a selectable interface element to create the incentives to fulfill the order and this may be done in manners similar to that described herein. The selectable interface element may automatically generate or create the incentives in a quantity that is equal to the number of incentives purchased. For example, an incentive order may include an order for twenty (20) digital gift cards of a denomination of $10 each and as such the selectable interface element may automatically generate or create a list of twenty (20) unique identifiers and may further generate or create the digital gift cards according to one or more scopes defined by the provider in manners similar to that described herein.

Each order itself may be selectable to view additional details. For example, the order status may be viewed and this may be done in real-time. Other details may include the time when the order was placed, the amount of the incentives purchased, the quantity of incentives purchased, the unique numbers of the incentives assigned to fulfill the order, etc. The other details may include an input field for entering customer notes and/or comments. The comments may be saved and displayed in a comment thread.

The graphical user interfaces may include a selectable interface element to define or assign one or more particular incentives to a particular incentive order. For example, in one or more embodiments, an incentive order may include a bulk purchase of digital incentives and as such within the incentive management application, the provider access level may include a graphical user interface that includes a list of all unique numbers of digital incentives offered by the provider available for purchase and may include selectable interface elements for assigning each digital incentive, by unique number, to fulfill or complete the order.

In one or more embodiments, providing the computing device access to the incentive management application at the provider access level may include providing, within the incentive management application, one or more interface elements to define one or more scopes to configure incentives to be offered. The one or more interface elements to define one or more scopes to configure incentives to be offered may include one or more interface elements for defining denominations of the incentives.

In one or more embodiments, providing the computing device access to the incentive management application at the provider access level may include providing, within the incentive management application, one or more graphical user interfaces for generating a customized incentive interface as described herein, for example with reference to FIG. 5.

In one or more embodiments, providing the computing device access to the incentive management application at the provider access level may include determining a status of one or more incentive orders, and providing, within the incentive management application, a graphical user interface that includes the status of the one or more incentive orders. The status may include pending, filled, etc. and may be based on whether or not incentives have been assigned to fulfill the order.

In one or more embodiments, providing the computing device access to the incentive management application at the provider access level may include providing one or more graphical user interfaces for submitting tracking data to track a shipment of one or more incentives from an incentive order completed from one or more purchaser accounts. The server computer system 120 may receive, from a provider account, the tracking data.

The server computer system 120 may determine that the access level is the purchaser access level and as such may perform operations to provide the computing device access to the incentive management application at the purchaser access level.

In one or more embodiments, providing the computing device access to the incentive management application at the purchaser access level may include determining one of a parent access level or a child access level, the parent access level providing full access to incentive orders completed by all purchaser accounts associated with an entity and the child access level providing access only to incentive orders completed by one of the purchaser accounts having the child access level. The parent access level may be provided in response to identifying a parent account and the child access level may be provided in response to identifying a child account. The parent and child accounts may be associated with an entity. In these embodiments, a computing device provided with the parent access level may define one or more child accounts. The child accounts may complete purchases within the incentive management application and may review, edit, receive updates, etc. for all purchases completed using the child account. The child account cannot, however, access purchases made by one or more other child accounts of the same entity or purchases made by the parent account of the same entity. The parent account may complete purchases within the incentive management application and may review, edit, receive updates, etc. for all purchases completed using the parent account and for all purchases completed using one or more child accounts of the same entity.

In one or more embodiments, providing the computing device access to the incentive management application at the purchaser level may include providing a graphical user interface that includes tracking data to track a shipment of one or more incentives from an incentive order completed from the purchaser account.

In one or more embodiments, providing the computing device access to the incentive management application at the purchaser level may include providing a graphical user interface for fulfilling incentives from an incentive order completed from the purchaser account, as will be described.

In manners described herein, fulfilling an order of incentives may be performed by the server computer system and this may be triggered by the provider of the incentives and/or the purchaser of the incentives. For example, a purchaser may complete a bulk order of incentives. Within the incentive management application, the provider may request that the server computer system fulfill the bulk order of the incentives by generating a unique number for each incentive in the bulk order of incentives and providing a list of the unique numbers to the purchaser. The purchaser may then request that the server computer system fulfill the bulk order by sending each incentive in the bulk order of incentives to electronic addresses of one or more recipients. In one or more embodiments, rather than the purchaser requesting that the server computer system send each incentive in the bulk order of incentives to electronic addresses of one or more recipients, the purchaser may request that the server computer system send a list of electronic addresses to the provider and the provider may request that the server computer system send each incentive in the bulk order of incentives to the electronic addresses of the one or more recipients.

The server computer system may perform operations to fulfill a bulk order of incentives. Reference is made to FIG. 22, which illustrates, in flowchart form, a method 2200 for fulfilling a bulk order of incentives. The method 2200 may be implemented by a computing device having suitable processor-executable instructions for causing the computing device to carry out the described operations. The method 2200 may be implemented, in whole or in part, by the server computer system 120.

The method 2200 includes obtaining a list of incentives associated with a bulk order of incentives and electronic addresses of recipients of the incentives (step 2210).

In one or more embodiments, obtaining the list of the incentives associated with the bulk order of incentives includes receiving, from a computing device, a digital file that includes the list of the incentives. The computing device may include a computing device associated with a provider of the incentives or may include a computing device associated with a purchaser of the incentives.

In one or more embodiments, the server computer system may maintain a list of incentives offered by the provider. Within the incentive management application, the provider may assign one or more of the incentives to the purchaser to fulfill a bulk order of incentives. The server computer system may update the list of the incentives in the database to indicate which incentives have been assigned to fulfill the bulk order of the incentives and this may include assigning the unique identifier of the bulk order of the incentives.

In one or more embodiments, the list of the incentives associated with the bulk order of incentives may be obtained from a database. The bulk order of incentives may be assigned a unique identifier that may be used to identify or locate the list of the incentives associated with the bulk order of incentives.

In one or more embodiments, the server computer system may obtain the list of the incentives associated with the bulk order of incentives from a database and may present the list of the incentives to the purchaser. For example, the purchaser may log into the incentive management application and a graphical user interface may be displayed that includes a list of all orders completed by the purchaser. The graphical user interface may include selectable interface elements for viewing more information about an associated order. The user may select one of the selectable interface elements and in response the server computer system may retrieve, from the database, a list of all incentives purchased for the order associated with the selectable interface element. The graphical user interface may be updated to display the list of the incentives.

In one or more embodiments, the list of the incentives associated with the bulk order of incentives may include at least one of a unique identifier of each incentive or a denomination of each particular incentive. For example, each incentive may be assigned a unique identifier similar to manners described herein and the list of the incentives may include the unique identifier of each incentive. As another example, each incentive may have a particular denomination such as for example $5, $10, etc. and as such the list of the incentives may include the denomination of each incentive.

In one or more embodiments, obtaining the electronic addresses of recipients of the incentives includes receiving, from a computing device, a digital file that includes a list of the electronic addresses of the recipients. The computing device may include a computing device associated with a provider of the incentives or may include a computing device associated with a purchaser of the incentives.

In one or more embodiments, within the incentive management application, the purchaser may upload the digital file that includes a list of electronic addresses of the recipients. Within the incentive management application, the list may be made available to the provider and the provider may provide the electronic addresses of recipients of the incentives to the server computer system.

In one or more embodiments the electronic addresses of the recipients may be generated by the server computer system. For example, the server computer system may perform operations similar to those described herein with reference to FIGS. 10 and 11 to obtain the electronic addresses of the recipients.

The method 2200 includes assigning one or more of the incentives to one or more of the electronic addresses (step 2220).

Each incentive is assigned to a particular electronic address of a recipient of the incentive. In one or more embodiments, the server computer system may automatically assign the incentives to the electronic addresses. It will be appreciated that the incentives may be assigned to the electronic addresses manually within the incentive management application by the purchaser and/or the provider.

In one or more embodiments, the number of electronic addresses may not be equal to the number of incentives in the bulk order. For example, the bulk order of incentives may be for five hundred (500) incentives however only four hundred and fifty (450) electronic addresses may be obtained. As such, the server computer system may assign electronic addresses to four hundred and fifty (450) incentives and the remaining fifty (50) incentives may remain unassigned or unfulfilled.

As another example, the bulk order of incentives may be for five hundred (500) incentives however one thousand (1000) electronic addresses may be obtained. In this example, the server computer system may generate an error message that may be communicated to a computing device associated with the purchaser and/or the provider of the incentives. The error message may be displayed within the incentive management application and/or as a notification. The error message may additionally or alternatively be sent via email. The error message may indicate the number of electronic addresses that do not have assigned incentives, which in this example may be five hundred (500) electronic addresses. The error message may include a selectable interface element for purchasing the outstanding amount of incentives, which in this example is five hundred (500) incentives. Responsive to selection of the selectable interface element, the server computer system may perform operations to generate the incentives and to assign the electronic addresses to the incentives.

Once an incentive has been assigned, the server computer system may update the status of the incentive to “assigned”. It will be appreciated that unassigned incentives may have the status “unassigned” or “unfulfilled”.

The method 2200 includes sending, to the one or more of the electronic addresses, the incentives (step 2230).

In one or more embodiments, within the incentive management application a selectable interface element may be provided to send the incentives to the electronic addresses. Responsive to selection of the selectable interface element, the server computer system may perform operations to send the incentives to the one or more electronic addresses.

In one or more embodiments, the server computer system 120 may engage an electronic mail server system to send the incentives to the one or more of the electronic addresses. For example, the provider or the purchaser may have an email account hosted by the electronic mail server system and the server computer system may engage the electronic mail server system to send the incentives from the email account. As another example, the server computer system may have an email account hosted by the electronic mail server system and the server computer system may engage the electronic mail server system to send the incentives from the email account.

In one or more embodiments, the server computer system 120 may engage an application programming interface (API) associated with an electronic mail server system and may perform operations to request that the electronic mail server system send the incentives from an email account.

In one or more embodiments, the server computer system may include an electronic mail module and may engage the electronic mail module to send the incentives from an email account.

In one or more embodiments, the electronic account used to send the incentives may be associated with an administrator of the incentive management application and not the purchaser or the provider.

The method 2200 includes monitoring an error log to confirm successful delivery of the incentives (step 2240).

In one or more embodiments, the server computer system may determine, based on the error log, that at least one of the incentives was not successfully delivered. The error log may include an email error log and/or an email inbox. In embodiments where the error log includes the email inbox, the email inbox may be monitored to see if any email bounce backs have been received.

The server computer system may send, to a computing device, an indication that the at least one of the incentives was not successfully delivered. The indication may be an error message that may be communicated to a computing device associated with the purchaser and/or the provider of the incentives. The error message may be displayed within the incentive management application and/or as a notification. The error message may additionally or alternatively be sent via email.

In one or more embodiments, the indication that the at least one of the incentives was not successfully delivered may include a selectable interface element to provide an updated electronic address of the recipient. Responsive to selection of the selectable interface element, the computing device may display an input field for entering the updated electronic address of the recipient. In one or more embodiments, selection of the selectable interface element may cause the computing device to display a list of electronic addresses and this may be based on previous fulfilled orders, for example.

In one or more embodiments, the indication that the at least one of the incentives was not successfully delivered may indicate the electronic address of the recipient that did not successfully receive the incentive. For example, the error may be a result of a typo in the electronic address and as such the indication may display the electronic address that generated the error. The indication may include a selectable interface element to edit the electronic address or to enter a new electronic address.

In one or more embodiments, the server computer system may confirm successful delivery of at least one of the incentives and may update a fulfillment status of the at least one of the incentives to “fulfilled”. In embodiments where the number of incentives in the bulk order is greater than the number of electronic addresses obtained, the status of the incentives that have not yet been sent out (or that have not yet been assigned an electronic address) may remain “assigned” or may remain “unfulfilled” or “unassigned”.

In one or more embodiments, prior to sending the incentives to the one or more of the electronic addresses, the server computer system may generate a customized incentive interface by populating one or more interface elements of a white label incentive interface according to one or more scopes in manners similar to that described herein. Further, the customized incentive interface may include a selectable interface element to accept one of the incentives in manners similar to that described herein. It will be appreciated that in these embodiments sending the incentives may include sending the customized incentive interface generated by the server computer system.

An example of fulfilling a bulk order of incentives will now be described. A purchaser may open the incentive management application on a computing device and may provide authentication information to access the incentive management application. The server computer system may receive the authentication information and may determine an access level to be provided to access the incentive management application. In this example, the authentication information may cause the server computer system to determine that the access level is the purchaser access level and as such the computing device is provided access to the incentive management application at the purchaser access level.

Within the incentive management application, the purchaser may complete a purchase of a bulk order of incentives. The server computer system may perform operations to allow a provider of the purchased bulk order of incentives to fulfill the order by generating a list of incentives that are be provided to the purchaser. The list may identify each incentive using a unique identifier. Once the provider has fulfilled the order, the server computer system may perform operations to provide the order details to the purchaser.

Within the incentive management application, the purchaser may see a list of all purchases completed and this may be based on a determination as to whether the purchaser has a parent level access or a child level access. In any regard, the server computer system may provide a graphical user interface that includes a list of all purchases may by the purchaser.

An example graphical user interface 2300 is shown in FIG. 23. As can be seen, each purchase displayed on the graphical user interface 2300 is identified using a unique identifier. The graphical user interface 2300 includes selectable interface elements 2310 to view more information about a particular order. It will be appreciated that in one or more embodiments the graphical user interface may additionally or alternatively include an input field that may be used to enter an order number.

Responsive to selection of one of the selectable interface elements 2310, the server computer system may provide a graphical user interface that includes a list of all incentives associated with the bulk order of incentives.

An example graphical user interface 2400 is shown in FIG. 24. As can be seen, the graphical user interface 2400 includes a list of incentives associated with the bulk order of incentives. The list of the incentives identifies each incentive by a unique identifier and includes a denomination or amount of the incentive. The list of incentives also includes an input field for entering an electronic address of a recipient of the incentive. The graphical user interface 2400 includes a selectable interface element 2410 to upload recipient information.

The purchaser may select the selectable interface element 2410 and in response a window may be displayed that allows the user to select a digital file that includes electronic addresses of one or more of the recipients. The digital file may be, for example, a Microsoft(TM) Excel(TM) file that includes a list of electronic addresses. Once the digital file has been selected, the server computer system may perform operations to assign the incentives to the electronic addresses. In this example, the bulk order of incentives may include five hundred (500) incentives and the number of electronic addresses in the digital file may also be five hundred (500). As such, the server computer system may assign one incentive to each electronic address. The server computer system may update the list of the incentives to include the electronic addresses.

In one or more embodiments, the selectable interface element 2410 may not be displayed once all of the incentives have an assigned recipient.

The graphical user interface 2400 may additionally include a selectable interface element 2420 for sending the incentives to the recipients. In one or more embodiments, the selectable interface element 2420 may only be displayed when at least one of the incentives has an assigned recipient (or an assigned electronic address). In one or more embodiments, the selectable interface element 2420 may be displayed in a first format such as a greyed out format when none of the incentives have an assigned recipient (or an assigned electronic address) and may be displayed in a second format such as a black and white line format when at least one of the incentives has an assigned recipient (or an assigned electronic address).

Responsive to selection of the selectable interface element 2420, the server computer system may perform operations to send out all incentives that have an assigned recipient (or an assigned electronic address). The server computer system may monitor an error log to ensure successful delivery of the incentives similar to that described herein. The server computer system may update the status of each incentive and/or each bulk order of incentives in manners similar to that described herein.

It will be appreciated that within the incentive management application other features and/or functions may be provided to the purchaser. For example, the purchaser may view purchased incentives. For example, the unique identifier of each incentive displayed on the graphical user interface 2400 may be selectable to view the incentive. In one or more embodiments, viewing the incentive may include viewing a customized incentive interface that is to be sent to the recipient. The customized incentive interface may include one or more input fields that may be used to enter, for example, a personal message to the recipient from the purchaser.

The methods described herein may be modified and/or operations of such methods combined to provide other methods.

Example embodiments of the present application are not limited to any particular operating system, system architecture, mobile device architecture, server architecture, or computer programming language.

It will be understood that the applications, modules, routines, processes, threads, or other software components implementing the described method/process may be realized using standard computer programming techniques and languages. The present application is not limited to particular processors, computer languages, computer programming conventions, data structures, or other such implementation details. Those skilled in the art will recognize that the described processes may be implemented as a part of computer-executable code stored in volatile or nonvolatile memory, as part of an application-specific integrated chip (ASIC), etc.

As noted, certain adaptations and modifications of the described embodiments can be made. Therefore, the herein discussed embodiments are considered to be illustrative and not restrictive.

	Number	Date	Country
Parent	17592572	Feb 2022	US
Child	17952664		US

SYSTEM AND METHOD FOR CONFIRMING ELECTRONIC DELIVERY OF DIGITAL INCENTIVES

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS-REFERENCE TO RELATED APPLICATIONS

Continuation in Parts (1)