System for marketing linkage service based on payment message
The payment message-based marketing linkage system addresses the underutilization of payment messages by enabling marketing through contractual agreements, enhancing user engagement and revenue generation.
Patent Information
- Application Number
- KR1020240045401
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-04-03
- Publication Date
- 2026-11-11
- Estimated Expiration
- 2044-04-03
AI Technical Summary
Financial institutions and credit card companies are unable to utilize the vast number of payment text messages sent daily for marketing purposes, despite increasing card usage and user engagement with these services.
A payment message-based marketing linkage system that includes a payment approval server and a message sending server, where the latter can utilize payment information for marketing purposes based on contractual agreements, and sends payment messages with embedded links to induce additional purchases or promotions.
Payment messages are effectively utilized for marketing, increasing user engagement and generating new revenue by providing direct access to additional order or gifting options, thereby enhancing user satisfaction.
Smart Images

Figure 112024037208189-PAT00001_ABST
Abstract
Description
Technology Field
[0001] The present disclosure relates to a payment message-based marketing linkage system. Background Technology
[0002] Financial institutions or credit card companies provide a service that sends payment text messages so that users can check their payment history.
[0003] Currently, as card usage increases due to rising consumption across various sectors, and with the growing number of users utilizing payment text messaging services, the volume of payment text messages sent by financial institutions or card companies is also increasing.
[0004] However, the reality is that financial institutions or credit card companies are unable to utilize the thousands or tens of thousands of payment text messages sent daily for marketing purposes. Prior art literature
[0005] Korean Patent Publication No. 10-0980641 (September 1, 2010) The problem to be solved
[0006] The embodiments disclosed in this disclosure are intended to provide a payment message-based marketing linkage system.
[0007] The problems that this disclosure aims to solve are not limited to those mentioned above, and other unmentioned problems will be clearly understood by a person skilled in the art from the description below. means of solving the problem
[0008] A payment message-based marketing linkage system according to one aspect of the present disclosure for achieving the aforementioned technical problem comprises a payment approval server that receives a payment approval request for a product from a payment server and performs approval for the requested payment, and a message sending server that receives a request to send a payment message for the approved payment from the payment approval server and sends the payment message to a terminal of a user who purchased the product, wherein the message sending server may send the payment message in a different manner depending on whether a contract is concluded with the payment approval server.
[0009] In addition, the above contract grants the message sending server the authority to utilize payment information regarding the above product for marketing purposes, and the payment information may include merchant information, customer information, and product information.
[0010] In addition, if the above contract is not concluded, the payment approval server may send linkage information regarding at least one of the merchant and the product together when requesting the sending of the payment message to the message sending server.
[0011] In addition, when the above contract is concluded, the message sending server checks whether the above merchant is affiliated based on the above payment information, and if the above merchant is affiliated, it can extract linkage information for at least one of the above merchant and the above product.
[0012] In addition, the above linkage information may include at least one of a link for placing an additional order for the above product, a link for gifting the above product, a link for making a reservation for the above franchise store, and a link for checking an event being conducted by the above franchise store.
[0013] In addition, the message sending server may include a button for accessing the linked information in the payment message and send it to the user terminal.
[0014] In addition, a payment message-based marketing linkage system according to another aspect of the present disclosure for achieving the aforementioned technical objectives comprises: a payment approval server that receives a payment approval request for a product from a payment server and performs approval for the requested payment; a message sending request agency server that receives approval information for the approved payment from the payment approval server; and a message sending server that receives a request to send a payment message for the approved payment from the message sending request agency server and sends the payment message to a terminal of a user who purchased the product, wherein the message sending server may send the payment message in a different manner depending on whether a contract is concluded with the payment approval server.
[0015] In addition, the above contract grants the message sending server the authority to utilize payment information regarding the above product for marketing purposes, and the payment information may include merchant information, customer information, and product information.
[0016] In addition, if the above contract is not concluded, when the message sending request agency server requests the sending of the payment message to the message sending server, it may also send linkage information regarding at least one of the merchant and the product received from the payment approval server.
[0017] In addition, when the above contract is concluded, the message sending server checks whether the above merchant is affiliated based on the above payment information, and if the above merchant is affiliated, it can extract linkage information for at least one of the above merchant and the above product.
[0018] In addition, a computer program stored on a computer-readable recording medium for executing a method for implementing the present disclosure may be further provided.
[0019] In addition, a computer-readable recording medium for recording a computer program for executing a method for implementing the present disclosure may be further provided. Effects of the invention
[0020] According to the aforementioned means for solving the problem of the present disclosure, payment messages sent to users can be utilized for marketing to induce additional consumption, thereby generating new revenue.
[0021] In addition, by providing options such as placing additional orders or gifting the same product along with the payment message, users can access these options directly through the message without having to search for them separately, thereby increasing user satisfaction.
[0022] The effects of the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by a person skilled in the art from the description below. Brief explanation of the drawing
[0023] FIG. 1 is a drawing for explaining a payment message-based marketing linkage system according to one embodiment of the present disclosure. FIG. 2 is a diagram illustrating a process for sending a payment message when an agreement is not concluded between a payment approval server and a message sending server according to one embodiment of the present disclosure. FIG. 3 is a diagram illustrating a payment message sending process when an agreement is concluded between a payment approval server and a message sending server according to one embodiment of the present disclosure. FIGS. 4a and FIGS. 4b are drawings for illustrating a payment message according to one embodiment of the present disclosure. FIG. 5 is a drawing for explaining a payment message-based marketing linkage system according to another embodiment of the present disclosure. Specific details for implementing the invention
[0024] Throughout this disclosure, the same reference numerals denote the same components. This disclosure does not describe all elements of the embodiments, and general content in the art to which this disclosure pertains or content that overlaps between embodiments is omitted. The terms “part, module, component, block” as used in the specification may be implemented in software or hardware, and depending on the embodiments, a plurality of “parts, modules, components, blocks” may be implemented as a single component, or a single “part, module, component, block” may include a plurality of components. Throughout the specification, when a part is described as being “connected” to another part, this includes not only direct connection but also indirect connection, and indirect connection includes connection via a wireless communication network.
[0025] Furthermore, when it is stated that a part "includes" a certain component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components.
[0026] Throughout the specification, when it is stated that a component is located "on" another component, this includes not only cases where a component is in contact with another component, but also cases where another component exists between the two components.
[0027] The terms first, second, etc. are used to distinguish one component from another, and the components are not limited by the aforementioned terms.
[0028] Singular expressions include plural expressions unless there is an obvious exception in the context.
[0029] In each step, identification codes are used for convenience of explanation and do not describe the order of the steps; the steps may be performed differently from the specified order unless a specific order is clearly indicated in the context.
[0030] The operating principles and embodiments of the present disclosure will be described below with reference to the attached drawings.
[0031] Prior to the explanation, the meanings of the terms used in this specification are briefly explained. However, since the explanation of terms is intended to aid in understanding this specification, it should be noted that they are not used to limit the technical scope of this disclosure unless explicitly stated to be a limiting factor.
[0032] In this specification, the term "server" includes all various devices capable of performing computational processing and providing results to a user. For example, a server may include a computer, a server device, and a portable terminal, or may be any one of these forms.
[0033] Here, the computer may include, for example, a notebook, desktop, laptop, tablet PC, slate PC, etc. equipped with a web browser.
[0034] The above server device is a server that processes information by communicating with an external device, and may include an application server, a computing server, a database server, a file server, a game server, a mail server, a proxy server, and a web server.
[0035] The above portable terminal may include, for example, all types of handheld-based wireless communication devices such as PCS (Personal Communication System), GSM (Global System for Mobile communications), PDC (Personal Digital Cellular), PHS (Personal Handyphone System), PDA (Personal Digital Assistant), IMT (International Mobile Telecommunication)-2000, CDMA (Code Division Multiple Access)-2000, W-CDMA (W-Code Division Multiple Access), WiBro (Wireless Broadband Internet) terminals, smartphones, etc., as well as wearable devices such as watches, rings, bracelets, anklets, necklaces, glasses, contact lenses, or head-mounted devices (HMDs).
[0036] In this specification, the 'server' (specifically, the payment approval server (10), message sending request agency server (15), and message sending server (20) to be described below) may include a communication unit, memory, and a processor. However, in some embodiments, the server may include a smaller number of components or a larger number of components.
[0037] The communication unit may include one or more modules that enable wireless or wired communication between a server and another server, another device, a user terminal, or a communication network. For example, it may include at least one of a wired communication module, a wireless communication module, a short-range communication module, and a location information module.
[0038] Various types of communication networks may be used, for example, wireless communication methods such as WLAN (Wireless LAN), Wi-Fi, Wibro, Wimax, and HSDPA (High Speed Downlink Packet Access), or wired communication methods such as Ethernet, xDSL (ADSL, VDSL), HFC (Hybrid Fiber Coax), FTTC (Fiber to The Curb), and FTTH (Fiber to The Home).
[0039] Meanwhile, the communication network is not limited to the communication method presented above, and may include all forms of communication methods that are widely known or will be developed in the future, in addition to the communication method described above.
[0040] The wired communication module may include various wired communication modules such as a Local Area Network (LAN) module, a Wide Area Network (WAN) module, or a Value Added Network (VAN) module, as well as various cable communication modules such as USB (Universal Serial Bus), HDMI (High Definition Multimedia Interface), DVI (Digital Visual Interface), RS-232 (recommended standard 232), power line communication, or POTS (plain old telephone service).
[0041] In addition to Wi-Fi modules and WiBro (Wireless broadband) modules, the wireless communication module may include wireless communication modules that support various wireless communication methods such as GSM (global System for Mobile Communication), CDMA (Code Division Multiple Access), WCDMA (Wideband Code Division Multiple Access), UMTS (universal mobile telecommunications system), TDMA (Time Division Multiple Access), LTE (Long Term Evolution), 4G, 5G, and 6G.
[0042] A short-range communication module is for short-range communication and can support short-range communication by using at least one of Bluetooth™, RFID (Radio Frequency Identification), Infrared Data Association (IrDA), UWB (Ultra Wideband), ZigBee, NFC (Near Field Communication), Wi-Fi (Wireless-Fidelity), Wi-Fi Direct, and Wireless USB (Wireless Universal Serial Bus) technologies.
[0043] Memory can store data supporting various functions of the server and programs for the operation of the processor, and can store input / output data (e.g., music files, still images, videos, etc.), and can store multiple application programs running on the server, data for the operation of the server, and instructions. At least some of these application programs can be downloaded from an external server via wireless communication.
[0044] Such memory may include at least one type of storage medium among flash memory type, hard disk type, SSD type (Solid State Disk type), SSD type (Silicon Disk Drive type), multimedia card micro type, card type memory (e.g., SD or XD memory, etc.), RAM (random access memory; RAM), SRAM (static random access memory), ROM (read-only memory; ROM), EEPROM (electrically erasable programmable read-only memory), PROM (programmable read-only memory), magnetic memory, magnetic disk, and optical disk. Additionally, the memory may be a database that is separated from the server but connected via wired or wireless connection.
[0045] The processor may perform the aforementioned operation using memory that stores data regarding an algorithm for controlling the operation of components within the server or a program that reproduces the algorithm, and the data stored in the memory. In this case, the memory and the processor may each be implemented as separate chips. Alternatively, the memory and the processor may be implemented as a single chip.
[0046] In addition, the processor may control any one or a combination of the components described above in order to implement various embodiments according to the present disclosure described in FIGS. 1 to 5 below on the processor.
[0047] In this specification, the term "financial company" may include card companies that possess their own card networks and banks that use the card networks of card companies. However, it is not limited thereto and may include all card companies, financial companies, and financial institutions that provide financial services.
[0048] In this specification, "financial products" may include card products subscribed to through a card company or bank, and account products subscribed to through a bank. However, it is not limited thereto and may include all financial products sold by a card company, financial company, or financial institution.
[0049] Embodiments of the present disclosure will be described in detail below with reference to the attached drawings.
[0050] FIG. 1 is a drawing for explaining a payment message-based marketing linkage system according to one embodiment of the present disclosure.
[0051] FIG. 2 is a diagram illustrating a process for sending a payment message when an agreement is not concluded between a payment approval server and a message sending server according to one embodiment of the present disclosure.
[0052] FIG. 3 is a diagram illustrating a payment message sending process when an agreement is concluded between a payment approval server and a message sending server according to one embodiment of the present disclosure.
[0053] FIGS. 4a and FIGS. 4b are drawings for illustrating a payment message according to one embodiment of the present disclosure.
[0054] Referring to FIG. 1, a payment message-based marketing linkage system (hereinafter, system) (1) according to one embodiment of the present disclosure may include a payment approval server (10), a message sending server (20), a payment server (30), and a user terminal (40). However, in some embodiments, the system (1) may include fewer or more components than the components shown in FIG. 1.
[0055] The payment approval server (10) may be a server having a payment approval system that receives a payment approval request from the payment server (30) and performs approval for the requested payment.
[0056] The payment approval server (10) may refer to a server of any card company, bank, financial company, or financial institution that provides financial services.
[0057] The message sending server (20) may be a server having a message sending system that sends a message about an approved payment transaction to a user terminal (40).
[0058] The message sending server (20) may refer to a server of a company providing SNS platform services. However, it is not limited to this, and if a server providing financial services has its own message sending system, the message sending server (20) may be a server of any card company, bank, financial company, or financial institution providing financial services.
[0059] The payment server (30) may refer to a POS device for offline payment or a server of a PG company for online payment.
[0060] The user terminal (40) may refer to a user who has purchased a product offline or online.
[0061] The user terminal (40) may include information processing means such as a computer, a processor such as a control unit, a shooting means such as a camera, an input / output means including a touch screen, and any device including a communication function. That is, any device such as a smartphone, tablet, PDA, laptop, desktop, etc., can be applied.
[0062] When a user terminal (40) requests payment for purchasing a product, the payment server (30) requests payment approval from the payment approval server (10). If the payment approval server (10) determines that the request is a valid request, it approves the payment. Once approval is complete, the payment approval server (10) may request the message sending server (20) to send a payment message regarding the payment. The message sending server (20) may send the payment message to the user terminal (40).
[0063] At this time, the message sending server (20) can send payment messages in different ways depending on whether a contract is concluded with the payment approval server (10).
[0064] Here, the contract may be entered into to grant the message sending server the authority to utilize payment information regarding the said product for marketing purposes. Here, the payment information may include, but is not limited to, merchant information, customer information, and product information, and may include all information related to product purchase and payment.
[0065] That is, depending on whether the message sending server (20) acting as an agent for sending messages can utilize the payment information received from the financial institution or card company for marketing, the sending of payment messages may be carried out in different ways. Each of the two cases will be explained below.
[0066] In cases where no contract is concluded between the payment approval server (10) and the message sending server (20), linked information regarding a merchant or product provided to the user terminal (40) to induce additional purchases may be generated by the payment approval server (10). Here, the merchant may refer to a place where payment is made, or may refer to a company that has entered into a marketing contract with the payment approval server (10) (e.g., a delivery app company).
[0067] Referring to FIG. 2, the payment approval server (10) can receive a payment approval request for a product from the payment server (30) (S21).
[0068] The payment approval server (10) can perform approval for the requested payment (S22).
[0069] After approval is completed, the payment approval server (10) may request the message sending server (20) to send a payment message regarding the payment. When the payment approval server (10) requests the message sending server (20) to send the payment message, it may also send linkage information for at least one of the merchant and product (S23).
[0070] The message sending server (20) can send a payment message to the user terminal (40) (S24). Here, the payment message may include linkage information.
[0071] When a contract is concluded between the payment approval server (10) and the message sending server (20), linked information regarding merchants or products provided to the user terminal (40) to induce additional purchases can be generated at the message sending server (20).
[0072] Referring to FIG. 3, the payment approval server (10) can receive a payment approval request for a product from the payment server (30) (S31).
[0073] The payment approval server (10) can perform approval for the requested payment (S32).
[0074] After approval is complete, the payment approval server (10) may request the message sending server (20) to send a payment message for the payment (S33).
[0075] The message sending server (20) checks whether a merchant is affiliated based on payment information provided by the payment approval server (10), and if the merchant is affiliated with the message sending server (20), it can extract linkage information for at least one of the merchant and the product (S34).
[0076] The message sending server (20) can send a payment message to the user terminal (40) (S35). Here, the payment message may include linkage information.
[0077] That is, when the message sending server (20) is able to utilize payment information through the conclusion of a contract, the message sending server (20) uses the payment information to determine whether the merchant is a sales outlet affiliated with the message sending server (20)'s own service, and if it is an affiliated sales outlet, since all information about the merchant is stored within the message sending server (20), it is possible to extract the linked information independently.
[0078] Conversely, if the contract has not been concluded, the message sending server (20) cannot utilize the payment information, so it receives the linked information generated by the payment approval server (10), includes it in the payment message, and sends it.
[0079] The linked information generated by the payment approval server (10) or message sending server (20) may include at least one of a link for an additional order for a product purchased by the user, a link for gifting a product purchased by the user, a link for making a reservation for a merchant selling the product purchased by the user, and a link for checking an event being held by a merchant selling the product purchased by the user.
[0080] Specifically, when a user purchases a product online, the linked information may include a link for placing an additional order for the product and a link for gifting the product.
[0081] According to an embodiment, even if a user has purchased a product online, if there is an offline store of the relevant merchant, the linked information may further include a link for making a reservation for the merchant, a link for checking events being held by the merchant, and a link for checking the location of the merchant's offline store.
[0082] Additionally, if the user purchases the product offline, the linked information may include a link for making a reservation at the merchant and a link to check the locations of other offline stores of the merchant.
[0083] According to an embodiment, even if a user has purchased a product offline, if the merchant has an online store, the linked information may further include a link for placing an additional online order for the product, a link for gifting the product online, a link for checking events being held by the merchant, and a link to access the merchant's website.
[0084] Various linked information is included in the payment message and transmitted to the user terminal (40).
[0085] Specifically, the message sending server (20) can generate a payment message to be sent to a user terminal (40) based on payment information. Additionally, the message sending server (20) can include a button for accessing linked information in the payment message. Referring to FIGS. 4a and 4b, the payment message can be sent to a user terminal (40) by including payment history information (41) and a button (42) for accessing linked information below it.
[0086] Below, an embodiment different from the system described above will be explained.
[0087] FIG. 5 is a drawing for illustrating a payment message-based marketing linkage system according to another embodiment of the present disclosure.
[0088] Referring to FIG. 5, a system (1) according to another embodiment of the present disclosure may include a payment approval server (10), a message sending request agency server (15), a message sending server (20), a payment server (30), and a user terminal (40). However, in some embodiments, the system (1) may include fewer or more components than the components shown in FIG. 5.
[0089] The payment approval server (10) may be a server having a payment approval system that receives a payment approval request from the payment server (30) and performs approval for the requested payment.
[0090] The payment approval server (10) may refer to a server of any card company, bank, financial company, or financial institution that provides financial services.
[0091] The message sending request agency server (15) can request the sending of a payment message to the message sending server (20) when payment approval is completed at the payment approval server (10).
[0092] The message sending request agency server (15) may refer to a server of a company that provides services to send and manage payment messages on behalf of the payment approval server (10) or to manage customers in accordance with the request of the payment approval server (10).
[0093] The message sending server (20) may be a server having a message sending system that sends a message about an approved payment transaction to a user terminal (40).
[0094] The message sending server (20) may refer to a server of a company providing SNS platform services. However, it is not limited to this, and if a server providing financial services has its own message sending system, the message sending server (20) may be a server of any card company, bank, financial company, or financial institution providing financial services.
[0095] The payment server (30) may refer to a POS device for offline payment or a server of a PG company for online payment.
[0096] The user terminal (40) may refer to a user who has purchased a product offline or online.
[0097] The user terminal (40) may include information processing means such as a computer, a processor such as a control unit, a shooting means such as a camera, an input / output means including a touch screen, and any device including a communication function. That is, any device such as a smartphone, tablet, PDA, laptop, desktop, etc., can be applied.
[0098] When a user terminal (40) requests payment for purchasing a product, the payment server (30) requests payment approval from the payment approval server (10). If the payment approval server (10) determines that the request is a valid request, it approves the payment. Once approval is complete, the payment approval server (10) transmits approval information regarding the approved payment to the message sending request agency server (15). The message sending request agency server (15) may request the message sending server (20) to send a payment message regarding the approved payment. The message sending server (20) may send the payment message to the user terminal (40).
[0099] At this time, the message sending server (20) can send payment messages in different ways depending on whether a contract is concluded with the payment approval server (10).
[0100] Here, the contract may be entered into to grant the message sending server the authority to utilize payment information regarding the said product for marketing purposes. Here, the payment information may include, but is not limited to, merchant information, customer information, and product information, and may include all information related to product purchase and payment.
[0101] That is, depending on whether the message sending server (20) acting as an agent for sending messages can utilize the payment information received from the financial institution or card company for marketing, the sending of payment messages may be carried out in different ways. Each of the two cases will be explained below.
[0102] If no contract is concluded between the payment approval server (10) and the message sending server (20), the linked information regarding the merchant or product provided to the user terminal (40) to induce additional purchases may be generated by the payment approval server (10). Here, the merchant may refer to a place where payment is made, or may refer to a company that has entered into a marketing contract with the payment approval server (10).
[0103] The payment approval server (10) can receive a payment approval request for a product from the payment server (30).
[0104] The payment approval server (10) can perform approval for the requested payment.
[0105] After approval is completed, the payment approval server (10) can transmit approval information for the approved payment to the message sending request agency server (15). At this time, the payment approval server (10) can transmit payment information and linkage information together.
[0106] The message sending request agency server (15) can confirm that the payment is approved through approval information and request the message sending server (20) to send a payment message regarding the payment. When the message sending request agency server (15) requests the message sending server (20) to send the payment message, it can send payment information and linked information regarding at least one of the merchant and product together.
[0107] The message sending server (20) can send a payment message to a user terminal (40). Here, the payment message may include linkage information.
[0108] When a contract is concluded between the payment approval server (10) and the message sending server (20), linked information regarding merchants or products provided to the user terminal (40) to induce additional purchases can be generated at the message sending server (20).
[0109] The payment approval server (10) can receive a payment approval request for a product from the payment server (30).
[0110] The payment approval server (10) can perform approval for the requested payment.
[0111] After approval is completed, the payment approval server (10) can send approval information for the approved payment to the message sending request agency server (15). At this time, the payment approval server (10) can also send payment information.
[0112] The message sending request agency server (15) can confirm that the payment is approved through the approval information and request the message sending server (20) to send a payment message regarding the payment. When the message sending request agency server (15) requests the message sending server (20) to send the payment message, it can send the payment information together.
[0113] The message sending server (20) checks whether a merchant is affiliated based on payment information provided by the message sending request agency server (15), and if the merchant is affiliated with the message sending server (20), it can extract linkage information for at least one of the merchant and the product.
[0114] The message sending server (20) can send a payment message to a user terminal (40). Here, the payment message may include linkage information.
[0115] That is, when the message sending server (20) is able to utilize payment information through the conclusion of a contract, the message sending server (20) uses the payment information to determine whether the merchant is a sales outlet affiliated with the message sending server (20)'s own service, and if it is an affiliated sales outlet, since all information about the merchant is stored within the message sending server (20), it is possible to extract the linked information independently.
[0116] Conversely, if a contract has not been concluded, the message sending server (20) cannot utilize the payment information, so the linked information generated by the payment approval server (10) is received from the message sending request agency server (15), included in the payment message, and sent. However, this is not limited to this, and the message sending request agency server (15) may also generate linked information based on the payment information received from the payment approval server (10).
[0117] As described above, generating a payment message by including the linkage information generated in this way and sending it to the user terminal (40) is as described above, so a detailed explanation will be omitted.
[0118] The systems of the two embodiments described above with reference to FIGS. 1 to 5 relate to a payment message sending process. Below, a platform service for managing customer information related to message sending will be described.
[0119] In the system described with reference to FIGS. 1 to 4b above, the server providing a platform service for managing customer information related to message sending (hereinafter, platform service server) may be another server not shown in FIG. 1.
[0120] In the system described above with reference to FIG. 5, the platform service server may be the message sending request agency server (15) shown in FIG. 5. However, it is not limited thereto and may be another server not shown in FIG. 5.
[0121] The platform service server can manage financial information for each financial product of the user. Here, the financial information may include, but is not limited to, at least one of whether a payment message is received, whether a marketing message is received, a message receiving channel, a payment account, and a payment date.
[0122] In addition, message receiving channels may include, but are not limited to, text messages, email, and SNS notification messages.
[0123] The platform service server can retrieve and store financial information regarding all financial products of a user, and subsequently, if there is a request for a change regarding a specific product, it can perform the role of transmitting the change details to the financial company server (payment approval server (10)) of the product. Then, when the financial company completes applying the change details, the platform service server can retrieve the financial information with the applied changes from the financial company and update the user's financial information.
[0124] According to an embodiment, if the message receiving channel for a specific financial product of a user is changed and updated from A Notification Talk to B Notification Talk, the message sending server (20) may be a server providing the B Notification Talk service. That is, the payment approval server (10) or the message sending request agency server (15) may request the sending of a payment message to the server providing the B Notification Talk.
[0125] Although the steps are described as being executed sequentially in the drawings, this is merely an illustrative explanation of the technical concept of the present embodiment. A person skilled in the art to which the present embodiment belongs could modify and adapt the steps in various ways, such as changing the order described in the drawings or executing them in parallel, without departing from the essential characteristics of the present embodiment; therefore, the drawings are not limited to a chronological order.
[0126] Meanwhile, in the description above, the steps described in the drawings may be further divided into additional steps or combined into fewer steps according to an embodiment of the present disclosure. Additionally, some steps may be omitted as necessary, and the order of the steps may be changed.
[0127] Meanwhile, the disclosed embodiments may be implemented in the form of a recording medium that stores instructions executable by a computer. The instructions may be stored in the form of program code and, when executed by a processor, may generate a program module to perform the operation of the disclosed embodiments. The recording medium may be implemented as a computer-readable recording medium.
[0128] Computer-readable recording media include all types of recording media that store instructions that can be decoded by a computer. Examples include ROM (Read Only Memory), RAM (Random Access Memory), magnetic tape, magnetic disk, flash memory, optical data storage devices, etc.
[0129] As described above, the disclosed embodiments have been explained with reference to the attached drawings. Those skilled in the art will understand that the present disclosure may be practiced in forms different from the disclosed embodiments without changing the technical spirit or essential features of the present disclosure. The disclosed embodiments are illustrative and should not be interpreted restrictively. Explanation of the symbols
[0130] 1: System 10: Payment approval server 15: Message sending request proxy server 20: Message sending server 30: Payment Server 40: User terminal
Claims
Claim 1 A payment message-based marketing linkage system comprising: a payment approval server that receives a payment approval request for a product from a payment server and performs approval for the payment for which approval was requested; and a message sending server that receives a request to send a payment message for the approved payment from the payment approval server and sends the payment message to a terminal of a user who purchased the product; wherein the message sending server sends the payment message in a different manner depending on whether a contract is concluded with the payment approval server, and the contract grants the message sending server the authority to utilize payment information for the product for marketing; if the contract is not concluded, the payment approval server generates linkage information for at least one of a merchant and a product and transmits a request to send a payment message along with the linkage information to the message sending server, and the message sending server sends the payment message containing the received linkage information to the user terminal; and if the contract is concluded, the message sending server verifies whether the merchant is affiliated based on the payment information received from the payment approval server, extracts the linkage information from internally stored information for affiliated merchants, and sends the payment message containing the extracted linkage information to the user terminal. Claim 2 delete Claim 3 delete Claim 4 delete Claim 5 A payment message-based marketing linkage system according to claim 1, wherein the linkage information comprises at least one of a link for an additional order for the product, a link for gifting the product, a link for making a reservation for the merchant, and a link for checking an event being conducted by the merchant. Claim 6 In paragraph 5, the above message sending server sends the above payment message to the user terminal by including a button for accessing the above linkage information in the above payment message, a payment message-based marketing linkage system. Claim 7 A message sending request agency server that receives approval information for an approved payment from a payment approval server; A payment message-based marketing linkage system comprising: a message sending server that receives a request to send a payment message regarding the approved payment from the message sending request agency server and sends the payment message to the terminal of a user who has purchased a product; wherein the message sending server sends the payment message in a different manner depending on whether a contract is concluded with the payment approval server, and the contract grants the message sending server the authority to utilize payment information regarding the product for marketing; if the contract is not concluded, the payment approval server generates linkage information for at least one of a merchant and a product, and the message sending request agency server transmits a request to send a payment message along with the linkage information to the message sending server, and the message sending server sends the payment message containing the received linkage information to the user terminal; and if the contract is concluded, the message sending server verifies whether the merchant is affiliated based on the payment information transmitted from the payment approval server through the message sending request agency server, extracts the linkage information from internally stored information for affiliated merchants, and sends the payment message containing the extracted linkage information to the user terminal. Claim 8 delete Claim 9 delete Claim 10 delete
Citation Information
Patent Citations
System for transmitting advertisement message according to paying by card and control method thereof
KR1020090109653A
Web messaging system and method based on context awareness for broadening marketing campaign channel
KR1020120082316A
