JP2023036426A - Method and system for cashback - Google Patents

Abstract

To provide a method and system enabling selecting means for receiving cashback.SOLUTION: A system includes a management server, a first web server, and a second web server. The first web server allows a payee for cashback to be designated from among multiple financial entities. A purchase condition matching module of the management server generates or reads data from receipt information. The purchase condition matching module of the management server determines whether the cashback is applicable or not on the basis of the generated data. The second web server displays, in response to a request from a terminal of a provider of a commodity and/or a service, cashback application information and a result of determining the applicability of the cashback. A remittance execution module of the management server outputs a remittance instruction.SELECTED DRAWING: Figure 1

Description

The present disclosure relates to methods and systems for providing cashback.

In recent years, there are increasing cases of using electronic payment means instead of cash when enjoying services and/or purchasing goods. Electronic payment means are classified in various forms, but typically include credit cards, bar code payments, electronic money, crypto assets, and the like. In these days, when various payment methods are proliferating, it is not uncommon for one individual to use multiple electronic payment methods.

Japanese Patent Laid-Open No. 2004-100001 discloses a configuration capable of performing point-electronic money exchange processing in which points owned by a user are exchanged for electronic money. Patent Document 2 discloses that money is transferred to an electronic money account at the time of cashback.

WO2016/103772 Japanese Patent No. 6710820

As mentioned above, it is not uncommon for a single individual to use multiple electronic payment methods. Under these circumstances, we may offer cash back on purchases of services and/or goods. From the point of view of consumers who receive cash back, there are cases where multiple electronic payment methods are used according to their purpose (for example, for the purpose of managing household finances, events corresponding to income are paid with specific electronic money). centralized management, etc.). Therefore, it may not always be desired to receive cash back with the electronic payment means used at the time of purchase.

Accordingly, an object of the present disclosure is to provide a method and system that allow selection of cashback receiving means.

As a result of intensive studies, the inventor of the present invention came up with a configuration in which a consumer can select a cashback receiving means when applying for cashback by providing receipt information or the like. As a result, the consumer can receive the cashback through a convenient electronic payment method.

The invention has been completed based on the above findings, and the present disclosure includes the following inventions in one aspect.
(Invention 1)
A method for providing cashback to a consumer, comprising:
The system comprises a management server, a first web server, and a second web server,
The management server includes a purchase condition matching module and a remittance execution module,
The method includes:
the first web server receiving cashback application information from a consumer terminal;
a step of the first web server transmitting the cashback application information to the management server;
a step in which the purchase condition matching module of the management server generates or reads text data from the cashback application information;
a step in which the purchase condition matching module of the management server determines whether or not cashback is applicable based on the generated or read text data;
The second web server, in response to a request from a terminal of a product and/or service provider, acquires and displays the cashback application information and the determination result as to whether or not the cashback is applicable from the management server. and
a step of the remittance execution module of the management server outputting a remittance instruction;
including
here,
The first web server provides an interface that allows designation of cashback remittance destinations from a plurality of financial entities,
The first web server provides an interface that enables receipt information to be uploaded from a consumer's terminal,
the remittance execution module outputs a remittance instruction to the specified financial entity;
Method.
(Invention 2)
The method of Invention 1,
a step in which the second web server displays receipt information in addition to the determination result as to whether or not the cashback is applicable;
the second web server providing an interface for setting visual confirmation as to whether the cashback is applicable;
The method further comprising
(Invention 3)
A system for providing cashback to consumers, comprising:
The system comprises a management server, a first web server, and a second web server,
The management server includes a purchase condition matching module and a remittance execution module,
The first web server is configured to receive cashback application information from a consumer's terminal,
The first web server is configured to transmit the cashback application information to the management server,
The purchase condition matching module of the management server is configured to generate or read text data from the cashback application information,
The purchase condition matching module of the management server is configured to determine whether cashback is applicable based on the generated or read text data,
The second web server acquires and displays the cashback application information and the determination result as to whether the cashback is applicable or not in response to a request from a terminal of a product and/or service provider from the management server. is configured to
the remittance execution module of the management server is configured to output a remittance instruction;
here,
The first web server is configured to provide an interface that allows designation of cashback remittance destinations from a plurality of financial entities,
The first web server is configured to provide an interface that allows receipt information to be uploaded from a consumer's terminal;
The purchase condition matching module is configured to generate or read text data from the receipt information,
the remittance execution module is configured to output a remittance instruction to the specified financial entity;
system.
(Invention 4)
The system of Invention 3,
wherein the second web server is configured to display the receipt information in addition to the determination result as to whether the cashback is applicable;
wherein the second web server is configured to provide an interface for setting visual confirmation as to whether the cashback is applicable;
system.

In one aspect of the above invention, the first web server provides an interface that allows designation of a financial entity to be used for cashback from a plurality of financial entities. As a result, the consumer can receive the cashback through a convenient electronic payment method.

In one embodiment, an overview of the URL database is shown. 1 illustrates an overview of a cashback master database, in one embodiment. 1 illustrates an overview of a cashback offer database, in one embodiment. 1 illustrates, in one embodiment, an overview of a financial entity database; 1 illustrates an overview of an interface for uploading receipt information in one embodiment. 1 illustrates an overview of an interface for specifying a remittance destination in one embodiment; 1 illustrates an overview of an interface for specifying a remittance destination in one embodiment; This is displayed when the account transfer is selected (for example, by tapping "bank account") in the interface shown in FIG. 1 illustrates an overview of an interface for specifying a remittance destination in one embodiment; This is displayed when electronic money is selected (for example, by tapping "AX Pay") on the interface shown in FIG. 1 illustrates an overview of an interface for specifying a remittance destination in one embodiment; This is displayed when electronic money is selected (for example, tapping "LL Pay") on the interface shown in FIG. 1 illustrates an overview of an interface for specifying a remittance destination in one embodiment; This is displayed when receiving from an ATM is selected (for example, tapping "ABC Bank ATM Receipt") on the interface shown in FIG. FIG. 11B shows an overview of an interface for confirming order information, in one embodiment. FIG. Application information is displayed in a list format, and it is implemented so that an operation (remittance execution button) for executing remittance can be performed according to the remittance status. FIG. 11B shows an overview of an interface for confirming order information, in one embodiment. FIG. Detailed information is displayed from the list format in FIG. The items to be displayed may include receipt image information. A visual determination result item may be provided so that the visual determination result can be recorded.

Specific embodiments for carrying out the invention will be described below. The following description is intended to facilitate understanding of the invention. it is not intended to limit the scope of the invention.

1. System Overview In one embodiment, the present disclosure relates to a system for providing cash back to consumers. The system includes at least a management server, a first web server, and a second web server. These components are networked together. The type of network is not particularly limited, and may be the Internet, WAN, or LAN, regardless of whether it is wired or wireless, and any known network may be employed.

Note that the server described in this specification is not limited to one physical information processing device. For example, load distribution means may be used to make a plurality of information processing apparatuses perform the same functions and roles, so that it appears as if one server is operating from the outside. Alternatively, if one server has a plurality of different functions and roles, it may be distributed to a plurality of physical information processing devices for each function and role. On the other hand, servers with different functions and roles may be integrated into one physical information processing device.

As described above, the system of the present disclosure in one embodiment includes at least a management server, a first web server, and a second web server. However, this is not limited to configurations in which there are three servers, one for each. For example, the first web server may be distributed over multiple physical information processing devices. In another example, the first web server and the second web server may be aggregated into one physically identical information processing device. Further, when the management server has a plurality of modules, it may be distributed to a plurality of physical information processing devices corresponding to each module.

An information processing device as a server can employ a device known in the art. Typically, it may include at least a processor, memory, communication function, storage medium, and the like. A desired program is installed in the information processing apparatus, and the processor executes the program to implement modules that perform various functions.

Hereinafter, the role and configuration of each of the management server, first web server, and second web server will be described in detail.

2. First Web Server The first Web server is a server for providing a website when accessed by a terminal owned by a consumer (for example, a smart phone). As a specific example, the first web server can provide a web site that serves as an interface for accepting cashback applications from consumer terminals.

To implement these functions, the first web server has an interface generation module, a reception module, and a transmission module.

The interface generation module can have a function of dynamically generating a web page serving as an interface for accepting cashback applications. In addition, the interface generation module can acquire necessary information as appropriate from a database or the like, which will be described later.

The receiving module and the transmitting module have functions for transmitting and receiving necessary information. For example, the interface generation module acquires information necessary for generating a web page (for example, from a management server, etc.), receives various requests, inputs, etc. from the consumer's terminal, and conversely, It plays a role of transmitting information necessary for presentation to the terminal (for example, to a management server, etc.).

3. Second Web Server The second Web server is a server for providing a website when accessed by a terminal owned by a product and/or service provider (e.g., smart phone, tablet terminal, personal computer, etc.). . As a specific example, the second web server can provide web pages for setting cashback conditions, checking application status, checking remittance status, and the like.

To implement these functions, the second web server has an interface generation module, a reception module, and a transmission module.

The interface generation module can have a function of dynamically generating a web page that serves as an interface for setting cashback conditions, checking application status, executing remittance, checking remittance status, and the like. Also, the interface generation module can acquire necessary information from a management server (for example, a database described later) or the like. The functions of the receiving module and the transmitting module may be similar to the receiving module and transmitting module of the first web server described above.

4. Management Server The management server can provide necessary information to the first web server and the second web server. Also, the management server can process requests received via the first web server and the second web server.

For the purpose of realizing these functions, the management server has a purchase condition matching module and a remittance execution module.

Preferably, the management server may further include a receiving module, a transmitting module, a database, and a cashback application receiving module.

4-1. Purchasing Condition Matching Module The purchasing condition matching module has two functions. The first is a function of extracting receipt information that serves as proof of purchase or the like. The second function is to determine whether or not the content of the cashback application information satisfies the cashback application conditions. Corresponding to these, the purchase condition matching module may include, as sub-modules, a receipt information collection sub-module and a matching sub-module.

4-1-1. Receipt Information Gathering Sub-Module The receipt information gathering sub-module is configured to extract receipt information. As one example, the receipt information extraction sub-module is configured to generate or read text data from the recorded cashback application information. Typically, the condition for the cashback to be applied includes the purchase of certain goods and/or services. Therefore, when applying for cashback, proof of purchase (for example, a receipt) is required. Therefore, receipt information that serves as proof of purchase (e.g., image file of receipt, electronic receipt file (e.g., PDF format, etc.), identification information for specifying purchase (e.g., transaction number, contract code, etc.), etc.) must be received. After receiving the cashback application information, text data is generated from the cashback application information in order to perform various processes. Along with this, information such as characters contained in the image file of the receipt is also converted into text. Alternatively, if the cashback application information is data in a format that does not require processing such as OCR (for example, an electronic receipt), text data may be read from the cashback application information.

It should be noted that the "receipt information collection submodule" described in this specification does not have the text conversion function itself, but may only have the interface function with an external text conversion tool. For example, if the OCR analysis API submodule is further provided and text data is generated from the above-described receipt image, etc., the image is uploaded to an external text conversion tool, and the text conversion result and may be configured to receive data such as Therefore, the case of "generating text data from cashback application information" also includes the case of generating text data using an external text conversion tool.

The external text conversion tool is not particularly limited, and may be anything as long as it has an OCR function. External textualization tools may exist external to the system of the present disclosure in one embodiment, ie, may be provided via a network by a third party. When using a tool provided by such a third party, the receipt information collection module can have an API for using the tool. Tools provided by third parties are not particularly limited, but examples thereof include Clova OCR, Azure Computer Vision OCR, and Cloud Vision API.

In another example, the receipt information extraction sub-module may extract information specifying a purchase included in the recorded cashback application information and refer to an external database to obtain purchase information. For example, in the cashback application information, only a code that identifies the purchase is entered (for example, a transaction number), and the receipt information extraction submodule queries the seller's database etc. based on the code ( For example, a query may be issued) to acquire detailed purchase information. In this case, the convenience of inputting receipt information is reduced for the consumer, which is a great advantage.

In either example, the purchase condition matching module can generate text data by using the receipt information extraction sub-module. This text data is used in the purchase decision to be described below.

4-1-2. Purchasing Condition Matching Submodule The purchase condition matching submodule can determine whether or not the content of the cashback application information satisfies the cashback application conditions. In that case, the above-described text data, read data, or the like can be used.

The conditions used for determination are not particularly limited, and can be appropriately set by the product/service provider. Examples of conditions include, for example, one or more items selected from the following: purchase chain, purchase store, purchase date and time, purchase product and/or service, purchase amount, consumer profile (age, gender, occupation , family structure, etc.).

For example, if the purchase is made during the campaign period, the start date and end date of the campaign period are stored as the determination conditions. Then, the purchase date is obtained from the text data. By determining whether or not the purchase date is between the start date and the end date, it is possible to determine whether or not the conditions for cashback are satisfied.

The purchasing condition matching module can record the judgment result. For example, it is possible to record the determination result (for example, the determination result as to whether or not the condition regarding the applicability of cashback is satisfied) in the database that records the cashback application information.

4-2. Remittance Execution Module The remittance execution module is configured to output remittance instructions. The output instruction may be based on a request from the second web server, for example. For example, in an interface provided by the second web server, a remittance instruction request may be generated in response to an operation from the terminal of the product and/or service provider. The generated request may then be sent from the second web server to the management server. Further, the remittance execution module may output remittance instructions based on this.

The specific contents of the remittance instruction are not particularly limited, but include, for example, the following items. Information that identifies the remittance destination, remittance date, remittance amount, etc. Examples of information specifying a remittance destination may be account information (eg, head office code, branch code, deposit type, account number, etc.) in the case of a financial institution such as a bank. Also, in the case of an electronic money settlement institution, account identification information (for example, account ID, bar code, etc.) may be used.

4-3. Other modules and/or the management server such as a database may further include another module in addition to the above. For example, the management server may include a cashback application acceptance module, a reception module, a transmission module, a database, and the like. The cashback application reception module is configured to record cashback application information received via the first web server. Preferably, the cashback application information may be recorded in a database or the like. The receiving module and the transmitting module can communicate with various components (eg, first web server, second web server, etc.) other than the management server. In addition, the management server can be provided with various databases depending on the purpose and function, although not limited thereto.

The format of the database is not particularly limited, and methods known in the art (NoSQL, relational, etc.) can be adopted.

For example, the management server may comprise one or more of the following databases.
URL database,
cashback master database,
cashback application database,
financial entity database

A URL database may be used to store URL information, for example, if a different URL is used for each cashback campaign. An example is shown in FIG. For example, URLs used by consumers (corresponding to the site provided by the first web server) and URLs used by product/service providers (corresponding to the site provided by the second web server) are different. may be included. As for the URL used by the consumer, since there is a high probability that the interface will be different for each cashback campaign, a different URL may be used for each campaign. On the other hand, the URL used by the product/service provider may be different for each cashback campaign. However, for this, the range of customization is not as large as the URL used by the consumer side, so it may be a common URL (and the display content may be changed according to the authentication information when logging in). .

A cashback master database may be used to store master information regarding cashback campaigns. For example, as shown in FIG. 2, information such as cashback campaign identification information, accounts and passwords for managing cashback campaigns, campaign names, criteria for applying cashback, and available financial entities are stored. may be used to For some items, any technique in the art may be used to accommodate various conditions and formats. For example, a column may be provided for each determination item, such as the criteria for applying cashback, but a format such as JSON may be used so that unique items can be flexibly set for each campaign.

A cashback offer database may be used to store information about cashback offers from consumers. For example, as shown in FIG. 3, the cashback application information includes campaign identification information, information specifying the application (e.g., application number), receipt information (e.g., image data of receipt, receipt information in text format, etc.). ), remittance recipient identification information, applicant's basic information, questionnaire information, remittance amount, judgment result of cashback application, visual judgment result, remittance processing status (whether or not remittance processing is executed and its result), etc. Information may be included.

A financial entity database may be used to manage master information about financial entities (eg, banks, cashless payment institutions, etc.). For example, as shown in FIG. 4, the financial entity database includes financial entity identification information, name, type (for example, a code for distinguishing bank, credit card, crypto asset, electronic money, etc.), required input items, their properties (for example, information on the number of digits, restrictions on numbers, characters and symbols that can be entered, etc.), an authentication code for a cooperating institution, and the like. It should be noted that electronic money is a technical means that allows settlement without the use of cash, and indicates that data is managed in units of currencies circulating in a specific country. In addition, electronic money may be of a prepaid type (that is, it is necessary to charge a certain amount in advance), or an instant payment type (that is, it is debited from a bank account at the time of purchase of a product, etc.). or a deferred payment system (withdrawn from a bank account after a certain period of time has passed since the purchase of the product). Also, the electronic money may be of a contactless type, a code (for example, QR code (registered trademark), etc.) reading type, or an online remittance method through an application.

Hereinafter, a specific example of a method for providing cashback to consumers using the system configured as described above will be described in detail.

5. Cash Back Method In one embodiment, the present disclosure relates to a method for providing cash back to consumers. The method includes at least the following steps.
A step in which the first web server receives the cashback application information from the consumer's terminal A step in which the first web server transmits the cashback application information to the management server A purchase condition matching module of the management server A step of generating or reading text data from the cashback application information A step of determining whether or not cashback is applicable based on the text data generated or read by the purchase condition matching module of the management server A second Web A step in which the server responds to a request from the terminal of the product and/or service provider and displays the cashback application information and the judgment result as to whether or not the cashback is applicable. The remittance execution module of the management server outputs the remittance instruction. steps to

The above steps and the like will be described in detail below.

5-1. Receipt and transmission of cashback application information A consumer accesses a website using an information processing terminal (for example, a smart phone, etc.). Applications for accessing the website are not particularly limited. For example, it may be browser software or an SNS application (more precisely, a browser function incorporated in the application).

Also, when accessing a website, for example, a receipt or a two-dimensional barcode displayed on a bulletin board in an actual store may be used for access. Alternatively, access may be made via advertisements with links displayed on SNS or other applications with advertisements. Furthermore, you may access via a link embedded in a push notification or the like.

In response to the access, the first web server can provide the consumer's terminal with an interface screen for making a cashback application.

The interface is configured to allow various types of information to be input, and may be configured to allow at least the following information to be input.
・Enter receipt information ・Enter cashback destination information

Receipt information can be input by, for example, taking a picture of a paper receipt using a camera function installed in a consumer's information processing terminal and uploading the data after the picture is taken, as shown in FIG. good. In addition, if a paper receipt is too long to be photographed in one sheet, the interface may be configured so that multiple sheets can be uploaded. In that case, the first Web server or management server may be provided with an image processing module so that the information of one receipt can be reconstructed.

As an example where paper receipts are not used, for example, in online shopping, there are cases where receipts are downloaded in the form of electronic files (for example, PDF) as needed. In that case, the receipt in the form of an electronic file may be uploaded. Another example of not using a paper receipt is an interface that allows you to enter a code that identifies your purchase. In this case, an inquiry may be made on the management server side based on the entered code, and a process of separately acquiring detailed purchase information may be executed.

As for the input of cashback destination information, for example, as shown in FIG. 6, first, the first web server may provide an interface screen that enables selection of a financial entity.

After selecting a financial entity (for example, after selecting one of the multiple radio buttons shown in FIG. 6), the items required for input are switched and displayed according to the characteristics of the selected financial entity. Alternatively, the interface screen may be provided by the first web server.

For example, when a financial institution such as a bank is selected as a financial entity, as shown in FIG. 7, the head office name (or financial institution code), branch name (or branch code), deposit type (or deposit type code) , account number, account holder, etc. may be displayed on the interface screen. On the other hand, when electronic money is selected, input items such as the account may be displayed on the interface screen. For example, as shown in FIG. 8, input items for the management number corresponding to the type of electronic money selected may be displayed. Alternatively, as shown in FIG. 9, the management number corresponding to the type of electronic money selected and at least part of the input items of the telephone number associated with the management number may be displayed. In this manner, even with the same electronic money, the input items may be switched according to the selected content. Alternatively, as shown in FIG. 10, when a financial entity linked to an ATM is selected, input items such as the customer number, recipient name, and recipient's kana may be displayed.

Such switching of input items is performed, for example, by managing input items corresponding to each financial entity in the above-described financial entity database, and obtaining information from the database by the first web server, Then, the interface generation module may generate the display items. Alternatively, if different URLs are managed for each campaign, customization may be performed for each individual URL.

The first web server may provide, for example, an interface for inputting basic information of the applicant, in addition to inputting receipt information and cashback destination information. The basic information may include, for example, name, furigana, gender, age, occupation, e-mail address, zip code, address, contact phone number, check of agreement on terms, and the like. In addition to the basic information, for example, input items such as questionnaire information, a final confirmation screen of input contents, and the like may be displayed. At the information processing terminal of the consumer, for example, the operation indicating the application is executed through the final confirmation screen or the like.

In this way, the first web server can receive cashback application information from the consumer's terminal. After receiving, the first web server can transmit the cashback application information to the management server.

5-2. Processing by the management server (recording cashback applications from consumers)
The management server can perform various processes on the cashback application information sent from the first web server. Correspondingly, the management server may comprise the various modules described above or other modules.

First, the cashback application reception module of the management server records the cashback application information. The recording location is not particularly limited, and may be a local storage medium or a cloud storage.

The recording format is not particularly limited, but it is typically preferable to store in a format compatible with a database (for example, a cashback application database, etc.). For example, if it is a relational database, it is preferable to use a table format.

5-3. Processing by the management server (processing of cashback application records)
After recording the cashback application information, the purchase condition matching module of the management server can generate or read text data from the cashback application information. Preferably, the text data can be generated from the receipt information included in the cashback application information. In another preferred example, the text data can be generated based on the code specifying the purchase content included in the cashback application information.

The mechanism for generating or reading the text data is not particularly limited, and can be appropriately set according to the format of the receipt information. For example, if the receipt information is a PDF file in text format, the text data embedded in the file may be extracted.

If the receipt information is image data (for example, an image-format PDF file, a photograph of the receipt (for example, JPEG, Gif, PNG data, etc.)), text data may be generated from the image data. For example, text data may be generated by using a tool such as OCR.

Also, the OCR tool need not be implemented within the system of the present disclosure, and may use an external service using an API or the like.

After creating the text data, the purchase condition matching module (or the receipt information collection sub-module) can store the data in a database (for example, receipt information analysis results of a cashback application database, etc.).

5-4. Processing by the management server (judging whether cashback is applicable)
After creating or reading the text data, the purchase condition matching module (eg, matching sub-module) can make determinations. Specifically, it is possible to determine whether or not the content of the text data is a purchase that satisfies the conditions for applying the cashback campaign.

In performing the above determination, the information of the determination conditions may be acquired from another source. For example, the purchasing condition matching module may acquire the criteria from the cashback master database. Then, based on the acquired information, it may be determined whether or not the information included in the text data is a purchase that satisfies the conditions for applying the cashback campaign.

The purchase condition matching module (eg, matching sub-module) can then store the determination results in a database (eg, cashback application database).

6. Judgment result display by the second web server
The product and/or service provider accesses the second web server from the information processing terminal and confirms the application status of the cashback campaign described above. Specifically, after appropriately performing authentication (login authentication processing, etc.), the second web server responds to a request from the information processing terminal by the product and/or service provider, and/or , application details for past cashback campaigns can be displayed in a list format. For example, as shown in FIG. 11, the application contents can be displayed in a list format. Then, the details of each application can be displayed in the format shown in FIG.

Items to be displayed are not particularly limited, but applicant's name, receipt information (for example, textual information or image information before textualization), cashback applicability determination result by purchase condition matching module, One or more of the result of visual confirmation, remittance amount, presence/absence of remittance processing, remittance processing result, and the like can be mentioned. It is not necessary to display all of these pieces of information on one screen. Then, other items may be displayed in response to the operation of displaying the detailed information.

The product and/or service provider can confirm the applicability determination result of the cashback by the purchase condition matching module for each application while browsing the application content list. For example, after selecting information in a specific row from the list format shown in FIG. 11, an operation for displaying detailed information may be performed. Thereby, for example, a detailed information screen as shown in FIG. 12 may be displayed. Also, the receipt information may be separately visually confirmed to confirm whether the determination result of the purchase condition matching module is correct. The result of visual confirmation can be recorded on the screen (for example, in FIG. 12, the item "visual judgment result" is used). For this purpose, the second web server can provide an interface for inputting visual confirmation results in the list of application details.

Also, in another embodiment, for example, visual confirmation work may be omitted, and in that case, items of visual confirmation results can be omitted from the display items.

7. The remittance execution product and/or service provider can request a remittance instruction by appropriately selecting and designating a specific application while viewing the list of application details through operation of the terminal. For example, as shown in FIG. 11, a remittance execution button can be provided to execute remittance.

The request is transmitted from the terminal to the second web server, and further transmitted from the second web server to the management server. The remittance execution module of the management server can issue remittance instructions based on the request.

The remittance instruction of the remittance execution module is transmitted through the network to the specified financial entity destination included in the cashback application information.

Specific destinations to be sent may be obtained, for example, using a financial entity database, or alternatively, APIs provided by each financial entity may be used (in that case, A call API or the like may be managed by a database).

After that, it is appropriately processed by the destination server or the like, and is cashed back to the consumer. It should be noted that if the cashback process is unsuccessful, an error notification is sent from the financial entity's server and received by the remittance execution module. Then, as a result of the remittance process, a record indicating that the remittance failed is made in a database (for example, a cashback application database). Conversely, when the remittance is completed, a notification of remittance completion is sent from the server on the financial entity side and recorded in the database.

8. Master Generation It is preferable to prepare some master data as a pre-stage before implementing the above series of steps. Creation of such master data can be appropriately executed on the master screen.

Master data related to cashback includes the following data.
・Identification information of the cashback campaign ・URL of the application acceptance site for the cashback campaign (URL of the site provided by the first web server)
・URL of the cashback campaign management site (URL of the site provided by the second web server)

In addition to the above, the following data are also included.
・Product and/or service provider account ・Authentication password ・Campaign name ・Cashback application conditions ・Corresponding financial entity

Preferably, master data related to financial entities is also pre-created. For example, it is preferable to be configured to store at least the following items of data.
・Financial entity identification information ・Financial entity name ・Type ・Item 1
・Item 1 property ・Item 2
・Item 2 property...
・Item N
・Item N property ・Authentication code (information necessary to connect to a settlement institution for remittance processing, etc.)

Specific embodiments of the invention have been described above. The above embodiments are only specific examples, and the present invention is not limited to the above embodiments. For example, technical features disclosed in one of the above embodiments may be applied to other embodiments. Also, unless otherwise stated, for a particular method, some steps may be interchanged with other steps, and additional steps may be added between two particular steps. The scope of the invention is defined by the claims.

Claims (4)

A method for providing cashback to a consumer, comprising:
The system comprises a management server, a first web server, and a second web server,
The management server includes a purchase condition matching module and a remittance execution module,
The method includes:
the first web server receiving cashback application information from a consumer terminal;
a step of the first web server transmitting the cashback application information to the management server;
a step in which the purchase condition matching module of the management server generates or reads text data from the cashback application information;
a step in which the purchase condition matching module of the management server determines whether or not cashback is applicable based on the generated or read text data;
The second web server, in response to a request from a terminal of a product and/or service provider, acquires and displays the cashback application information and the determination result as to whether or not the cashback is applicable from the management server. and
a step of the remittance execution module of the management server outputting a remittance instruction;
including
here,
The first web server provides an interface that allows designation of cashback remittance destinations from a plurality of financial entities,
The first web server provides an interface that enables receipt information to be uploaded from a consumer's terminal,
the remittance execution module outputs a remittance instruction to the designated financial entity;
Method. The method of claim 1, wherein
a step in which the second web server displays receipt information in addition to the determination result as to whether or not the cashback is applicable;
the second web server providing an interface for setting visual confirmation as to whether the cashback is applicable;
The method further comprising A system for providing cashback to consumers, comprising:
The system comprises a management server, a first web server, and a second web server,
The management server includes a purchase condition matching module and a remittance execution module,
The first web server is configured to receive cashback application information from a consumer's terminal,
The first web server is configured to transmit the cashback application information to the management server,
The purchase condition matching module of the management server is configured to generate or read text data from the cashback application information,
The purchase condition matching module of the management server is configured to determine whether cashback is applicable based on the generated or read text data,
The second web server acquires and displays the cashback application information and the determination result as to whether the cashback is applicable or not in response to a request from a terminal of a product and/or service provider from the management server. is configured to
the remittance execution module of the management server is configured to output a remittance instruction;
here,
The first web server is configured to provide an interface that allows designation of cashback remittance destinations from a plurality of financial entities,
The first web server is configured to provide an interface that allows receipt information to be uploaded from a consumer's terminal;
The purchase condition matching module is configured to generate or read text data from the receipt information,
the remittance execution module is configured to output a remittance instruction to the specified financial entity;
system. The system of claim 3, wherein
wherein the second web server is configured to display the receipt information in addition to the determination result as to whether the cashback is applicable;
wherein the second web server is configured to provide an interface for setting visual confirmation as to whether the cashback is applicable;
system.

Images