JP2020149316A - Data processor, data processing method, and program - Google Patents

Abstract

To provide unified usage statement data associated with data of card payment performed by multiple persons, set transactions to be restricted in advance to prevent the occurrence of such transactions, and notify a card contractor and a card user of them.SOLUTION: A data processor unifies and provides deposit/withdrawal details data related to a first card identifier and a second card identifier associated with each other. When a transaction based on payment data received from an affiliated store terminal is a transaction preset and restricted by a user, the data processor notifies an affiliated store, a card contractor, and a card user of it.SELECTED DRAWING: Figure 8

Description

The present invention relates to data processing devices, data processing methods and programs. More specifically, the present invention relates to a data processing device, a data processing method, and a program that provides a household management service for associating card payment data performed by a plurality of persons by associating a plurality of card accounts. The present invention also relates to a data processing device, a data processing method, and a program that provide various notification services based on card payment data.

Cashless payments are gradually becoming widespread through various payment methods. However, although cashless payments are becoming widespread on an individual basis, it is rare for multiple people to share one cashless payment method, and only a limited number of situations have been known. By inserting the parent prepaid card and child prepaid card in succession and entering the number of participants, it has a function to settle the amount including the child prepaid card from the parent prepaid card without paying from the child prepaid card. Although a multi-person settlement system (Patent Document 1) using an automatic ticket gate compatible with parent-child prepaid cards was known, the situations in which it could be used were still limited.

In addition, cash has become the mainstream payment method for some generations such as children and the elderly. The mainstream of money flow between families is cash, for example, when parents give their children pocket money. Try to use the household account book creation system (Patent Document 2) that manages information on individual products and services for credit card payments and expenditure items, or set up a common wallet for the money to be used systematically every month to manage the household budget. Even if you try to do it, it is often difficult to centrally manage your wallet because the family's outing and spending activities are carried out separately, which obscures budget management and spending management. For this reason, even if a common wallet is provided, situations such as not being able to see wasteful spending and not being able to grasp how much more to use will occur.

Japanese Unexamined Patent Publication No. 2005-135361 Japanese Unexamined Patent Publication No. 2016-042236 (Patent No. 5922197)

Although cashless payments are becoming widespread, it has been difficult to grasp the flow of money between families and the usage status and balance of individual family members. Regarding pocket money and remittances that are handed over to each person at home and managed by each person, the flow of cash is the main, and there is the inconvenience of handing over cash regularly, so even if cash is used, the usage details can be understood. It was difficult to manage the household budget by grasping the income and expenditure status of each member of the family.

Even if the wallet is shared, a prepaid card that can be used by multiple people, such as Patent Document 1, cannot systematically realize a wallet that covers a wide range of age groups, including oneself, spouse, children, and parents. It was.

Even in families, outing and spending behaviors are often separate, unless there are special circumstances. For this reason, it is also burdensome to confirm the safety of the family, such as whether it is safe and whether it is in an abnormal situation.

The present invention has been made to solve such a problem, and is a data processing device and data processing that provides a household management service for associating card payment data performed by a plurality of people by associating a plurality of card accounts. The purpose is to provide methods and programs. Another object of the present invention is to provide a data processing device, a data processing method, and a program that provide various notification services based on card payment data.

The data processing device according to one aspect of the present invention is
A request for acquisition of centralized usage detail data is received from the first user device, and the first card identifier and the second card identifier associated with each other are specified based on the user identifier included in the acquisition request. Acquires the specified deposit / withdrawal detail data associated with the first card identifier and the second card identifier, and transmits the data to the first user device based on the acquired deposit / withdrawal detail data. As a first means of generating centralized usage statement data for
The second card identifier is specified based on the payment card number included in the payment data received from the member store terminal, and one or more transaction restriction information associated with the specified second card identifier is acquired. , The transaction information included in the received settlement data and the information indicating the transaction restriction are provided on the condition that the information indicating the transaction restriction is set in any of the acquired one or more transaction restriction information. Based on the set one or more transaction restriction information, it is determined whether or not the transaction based on the received settlement data corresponds to the restricted transaction, and the transaction based on the received settlement data is It is provided with a second means of transmitting a first non-settlement notification to the member store terminal on the condition that it corresponds to a restricted transaction.

The data processing method executed by the data processing apparatus according to another aspect of the present invention is
A request for acquisition of centralized usage detail data is received from the first user device, and the first card identifier and the second card identifier associated with each other are specified based on the user identifier included in the acquisition request. Acquires the specified deposit / withdrawal detail data associated with the first card identifier and the second card identifier, and transmits the data to the first user device based on the acquired deposit / withdrawal detail data. The first processing method for generating centralized usage detail data for
The second card identifier is specified based on the payment card number included in the payment data received from the member store terminal, and one or more transaction restriction information associated with the specified second card identifier is acquired. , The transaction information included in the received settlement data and the information indicating the transaction restriction are provided on the condition that the information indicating the transaction restriction is set in any of the acquired one or more transaction restriction information. Based on the set one or more transaction restriction information, it is determined whether or not the transaction based on the received settlement data corresponds to the restricted transaction, and the transaction based on the received settlement data is It is provided with a second processing method of transmitting a first non-settlement notification message to the member store terminal on the condition that it corresponds to a restricted transaction.

According to the present invention, a household management service that can separately manage the balance of each individual and provides centralized usage statement data in which card payment data performed by a plurality of persons is associated with each other by associating a plurality of card accounts. Can be realized. According to the present invention, by setting the transactions to be restricted in advance, the occurrence of such transactions can be prevented, and the card contractor or the card user is notified that such a transaction has occurred. be able to. Further, according to the present invention, even if the family members are acting separately, the safety confirmation can be automatically performed by the notification service based on the card payment data.

A detailed understanding of the embodiments disclosed herein can be obtained from the following description illustrated in connection with the accompanying drawings.

It is a block diagram of the whole system including the data processing apparatus which concerns on one Embodiment. It is a system block diagram of the data processing apparatus which concerns on one Embodiment. It is a figure explaining an example of the data structure of the user master which concerns on one Embodiment. It is a figure explaining an example of the data structure of the settlement data which concerns on one Embodiment. It is a figure explaining an example of the data structure of the deposit / withdrawal details which concerns on one Embodiment. It is a figure which illustrates the user interface for setting and registering some data items of a user master. It is a figure explaining the deposit / withdrawal detail data generation processing executed by a data processing apparatus. It is a figure explaining the usage detail data unification process executed by a data processing apparatus. It is a figure explaining the card use notification processing executed by a data processing apparatus. It is a figure explaining the restriction transaction corresponding notification processing executed by the data processing apparatus.

(overall structure)
Hereinafter, embodiments of the present invention will be described in detail. As a means of cashless payment, for example, a prepaid card (prepaid payment method), a debit card (immediate payment method) and a credit card (postpaid payment method) are used, but in the present specification, the prepaid card is mainly used. An embodiment of card payment will be described. The gist of the present invention is not limited to prepaid card payment, and can be applied to other payment methods. Further, in the present specification, the "card" may be a physically tangible card-shaped recording carrier, or may be in a form electronically realized by software, and is not limited thereto.

In the present specification, the case where Japanese yen is used as the type of transaction currency will be mainly described, but the present invention can be applied to other types of currencies, for example, conventional currencies such as US dollars. The gist of the present invention can be applied to virtual currencies such as Bitcoin (registered trademark) and electronic money of any kind.

FIG. 1 is a configuration diagram of the entire system including the data processing device 100 according to the embodiment of the present invention. The data processing device 100 is communicably connected to one or more merchant terminals 110 and one or more user devices 120 via a known network such as the Internet and a leased line. In FIG. 1, only one member store terminal 110 and one user device 120 are shown, but there may be a plurality of these. In this specification, the data processing device 100 is described as one device, but various processes executed by the data processing device 100 may be configured to be distributed and executed by a plurality of devices.

The data processing device 100 provides a household management service that provides centralized usage statement data in which data of card payments made by a plurality of persons are associated with each other by associating a plurality of card accounts. As described herein, one card account is identified by one card ID 304 and associated with one card balance. The data processing device 100 receives payment data from the member store terminal 110, and collectively provides the detailed data of the card payment of the related card account to the user device 120. For example, if a card contractor contracts for a spouse, child, or parent card in addition to his / her own card, the detailed data of the card payment made with each card is centralized and provided to the card contractor. .. The cards of oneself, spouse, child, and parent have different card numbers.

The data processing device 100 provides various notification services based on card payment data. Based on the received payment data, the data processing device 100 notifies the notification destination of the card contractor and / or the notification destination of the card user (for example, child, parent) of the occurrence of card payment and the payment content. Further, when the card contractor and / or the card user is about to carry out a transaction that matches the pre-restricted transaction, the data processing device 100 transmits a transaction prohibition notification to the member store terminal 110 and the card. It is also sent to the contractor and / or the card user's notification destination.

The member store terminal 110 may be a card payment terminal installed at the member store, which can process payment with a card issued by an issuer (prepaid payment method issuer), or the member store. It may be a system for electronic commerce operated by. The member store terminal 110 may be incorporated in the POS terminal. The member store terminal 110 transmits payment data (for example, authorization data) to the data processing device 100 at the time of card payment, and receives the result (for example, transaction possible, transaction impossible).

The user device 120 has an application program for viewing the screen provided by the data processing device 100, and can send and receive data to and from the data processing device 100 via the application program. The user device 120 may be, for example, a personal computer (PC), a computer having a communication function such as a smartphone or a tablet terminal, but is not limited to a specific device. The user device 120 can acquire the card balance information and the card usage statement information provided by the data processing device 100 and display them on the screen. The user device 120 can transmit various setting information to the data processing device 100 for data registration via the application program. In this specification, for convenience of explanation, the user device 120 used by the card contractor may be referred to as a first user device, and the user device used by the card user may be referred to as a second user device. ..

The application program can provide the ability to perform the transfer of funds between the balances of the associated card account. As a result, for example, a card contractor can give pocket money to a child by increasing or decreasing the balance instead of cash. In addition, the application program can also provide a function of executing the transfer of funds between balances at predetermined designated days and a function of dynamically transferring funds when the balance falls below a predetermined amount. In addition, application programs can be configured to perform traditional methods, such as credit card charging, bank account charging, points charging, etc., when charging balances.

(System configuration)
FIG. 2 is a system configuration diagram of the data processing device 100 according to the embodiment of the present invention. As shown in FIG. 2, the data processing device 100 has a control unit 201, a main storage unit 202, an auxiliary storage unit 203, and an interface (IF) unit 204 connected to each other by a bus 210 or the like, similarly to a general computer. And an output unit 205. Further, the data processing device 100 includes a user master 206, payment data 207, and deposit / withdrawal details 208 as a file / database format.

The control unit 201 is also called a central processing unit (CPU), controls each component in the data processing unit 100, calculates data, and stores various programs stored in the auxiliary storage unit 203 as a main storage unit. It can be read into 202 and executed. The main storage unit 202, also called a main memory, can store various received data, computer-executable instructions, data after arithmetic processing by the instructions, and the like. The auxiliary storage unit 203 is a storage device typified by a hard disk (HDD) or the like, and is used when storing data or programs for a long period of time.

The embodiment of FIG. 2 describes an embodiment in which the control unit 201, the main storage unit 202, and the auxiliary storage unit 203 are provided in the same computer, but as another embodiment, the data processing device 100 includes the control unit 201, By using a plurality of main storage units 202 and auxiliary storage units 203, it is possible to configure parallel distributed processing by a plurality of computers. Further, as another embodiment, it is also possible to install a plurality of servers for the data processing device 100 so that the plurality of servers share one auxiliary storage unit 203.

The IF unit 204 serves as an interface for transmitting and receiving data to and from other systems and devices, and also provides an interface for receiving various commands and input data (various masters, tables, etc.) from the system operator. Can be done. The output unit 205 can provide a display screen for displaying the processed data, a printing means for printing the data, and the like.

The user master 206 is a master file that stores information on the card contractor and the card user, and is information about the usage detail data centralization processing, the card usage notification processing, and the restricted transaction applicable notification processing executed by the data processing device 100. including.

FIG. 3 is a diagram illustrating an example of a data structure of the user master 206 according to the embodiment of the present invention. The user master 206 includes user ID 301, authentication information 302, user information 303, card ID 304, first card number 305, second card number 306, related card ID 307, notification destination information 308, overseas restriction category 309, and domestic restriction category. It may include 310, face-to-face restriction categories 311, non-face-to-face restriction categories 312, transaction value thresholds 313, and period transaction amount thresholds 314, but is not limited to these data items and may include other data items as well. It is possible.

The user ID 301 is a user identifier for accessing the data processing device 100 via the application program, and is a user identifier that identifies each of the card contractor and the card user. The authentication information 302 is the authentication information used in the authentication process performed by the data processing device 100. The authentication information 302 may be well-known authentication information such as a password and biometric information. The user information 303 indicates attribute information such as the name and address of the card user. Each of the cardholder and the card user can query the balance information and card usage statement associated with their card via an application program. In addition, the card contractor can also inquire the balance information and the card usage statement information of each card user, and also inquire the card usage statement information of each card contractor and the card user collectively. Can be done.

The card ID 304 is an identifier that identifies a card account, which is a unit for managing balances and usage details. The first card number 305 and the second card number 306 indicate their respective card numbers associated with the card ID 304. Each of the first card number 305 and the second card number 306 is associated with a corresponding card. The associated card ID 307 indicates a card ID associated with the card ID 304. In other words, if the card ID 304 is the parent card ID, the card ID stored in the related card ID 307 is the child card ID. The related card ID 307 may indicate a plurality of card IDs.

In another embodiment of the present invention, conversely, the related card ID 307 may include the card ID 304 of the parent card. In such a case, the related card ID 307 of the data of the parent card indicates a Null value, and the related card ID 307 of the data of the child card indicates the card ID 304 of the parent card.

As described above, in the present embodiment, since a plurality of card numbers (first card number 305 and second card number 306) are associated with one card ID 304, one balance can be set by a plurality of persons (1st card number 305 and 2nd card number 306). For example, it can be shared by a card contractor and a spouse. In addition, card users (for example, family members of card contractors (children, parents, etc.)) can use separate card balances (balances of different card accounts), but card users such as family members can use them. The possessed card is associated with the card contractor's card by the associated card ID 307. Since a plurality of card accounts (card IDs) are associated with each other in this way, the data processing device 100 can unify the usage statement data of the plurality of cards held by the card contractor and the card user. ..

The notification destination information 308 is for notifying that the card payment has been made, that the payment amount at one time or the payment amount for a predetermined period has exceeded a predetermined threshold value, and that the card payment has been made falls under the transaction restriction. Indicates the information of the notification destination (for example, the e-mail address of the card contractor or the card user). The notification destination information 308 can store one or more notification destinations. For example, it can be configured to reach each of the cardholder and spouse.

The overseas restriction category 309, the domestic restriction category 310, the face-to-face restriction category 311 and the non-face-to-face restriction category 312 are categories indicating transaction restrictions that can be set by the card contractor and / or the card user. That is, the card contractor and / or the card user can restrict a specific transaction to any card account, for example, want to prohibit card payment at an overseas member store, via the Internet or the like. You can set restrictions such as not allowing card payments in electronic commerce.

The overseas restriction category 309 indicates whether to restrict the card payment at the overseas member store, and the domestic restriction category 310 indicates whether to restrict the card payment at the domestic member store. The face-to-face restriction category 311 indicates whether or not to limit the card payment in the face-to-face transaction, and the non-face-to-face restriction category 312 indicates whether or not to restrict the card payment in the non-face-to-face transaction (for example, electronic commerce). As is well known to those skilled in the art, the payment data transmitted from the member store terminal 110 includes information indicating the transaction content. This information includes the classification of whether the transaction is a face-to-face transaction or a non-face-to-face transaction, and the classification indicating whether the transaction is a domestic transaction or an overseas transaction.

The transaction amount threshold value 313 indicates the transaction upper limit amount (first threshold value) in one transaction. The period transaction amount threshold value 314 indicates the cumulative transaction amount (second threshold value) in a predetermined period. Based on this information, the data processing device 100 can notify the corresponding user device 120 based on the information of the notification destination information 308 when a transaction exceeding the first threshold value or the second threshold value is performed. .. In another embodiment of the present invention, when a transaction exceeding the first threshold value or the second threshold value is about to be performed, the data processing device 100 can refuse the establishment of the transaction and notify that the transaction is not possible. It can be transmitted to the member store terminal 110.

FIG. 6 is a diagram illustrating a user interface 600 for setting and registering some data items of the user master 206. Hereinafter, a process in which the card contractor sets some data items of the user master 206 of the card user (for example, a child, a parent, etc.) and registers them in the user master 206 will be described with reference to FIG. As a premise of the explanation, it is assumed that the card contractor has applied to the issuer to issue multiple cards, and multiple cards for the family have already been issued.

The card contractor accesses the data processing device 100 via the user device 120. At the time of access, the authentication process based on the user ID 301 and the authentication information 302 may be performed. When the data processing device 100 receives a signal from the user device 120 indicating that a predetermined menu has been selected, the data processing device 100 causes the user interface 600 to be displayed on the display of the user device 120.

The user interface 600 can include an end button 601, a user icon 602, a card number 603, a notification destination information 604, a restricted transaction 605, and a registration button 606, but an icon or input field for setting other information. May be included.

The end button 601 is a button for ending the display of the user interface 600. The user icon 602 is an icon for selecting a user who wants to set various information. In the embodiment of FIG. 6, the cardholder's co-owner (eg, spouse), one or more children, or one or more parents can be selected, but the names and numbers of icons displayed are , May be changed depending on the family type.

The card number 603 is an input field for inputting the card number associated with the co-owner and the card user selected by the user icon 602, and is a field for inputting which family the card number issued by the issuer is assigned. For example, if a co-owner is selected with the user icon 602 and then the card number used by the co-owner is entered into the card number 603 and registered, the co-owner's card number is the same card account as the card contractor (same card). It will be registered in association with ID304). Further, after selecting the card user (icon names are "1" and "2") with the user icon 602, if the card number used by the card user is entered into the card number 603 and registered, the card number of the card user is entered. Is registered in association with a card account (different card ID 304) different from that of the card contractor, and the different card ID 304 is registered in the related card ID 307 of the card account (card ID 304) of the card contractor. ..

The notification destination information 604 provides notification destination information for notifying that the card payment has been made, that the payment amount for one payment or the payment amount for a predetermined period has exceeded a predetermined threshold value, and that the transaction restriction has been met. This is an input field to enter. When registering the card user's information, if the notification destination information of the card contractor is registered, the card contractor will be notified when the card user makes a card payment. The restricted transaction 605 is a selection field for selecting the card transaction whose use is to be restricted from the card transactions of the co-owner and the card user selected by the user icon 602. The registration button 606 is a button for registering the information input in the user interface 600 in the user master 206. In the embodiment of FIG. 6, an example in which the card contractor sets some data items of the user master 206 of the co-owner and the card user has been described, but the card contractor himself / herself via the user interface 600. It is also possible to set some data items of its own user master 206.

Returning to FIG. 2, the payment data 207 stores the payment data received from the member store terminal 110. FIG. 4 is a diagram illustrating an example of a data structure of settlement data 207 according to an embodiment of the present invention. The settlement data 207 may include transaction ID 401, settlement card number 402, transaction date 403, merchant information 404, and transaction amount 405, but is not limited to these data items and also includes other data items. It is possible.

The transaction ID 401 is an identifier for identifying a card payment transaction. The payment card number 402 indicates the card number of the card used for the card payment. The transaction date 403 indicates the date on which the card payment was made. The trading day 403 may be configured to indicate the trading time. The member store information 404 indicates information such as a member store ID, a member store name, and an industry. The transaction amount 405 indicates the transaction amount (settlement amount) of the card settlement. The transaction amount 405 may indicate the type of currency.

The member store terminal 110 holds information such as the member store ID, the member store name, and the type of business of the member store in advance. When card payment is performed at the member store, the member store terminal 110 generates a transaction ID 401 at the time of card payment, and processes payment data including information on the card number, transaction date, and transaction amount together with the information held in the data processing device 100. Send to. The data processing device 100 stores the received payment data in the payment data 207.

Returning to FIG. 2 again, the deposit / withdrawal statement 208 stores the deposit / withdrawal statement and the balance information of the card. FIG. 5 is a diagram illustrating an example of the data structure of the deposit / withdrawal detail 208 according to the embodiment of the present invention. The deposit / withdrawal statement 208 can include a card ID 304, a settlement card number 402, a transaction date 403, a transaction content 501, a deposit / withdrawal category 502, a currency category 503, a transaction amount 405, and a balance 504. It is not limited and can include other data items.

Since the card ID 304, the payment card number 402, the transaction date 403, and the transaction amount 405 are as described above, detailed description thereof will be omitted. The transaction content 501 indicates the content of the transaction, for example, the name of the member store, the type of business, and the like. The deposit / withdrawal category 502 indicates whether the transaction performed is a deposit transaction (charge) or a withdrawal transaction. The currency category 503 indicates the type of transaction currency of the transaction performed (for example, conventional currency such as Japanese yen and US dollar, virtual currency such as Bitcoin, and any kind of electronic money). The balance 504 indicates the balance information after the deposit transaction or the withdrawal transaction.

(Processing flow: Deposit / withdrawal detail data generation processing)
FIG. 7 is a diagram illustrating a deposit / withdrawal detail data generation process executed by the data processing device 100. A process in which deposit / withdrawal detail data is generated based on the settlement data received from the member store terminal 110 and stored in the deposit / withdrawal detail 208 will be described with reference to this processing flow. In this processing flow, it is assumed that the balance is not insufficient as a result of the authorization processing.

When the payment data is received from the member store terminal 110 in S701, the data processing device 100 stores the received payment data in the payment data 207.

In S702, the data processing device 100 accesses the user master 206 and identifies the corresponding card ID 304 based on the payment card number 402 included in the received payment data. More specifically, the data processing device 100 identifies the card ID 304 in which the card number indicated by the payment card number 402 is stored in the first card number 305 or the second card number 306.

In S703, the data processing device 100 accesses the deposit / withdrawal statement 208 and acquires the most recent deposit / withdrawal statement data associated with the currency type included in the received payment data and the specified card ID 304. For example, when the received settlement data indicates a transaction in Japanese yen, the latest deposit / withdrawal detail data among the deposit / withdrawal detail data of Japanese yen associated with the specified card ID 304 is acquired.

In S704, the data processing device 100 determines that the received payment data corresponds to the withdrawal processing from the prepaid card, and based on the information included in the received payment data, the payment card number 402, the transaction date 403, and the transaction. The information of the content 501, the deposit / withdrawal category 502, the currency category 503, and the transaction amount 405 is specified. The data processing device 100 calculates a new value of the balance 504 based on the value of the balance 504 of the deposit / withdrawal detail data acquired in S703 and the value of the specified transaction amount 405. The data processing device 100 generates deposit / withdrawal detail data based on the specified information, the calculated value of the balance 504, and the card ID 304 specified in S702, and stores it in the deposit / withdrawal detail 208.

In this processing flow, an example in which the balance decreases due to card payment has been described, but the same processing flow can be applied to the processing in which the balance increases due to charging. Charging can be performed from the member store terminal 110, but as is well known to those skilled in the art, charging from a credit card, charging from a bank account, charging from a charging device, charging by converting points held, etc. It can be done by conventional means. In the case of charging, in S704, the data processing device 100 determines that it corresponds to the deposit processing, generates the deposit / withdrawal detail data, and stores it in the deposit / withdrawal detail 208.

(Processing flow: Usage statement data centralized processing)
FIG. 8 is a diagram illustrating a usage detail data unification process executed by the data processing device 100. With reference to this processing flow, a process of centralizing deposit / withdrawal detail data associated with a plurality of card IDs 304 and providing them to the user device 120 in response to a request from the user device 120 operated by the card contractor will be described. To do.

In S801, the data processing device 100 receives a centralized acquisition request for usage detail data from the user device 120 (first user device). The data processing device 100 accesses the user master 206, and based on the user ID 301 included in the acquisition request, the card ID 304 (first card ID) and one or more card ID 304s (first card ID 304) indicated by the related card ID 307. 2 card ID) is specified. In this embodiment, the first card ID is associated with the card contractor and the second card ID is associated with the card user (eg, child, parent). As described with reference to FIG. 3, the card ID 304 (first card ID) is associated with the first card number 305 and the second card number 306. Therefore, the balance of the card account indicated by the first card ID can be shared by a plurality of people (for example, a card contractor and a spouse).

In S802, the data processing device 100 accesses the deposit / withdrawal detail 208 and acquires the identified first card ID and the deposit / withdrawal detail data associated with the second card ID.

In S803, the data processing device 100 collects the deposit / withdrawal detail data acquired in S802 for, for example, the card ID 304 and the payment card number 402, and generates unified usage detail data.

In S804, the data processing device 100 transmits the generated unified usage detail data to the user device 120.

As a result, the card contractor can collectively refer to the usage statement data associated with the plurality of card IDs 304 related to each other, and grasp the usage status of the card user (for example, child, parent). You will be able to.

(Processing flow: Card usage notification processing)
FIG. 9 is a diagram illustrating a card usage notification process executed by the data processing device 100. The notification processing to the card user and the card contractor when the card payment is made by the card user (for example, child, parent) will be described with reference to this processing flow.

Upon receiving the payment data from the member store terminal 110 in S901, the data processing device 100 accesses the user master 206 and identifies the card ID 304 based on the payment card number 402 included in the received payment data. The data processing device 100 accesses the deposit / withdrawal detail 208, acquires the value of the balance 504 of the latest deposit / withdrawal detail data associated with the card ID 304 based on the specified card ID 304, and makes a payment based on the received payment data. Determine if processing is possible (whether or not the balance is insufficient). This determination process is also called authorization.

In S902, the data processing device 100 sends the notification destination information 308 associated with the identified card ID 304 after the authorization process is successfully completed (that is, after it is confirmed that the settlement is within the balance). Read the stored notification destination information (second notification destination information). The data processing device 100 further accesses the user master 206 and reads out another card ID 304 (that is, the card contractor's card ID 304) in which the identified card ID 304 is included in the related card ID 307. The data processing device 100 reads out the notification destination information (first notification destination information) stored in the notification destination information 308 associated with the other read card ID 304. In the present embodiment, the first notification destination information is associated with the card contractor, and the second notification destination information is associated with the card user.

In S903, the data processing device 100 selects one or more of the information included in the payment data received in S901 (for example, payment card number 402, transaction date 403, member store information 404, transaction amount 405). The usage notification text is generated by using the usage notification text, and the usage notification text is sent to the corresponding user devices 120 (first user device, second user device) using the first notification destination information and the second notification destination information. To send.

By this process, even if the child or parent makes a card payment, the card contractor is notified that the card has been used so that the card contractor can know the card usage of the child or parent. (Safety confirmation). In addition, when the card user receives his / her own card payment information, the transaction details can be grasped, and it becomes easy to grasp the unauthorized use of a third party.

(Processing flow: Restricted transaction applicable notification processing)
FIG. 10 is a diagram illustrating a restricted transaction corresponding notification process executed by the data processing device 100. While referring to this processing flow, it is determined whether or not the card payment to be executed corresponds to the restricted transaction, and if so, the member store terminal 110 is notified that the card payment cannot be performed, and the user. The process of notifying the device 120 will be described. Note that this process may be performed before or after the authorization process is executed, and is not particularly limited. If you do this after performing authorization, the balance will not be updated.

When the payment data is received from the member store terminal 110 in S1001, the data processing device 100 accesses the user master 206 and identifies the card ID 304 based on the payment card number 402 included in the received payment data. In the present embodiment, the case where the card user makes the card payment will be described, so that the specified card ID 304 is associated with the card user.

In S1002, the data processing apparatus 100 has one or more of the information of the overseas restriction category 309, the domestic restriction category 310, the face-to-face restriction category 311, and the non-face-to-face restriction category 312 associated with the specified card ID 304. Is obtained from the user master 206.

In S1003, the data processing apparatus 100 determines whether or not information indicating transaction restrictions is set for each of the acquired overseas restriction category 309, domestic restriction category 310, face-to-face restriction category 311, and non-face-to-face restriction category 312. To do. If information indicating a transaction restriction is set in any of the categories, the process proceeds to step S1004, while if it is not set, the present process flow ends.

In S1004, the data processing device 100 determines the transaction information included in the received settlement data (classification of whether the transaction is a face-to-face transaction or a non-face-to-face transaction, and a classification indicating whether the transaction is a domestic or overseas transaction. , Etc.) and the information of categories 309 to 312 in which the information indicating the transaction restriction is set, which is acquired in S1002, and whether or not the transaction based on the received settlement data corresponds to the restricted transaction. judge. If applicable, the process proceeds to S1005, and if not applicable, the present processing flow ends.

In S1005, the data processing device 100 transmits a notification that card payment is not possible to the member store terminal 110. Further, the data processing device 100 accesses the user master 206 and reads out the notification destination information 308 (second notification destination information) associated with the card ID 304 specified in S1001. The data processing device 100 includes one or more pieces of information included in the received payment data (for example, payment card number 402, transaction date 403, member store information 404, transaction amount 405), and the reason why card payment is not possible. The non-settlement notification text including the above is generated, and the non-settlement notification text is transmitted to the corresponding user device 120 (second user device) using the read notification destination information 308 (second notification destination information). As a result, the card user can know the details of the transaction that cannot be settled and the reason (which restriction category is applicable).

The data processing device 100 further accesses the user master 206 and reads out another card ID 304 (that is, the card contractor's card ID 304) in which the card ID 304 specified in S1001 is included in the related card ID 307. The data processing device 100 reads out the notification destination information (first notification destination information) stored in the notification destination information 308 associated with the other read card ID 304. The data processing device 100 can transmit the non-settlement notification text generated in S1005 to the corresponding user device 120 (first user device) using the first notification destination information. As a result, not only the card user but also the card contractor will be notified of the details of the transaction that cannot be settled and the reason (which restriction category is applicable).

If a card payment that meets the preset transaction restrictions occurs due to this processing, not only will the transaction not be completed, but also the card contractor and card user will be notified that payment is not possible, as well as the member store. You will be able to do it.

Although the principles of the present invention have been described above with reference to exemplary embodiments, those skilled in the art will appreciate that various embodiments that change in configuration and details can be realized without departing from the gist of the present invention. You will understand. That is, the present invention can be implemented as, for example, a system, an apparatus, a method, a program, a storage medium, or the like.

100 Data processing device 110 Merchant terminal 120 User device 201 Control unit 202 Main memory unit 203 Auxiliary storage unit 204 Interface (IF) unit 205 Output unit 206 User master 207 Payment data 208 Deposit / withdrawal details 210 Bus

Claims (14)

It is a data processing device
A request for acquisition of centralized usage detail data is received from the first user device, and the first card identifier and the second card identifier associated with each other are specified based on the user identifier included in the acquisition request. Acquires the specified deposit / withdrawal detail data associated with the first card identifier and the second card identifier, and transmits the data to the first user device based on the acquired deposit / withdrawal detail data. As a first means of generating centralized usage statement data for
The second card identifier is specified based on the payment card number included in the payment data received from the member store terminal, and one or more transaction restriction information associated with the specified second card identifier is acquired. , The transaction information included in the received settlement data and the information indicating the transaction restriction are provided on the condition that the information indicating the transaction restriction is set in any of the acquired one or more transaction restriction information. Based on the set one or more transaction restriction information, it is determined whether or not the transaction based on the received settlement data corresponds to the restricted transaction, and the transaction based on the received settlement data is A data processing device provided with a second means for transmitting a first non-settlement notification message to the member store terminal on the condition that it corresponds to a restricted transaction. The data processing device according to claim 1, wherein the one or more transaction restriction information associated with the second card identifier is set by a card contractor associated with the first card identifier. Read the second notification destination information associated with the identified second card identifier,
Generates a second non-settlement notification statement that includes one or more of the information contained in the received payment data and the reason why card payment is not possible.
According to the second notification destination information, the second non-settlement notification text is transmitted to the corresponding second user device.
Read the first notification destination information associated with the first card identifier associated with the identified second card identifier,
The data processing device according to claim 1, further configured to transmit the second non-settlement notification message to the corresponding first user device according to the first notification destination information. Read the second notification destination information associated with the identified second card identifier,
Read the first notification destination information associated with the first card identifier associated with the identified second card identifier,
A usage notification statement is generated using one or more of the information included in the received payment data, and the corresponding first notification destination information and the second notification destination information are used to correspond to each other. The data processing device according to claim 1, further configured to transmit the usage notification text to the user device. It is a data processing device
Receives a centralized usage statement data acquisition request from the user device and receives it.
Based on the user identifier included in the acquisition request, the first card identifier and the second card identifier associated with each other are identified.
Acquire the deposit / withdrawal detail data associated with the identified first card identifier and the second card identifier, and obtain
A data processing device configured to generate centralized usage detail data for transmission to the user device based on the acquired deposit / withdrawal detail data. The data processing device according to claim 5, wherein the first card identifier is associated with a plurality of card numbers, and the card number is included in payment data transmitted from a member store terminal. The data processing apparatus according to claim 6, wherein each of the card numbers is associated with a corresponding card. It is a data processing device
The second card identifier is specified based on the payment card number included in the payment data received from the member store terminal.
Acquires one or more transaction restriction information associated with the identified second card identifier,
The transaction information included in the received settlement data and the information indicating the transaction restriction are set on the condition that the information indicating the transaction restriction is set in any of the acquired one or more transaction restriction information. Based on the one or more transaction restriction information, it is determined whether or not the transaction based on the received settlement data corresponds to the restricted transaction.
A data processing device configured to send a first non-settlement notification to the member store terminal on the condition that the transaction based on the received payment data corresponds to a restricted transaction. Read the second notification destination information associated with the identified second card identifier,
Generate a second non-settlement notification statement including one or more of the received information contained in the payment data and the reason why card payment is not possible.
According to the second notification destination information, the second non-settlement notification text is transmitted to the corresponding second user device.
Read the first notification destination information associated with the first card identifier associated with the identified second card identifier,
The data processing device according to claim 8, further configured to transmit the second non-settlement notification message to the corresponding first user device according to the first notification destination information. Read the second notification destination information associated with the identified second card identifier,
Read the first notification destination information associated with the first card identifier associated with the identified second card identifier,
A usage notification statement is generated using one or more of the information included in the received payment data, and the corresponding first notification destination information and the second notification destination information are used to correspond to each other. The data processing device according to claim 8, further configured to send a usage notification to the user device. A data processing method performed by a data processing device.
A request for acquisition of centralized usage detail data is received from the first user device, and the first card identifier and the second card identifier associated with each other are specified based on the user identifier included in the acquisition request. Acquires the specified deposit / withdrawal detail data associated with the first card identifier and the second card identifier, and transmits the data to the first user device based on the acquired deposit / withdrawal detail data. The first processing method for generating centralized usage detail data for
The second card identifier is specified based on the payment card number included in the payment data received from the member store terminal, and one or more transaction restriction information associated with the specified second card identifier is acquired. , The transaction information included in the received settlement data and the information indicating the transaction restriction are provided on the condition that the information indicating the transaction restriction is set in any of the acquired one or more transaction restriction information. Based on the set one or more transaction restriction information, it is determined whether or not the transaction based on the received settlement data corresponds to the restricted transaction, and the transaction based on the received settlement data is A data processing method comprising a second processing method for transmitting a first non-settlement notification message to the member store terminal on the condition that it corresponds to a restricted transaction. A data processing method performed by a data processing device.
Receiving a centralized usage statement data acquisition request from the user device and
Identifying the first card identifier and the second card identifier associated with each other based on the user identifier included in the acquisition request.
Acquiring the identified deposit / withdrawal detail data associated with the first card identifier and the second card identifier, and
A data processing method comprising generating centralized usage detail data for transmission to the user apparatus based on the acquired deposit / withdrawal detail data. A data processing method performed by a data processing device.
Identifying the second card identifier based on the payment card number included in the payment data received from the member store terminal, and
Acquiring one or more transaction restriction information associated with the identified second card identifier,
The transaction information included in the received settlement data and the information indicating the transaction restriction are set on the condition that the information indicating the transaction restriction is set in any of the acquired one or more transaction restriction information. Based on the one or more transaction restriction information, it is determined whether or not the transaction based on the received settlement data corresponds to the restricted transaction.
A data processing method comprising transmitting a first non-settlement notification to the member store terminal on the condition that the transaction based on the received settlement data corresponds to a restricted transaction. A program that causes a data processing device to execute the method according to any one of claims 11 to 13 when executed by a processor.

Images