KR20190096592A - A method for processing of payment messages - Google Patents

Abstract

The present invention relates to a method for processing a payment message of a user terminal. The method comprises the steps of: receiving a payment history message generated by performing message fusion in a payment message fusion service providing device from the payment message fusion service providing device if a payment message of a payment provider and a sales item message of an affiliated store received by the payment message fusion service providing device are associated messages of the same matter for the same recipient; and generating database using the received payment history message.

Description

How to process payment messages on your device {A METHOD FOR PROCESSING OF PAYMENT MESSAGES}

The present invention relates to a payment message processing method of a user terminal. More specifically, the present invention relates to a method for generating a database by receiving a payment history message.

The widespread use of the Internet today has led to the rapid development of wireless mobile communication technology over the wire, and in the real world, information retrieval on the Internet through mobile user terminals such as mobile phones, PDAs, hand-held computers, etc. It became possible regardless of this time and place.

In particular, as various functions can be implemented through various user terminals such as smartphones, various dedicated application programs and contents driven in the user terminal are being developed. Is being provided.

Among these, the message service is a core function of the user terminal program most basically provided. This is a function for transmitting and receiving a user-specified message through a network, which is being expanded in various forms by diversification of communication networks and diversification of data protocols. For example, the message service application may provide transmission and reception of short messages and long messages through a mobile communication network, or may transmit and receive message content data through an Internet protocol network, and each application may transmit and receive message data accurately and safely. It can also provide management services for data storage, data tampering and encryption.

Accordingly, the message service is very effective as an information service provider and a notification means of operators, and in particular, the service is generally used in payment services.

However, as the use of such a message service is greatly increased, there are cases in which excessively distributed and subdivided information is provided as a partial message by the interests of each service provider.

For example, FIG. 1 illustrates a conventional payment approval message service flow when a customer payment occurs. When a card payment of one customer occurs, the card company server 10 of the card company operator connects to the payment message server 11 connected thereto. ) And a payment approval message related to card payment to the user terminal 30 through a first communication network (mobile communication network, etc.), and the affiliated store server 20 of the affiliated store provider that provides the product is separately connected to the sales item message server 21. And messages related to goods, delivery, or points through a second communication network (such as an internet network) to the user terminal 30.

In such a case, in order to provide the relevant information about the same billing, the message server operation costs and communication network usage costs for each service provider are generated as the number of each service provider, which causes duplicate charging for each service provider. Socially, this can lead to increased network costs and increased network load.

In addition, even if a user of the user terminal 30 receives a payment approval message from a payment related card company server 10, it is often difficult to know exactly which goods / shipping / points are related to the consumer, and accordingly, The user cannot check separately whether the actual payment of the goods is actually made or what is the information related to the delivery or points, unless the user makes a direct inquiry request to the affiliated party.

As such, according to the current message service architecture, the messages of the same information are excessively distributed and separated by operators, so that not only double or multiple billing and network loads are generated, but also users who receive the messages are distributed. It is very difficult to collect the collected information again or connect related information.

The present invention is to solve the above problems, and when the payment message and the sale item message received for the same user of the same issue is received by fusion processing to generate a database, according to the payment information item of the payment history message and An object of the present invention is to provide a method for generating a personal account book of a user of a user terminal according to a product information item classification and a summation process for a predetermined period of time.

The method according to an embodiment of the present invention for solving the above problems, when the payment message of the payment operator and the sale item message of the merchant received by the payment message fusion service providing apparatus is an association message of the same issue for the same recipient. And receiving, from the payment message fusion service providing device, a payment history message generated by performing a message fusion process in the payment message fusion service providing device and generating a database using the received payment history message.

According to an embodiment of the present invention, the user receiving the payment history message receives the fused message, thereby improving convenience for eliminating user inconvenience caused by the distribution of existing information.

In addition, according to an embodiment of the present invention, it is easy to classify and process the data according to the payment history message, so that it is possible to create a database such as an account book to maximize its effectiveness.

1 is a view for explaining an existing system structure.
2 is a view schematically showing an entire system according to an embodiment of the present invention.
3 is a block diagram illustrating in more detail an apparatus for providing a payment message fusion service according to an exemplary embodiment of the present invention.
4 is a block diagram illustrating in more detail an outgoing message fusion processing unit according to an embodiment of the present invention.
5 is a diagram illustrating an application example of a payment message fusion service according to an embodiment of the present invention.
6 to 7 are flowcharts illustrating a payment message fusion service providing method according to an exemplary embodiment of the present invention.
8 to 10 are diagrams for illustrating a payment history message according to an embodiment of the present invention.
11 is a flowchart illustrating an application operation of a user terminal using a payment message fusion service according to an embodiment of the present invention.

The following merely illustrates the principles of the invention. Therefore, those skilled in the art, although not explicitly described or illustrated herein, can embody the principles of the present invention and invent various devices that fall within the spirit and scope of the present invention. Furthermore, all conditional terms and embodiments listed herein are in principle clearly intended for the purpose of understanding the concept of the invention and are not to be limited to the specifically listed embodiments and states. Should be.

In addition, it is to be understood that all detailed descriptions, including the principles, aspects, and embodiments of the present invention, as well as listing specific embodiments, are intended to include structural and functional equivalents of these matters. In addition, these equivalents should be understood to include not only equivalents now known, but also equivalents to be developed in the future, that is, all devices invented to perform the same function regardless of structure.

Thus, for example, it should be understood that the block diagrams herein represent a conceptual view of example circuitry embodying the principles of the invention. Similarly, all flowcharts, state transitions, pseudocodes, and the like are understood to represent various processes performed by a computer or processor, whether or not the computer or processor is substantially illustrated on a computer readable medium and whether the computer or processor is clearly shown. Should be.

In addition, the explicit use of terms presented in terms of processor, control, or similar concept should not be interpreted exclusively as a citation to hardware capable of running software, and without limitation, ROM for storing digital signal processor (DSP) hardware, software. (ROM), RAM, and non-volatile memory are to be understood to implicitly include. Other hardware for the governor may also be included.

The above objects, features, and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, whereby those skilled in the art may easily implement the technical idea of the present invention. There will be. In addition, in describing the present invention, when it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

2 is a view schematically showing an entire system according to an embodiment of the present invention.

Referring to FIG. 2, a system according to an embodiment of the present invention includes a user terminal 100, a payment message fusion service providing apparatus 200 (hereinafter, referred to as a service providing apparatus), and a plurality of service providers (payment providers, affiliated stores, etc.). (300A, 300B, ...).

More specifically, the user terminal 100, the service providing apparatus 200, and the plurality of service provider servers 300A, 300B, ... may be connected by wire or wirelessly through a network.

Each user user terminal 100, the service providing apparatus 200, and the plurality of service provider servers 300A, 300B, ... for communication between networks are connected to an Internet network, a LAN, a WAN, a public switched telephone network (PSTN), Data can be transmitted / received through a Public Switched Data Network (PSDN), a cable TV network, WIFI, a mobile communication network, and other wireless communication networks. In addition, each user terminal 100, the service providing apparatus 200, and the plurality of service provider servers 300A, 300B, ... may include respective communication modules for communicating with a protocol corresponding to each communication network.

In addition, the user terminal 100 described herein includes a mobile phone, a smart phone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), navigation, and the like. Although not limited thereto, the present invention may include various devices capable of displaying a user input and information.

In such a system, each of the plurality of service provider servers 300A, 300B, ... may check whether a message transmission request for the same issue occurs. For example, the payment provider server 300A may be a card company server, and the affiliated store server 300B may be a server provided in a shopping mall that provides product information and transaction services. Accordingly, when a customer payment or the like occurs, the payment service provider server 300A and the affiliated server 300B may generate a payment message and a sale item message to be transmitted to the user terminal 100 according to respective checking means.

In addition, the payment service provider server 300A according to the present invention may include a message transmission server that transmits a payment message to a communication network, or may be a message transmission server itself, or a message that transmits a merchandise server 300B sale item message to a communication network. It may include a transmission server or may be a message transmission server itself.

In addition, according to an embodiment of the present disclosure, the service providing apparatus 200 may perform association processing between the payment message and the sale item message respectively received from the payment provider server 300A and the affiliate server 300B.

When the payment message and the sale item message are related messages of the same issue for the same recipient, the service providing device 200 may generate a payment history message by performing a message fusion process. The transmission may be transmitted to the user terminal 100 corresponding to the receiver.

Accordingly, the apparatus 200 for providing a service according to an embodiment of the present disclosure classifies and associates messages related to the same matter between the payment provider server 300A and the affiliate server 300B, and merges a single payment history message. And, the generated billing history message includes all the delivery information of the payment message and the sale item message, it is possible to sufficiently transfer the information of the same matter, while preventing separate double or duplicate billing, the user terminal ( 100) User's information can be checked and sorted conveniently.

In this case, the service providing apparatus 200 may perform a conversion and transmission process in a data format corresponding to various networks for sending a payment history message.

More specifically, the payment history message may include data in a corporate message format, and the service providing apparatus 200 may transmit the payment history message to the user terminal through a corporate messaging service network.

In addition, the payment history message may include data of a social network messenger format, and the service providing apparatus 200 may transmit the payment history message to the user terminal through a social network-based messenger network.

The payment history message may include data of an e-mail, short or long text message format, and the service providing apparatus 200 may transmit the payment history message to the e-mail, short or long text through a mobile communication network or a dedicated internet network. Data in the message format can be transmitted.

In addition, the sender information of the payment history message may include identification information corresponding to the payment provider server (300A). In the case of the existing data format as described above, one sender may be designated, and thus, a payment provider determined according to a preset priority may not include a plurality of operators and may also be used to send a reply message. Identification information corresponding to the server 300A may be included in the caller information.

The service providing apparatus 200 may include a communication protocol conversion, a file server, a collect server, a push gateway server, a transmission server, an account server, an administration server, a reception server, a conversion server, a messaging server, It can be implemented as a server device that performs the overall role, such as push receiving server, push sending server function.

In this case, the user terminal 100 and the service providing apparatus 200 may communicate with each other through a first network, and the service providing apparatus 200 and the plurality of service provider servers 300A, 300B, ... may use a second network. It can communicate via, and the protocol or encryption scheme of each network may be different. In addition, the communication network with each of the plurality of operator servers 300A, 300B, ... may also be different networks, and accordingly, the service providing apparatus 200 may provide data conversion processing according to each network protocol. have.

The service providing apparatus 200 may encrypt and manage all or part of the operator information and the message information as necessary.

In addition, the service providing apparatus 200 according to an embodiment of the present invention may provide various additional information and functions processed according to a payment message fusion service to the user terminal 100, and each of a plurality of operator servers 300A and 300B. , ...) service subscription and alliance processing, or communicate with a financial server to perform a billing process for providing a converged service to a plurality of operators server (300A, 300B, ...) and the like.

Meanwhile, when the payment message of the first operator and the sale item message of the second operator received by the payment message fusion service providing apparatus 200 are related messages of the same matter with respect to the same receiver, the user terminal 100 receives the payment message. The payment message may be received from the payment message fusion service providing apparatus 200 by performing a message fusion process in the convergence service providing apparatus 200, and may generate a database using the received payment history message. .

For example, the payment operator may include a card company operator, and the payment message may include a card payment related payment information message transmitted from a card company server, the affiliate store includes an affiliate store operator, and the sale item message includes an affiliate store. It may include a product-related product information message sent from the server.

Accordingly, the database may include a personal account book database of the user terminal user according to the classification of each payment information item and product information item of the payment history message and a summation process for a predetermined period of time, and the user terminal 100 generates a database. And the above classification and summation processing for output.

In addition, a separate application may be installed in the user terminal 100, and a general portable terminal including a separate controller, a storage unit (not shown), an output unit (not shown), and a communication unit (not shown). It can basically include the configuration of.

3 is a block diagram illustrating a payment message fusion service providing apparatus according to an embodiment of the present invention in more detail, Figure 4 is a block diagram for explaining in more detail the outgoing message fusion processing unit according to an embodiment of the present invention; to be.

3 and 4, the service providing apparatus 200 according to an exemplary embodiment of the present invention may include a communication unit 210, a control unit 220, a database 230, a management service providing unit 240, and a message fusion processing unit ( And a reply message processing unit 260, wherein the message fusion processing unit 250 includes a message classification unit 251, an association processing unit 253, a payment history message generation unit 254, and an origination information allocation unit 255. It may include.

The controller 220 may control the overall operation of each module to provide operation processing according to a service providing method according to an exemplary embodiment of the present invention, and may include one or more microprocessors.

The communication unit 210 may include one or more modules that enable wired or wireless communication between the user terminal 100 or a network in which a plurality of operator servers 300A, 300B, ... are located. For example, the communication unit 210 may include at least one of a mobile communication module, a wired internet module, a wireless internet module, and a short range communication module.

In addition, the management service provider 240 may register and manage operator information and user information corresponding to operators and users who use the payment message fusion service according to an exemplary embodiment of the present invention. The user information may include the operator identification information of the operator who sends the message, the partnership information between the operators, or the identification information of the user who will receive the payment history message. The user information may include the user terminal 100 or a plurality of operator servers 300A, 300B, ...) may be newly registered, updated, and managed according to a user information registration or renewal request received. In addition, all or part of the user information may be encrypted and stored.

On the other hand, the database 230 may store a program for the operation of each component, and may store the input / output data (for example, message information, payment history message information, user information, etc.), message fusion And a separate classified database can be stored and managed for reply processing.

As described above, the message fusion processing unit 250 performs an association process between the payment message received from a plurality of service provider servers 300A, 300B, ... and one or more of the sale item message, and the payment message and If the sale item message is a related message of the same issue for the same recipient, the payment history message may be generated by performing a message fusion process. Accordingly, the communication unit 210 transmits the payment history message to the user terminal corresponding to the receiver. This will be described in more detail with reference to FIG. 4.

4 illustrates the fusion processor 250 according to an embodiment of the present invention in more detail. The fusion processor 250 may include a message classifier 251, an association processor 253, and a payment history message generator 254. And an origination information allocator 255.

The message classification unit may classify each message received from the plurality of operator servers 300A, 300B, ... according to a preset item criterion.

Here, the item criterion may include sender information, recipient information, origination time information, template code information, affiliate information, category information, or matching keyword information of the message, and the matching keyword information includes keyword information corresponding to each case information. It can indicate whether or not. For example, the case information may correspond to a payment matter, and the keyword information may include matching keyword information corresponding to at least one of a financial service provider, merchant information, a product name, a payment time, a payment amount, and a transaction code.

In addition, in the item criterion, the caller information may include identification information of each caller corresponding to the plurality of operator servers 300A, 300B, ..., for example, the management service provider 240 ID information, email information, network identification information of the operator server, or telephone number information for each operator may be exemplified through the pre-registered operator.

In addition, in the item criterion, ID information of a receiver, phone number information of a receiver, or network identification information of a receiver terminal may be exemplified in the receiver information.

In addition, in the item criterion, the template code information may include preset code information corresponding to the attribute of the message. The template code information may indicate the type information of the message data identifiable by the messenger service application or the messenger relay server of the receiver, and the template code information is predetermined according to the properties of the message to be transmitted for each operator and may be the same or different. have.

On the other hand, the affiliated information may be included in the message received from the service provider server corresponding to the service provider, if there is a payment message fusion service partnership relationship between each service provider server. For example, when registered in a partnership relationship between the payment provider server 300A and the affiliate server 300B, the management service provider 240 may provide the affiliate information matching the payment provider server 300A and the affiliate server 300B. It can be registered and managed, which can be provided to each operator server. Accordingly, the payment message and the sale item message transmitted from the affiliated payment provider server 300A and the affiliate server 300B may include affiliate information. The affiliate information may be exemplified by preset code information.

In this way, the association processing unit 253 may perform an association process for determining association between each message using the classified messages.

To this end, the association processing unit 253 may perform association determination processing according to similarity or equality within a preset reference value for each classified item criterion according to a preset condition criterion. For example, the recipient information and the case information of the message of the same payment matter may be the same or within a certain range, and thus the association message may be determined.

More specifically, the association processor 253 may compare the pre-classified item reference information according to the condition criteria. For example, the item criterion of each message may be the sender information, the receiver information, the origination time information, the template code information, the affiliate information, the category information, or the matching keyword information of the message, and the association processor 253 matches the condition for each category. It is possible to determine whether or not to correlate messages.

According to an embodiment of the present disclosure, the association processing unit 253 may primarily determine whether recipient information of messages is matched for association processing, and perform comparison processing of subsequent steps when the recipient information is the same. .

In addition, the association processing unit 253 determines whether or not other items of sale messages are related to each other according to whether or not it is within a predetermined time period based on the origination time information of the payment message received from the payment provider server 300A according to a preset priority between operators. You can decide. For example, when the transmission time of the payment message from the payment service provider server 300A for a specific receiver is 12: 0, the sale of another merchant server 300B received within one minute before and after the preset reception for the specific receiver is performed. When the item message exists, the payment message and the sale item message may be determined as an association message.

For example, the payment provider may be a card company server corresponding to a payment method in a card payment issue among the plurality of service provider servers 300A, 300B, .... Accordingly, the association processing unit 253 may index the sale item messages corresponding to the payment message received from the card company server, which is the payment provider server 300A, and associate the indexed messages with each other.

Further, in determining the association message, whether the template code information or the association information match between messages may be further considered.

The association processing unit 253 may filter and process only the messages in which the association information or the template code information match among the indexed messages as the association message.

On the other hand, the payment history message generation unit 254 processes the associated determined messages to generate a single fusion payment history message. To this end, the payment history message generator 254 may generate fusion format data corresponding to a separate payment history message.

More specifically, the payment history message generating unit 254 may generate fusion format data by fusion processing of each message according to a preset condition.

In the generation of the fusion format data, the contents of the payment message and the item of sale message may be selectively fused to the payment details message. For example, the contents of the payment message and the sale item message may be merged together with each caller information. In addition, the fusion processor 250 may extract necessary information that is not actually duplicated from the keyword information identified from each message and assign the extracted information to the payment history message.

The keyword information may be information extracted from a message through keyword analysis or information added to a separate field of message data to provide a payment message fusion service according to an embodiment of the present invention. When added to a separate field, each of the plurality of service provider servers 300A, 300B, ... may add keyword information necessary for generating a payment history message to the separate field in a predetermined order when transmitting a message. For example, in a separate field, as a keyword for payment, a payment method, a payment amount, a product name, a payment date, a transaction code, etc. may be added as keywords.

On the other hand, the origination information allocating unit 255 may allocate caller information, template code information, and other information necessary for origination to the generated payment history message. In particular, the caller information allocator 255 may process the caller information to include identification information corresponding to the payment operator server 300A determined according to a preset priority, and thus, the caller may be designated as the first operator. Can be transmitted over an existing message transmission network.

On the other hand, the caller information may include a plurality of caller information including the payment provider server 300A and the merchant server 300B. However, when it is difficult to designate a plurality of sender information in the current system, the plurality of sender information may be directly included in the payment history message. For example, contact or identification information for each caller may be inserted into the payment history message.

Accordingly, the communication unit 210 may convert the payment history message into an appropriate format for each service network to be transmitted to the user terminal 100, and transmit the payment history message to the user terminal 100 through a predetermined communication network for the service network.

Here, when it is confirmed that the transmission failure for the first network that transmitted the payment history message is confirmed, the communication unit 210 may retransmit the payment history message through another second network determined according to priority. For example, the use network for each service provider may be different, and the payment history message may be retransmitted through the selected network according to the priority.

Meanwhile, referring to FIG. 3 again, the reply message processor 260 may receive a reply message corresponding to the payment details message from the user terminal, and perform a transfer process accordingly. To this end, the reply message processor 260 may determine a payment operator or an affiliate store corresponding to the reply message according to the separate matching of the reply message and the payment history message, and the payment operator corresponding to the determined payment provider or affiliate store. The server may perform a process of transmitting the reply message to the server. Accordingly, the convenience of processing the reply message may also be provided.

5 is a diagram illustrating an application example of a payment message fusion service according to an embodiment of the present invention.

Referring to FIG. 5, the payment provider server 300A according to an embodiment of the present invention may be a caller server, and the affiliated store server 300B may be an affiliate server connected to a caller affiliate. To this end, the service providing apparatus 200 may perform an affiliate registration process between the payment provider server 300A and the affiliated store server 300B, and the preset affiliate setting information may be set to the payment provider server 300A and the affiliated store server 300B. Can be provided as For example, the affiliate setting information may include affiliate service code information and issue selection information. The affiliate service code information may indicate whether the message is affiliated, and the matter selection information may indicate keyword order and format information of the issue information to be included in the payment history message.

Accordingly, the service providing apparatus 200 may easily process the association between each message and the convergence process by using the affiliate information included in the messages received between the payment service provider server 300A and the affiliate server 300B. have.

For example, the affiliate information may include an affiliate service code and case information (eg, product name information, payment date information, payment amount information, etc.) provided from each provider server, and the service providing apparatus 200 may include a message. If the affiliate service code and the case information match, the fusion processor 250 may determine that it is related and perform a fusion process. However, when there is no affiliate information, the above-described template code may be additionally used.

In addition, the payment history message generation unit 254 may generate a payment history message of a predetermined format according to the keyword information of the affiliated information, and inserts keyword information of each operator message into the payment history message. By generating the detail message, it is possible to enable a more natural transmission of the payment history message.

Accordingly, the service providing apparatus 200 may generate a payment history message that combines a payment message with a payment operator and a sale item message, and transmits the payment history message to the user terminal 100 through various paths. Can be.

6 to 7 are flowcharts illustrating a payment message fusion service providing method according to an exemplary embodiment of the present invention.

FIG. 6 illustrates the origination process. First, the service providing apparatus 200 receives a message from the payment provider server 300A and the affiliate server 300B (S1001).

The service providing apparatus 200 identifies the classification information of the payment message through the fusion processor 250 (S1003), and identifies the classification information of the sales item message corresponding thereto (S1005).

Here, the receiver of the payment message and the sale item message may be the same, and may be a message received within a predetermined time. Accordingly, the message to be processed may be primarily determined.

Thereafter, the service providing apparatus 200 determines whether the payment message and the sale item message are related to each other through the fusion processor 250 (S1007). In determining the association, the aforementioned item criteria may be used.

In addition, the service providing apparatus 200 generates a payment history message through reprocessing and fusion processing using the payment message and the sale item message determined through the fusion processing unit 250 (S1009).

Subsequently, the service providing apparatus 200 determines a representative sender among payment providers and affiliated stores that transmit the payment message and the sale item message according to the priorities set in advance through the convergence processor 250 (S1011). Here, in the case where both the payment operator and the affiliate store can be included as the sender, step S1011 may be omitted.

In operation S1013, the service providing apparatus 200 allocates a fusion template code to the fusion processed payment message data and transmits the payment history message of the determined representative sender's name to the user terminal 100 (S1013).

Meanwhile, FIG. 7 illustrates a reply message processing process. First, the service providing apparatus 200 receives a reply message corresponding to a payment history message from the user terminal 100 through the reply message processor 260 (S2001). ).

In addition, the service providing apparatus 200 separately matches the payment details message through the reply message processor 260 to determine the payment provider server 300A to the affiliated store server 300B corresponding to the reply message (S2003).

For example, when the reply target operator information is identified from the reply message of the payment details message, one of the payment provider server or the affiliated store server may be determined in response to the operator information.

Accordingly, the service providing apparatus 200 transfers the reply message to the server corresponding to the determined operator information through the reply message processor 260 (S2005).

After the reply message is processed as described above, the service providing apparatus 200 may perform an exception process so as to deliver a message directly between the server of the payment provider or the affiliated store and the user terminal 100 without additional convergence.

8 to 10 are diagrams for illustrating a payment history message according to an embodiment of the present invention.

8 and 10 illustrate a case where the payment service provider server 300A is a card company server called 'Shinhan Card', and the merchant server 300B is a shopping mall server called '11th Street', and the payment history message is transmitted from each caller server. It may be configured as a fusion format of a payment message and a sale item message corresponding to the same payment issue received.

Referring to FIG. 8, the service providing apparatus 200 may extract payment approval information from a card payment approval message which is a payment message of a payment provider server 300A, and may receive a product from a product transaction result message of the affiliate server 300B. Information can be extracted. Accordingly, the service providing apparatus 200 may generate a payment history message in which the payment approval and the product information are fused, and transmit the generated payment history message to the user terminal 100. In addition, in the case where the preset affiliate information exists in the extraction, the service providing device 200 extracts necessary keyword information from the affiliate information or a separate message free field and selectively inserts the keyword information into a payment history message to generate a natural message. Can be.

On the other hand, if there is a data restriction according to the messenger characteristic, the service providing apparatus 200 may generate separate link information corresponding to the excess data and insert it into the payment history message. The link information may be, for example, a URL corresponding to detailed commodity transaction information.

In addition, the caller information may be a predetermined payment operator server 300A. However, when multiple caller information is possible according to an embodiment, information of the merchant server 300B may also be included.

Meanwhile, referring to FIG. 9, the payment history message may be simply generated by connecting a payment message and a sale item message to each caller information. In this case, faster data processing is possible by reducing the throughput of the service providing apparatus 200.

In addition, referring to FIG. 10, each caller information may be selectively included in a payment history message, and caller identification information for a reply may be included. For example, the caller identification information may be illustrated by each caller's telephone number. Accordingly, the user can recognize the identification information of the plurality of senders from the payment history message, and can easily reply to each operator.

11 is a flowchart illustrating an application operation of a user terminal using a payment message fusion service according to an embodiment of the present invention.

Referring to FIG. 11, the payment details message as described above is related to a payment matter in more detail. In accordance with the transmission of a payment history message for a payment issue, the user terminal 100 may be based on a payment history message. You can easily create an account book database.

In the conventional case, only the payment text message for each service provider knows only the amount and the use place, and there is a problem that is very difficult to associate with which transaction of which product. However, in the case of the payment history message according to an embodiment of the present invention, Since all of the above related information can be extracted even with a single detail message, the user terminal 100 can provide an account book database for each item according to a summation process for a predetermined period.

To this end, first, the user terminal 100 is installed and executed by the account book application through the control unit (S3001).

In addition, when the payment history message is received and identified by the user terminal 100, the user terminal 100 performs a data classification process according to preset item information through the control unit (S3003).

Here, the user terminal 100 may determine whether the payment history message using the template code information of the payment history message, and perform the data classification process for each item through keyword information in the payment history message. have. For example, the item information may include at least one of a payment means, a product name, a transaction date and time, and a transaction amount.

On the other hand, the user terminal 100 by using the classified data, and inputs the payment information for each purchase item (S3005), by adding up for each predetermined period, generates an account book database (S3007).

According to the present invention, the processes of S3001 to S3007 can be executed by a program or an application, and the present invention includes a computer-readable recording medium on which the program or application is recorded.

As described above, the service providing apparatus 200 according to an exemplary embodiment of the present invention fuses the messages received from each of the plurality of service provider servers 300A, 300B, ..., so that each service provider uses the cost of the message service. In addition to minimizing the number, it is possible to easily provide social services, reduce social network hatching, improve receiver convenience, and even provide additional services.

Meanwhile, the above-described method according to various embodiments of the present disclosure may be implemented in the form of installation data to be executed in a terminal device and stored in various non-transitory computer readable mediums in each server or device. Can be provided. Accordingly, the user terminal 100 may download the installation data by accessing the server or the device.

The non-transitory readable medium refers to a medium that stores data semi-permanently and is readable by a device, not a medium storing data for a short time such as a register, a cache, a memory, and the like. Specifically, the various applications or programs described above may be stored and provided in a non-transitory readable medium such as a CD, a DVD, a hard disk, a Blu-ray disk, a USB, a memory card, a ROM, or the like.

In addition, although the preferred embodiment of the present invention has been shown and described above, the present invention is not limited to the specific embodiments described above, but the technical field to which the invention belongs without departing from the spirit of the invention claimed in the claims. Of course, various modifications can be made by those skilled in the art, and these modifications should not be individually understood from the technical spirit or the prospect of the present invention.

Claims (3)

In the payment message processing method of the user terminal,
When the payment message of the payment operator and the sale item message of the merchant received by the payment message fusion service providing apparatus are related messages of the same issue for the same recipient, the payment message generated by performing the message fusion processing in the payment message fusion service providing apparatus Receiving a payment message from the payment message fusion service providing apparatus; And
Generating a database using the received payment history message;
Method of processing a payment message of a user terminal. The method of claim 1,
The payment service provider includes a card company service provider, and the payment message includes a card payment related payment information message transmitted from a card company server.
The affiliated store includes an affiliated store operator, and the sale item message includes a product related product information message transmitted from an affiliated store server.
Method of processing a payment message of a user terminal. The method of claim 1,
The database may include a personal account book database of the user terminal user according to the classification process for each payment information item and product information item of the payment history message and a summation process for a certain period of time.
Method of processing a payment message of a user terminal.

Images