KR102465890B1 - Device, method, system and computer readable storage medium for managing payment history - Google Patents

Abstract

According to the present invention, a method for managing payment information is described. The method for managing payment information according to an embodiment comprises the steps of: obtaining payment data by request of a user, wherein payment data includes a plurality of payment details, each of which is generated by payment by one payment method, and the plurality of payment details are generated by two or more payment methods; determining that there is payment relevance indicating that two payment details among the plurality of payment details result from one payment action; generating integrated payment details by integrating the payment details determined to have the payment relevance; and returning modified payment data including consolidated payment details to the user. The technology is developed with the "2021 Artificial Intelligence Technology Commercialization Support Project" (task number: CY210071) among industry-academia-research institute cooperation projects in Seoul through development of an AI solution which provides hyper-personalized customized management and recommendation services for modern people using subscription services which become a novel consumption pattern due to COVID-19. Accordingly, a higher quality of service can be provided to the user.

Description

Apparatus, method, system and computer readable storage medium for managing payment details

The present invention relates to an apparatus, method, system, and computer readable storage medium for integrating and managing payment details paid using a plurality of payment means, specifically, financial payment details.

Unless otherwise stated herein, the subject matter described in this section is not prior art to the claims in this application and is not to be considered prior art by reason of being described in this section.

Modern people consume through various payment methods, including account transfer, debit card, credit card, mobile phone micropayment, and simple pay such as Naver Pay. However, due to the diversification of payment methods, it is difficult to grasp the entire payment details until all payment details are separately checked and compared.

Of course, an expenditure management service in the form of managing the user's expenditure is currently provided, but the service simply shows the user's payment history in the latest order first, and at the bottom, shows the past payment history in time and date order. Since it is limited to the number of payments, it is difficult for the user to intuitively check which of the numerous payment details is a regular payment.

Accordingly, there is an increasing demand for an integrated management system capable of accurately determining payment details regularly spent through various payment means and providing the information to users.
This technology is the '2021 Artificial Intelligence Technology Commercialization Support Project' (Task Number: CY210071) among industry-academia-research-institute cooperation projects in Seoul Metropolitan City It is a technology developed through the development of an AI solution that provides

Korean Patent Publication No. 10-2019-0065924 (Publication date: 2019.06.12)

The present disclosure is to solve the above problems, and presents an apparatus, method, system, and computer readable storage medium for managing payment information.

In some embodiments of the present disclosure, a payment information management method is described. An exemplary payment information management method is a step of obtaining payment data at the request of a user, wherein the payment data includes a plurality of payment details, and each of the plurality of payment details is generated by payment by one payment method , obtaining payment data; Determining that there is a payment connection indicating that two payment details among a plurality of payment details result from one payment action; generating integrated payment details by integrating the payment details determined to have payment relevance; and returning payment data including integrated payment details to the user.

In addition, other methods and systems for implementing the present invention and computer readable recording media for recording computer programs for executing the methods are also achieved.

According to the present invention, it is possible to prevent a user's payment details from being aggregated in duplicate or from being mistaken for money transfer details to the user's account as income. In addition, by presenting integrated payment details to the user, it is possible to provide an improved user experience by allowing the user to comprehensively grasp the payment details. Furthermore, the process of managing payment information according to the present invention can be performed using other related services, such as subscription services (payment management, subscription management, recommendation management, expenditure management), change services (regular payment break, payment method change) and cancellation services ( By combining with regular payment management services such as cancellation route, cancellation navigation), it is possible to provide users with more improved quality of service.

The above brief summary and description of effects are merely illustrative and are not intended to limit the technical details intended in the present disclosure. In addition to the foregoing exemplary embodiments and technical features, additional embodiments and technical features may be understood by referring to the following detailed description and accompanying drawings.

The foregoing and other features of the present disclosure will become sufficiently apparent from the following description with reference to the accompanying drawings. Understanding that these drawings illustrate only a few embodiments according to the present disclosure and, therefore, should not be regarded as limiting of its scope, the present disclosure will be described in greater detail and detail through the use of the accompanying drawings. It will be.
1 is a diagram showing the configuration of an entire system 100 for managing payment information according to some embodiments of the present disclosure.
2 is a diagram showing in detail the internal configuration of the payment information management device 200 according to some embodiments of the present disclosure.
3 is a flow diagram illustrating an exemplary process for managing payment information, in accordance with some embodiments of the present disclosure.
4 is an example of a structure of payment data obtained according to some embodiments of the present disclosure.
5 is an example of a modified payment data structure created according to some embodiments of the present disclosure.
6 is a user interface screen displaying integrated payment details, according to some embodiments of the present disclosure.
7 illustrates a computer program product that may be used to manage payment information, in accordance with at least some embodiments of the present disclosure.
8 is an exemplary block diagram of a computing device arranged in accordance with at least some embodiments of the present disclosure.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The detailed description of the present invention which follows refers to the accompanying drawings which illustrate, by way of illustration, specific embodiments in which the present invention may be practiced. It should be understood that the various embodiments of the present invention are different from each other but are not necessarily mutually exclusive. Combinations of each block of the accompanying configuration diagram (block diagram) and each step of the flowchart in this disclosure may be performed by computer program instructions. Each such block or step may represent a module, segment or portion of code that contains one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative embodiments it is possible for the functions recited in blocks or steps to occur out of order. For example, two blocks or steps that are shown adjacent or in sequence may in fact be performed substantially concurrently, or the blocks or steps may sometimes be performed in reverse order depending on their function.

It should also be understood that the location or arrangement of individual components within each disclosed embodiment may be changed without departing from the spirit and scope of the invention. Accordingly, the detailed description set forth below is not to be taken in a limiting sense, and the scope of the present invention, if properly described, is limited only by the appended claims, along with all equivalents as claimed by those claims. Similar reference numerals in the drawings indicate the same or similar functions in various aspects, and the form may be exaggerated for convenience.

Meanwhile, the terms used in the present invention are terms used to appropriately express preferred embodiments of the present invention, which may vary according to a user's intention or customs in the field to which the present invention belongs. Therefore, definitions of these terms should be understood based on the content throughout this specification. Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily practice the present invention.

Composition of the whole system

1 is a diagram showing the configuration of an entire system 100 for managing a service based on regular payment according to an embodiment of the present invention.

Referring to FIG. 1, the entire system 100 according to an embodiment of the present invention includes a communication network 110, a payment information management system 120, a user terminal 130, a payment server 140 and a merchant server 150 It can be configured to include.

First, the communication network 110 according to an embodiment of the present invention is a network capable of performing a series of data transmission and reception operations for data transmission and information exchange, regardless of its communication mode, such as wired and / or wireless can be configured.

For example, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), an Integrated Services Digital Network (ISDN), and a wireless LAN (wireless LAN). It may be any one of a LAN) or a mobile telecommunication network, or various types of wired/wireless communication networks connected and configured by a combination thereof.

Preferably, the communication network 110 configured according to the present invention may be an Internet network capable of using World Wide Web (WWW) services. Through this communication network 110, devices such as one or more user terminals 110, payment information management system 120, and one or more merchant servers 130, which will be described later, can transmit and receive data with each other. .

The payment information management system 120 according to some embodiments of the present invention may receive a user's request for the payment information management system 120 to call the user's payment details from the user terminal 130, such Payment details may be received from one or more payment servers 140 based on a user's request. In some other examples, the user may directly transmit or input payment details to the payment information management system 120, and the payment information management system 120 may acquire the received or input payment details. In this way, the payment information management system 120 may collect payment details for each user requested from one or more user terminals 130 .

The collected payment details may be generated from various payment methods, and some of them may overlap with other payment details. The payment information management system 120 according to the present invention may analyze and integrate the collected payment details, and use a payment information management service that returns the integrated payment details to the user terminal 130 or the integrated payment details A service associated with a payment information management service may be provided. An operation performed by the payment information management system 120 will be described in more detail with reference to FIG. 2 below.

Services associated with the payment information management service may vary according to required implementations. In some examples, the payment information management system 120 extracts periodic payments in which regular expenditures are made from among the collected payment details, and provides subscription services (payment management, subscription management, recommendation management, expenditure management), change service (regular payment breaks). , payment method change) and cancellation service (cancellation route, cancellation navigation). More specifically, the payment information management system 120 collects payment details regularly paid by various payment means of the user in real time, and extracts the collected payment details with an intelligent algorithm to provide an integrated periodic payment management service. can provide

In addition, the payment information management system 120 may provide a subscription service including any one or more of payment management, subscription management, recommendation management, and expenditure management in order to provide an efficient periodic payment management service to users. In addition, the payment information management system 120 may provide a change service capable of stopping regular payment or changing a regular payment method (eg, change of credit card company) during a period desired by the user. In addition, the payment information management system 120 may provide a cancellation service that displays various cancellation routes for each corresponding service or cancellation navigation on the screen of the user terminal so that the user can easily and conveniently cancel regular payment.

In the user terminal 130, the user accesses the payment information management system 120, interlocks the user's financial payment details from one or more payment servers 140 to the payment information management system 120, and provides financial Digital devices (first, second, and n-th user terminals, n are natural number).

More specifically, the user terminal 130 accesses the payment information management system 120, registers as a member, logs in, and receives a payment information management service for the corresponding user and a service related thereto.

The user terminal 130 receives the above-described payment information management service and services related thereto from the payment information management system 120 and is provided with a dedicated web and/or app that can input and transmit related information. More programs may be included.

As such, the user terminal 130 according to an embodiment of the present invention is a mobile communication terminal device, an information communication device, a multimedia terminal device, a wired terminal device, a wireless terminal device, and an IP (Internet Protocol) terminal device. The device can be employed without limitation. Specifically, the customer terminal device 130 includes a smart phone, a portable terminal, a mobile terminal, a foldable terminal, a personal digital assistant (PDA), PMP (Portable Multimedia Player) terminal, telematics terminal, personal computer, notebook computer, tablet PC, IPTV (Internet Protocol Television) terminal, smart TV, digital broadcasting terminal, digital signage device It is a digital device equipped with a memory means such as a microprocessor and equipped with an arithmetic capability, as long as it includes input means such as a keyboard and mouse for inputting information and includes wired/wireless communication functions. It may be adopted as a terminal device according to the invention.

In addition, the user terminal 130 may include a display means capable of displaying the service according to the present invention. Here, the display means is LCD (Liquid Crystal Display), TFTLCD (Thin Film Transistor LCD), OLED (Organic Light Emitting Diodes), Light Emitting Diodes (LED), AMOLED (Active Matrix Organic LED), Flexible Display and 3 It may be configured with a 3D display or the like. At this time, since the display unit may be configured to include a touch screen, some or all of the functions of the input unit may be performed.

Next, the payment server 140 according to an embodiment of the present invention is an operation server of the payment method selected by the user terminal 130 (eg, credit card, bank account, simple payment (Smart Pay)) (first, second, nth payment server, n is a natural number) or may be a concept including a separate payment agency server interworking with the operating server.

The payment server 140 is an operation server of a payment method affiliated with the payment information management system 120, and at this time, the payment server 140 includes a server of a payment agency service company such as a PG (Payment Gateway) Could be a concept. For example, as a company that acts as an agent for payment and transactions with financial institutions (card companies, banks) (associate member store), there is a credit card PG as a representative.

For example, when a user pays with a credit card at an Internet shopping mall, etc., the payment and settlement procedure is performed through the credit card PG, and the credit card PG company relays transaction and approval information between the shopping mall and the VAN operator. I can act as a proxy for settlement.

Finally, the seller server 150 according to an embodiment of the present invention may be a supplier's operating server (first, second, and n-th seller servers, where n is a natural number) that provides products and services to users.

More specifically, the seller server 150 is a server of affiliates that have entered into a product-related alliance with the payment information management system 120, and can provide various services for each industry. For example, various types of multimedia services such as Netflix, Watcha, and Melon, or services that are regularly paid in daily life, such as apartment management fees or water purification services, may be included.

Configuration of the payment information management device 200

In the following description, the internal configuration and components of the payment information management device 200 that performs various functions according to the present invention will be described.

2 is a diagram showing in detail the internal configuration of the payment information management device 200 according to some embodiments of the present disclosure. The payment information management system 120 described with respect to FIG. 1 is an example of the payment information management device 200 . Accordingly, the payment information management device 200 may be implemented in the same environment as the entire system 100 shown in FIG. 1 .

As shown in FIG. 2, the exemplary payment information management system 200 according to the present disclosure includes a user request receiving unit 210, a payment data collection unit 220, a payment connectivity evaluation unit 230, and an integrated payment details generation unit. 240, a modified payment data return unit 250, and a database 260 may be included.

User request receiver 210

The user request receiving unit 210 may receive a request for integrated management of payment data from a user. The user request receiving unit 210 may be implemented in various ways according to implementation aspects of the payment information management device 200 . In some examples, the user may be an individual user, and the user may use a smart phone, a portable terminal, a mobile terminal, a foldable terminal, or a personal digital assistant. : Payment information management device (200) using a personal terminal such as a PDA, PMP (Portable Multimedia Player) terminal, telematics terminal, personal computer, notebook computer, tablet PC, smart TV, etc. ) can communicate with.

In this example, the user may install an application provided to communicate with the payment information management device 200 in the user terminal, and the user terminal may execute the application to access the payment information management device 200. In this example, the user may perform a user registration procedure (eg, membership registration) through the installed application and log in. Thereafter, the user terminal may transmit a request for integrated management of its own financial payment details through an application, and the user request receiving unit 210 may receive such a user request. In this example, the user's request is the user's information for obtaining payment details, eg, the name of a credit card company or financial institution such as a bank, other information (eg, card number, ID, password, account number, etc.), the user's mobile phone number, personal certificate information, other authentication information (eg, ARS authentication, mobile phone authentication, etc.), and the like, but are not limited thereto.

In some other examples, the user may be a company or organization, and in this case, the user may directly access the API (Application Program Interface) of the payment information management device 200 using a user terminal. In this case, the user performs the functions of the payment data collection unit 220, the payment connectivity evaluation unit 230, the integrated payment details generation unit 240, and the corrected payment data return unit 250 of the payment information management device 200 A request for accessing an API may be transmitted, and the user request receiving unit 210 may receive such a request from the user.

In some other examples, the user may be a user of the payment information management device 200 . In this example, the user enters the payment information management device 200 using an input device (not shown) of the payment information management device 200, the payment data collection unit 220, the payment connectivity evaluation unit 230, and the integrated payment. Commands or commands for performing the functions of the details generation unit 240 and the corrected payment data return unit 250 may be input, and the user request receiving unit 210 may receive such user input.

Payment data collection unit (220)

The payment data collecting unit 220 may obtain payment data in response to the user's request received by the user request receiving unit 210 . In some examples, the payment data collection unit 220 may receive payment data from one or more external payment servers, for example, one or more payment servers 140 of FIG. 1 . In this example, the payment data collection unit 220 may use the user's information included in the user's request received by the user request receiver 210 to access an external payment server, and the connected payment server may access the user's information. Payment data including payment details may be requested and received. In some other examples, the payment data collection unit 220 may receive payment data directly input by the user.

Payment data may include a plurality of payment details. Each payment detail is generated by one payment action, and is generated by one payment method. Payment details may include a variety of information related to a payment action. Payment details include, for example, payment method identifier (eg, card number), type of payment method (eg, credit card, bank, simple payment, etc.), name/identifier of the issuer of the payment method (eg, card company, bank name, etc.) ), a summary of payment details, name of payment store, payment store number, date and time of payment, currency of payment, amount of consumption, amount of income, balance after transaction, user memo, and the like. Additionally, when obtaining credit card payment details, the payment data collector 220 may further obtain information on the summed bill amount as well as individual payment details.

Payment data collected by the payment data collector 220 may be stored in the database 260 .

Payment connectivity evaluation unit (230)

The payment linkage evaluation unit 230 extracts payment details that have payment linkage with respect to a plurality of payment details collected by the payment data collection unit 220 . "Payment linkage" between payment details means that those payment details are generated from one payment activity. For example, when a user pays 1,000 won using debit card B linked to bank account A, the card company of debit card B creates card use details and payment details (first payment details) for 1,000 won, and The bank of A creates transfer details (second payment details) of 1,000 won. In this example, the first and second payment details are payment details with payment linkage, and result from one payment action. The payment data collection unit 220 may collect payment data including payment details having payment linkage.

The payment linkage evaluation unit 230 determines whether two payment details among a plurality of payment details have payment linkage. Even if one payment details and another payment details have payment linkage with each other, the corresponding information included in the payment details may be different from each other. For example, in the case of payment using a credit card (or debit card), the usage indicated in the payment details of the credit card (ie, the name of a member store registered with the card company) indicates that the credit card payment is transferred from the bank account to the credit card company. It may differ from the brief indicated in the bank account transfer statement, withdrawn. In another example, when a user makes an overseas payment using a credit card, the currency displayed in the payment details of the credit card (eg, US dollars) and the currency of the corresponding transfer details of the bank account (eg, KR won) may be different. can In another example, when paying for a specific usage fee (eg, communication fee) with a credit card, there is a difference of 48 hours or more between the payment time indicated in the payment details of the credit card and the time when the corresponding transfer in the bank account was performed there is As described above, even when the predetermined information of the payment details is different, the payment connectivity evaluation unit 230 according to the present disclosure may evaluate payment connectivity between the payment details as described below.

In some embodiments, the payment relevance evaluation unit 230 determines the similarity between the two payment details, and when the calculated similarity is greater than or equal to a predetermined value, determines that the payment relevance has payment relevance, and associates them with each other. The payment connectivity evaluation unit 230 may perform pre-processing on payment data, that is, a plurality of payment details, before evaluating payment connectivity between payment details, and modify each payment details into a format suitable for evaluation of payment connectivity.

In some examples, the payment connectivity evaluation unit 230 may calculate a similarity using a similarity function. The degree of similarity may be calculated based on, for example, at least one of distance-based calculation, angle-based calculation, covariance-based calculation, correlation calculation, and frequency-based calculation.

In the case of using a distance-based calculation, for example, a Euclidean distance function, a Manhattan distance function, or a Minkowski distance function may be used. The payment connectivity evaluation unit 230 may calculate a similarity between payment details by calculating a vector distance between elements included in the payment details using a Euclidean distance function, a Manhattan distance function, and a Minkowski distance function. When the number of elements included in the payment details increases, that is, as the dimension of the entity increases, it may be relatively advantageous to use the Manhattan distance function, while the Minkowski distance is known to be a generalization of the Euclidean distance function and the Manhattan distance function.

In the case of using an angle-based operation, for example, a cosine similarity function may be used. In the case of the cosine similarity function, the similarity is evaluated by focusing on the direction rather than the magnitude of the vector. In case of using covariance-based calculation or correlation-based calculation, for example, Mahalanobis distance function or Pearson's correlation coefficient may be used. In the case of using frequency-based calculation, for example, Jacquard similarity may be used.

In an alternative or additional example, the payment connectivity evaluation unit 230 may determine a similarity between two payment details using an artificial neural network. Such an artificial neural network may use an artificial neural network model trained in advance with respect to a plurality of payment details. Depending on the required implementation, this artificial neural network receives all of the plurality of payment details and outputs a similarity between any two of the plurality of payment details, or takes two pairs of payment details as input and calculates the similarity between them. It can be implemented to output.

When an artificial neural network is used, learning may be performed in advance on the artificial neural network model. In some examples, learning of the artificial neural network model may be performed using payment data of various users collected by the payment data collection unit 220 . The operator of the payment information management system 100 may perform de-identification processing, for example, removing user information, to use various payment data for learning of an artificial neural network model, and perform labeling of the payment data to Supervised learning can be performed.

In the case of performing comparison on any two payment details among a plurality of payment details, some of the plurality of comparisons may be unnecessary calculations. Therefore, in determining the degree of similarity, an additional condition for excluding unnecessary comparisons may be further used.

In some examples, when the payment linkage evaluation unit 230 compares two payment details with respect to a plurality of payment details, a pair of payment details that are the same payment method may not perform the comparison. That is, the payment connectivity evaluation unit 230 may compare two payment details with different payment methods. In the case of two payment details with the same payment method, since they are not due to one payment action, the processing speed of the payment connectivity evaluation unit 230 can be improved by excluding comparison of payment details with the same payment method. On the other hand, the probability of occurrence of an error in the evaluation of payment connectivity can be reduced. Here, it should be noted that, even if the same type of payment method is not the same payment method, it is not excluded from the payment connectivity evaluation.

In some other examples, the payment connectivity evaluation unit 230 may not compare corresponding payment details when a difference between predetermined elements such as payment time and payment amount is greater than a preset value.

As described above, the payment connectivity evaluation unit 230 calculates/determines the similarity of two payment details and compares them. However, depending on the payment method, an additional technique may be used. For example, payment details of a credit card include payment details for individual payments, but in a bank account, a charge sum of individual payment amounts of these credit cards is transferred. Accordingly, when comparing payment details of a credit card and transfer details of a bank account, the payment linkage evaluation unit 230 may additionally consider a bill date or a transfer date included in a credit card bill. In this example, the payment linkage evaluation unit 230 may link the credit card payment details and the charged amount of the bill including the corresponding payment details and utilize them as intermediate data.

In another example, when comparing bank accounts with bank accounts, transfers between bank accounts may not be evaluated as expenditures by comparing details of deposits and withdrawals between bank accounts.

In some additional embodiments, the payment connectivity evaluation unit 230 may determine payment method connectivity and evaluate payment connectivity based at least in part on the payment method connectivity.

Since some payment methods are continuously used for one payment activity, it can be seen that there is connectivity between payment methods. Accordingly, the payment connectivity evaluation unit 230 may determine connectivity between a plurality of payment means. Payment method association may be evaluated in advance before payment data is received, but is not limited thereto, and may be performed after payment data is received.

In some examples, the payment connectivity evaluation unit 230 may perform a test payment with respect to a predetermined payment method. Usually, the use of a credit card leads to the use of another credit card or bank account transfer, and the use of simple payment leads to the use of a credit card or bank account transfer. The payment connectivity evaluation unit 230 may determine the highest payment method by considering the above relationship. In some examples, the payment relevance evaluation unit 230 uses a top-level payment method, eg, easy payment or a credit card, to obtain a minimum amount (eg, "1 won") with an arbitrary requirement (eg, "red walnut"). It is possible to perform a test payment to pay for , and request the payment data collection unit 220 to receive a plurality of payment details resulting from this test payment. Thereafter, the payment connectivity evaluation unit 230 may determine payment details having the same brief from a plurality of payment details resulting from the test payment, and determine that a plurality of payment methods corresponding to the determined plurality of payment details have payment method connectivity. have.

In some other examples, the payment connectivity evaluation unit 230 may determine whether there is payment method connectivity between two payment methods by comparing payment details. The payment data acquired by the payment data collection unit 220 may include a set of payment details for each payment method. The payment linkage evaluation unit 230 may determine the similarity of sets of payment details for each payment method. Determination of similarity between payment methods may be performed in a manner similar to the above-described determination of similarity between payment details.

For example, the payment connectivity evaluation unit 230 may use a cosine similarity function to calculate similarity, and may compare each payment details of each payment method with payment details of other payment methods. The payment relevance evaluation unit 230 may determine that the two payment methods have payment method relevance when the average of similarities computed by comparing a plurality of payment details is equal to or greater than a predetermined value (eg, 70%).

The payment linkage evaluator 230 may determine whether or not two payment details have payment linkage based at least in part on the linkage of a payment method. In one example, the payment connectivity evaluation unit 230 may use payment method connectivity before evaluating payment connectivity. For example, the payment linkage evaluation unit 230 may compare only payment details of payment methods that have linkage with payment methods.

In another example, the payment connectivity evaluation unit 230 may use the payment method connectivity after the payment connectivity evaluation. For example, if the payment method corresponding to the two payment details evaluated as having payment connectivity has no payment method connectivity, the payment connectivity evaluation unit 230 determines that the evaluation of payment connectivity is not valid, and performs related follow-up processing, e.g., It is possible to perform exclusion of evaluated payment connectivity, modification of evaluated payment connectivity, and feedback on the artificial neural network model used.

Integrated payment details generation unit (240)

The integrated payment details generation unit 240 may generate integrated payment details by integrating two or more payment details determined by the payment relevance evaluation unit 230 to have payment relevance. For example, when the payment relevance evaluation unit 230 determines that the first to second payment details among the first to tenth payment details have payment relevance and the fourth to sixth payment details have payment relevance, generating integrated payment details The unit 240 may generate a first integrated payment detail by integrating the first and second payment details, and generate a second integrated payment detail by integrating the fourth to sixth payment details.

In some examples, some of the information included in the plurality of payment details integrated by the integrated payment details generation unit 240 may not be included in the integrated payment details, and the information not included is stored in the database 260 for future use. can be stored separately.

In some examples, the integrated payment details generation unit 240 may add partial details that may indicate payment connectivity of a plurality of payment details to each payment details to be integrated. Such partial details may include route identifier information indicating an upper level payment detail generated prior to the corresponding payment detail, eg, a higher level payment method used prior to a payment method corresponding to the corresponding payment detail. The root identifier information may have a null value or a predetermined value in the case of the highest payment details.

Modified payment data return unit (250)

The corrected payment data return unit 250 generates corrected payment data including the integrated payment details generated by the integrated payment details generator 240 and returns it to the user.

The corrected payment data return unit 250 may integrate payment details included in the payment data using integrated payment details. In integrating a plurality of payment details included in the payment data, the payment details included in the integrated payment details may use the integrated payment details. Since the payment details included in the integrated payment details are due to a single payment action, the user has paid only the amount of payment for one time. Accordingly, the corrected payment data returning unit 250 may avoid redundant summing by using the integrated payment details when integrating or summing the payment amounts of a plurality of payment details included in the payment data.

Specific examples of integrated payment details and modified payment data will be described below with reference to FIGS. 4 and 5 .

4 is an example of a structure of payment data obtained according to some embodiments of the present disclosure. In some examples, payment data acquired by the payment data collection unit 220 or payment data pre-processed by the payment connectivity evaluation unit 230 may have a data structure shown in FIG. 4 . As shown in FIG. 4, in the structure of payment data, one or more payment details may be included for each payment method, and each payment detail is "vendor_type", "store_name", "store_number", "memo", and "payment_date" ", "outbound", "inbound", and "balance", and their corresponding values.

5 is an example of a modified payment data structure created according to some embodiments of the present disclosure. In some examples, the payment data shown in FIG. 4 may be modified like the corrected payment data shown in FIG. 5 by the integrated payment details generation unit 240 and the corrected payment data returning unit 250 . As shown in FIG. 5 , the modified payment data may include integrated payment details, and the integrated payment details include a plurality of payment details with payment linkages. Each payment detail includes route identifier information specifying a parent payment detail. As shown in the payment history of FIG. 5 where “id” is 1, the root identifier information of the highest payment history has a null value. The data structures shown in FIGS. 4 and 5 are merely examples for explaining the structure of payment data and correction data according to the present invention, and are not limited thereto, and in actual implementation, the structure of payment data may have various formats. have.

The corrected payment data return unit 250 may allow the corrected payment data to have a format suitable for being displayed on the user's user terminal or display device. An example of the integrated payment details included in the modified payment data being displayed on the user terminal is shown in FIG. 6 .

Payment information management process

3 is a flow diagram illustrating an example process 300 for managing payment information, in accordance with some embodiments of the present disclosure. For example, process 300 may be performed under the control of a computing device such as payment information management system 120 and/or payment information management device 200 of FIG. 1 . Process 300 illustrated in FIG. 3 may include one or more actions, functions or actions as illustrated by blocks S310, S320, S330, S340 and/or S350. The schematic operations illustrated in FIG. 3 are provided by way of example only, and some of the operations may be optional, combined into fewer operations, or extended with additional operations, without departing from the essence of the disclosed embodiment. have. Process 300 may start at block S310 of receiving a user's request.

In block S310, the computing device receives a request for integrated management of payment data from the user. The computing device may perform various functions described with respect to the user request receiving unit 210 of FIG. 2 , for example. Thus, in some examples, the computing device may receive a request from an external user terminal. In some other examples, the computing device may receive a request for integrated management of payment data from a user of the computing device. Process 300 may continue from block S310 to block S320 to "obtain payment data".

At block S320, the computing device obtains payment data in response to the user's request received at block S310. The computing device may perform various functions described with respect to the payment data collection unit 220 of FIG. 2 , for example. Accordingly, the computing device may request payment data from an external payment server in response to a user's request and receive payment data in response thereto, or may directly receive payment data from the user. Process 300 may continue from block S320 to block S330 of "determining payment linkage between two payment details".

In block S330, the computing device extracts payment details having payment linkage with respect to a plurality of payment details included in the payment data obtained in block S320. The computing device may perform various functions described with respect to the payment connectivity evaluation unit 230 of FIG. 2 , for example. Accordingly, the computing device may determine a degree of similarity whether the two payment details have payment relevance. A predetermined function and/or an artificial neural network may be used to determine the degree of similarity. Further, in some examples, the computing device may evaluate the connectivity of the payment means and, based at least in part on the connectivity of the payment means, evaluate whether the payment details have connectivity. Process 300 may continue from block S330 to block S340 of “generating integrated payment details”.

In block S340, the computing device generates integrated payment details by integrating the payment details with payment linkage extracted in block S330. The computing device may, for example, perform various functions described with respect to the integrated payment details generation unit 240 of FIG. 2 . Therefore, in the integrated payment details generated by the computing device, a precedence relationship between each payment details, that is, a higher and lower relationship between payment means corresponding to each payment detail may be indicated. For example, each payment details in the integrated payment details may include route identifier information indicating a higher level payment means, and the root identifier information for the payment details by the higher level payment means may be null or a predetermined value. Process 300 may continue from block S340 to block S350 of "return corrected payment data".

In block S350, the computing device generates corrected payment data including the integrated payment details generated in block S340, and returns the generated corrected payment data to the user. For example, various functions described with respect to the corrected payment data returning unit 250 of FIG. 2 may be performed.

6 is a user interface screen displaying integrated payment details, according to some embodiments of the present disclosure. As shown in FIG. 6, in the integrated payment details, linked payment methods, date and time, amount, etc. are integrated into one item, and an explanation representing linked payment details, such as "Medium, I paid $5" can include The example shown in FIG. 6 shows an example of displaying integrated payment details on a user terminal, and the display of integrated payment details according to the present invention is not limited thereto and may have various modifications.

7 illustrates a computer program product 700 that may be used to manage payment information, in accordance with at least some embodiments of the disclosure. An exemplary embodiment of an exemplary computer program product is provided using a signal bearing medium 710. In some embodiments, signal bearing medium 710 of one or more computer program products 700 may include computer readable medium 730 and/or recordable medium 740 .

Instructions 720 included in signal bearing medium 710 may be executed by a computing device such as payment information management system 120 and/or payment information management device 130 . When the instruction 720 is executed, one or more instructions for causing the computing device to obtain payment data at the request of the user, wherein the payment data includes a plurality of payment details, and each of the plurality of payment details corresponds to one payment created by payment by means, and a plurality of payment details are created by two or more payment means; one or more instructions for determining that there is a payment linkage indicating that two payment details among a plurality of payment details result from one payment action; one or more instructions for generating integrated payment details by integrating the payment details determined to have payment relevance; and at least one of one or more instructions for returning modified payment data including integrated payment details to the user.

8 depicts a general purpose computing device 800 that may be used to implement a system for managing payment details, in accordance with at least some embodiments described herein. In this example, the components of computing device 800 may be arranged or configured for a system. In a very basic configuration 802 , computing device 800 typically includes one or more processors 804 and system memory 806 . A memory bus 808 may be used for communication between the processor 804 and system memory 806 .

Depending on the required configuration, the processor 804 may be of any type including, but not limited to, a microprocessor (μP), microcontroller (μC), digital signal processor (DSP), or any combination thereof. Processor 804 may include one or more levels of caching, such as level 1 cache 810 and level 2 cache 812 , processor core 814 and registers 816 . The exemplary processor core 814 may include an arithmetic logic unit (ALU), a floating point unit (FPU), a digital signal processing core (DSP core), or any combination thereof. An exemplary memory controller 818 may also be used with processor 804 , or in some implementations, memory controller 818 may be an internal component of processor 804 .

Depending on the configuration required, system memory 806 may be of any type, including but not limited to volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. System memory 806 may include an operating system 820 , one or more applications 822 and program data 824 . Application 822 includes functions described with respect to payment information management system 130 of FIG. 1 and payment information management device 200 of FIG. 2 and/or operations described with respect to process 300 of FIG. 3 herein. instructions 826 that can be arranged to perform the functions described in . Program data 824 may include data 828 that may be used to implement instructions 826 . In some examples, application 822 may be arranged to operate with program data 824 on operating system 820 to implement the instructions described herein.

Computing device 800 may have additional features or functionality, and additional interfaces to facilitate communication between basic configuration 802 and any required devices and interfaces. For example, bus/interface controller 830 may be used to facilitate communication between base component 802 and one or more data storage devices 832 over storage interface bus 834 . The data storage device 832 may be a removable storage device 836, a non-removable storage device 838, or a combination thereof. Examples of removable and non-removable storage devices include magnetic disk devices such as flexible disk drives and hard disk drives (HDDs), optical disks such as compact disk (CD) drives or digital versatile disk (DVD) drives, to name a few. drives, solid state drives (SSD), and tape drives. Exemplary computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. have.

System memory 806 , removable storage 836 and non-removable storage 838 are examples of computer storage media. Computer storage media may include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage device, magnetic cassette, magnetic tape, magnetic disk storage device or other magnetic storage device, or It includes, but is not limited to, any other medium that can be used to store desired information and that can be accessed by computing device 800 . Any such computer storage media may be part of computing device 800 .

Computing device 800 facilitates communication from various interface devices (e.g., output device 842, peripheral interface 844, and communication device 846) via bus/interface controller 830 to base configuration 802. It may also include an interface bus 840 for Exemplary output devices 842 include a graphics processing unit 848 and an audio processing unit 850, which may be configured to communicate via one or more A/V ports 852 to various external devices, such as displays or speakers. can Exemplary peripheral interface 844 includes serial interface controller 854 or parallel interface controller 856, which via one or more I/O ports 858 input devices (e.g., keyboard, mouse, pen, voice input). devices, touch input devices, etc.) or other peripheral devices (eg, printers, scanners, etc.). An exemplary communication device 846 includes a network controller 860, which may be arranged to facilitate communication with one or more other computing devices 862 over a network communication link via one or more communication ports 864. .

A network communication link may be one example of a communication medium. Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media. A “modulated data signal” may be a signal that has one or more of its characteristics set or changed in such a way as to encode information within the signal. By way of non-limiting example, communication media may include wired media such as a wired network or direct wired connection, and wireless media such as acoustic, radio frequency (RF), microwave, infrared (IR) and other wireless media. can include The term computer readable media as used herein may include both storage media and communication media.

Computing device 800 may be a mobile phone, personal data assistant (PDA), personal media player device, wireless web-watch device, personal headset device, special purpose device, or hybrid including any of the above functionality. It may be implemented as a part of a small-form factor portable (or mobile) electronic device such as a device. Computing device 800 may also be implemented as a personal computer including both laptop computer and non-laptop computer configurations.

In the detailed description of the present invention, specific details such as specific components and limited embodiments and drawings have been described, but this is only provided to help a more general understanding of the present invention, and the present invention is not limited to the above embodiments. , Those skilled in the art to which the present invention pertains may seek various modifications and variations from these descriptions. Therefore, the spirit of the present invention is not limited to the above-described embodiments, and not only the claims to be described later, but also all modifications equivalent or equivalent to the claims belong to the scope of the spirit of the present invention. will do it

100: entire system
110: communication network
120: Payment information management system
130: user terminal
140: payment server
150: Merchant Server
200: payment information management device
210: user request receiver
220: payment data collection unit
230: Payment connectivity evaluation unit
240: integrated payment details generation unit
250: Modified payment data return unit
260: database

Claims (10)

A payment information management method performed under the control of a computing device, comprising:
Acquiring payment data, including a plurality of payment details generated by each payment means, at a user's request;
Determining that there is a payment connection indicating that at least two payment details among the plurality of payment details result from one payment action;
generating integrated payment details by integrating the payment details determined to have the payment linkage; and
Returning modified payment data including the integrated payment details to the user;
The payment action includes withdrawal, deposit or transfer between the same users,
The determining step is
Including that one payment act appears as two or more withdrawal details of the same amount, two or more deposit details of the same amount, or deposit and withdrawal details of the same amount,
The determining step is
It is performed by comparing two or more payment details with different payment methods,
The integrated payment details,
It is generated to include two or more partial details corresponding to each of the two or more payment details determined to have payment relevance,
The two or more partial details include identifier information indicating the corresponding payment details and root identifier information indicating the upper payment details of the corresponding payment details. According to claim 1,
The determining step is
Determining payment method connectivity indicating connectivity between two or more payment methods associated with the plurality of payment details; and
and determining, based at least in part on the payment method association, that the at least two payment details have payment association. According to claim 2,
The step of determining the payment method linkage is
determining a highest payment method among the two or more payment methods;
performing a test payment to the highest payment method; and
and determining connection with the payment method based on payment data by the test payment. According to claim 2,
The payment information management method comprising determining a connection between payment methods includes calculating a similarity between payment methods using a set of payment details for each payment method. delete According to claim 1,
The determining step is
determining a degree of similarity between the at least two payment details; and
And if the calculated similarity is equal to or greater than a predetermined value, associating as payment details having payment linkage. According to claim 6,
Wherein the similarity is calculated based on at least one of a distance-based calculation, an angle-based calculation, a covariance-based calculation, a correlation calculation, and a frequency-based calculation. According to claim 6,
Wherein the step of determining the similarity is performed using an artificial neural network pre-learned for payment connectivity. delete According to claim 1,
If there is no upper payment history of the payment history corresponding to the specific partial history, the route identifier information of the specific partial history has a null value, payment information management method.

Images