JP7771124B2 - Washing system, washing method, and program - Google Patents

Description

This disclosure relates to a washing system, a washing method, and a program.

Conventionally, card (e.g., credit card or debit card) reconciliation has been performed. For example, Patent Document 1 describes a reconciliation implementation device that manages reconciliation data for each affiliated store, including credit card information and the identifier of the affiliated store that will charge the card, and performs reconciliation by obtaining updated credit card information for each affiliated store, including whether the credit card can be used, based on the reconciliation data.

Japanese Patent Application Laid-Open No. 2019-220235

For example, when multiple systems each manage information such as expiration dates, tokens may be sent between systems to prevent card numbers from being leaked to third parties. In such cases, it is necessary to achieve appropriate reconciliation. However, the technology in Patent Document 1 does not describe such reconciliation. As a result, conventional technology has not been able to achieve appropriate reconciliation.

One of the objectives of this disclosure is to achieve proper cleaning.

The refill system according to the present disclosure includes a management unit that associates and manages a first token and first card information related to a user's card; a token acquisition unit that acquires a second token and second card information related to the card; a refill execution unit that executes refilling of the card based on the first card information associated with the same first token as the second token; a comparison unit that, when the refilling is executed, compares the first card information associated with the same first token as the second token with the second card information; and a processing execution unit that executes a predetermined process based on the comparison result by the comparison unit.

This disclosure allows for proper cleaning and replacement.

FIG. 2 is a diagram illustrating an example of a hardware configuration of a washing system. FIG. 1 is a diagram showing an example of a flow in which a user uses a credit card. FIG. 10 is a diagram showing an example of a flow in which a user updates the expiration date of an old credit card to the expiration date of a new credit card. FIG. 10 is a diagram illustrating an example of functions realized by the washing system. FIG. 10 is a diagram illustrating an example of a first card database. FIG. 10 is a diagram illustrating an example of a second card database. FIG. 10 is a diagram showing an example of a third card database. FIG. 10 is a diagram illustrating an example of a process executed in the washing system. FIG. 10 is a diagram showing an example of a function realized by a washing system according to a modified example.

[1. Overall configuration of the washing system]
An example of an embodiment of a washing system according to the present disclosure will be described. FIG. 1 is a diagram showing an example of the hardware configuration of a washing system. The washing system 1 is connected to a network N such as the Internet or a LAN. In this embodiment, service providing systems 2-1, 2-2, ..., 2-a, card company systems 3-1, 3-2, ..., 3-b, and a user terminal 40 are also connected to the network N. a and b are integers equal to or greater than 3. The value of a and the value of b may be the same or different.

For example, the card replacement system 1 includes a card replacement server 10. The card replacement server 10 is a card replacement company's server computer. The card replacement company is the company that performs the card replacement. For example, the card replacement company is a company that manages all information related to cards. Card replacement is a process of checking whether the information managed by the card replacement company is up to date. Card replacement can also be described as a process of checking the validity of a card, or a process of checking whether the card is up to date. In this embodiment, a case is described in which the card replacement system 1 acts as a proxy for payments for various services, but the card replacement system 1 may also perform only card replacement without acting as a proxy for payments.

For example, the cleaning server 10 includes a control unit 11, a memory unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The memory unit 12 includes volatile memory such as RAM and non-volatile memory such as flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

The program stored in the memory unit 12 may be supplied to the washing server 10 via the network N. Also, the program stored on a computer-readable information storage medium may be supplied to the washing server 10 via a reading unit that reads the information storage medium (e.g., an optical disk drive or memory card slot), or an input/output unit that inputs and outputs data to and from an external device (e.g., a USB port).

Furthermore, the washing system 1 only needs to include at least one computer and is not limited to the example shown in Figure 1. For example, the washing system 1 may include a washing server 10 and another server computer. The washing system 1 may also include computers other than the server computer, such as a personal computer, tablet, or smartphone. The washing system 1 may not include a server computer, but may only include computers other than the server computer.

For example, service providing systems 2-1, 2-2, ..., 2-a include service providing servers 20-1, 20-2, ..., 20-a, respectively. Hereinafter, when there is no need to distinguish between service providing systems 2-1, 2-2, ..., 2-a, the reference numerals following the hyphen will be omitted. For the same reason, the reference numerals following the hyphens for service providing servers 20-1, 20-2, ..., 20-a, control units 21-1, 21-2, ..., 21-a, memory units 22-1, 22-2, ..., 22-a, and communication units 23-1, 23-2, ..., 23-a will be omitted.

For example, the service providing system 2 provides a service that allows users to use their cards. The service providing server 20 is the provider's server computer. A provider is a party that provides a service to a user. The service may be of any type, for example, an e-commerce service, a communication service, a travel reservation service, a payment service, a financial service, or a video distribution service. The provider of one service may be the same as or different from the provider of another service. For example, the provider may be a company that provides multiple services comprehensively. The service providing server 20 may be a device that manages multiple services using a single set of member information.

For example, the service providing server 20 includes a control unit 21, a memory unit 22, and a communication unit 23. The physical configurations of the control unit 21, the memory unit 22, and the communication unit 23 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. The program stored in the memory unit 22 may be provided to the service providing server 20 from the network N or an information storage medium. The service providing system 2 need only include at least one computer and is not limited to the example shown in Figure 1. These points are similar to those of the washing system 1.

For example, card company systems 3-1, 3-2, ..., 3-b include card company servers 30-1, 30-2, ..., 30-b, respectively. Hereinafter, when there is no need to distinguish between card company systems 3-1, 3-2, ..., 3-b, the reference numerals following the hyphen will be omitted. For the same reason, the reference numerals following the hyphens for card company servers 30-1, 30-2, ..., 30-b, control units 31-1, 31-2, ..., 31-b, memory units 32-1, 32-2, ..., 32-b, and communication units 33-1, 33-2, ..., 33-b will be omitted.

For example, the card company system 3 is a server computer of a card company. The card company is the company that issued the user's card. Cards may also be issued by parties other than the company. For example, cards may be issued by a store operated by a party other than the company, a country, a government agency, a local public body, or a non-profit corporation. The issuer of one card may be the same as or different from the issuer of another card. The card company system 3 manages the latest card information.

For example, the card company server 30 includes a control unit 31, a memory unit 32, and a communication unit 33. The physical configurations of the control unit 31, the memory unit 32, and the communication unit 33 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. The program stored in the memory unit 32 may be provided to the card company server 30 from the network N or an information storage medium. The card company system 3 is not limited to the example shown in Figure 1, and may include at least one computer. These points are similar to those of the washing system 1.

For example, the user terminal 40 is the user's personal computer, smartphone, tablet, or wearable terminal. The user can use their card with any of a number of services. For example, the user can use the card for payment, authentication, identity verification, or other purposes within the service. Although only one user terminal 40 is shown in FIG. 1, there may be a user terminal 40 for each of a number of users.

For example, the user terminal 40 includes a control unit 41, a memory unit 42, a communication unit 43, an operation unit 44, and a display unit 45. The physical configurations of the control unit 41, the memory unit 42, the communication unit 43, the operation unit 44, and the display unit 45 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. The operation unit 44 is an input device such as a keyboard, mouse, or touch panel. The display unit 45 is a display such as a liquid crystal display or an organic EL display. Note that the program stored in the memory unit 42 may be provided to the user terminal 40 from the network N or an information storage medium.

[2. Overview of the Washing System]
In this embodiment, a credit card will be described as an example of a card. The card is not limited to a credit card as long as it is a card that needs to be replaced. For example, the card may be a debit card, a transportation card, an electronic money card, a membership card, a personal identification number card, a prepaid card, an identification card, or an entrance/exit card. In this embodiment, the term "credit card" may be replaced with other cards. The card is not limited to an IC card or a magnetic card, and the IC chip of the user terminal 40 may also be treated as a card. The card may also be a virtual card that does not have a physical card.

For example, a user can use a credit card to pay for any of multiple services. In this embodiment, an example is given in which a user uses the same credit card to pay for both the e-commerce service provided by service providing system 2-1 and the communication service provided by service providing system 2-2. Hereinafter, when there is no need to distinguish between the e-commerce service and the communication service, they will simply be referred to as services. A user may use the same credit card to pay for three or more services.

Figure 2 shows an example of the flow of a user using a credit card. For example, if a user has not registered a credit card to be used for payment in an e-commerce service, the user logs in to the e-commerce service and enters various information related to the credit card on registration screen SC1. The user enters the credit card number, expiration date, and name in input forms F10 to F12. When the user selects button B13, the various information related to the credit card is registered in the service providing server 20-1. The various information related to the credit card may also be entered on another screen, such as a checkout page, rather than on registration screen SC1.

In this embodiment, the card replacement server 10 comprehensively manages various information, such as card numbers, entered by users for each of multiple services. The service providing server 20 manages only some of the credit card information. In the example of Figure 2, the user terminal 40 sends the card number and other information entered on the registration screen SC1 to the card replacement server 10 using a script such as JavaScript (registered trademark). The card replacement server 10 manages the entire 16-digit card number, expiration date, and name.

For example, the service providing server 20-1 manages part of the card number (for example, the last four digits), expiration date, and name. This information is sent from the reconciliation server 10 to the service providing server 20-1. In the e-commerce service, not all information related to the credit card is displayed; only the information managed by the service providing server 20-1 is displayed. In the example of Figure 2, a completion screen SC2 indicating that the credit card registration has been completed is displayed on the display unit 45.

In this embodiment, not all card numbers are registered in the service providing server 20-1. However, when a user orders a product, the minimum information about the credit card is displayed, as shown on the order screen SC3 in Figure 2, without the service providing server 20-1 querying the replacement server 10 for information. Furthermore, when a user registers a credit card through an e-commerce service, the user can use the same credit card for communication services as well.

For example, the replacement server 10 works in conjunction with the service providing server 20-2. The replacement server 10 sends part of the card number, expiration date, and name to the service providing server 20-2. The service providing server 20-2 manages part of the card number, expiration date, and name. In the communication service, as with e-commerce services, not all information related to the credit card is displayed; only the information managed by the service providing server 20-2 is displayed.

In the example of Figure 2, the confirmation screen SC4 for confirming the payment method for the communication service displays part of the card number, expiration date, and name. Like the service providing server 20-1, the service providing server 20-2 can display the minimum information about the credit card on the confirmation screen SC4 without querying the payment server 10 for information. The user can also register a new credit card from the communication service. In this case, some of the information about the new credit card is shared with the e-commerce service.

In this embodiment, a token is used to identify a credit card between the credit card issuer and the credit card provider. A token is an example of card identification information that can identify a credit card. While a card number also corresponds to card identification information, a credit card can also be identified using a token. However, while a card number generally does not change, a token may change even for the same credit card. For example, a token for the same credit card may be updated periodically.

For example, a token is information in which a card number has been tokenized. Tokenization is sometimes called encryption or hashing. For example, the card exchange server 10 inputs the card number into a function for tokenization. The card exchange server 10 obtains the token output from the function. The tokenization itself can use known methods, such as a one-way hash function, a pseudorandom function, or an encryption algorithm. The token is shared between the card exchange system 1 and the service providing system 2. The token is not shared with the card company system 3, but may be shared with the card company system 3.

Hereinafter, the token, card number, expiration date, and name managed by the payment system 1 will be referred to as the first token, first card number, first expiration date, and first name, respectively. The token, card number, expiration date, and name managed by the service providing system 2 will be referred to as the second token, second card number, second expiration date, and second name, respectively. When there is no need to distinguish between the first token and the second token, they will simply be referred to as tokens.

Furthermore, the card number, expiration date, and name managed by the card company system 3 are referred to as the third card number, third expiration date, and third name, respectively. When the first card number, second card number, and third card number are not distinguished, they are simply referred to as the card number. When the first expiration date, second expiration date, and third expiration date are not distinguished, they are simply referred to as the expiration date. When the first name, second name, and third name are not distinguished, they are simply referred to as the name.

For example, a card company sends a user a new credit card before the expiration date of their current credit card. The card number and name on the new credit card are essentially the same as those on the old credit card. The expiration date of the new credit card is different from the expiration date of the old credit card. Since the user will no longer be able to use the old credit card once it expires, they update the expiration date of the old credit card to the expiration date of the new credit card.

Figure 3 shows an example of the process by which a user updates the expiration date of an old credit card to the expiration date of a new credit card. For example, the user logs in to an e-commerce service and enters the expiration date of the new credit card in the input form F50 on the update screen SC5. When the user selects button B51, a completion screen SC6 is displayed indicating that the expiration date has been updated.

In this embodiment, even if the user updates the expiration date through the e-commerce service, the expiration date registered on the service provider server 20-2 will not be updated. For this reason, as shown in Figure 3, the confirmation screen SC4 for the communication service displays the expiration date of the old credit card. For communication services, the credit card is recharged before the monthly usage fee is paid. In the example of Figure 3, the usage fee is paid on the 20th of each month. For this reason, the credit card is recharged on or before the 20th of each month.

For example, before the monthly fee is paid, the service providing server 20-2 transmits the second token and second expiration date to the reimbursement server 10. The reimbursement server 10 acquires the first card number, first expiration date, and first name that are associated with and managed as the first token, which is the same as the second token received from the service providing server 20. The reimbursement server 10 performs reimbursement with the card company server 30 based on the acquired first card number, first expiration date, and first name.

In the example shown in Figure 3, the user updated the first expiration date via the e-commerce service, so the reimbursement server 10 manages the latest first expiration date. Therefore, the reimbursement server 10 receives an execution result from the card company server 30 indicating that there has been no change to the credit card as a result of the reimbursement. In this case, even though the second expiration date managed by the service provider server 20-2 is old, the reimbursement execution result indicates that there has been no change to the credit card information.

The replacement server 10 of this embodiment therefore compares the first expiration date, which has been confirmed to be the latest based on the results of the replacement execution, with the second expiration date received from the service providing server 20-2. If the first expiration date and the second expiration date do not match, the replacement server 10 notifies the service providing server 20-2 that the second expiration date is older. This allows the replacement server 10 to achieve appropriate replacement. The replacement system 1 will be described in detail below.

[3. Functions realized by the washing system]
Fig. 4 is a diagram showing an example of functions realized by the washing system 1. Fig. 4 also shows an example of functions realized by each of the service providing system 2, the card company system 3, and the user terminal 40.

[3-1. Functions realized by the washing system]
For example, the re-cleaning server 10 includes a data storage unit 100, a management unit 101, a first reception unit 102, a first update unit 103, a token acquisition unit 104, a re-cleaning execution unit 105, a comparison unit 106, and a processing execution unit 107. The data storage unit 100 is realized by the memory unit 12. The management unit 101, the first reception unit 102, the first update unit 103, the token acquisition unit 104, the re-cleaning execution unit 105, the comparison unit 106, and the processing execution unit 107 are realized by the control unit 11.

[Data storage unit]
The data storage unit 100 stores data necessary for the replacement. For example, the data storage unit 100 stores a first card database DB1.

Figure 5 is a diagram showing an example of the first card database DB1. The first card database DB1 is a database that stores various information related to credit cards. For example, the first card database DB1 stores a user ID, a first token, a first card number, a first expiration date, and a first name. The first card database DB1 may store any information related to credit cards, and the information stored in the first card database DB1 is not limited to the example shown in Figure 5. For example, the first card database DB1 may store personal information about the user or a history of the first token. If the history of the first token is stored in the first card database DB1, the repayment server 10 can identify which credit card the old second token belongs to, even if it receives an old second token from the service providing server 20.

A user ID is an example of user identification information that can identify a user. Therefore, the term "user ID" can be read as "user identification information." User identification information can be information other than a user ID and is not limited to a user ID. For example, user identification information can be an email address or a phone number. User identification information can be any information that can identify a user in some way. In this embodiment, an example is given in which the user ID is the same for all services, but the user ID may be different for each service. If the user ID is different for each service, it is assumed that a correspondence indicating which user IDs correspond to the same user is recorded in the data storage unit 100.

In this embodiment, the first expiration date is an example of first card information. Therefore, any description of the first expiration date can be read as first card information. The first card information is information that may be updated when a new credit card is issued. The first card information does not necessarily have to be updated when a new credit card is issued. The first card information is not limited to the first expiration date, and may be other information. For example, the first card information may be the first card number or the first name. The first card information may be a security code, a point card number for points attached to the credit card, or other information.

The data storage unit 100 can store any data. The data stored in the data storage unit 100 is not limited to the first card database DB1. For example, the data storage unit 100 may store a function for tokenization, a program for sharing information with the service providing system 2, a program for performing reconciliation with the card company system 3, or data indicating the relationship between the card number and the card company system 3.

[Management Department]
The management unit 101 manages a first token and a first expiration date related to a user's credit card in an associated manner. Managing the first token and the first expiration date means storing multiple pieces of information in memory in a state in which one piece of information can be searched for from the other piece of information. In this embodiment, storing information in the same record in the first card database DB1 corresponds to associating the information. The management unit 101 manages the first token and the first expiration date in an associated manner by storing the first token and the first expiration date in the same record in the first card database DB1. In this embodiment, the management unit 101 manages not only the first expiration date but also the user ID, the first card number, and the first name in an associated manner with the first token.

In the example of Figure 2, when a user performs the procedure to register a credit card through an e-commerce service, the reimbursement server 10 obtains the user ID, first card number, first expiration date, and first name from the service providing server 20-1. The management unit 101 issues a first token. In this embodiment, the management unit 101 inputs the first card number into a function for tokenization and obtains the first token output from the function. The management unit 101 associates the obtained first token with the user ID, first card number, first expiration date, and first name of the user who requested credit card registration and stores them in the first card database DB1. The management unit 101 sends the first token to the service providing server 20-2. This first token is managed by the service providing server 20-2 as a second token.

The first token is not limited to the example of this embodiment, as long as it can identify the credit card and is information different from the card number. For example, the management unit 101 may generate a random character string unrelated to the first card number as the first token. The management unit 101 may also generate the first token by tokenizing other information such as the user's name, address, telephone number, or email address.

[First Reception Unit]
The first reception unit 102 receives a first update request for updating the first expiration date. For example, the first reception unit 102 receives a first update request for updating the first expiration date input by the user terminal 40. The first update request is data for requesting an update of the first expiration date. The first update request may be data in a predetermined format. In this embodiment, the first reception unit 102 receives the first update request from the user terminal 40, but may also receive the first update request from another device.

For example, the first reception unit 102 accepts the first update request by receiving data in a predetermined format input by the user terminal 40. In this embodiment, the first update request includes the second token of the credit card to be updated and the new first expiration date input by the user. The new first expiration date is the same as the new second expiration date. The second token and new first expiration date may be added to the first update request as separate data from the first update request.

For example, when a user inputs a new first expiration date on the update screen SC5, the replacement server 10 obtains the new first expiration date from the user terminal 40. The service providing server 20 updates the second card database DB2 (described below) at a predetermined timing so that the new first expiration date obtained from the replacement server 10 becomes the new second expiration date. The first reception unit 102 receives the first update request from the service providing server 20, thereby accepting the first update request.

In this embodiment, the first reception unit 102 receives a first update request from the user terminal 40. In the example of Figures 2 and 3, the service provision system 2-1 corresponds to the first service provision system 2. The first service provision system 2 is not limited to the service provision system 2-1. Other service provision systems 2-2 to 2-a may also correspond to the first service provision system 2. For example, when a user logs in to a communication service to update credit card information, the service provision system 2-2 corresponds to the first service provision system 2.

[First update part]
The first updating unit 103 updates the first expiration date based on the first update request. For example, the first updating unit 103 updates the first expiration date by overwriting, among the first expiration dates stored in the first card database DB1, the first expiration date associated with the same first token as the second token included in the first update request with the new first expiration date included in the first update request. If the second token and the new first expiration date are separate data from the first update request, the first updating unit 103 may simply overwrite the first expiration date associated with the same first token as the separate data, the second token, with the separate data, the new first expiration date.

[Token acquisition section]
The token acquiring unit 104 acquires the second token and the second expiration date. For example, the token acquiring unit 104 acquires the second token and the second expiration date from the user terminal 40. The first accepting unit 102 also acquires the second token, but the token acquiring unit 104 acquires the second token of the credit card that is the target of the reimbursement. As described above, the second token is a token managed by the service providing system 2. In principle, the second token is the same as the first token. However, if the first token of a certain credit card is updated for some reason and the second token of this credit card is not updated, the first token and the second token may be different from each other. In this embodiment, the token acquiring unit 104 acquires the second token and the second expiration date from the user terminal 40, but the second token and the second expiration date may also be acquired from another device.

In this embodiment, an example is given in which the second token is the same for each of the multiple service providing systems 2, but the second tokens for each of the multiple service providing systems 2 may be different from each other. For example, even if the same credit card is used, the second token for service providing system 2-1 and the second token for service providing system 2-2 may be different from each other. In this case, a unique second token will be issued for each service providing system 2.

As mentioned above, the second expiration date is an expiration date managed by the service providing system 2. The second expiration date is an example of second card information. Therefore, the phrase "second expiration date" can be read as "second card information." The second card information is information that may be updated when a new credit card is issued. The second card information does not necessarily have to be updated when a new credit card is issued. The second card information is not limited to the second expiration date, and may be other information. For example, the second card information may be a second card number or a second name. The second card information may be a security code, a point card number for points attached to a credit card, or other information.

For example, after the first expiration date is updated, the token acquisition unit 104 acquires the second token and the second expiration date from a second service provision system 2 that is different from the first service provision system 2 among the multiple service provision systems 2. In the examples of Figures 2 and 3, service provision system 2-2 is an example of a second service provision system 2. The second service provision system 2 is the service provision system 2 that manages the old second expiration date.

In this embodiment, the service providing system 2 transmits the second token and the second expiration date to the washing system 1 when the reservation time for payment for the service arrives. For example, the token acquisition unit 104 acquires the second token and the second expiration date from the service providing system 2 when the reservation time arrives. The reservation time is the time when payment by credit card is reserved.

In this embodiment, the reservation time when the communication service fee is paid is determined in advance, so the service providing server 20-2 transmits the second token and second expiration date to the replacement server 10 when the reservation time arrives. In the example of Figures 2 and 3, the reservation time corresponds to the 20th of each month or the time before that. The token acquisition unit 104 acquires the second token and the second expiration date transmitted by the service providing server 20-2.

[Replacement Department]
The reconciliation execution unit 105 executes reconciliation for the credit card based on the first expiration date associated with the first token that is the same as the second token acquired by the token acquisition unit 104. The reconciliation execution unit 105 searches the first card database DB1 for a first token that is the same as the second token. The reconciliation execution unit 105 executes reconciliation based on the first expiration date that is associated with the searched first token and stored in the first card database DB1.

The reconciliation itself can use known methods. For example, the reconciliation execution unit 105 transmits the first card number, first expiration date, and first name of the credit card to be reconciled to the card company system 3 of the card company that manages the credit card to be reconciled. The relationship between the credit card and the card company is assumed to be pre-recorded in the data storage unit 100. For example, the card start date may be identified by part of the card number. A token may be shared between the reconciliation system 1 and the card company system 3. In this case, the first card number is not transmitted.

For example, the reconciliation execution unit 105 receives the reconciliation execution result from the card company system 3. The reconciliation execution result indicates a first value, which means that there is no change in the credit card, or a second value, which means that there is a change in the credit card. The reconciliation execution result may be data in a predetermined format. The reconciliation execution result may include the latest expiration date. In this embodiment, the reconciliation execution result indicates whether the first expiration date is the latest. The reconciliation may be performed primarily by the reconciliation system 1, rather than the card company system 3. For example, the reconciliation execution unit 105 may perform the reconciliation by obtaining the latest first expiration date, etc. from the card company system 3 and comparing it with the first expiration date stored in the first database DB1.

For example, the replacement execution unit 105 performs replacement based on the first expiration date associated with the same first token as the second token obtained from the second service providing system 2. In other words, the replacement execution unit 105 performs replacement based on the second token obtained from the second service providing system 2 that manages the old second token, rather than the first service providing system 2 that caused the first expiration date to be updated.

For example, the replacement execution unit 105 may not perform replacement when the first expiration date is updated, but may perform replacement when the second token and second expiration date are acquired. In the example of Figure 3, replacement is not performed when the user inputs a new first expiration date from the update screen SC5. The replacement execution unit 105 only performs replacement when the second token and second expiration date are acquired from the service providing system 2. Note that when the first expiration date is updated, the replacement execution unit 105 may perform replacement to confirm whether the new expiration date input by the user is correct.

The re-washing execution unit 105 can perform re-washing at any timing. The re-washing execution unit 105 may perform re-washing not only at the time of reservation as in this embodiment, but also at a timing when no payment occurs, or at a predetermined timing. For example, when a user requests re-washing, the re-washing execution unit 105 may perform re-washing at a timing specified by the re-washer or at a timing specified by the card company.

[Comparison section]
When replacement is performed, the comparison unit 106 compares the first expiration date associated with the same first token as the second token with the second expiration date. The comparison unit 106 determines whether the first expiration date and the second expiration date match. In this embodiment, when replacement is performed, the comparison unit 106 compares the first expiration date associated with the same first token as the second token with the second expiration date obtained from the second service providing system 2.

For example, the comparison unit 106 compares the first expiration date and the second expiration date when the reconciliation execution result received from the card company system 3 indicates that there has been no change to the credit card. The comparison unit 106 does not need to compare the first expiration date and the second expiration date when the reconciliation execution result received from the card company system 3 indicates that there has been a change to the credit card, and may also compare the first expiration date and the second expiration date in this case. The comparison unit 106 may compare the first expiration date and the second expiration date after the reconciliation has been executed.

[Processing execution unit]
The processing execution unit 107 executes a predetermined process based on the comparison result by the comparison unit 106. For example, the processing execution unit 107 executes the predetermined process by sending a predetermined notification to the service providing system 2. The notification may be performed by sending some kind of data. The notification may be performed by means of email or the like. Note that the predetermined process executed by the processing execution unit 107 is not limited to the process of sending a predetermined notification. For example, the predetermined process may be other processes such as payment or authentication. In this case, if it is not confirmed that the second expiration date is the latest, other processes such as payment or authentication will not be executed. Payment or authentication is executed by the repayment server 10.

For example, if the reconciliation execution result received from the card company system 3 indicates that there has been a change to the credit card and the comparison result of the first expiration date and the second expiration date indicates a match, the processing execution unit 107 sends a notification to the service providing system 2 indicating that the second expiration date is the latest expiration date. If the reconciliation execution result received from the card company system 3 indicates that there has been no change to the credit card and the comparison result of the first expiration date and the second expiration date indicates a mismatch, the processing execution unit 107 sends a notification to the service providing system 2 indicating that the second expiration date is not the latest expiration date.

In addition, if the reconciliation execution result received from the card company system 3 indicates that the credit card has been changed, the processing execution unit 107 may send a notification to the service providing system 2 indicating that the credit card has been changed, regardless of the comparison result by the comparison unit 106. In this case, the comparison unit 106 may not perform a comparison, or if the comparison unit 106 performs a comparison, the processing execution unit 107 may send a notification to the service providing system 2 indicating the comparison result by the comparison unit 106. In addition, if the reconciliation execution result received from the card company system 3 indicates that the credit card has been changed, the processing execution unit 107 may send the first expiration date to the service providing system 2.

[3-2. Functions realized by the service provision system]
In this embodiment, a case will be described in which each of the multiple service providing systems 2 has similar functions. For example, the service providing server 20 includes a data storage unit 200, a token transmission unit 201, and a display control unit 202. The data storage unit 200 is realized by the storage unit 22. The token transmission unit 201 and the display control unit 202 are realized by the control unit 21.

[Data storage unit]
The data storage unit 200 stores data necessary for providing services. For example, the data storage unit 200 stores a second card database DB2.

Figure 6 is a diagram showing an example of the second card database DB2. The second card database DB2 contains various information related to credit cards managed by the service providing system 2. For example, the second card database DB2 stores a user ID, a second token, a second card number, a second expiration date, and a second name. The second card database DB2 only needs to store any information related to credit cards, and the information stored in the second card database DB2 is not limited to the example shown in Figure 6. For example, the second card database DB2 may store personal information about the user. Note that the second card number contains less information than the first card number.

[Token sending unit]
The token sending unit 201 sends the second token and the second expiration date to the credit card refill system 1. For example, when a user's credit card needs to be refilled, the token sending unit 201 refers to the second card database DB2 and acquires the user ID, the second token, and the second expiration date of the user. The token sending unit 201 transmits the acquired user ID, the second token, and the second expiration date to the credit card refill system 1. The token sending unit 201 may also transmit at least one of the second card number and the second name to the credit card refill system 1.

[Display control unit]
The display control unit 202 transmits display data for each screen to the user terminal 40. The display data may be any data for displaying a screen on the user terminal 40, such as HTML data or image data.

[3-3. Functions realized by the card company system]
In this embodiment, a case will be described in which each of the multiple card company systems 3 has similar functions. For example, the card company server 30 includes a data storage unit 300 and a reconciliation execution unit 301. The data storage unit 300 is realized by the storage unit 32. The reconciliation execution unit 301 is realized by the control unit 31.

[Data storage unit]
The data storage unit 300 stores data necessary for managing credit cards. For example, the data storage unit 300 stores a third card database DB3.

Figure 7 is a diagram showing an example of the third card database DB3. The third card database DB3 contains various information related to credit cards managed by the card company system 3. For example, the third card database DB3 stores a third card number, a third expiration date, and a third name. The third card database DB3 may store any information related to credit cards, and the information stored in the third card database DB3 is not limited to the example shown in Figure 7. For example, the third card database DB3 may store a user ID and personal information of the user.

[Replacement Department]
The replacement execution unit 301 executes the replacement. For example, the replacement execution unit 301 determines whether a third card number, third expiration date, and third name that are the same as the first card number, first expiration date, and first name received from the replacement system 1 exist in the third card database DB3. In other words, the replacement execution unit 301 determines whether the third expiration date and third name associated with the third card number that is the same as the first card number in the third card database DB3 match the first expiration date and first name received along with the first card number. The replacement execution unit 301 transmits the execution result of the replacement to the replacement system 1.

[3-4. Functions implemented on user terminals]
The user terminal 40 includes a data storage unit 400 and a display control unit 401. The data storage unit 400 is realized by the storage unit 42. The display control unit 401 is realized by the control unit 41.

[Data storage section]
The data storage unit 400 stores data necessary for the user to use the service. For example, the data storage unit 400 stores a browser or dedicated application for displaying each screen.

[Display control unit]
The display control unit 401 displays each screen on the display unit 45 based on the display data received from the service providing system 2. For example, the user terminal 40 may be configured to acquire information such as the second token and the second expiration date by a script of each screen.

4. Processes performed in the washing system
Fig. 8 is a diagram showing an example of processing executed in the washing system 1. Fig. 8 also shows an example of processing executed in each of the service providing system 2, the card company system 3, and the user terminal 40. The processing in Fig. 8 is executed by the control units 11, 21, 31, and 41 operating in accordance with the programs stored in the memories 12, 22, 32, and 42, respectively. Fig. 8 explains the processing when a user performs a procedure to update the first expiration date and the second expiration date from the e-commerce service.

As shown in FIG. 8, when a user operates the user terminal 40 to log in to the e-commerce service, processing is executed between the service providing server 20-1 and the user terminal 40 to display the update screen SC5 on the display unit 45 (S1). When the second expiration date is entered on the update screen SC5, the user terminal 40 sends a first update request to the replacement server 10 (S2). When the replacement server 10 accepts the first update request (S3), it updates the first expiration date associated with the second token included in the first update request in the first card database DB1 (S4). As described above, the replacement server 10 sends a new first expiration date to the service providing server 20-1 at any time thereafter. The service providing server 20-1 updates the second expiration date it manages so that it is the same as the new first expiration date.

The service providing server 20-2 determines whether the reservation time for payment of the communication service usage fee has arrived (S5). If it is determined that the reservation time has not arrived (S5: N), the process of S5 is executed again. If it is determined that the reservation time has arrived (S5: Y), the service providing server 20-2 transmits the second token and second expiration date stored in the second card database DB2 for the communication service to the re-certification server 10 (S6).

When the reimbursement server 10 receives the second token and second expiration date for the communication service (S7), it references the first card database DB1 and performs reimbursement with the card company server 30 based on the first card number and other information associated with the second token, which is the same as the first token (S8). The reimbursement server 10 references the reimbursement execution results received from the card company server 30 (S9). If the reimbursement execution results indicate that the credit card information has been changed (S9: Changed), the reimbursement server 10 notifies the service provider server 20-2 that the credit card information has been changed (S10), and this process ends.

If the result of the reconciliation in S9 indicates that the credit card has not been changed (S9: No change), the reconciliation server 10 compares the first expiration date of the credit card that was the subject of the reconciliation with the second expiration date of the communication service (S11). If the first expiration date and the second expiration date of the communication service match (S11: Match), the reconciliation server 10 notifies the service provider server 20-2 that the credit card information has not been changed (S12), and the process ends. In this case, the reconciliation server 10 may execute a settlement process for the user to pay the communication service usage fee.

If the first expiration date and the second expiration date do not match in S11 (S11: Mismatch), the replacement server 10 notifies the service providing server 20-2 that the second expiration date has been updated (S13), and this process ends. In this case, the replacement server 10 may suspend the payment process. If the user updates the second expiration date for the communication service, the replacement server 10 may execute the suspended payment process. The service providing server 20-2 may update the old second expiration date based on the notification in S13. In this case, the notification shall include the latest second expiration date.

5. Summary of the embodiment
In this embodiment, when the reimbursement system 1 acquires the second token and the second expiration date, it performs reimbursement based on the first expiration date associated with the same first token as the second token. When reimbursement is performed, the reimbursement system 1 compares the first expiration date associated with the same first token as the second token with the second expiration date. The reimbursement system 1 executes a predetermined process based on the comparison result. This allows the reimbursement system 1 to achieve appropriate reimbursement. For example, if a user updates the first expiration date via an e-commerce service, the first expiration date on the reimbursement server 10 is the latest expiration date. Therefore, even if the second expiration date in the communication service is older, the reimbursement execution result received by the reimbursement server 10 from the card company server 30 indicates no change. By comparing the first expiration date with the second expiration date in the communication service, the reimbursement server 10 can determine that the second expiration date in the communication service is older. This allows appropriate reimbursement.

Furthermore, after the first expiration date has been updated, the re-launching system 1 obtains the second token and the second expiration date from the second service providing system 2. The re-launching system 1 performs re-launching based on the first expiration date associated with the same first token as the second token obtained from the second service providing system 2. When re-launching is performed, the re-launching system 1 compares the first expiration date associated with the same first token as the second token with the second expiration date obtained from the second service providing system 2. As a result, even if the first expiration date is updated by the first service providing system 2 and the second expiration date in the second service providing system 2 becomes outdated, the re-launching system 1 can perform appropriate re-launching.

Furthermore, the re-scrubbing system 1 does not perform re-scrubbing when the first expiration date is updated, but performs re-scrubbing when the second token and second expiration date are acquired. This allows for appropriate re-scrubbing without performing unnecessary re-scrubbing. For example, if re-scrubbing incurs costs to the card company, frequent re-scrubbing will incur unnecessary costs. In this regard, reducing the frequency of re-scrubbing can avoid unnecessary costs.

In addition, the washing system 1 transmits the second token and second expiration date to the washing system when the time for booking the service arrives. The washing system 1 obtains the second token and second expiration date from the service providing system when the time for booking arrives. This allows the washing system 1 to perform an appropriate washing when the time for booking arrives.

The washing system 1 also executes a predetermined process by sending a predetermined notification to the service providing system 2. This allows the washing system 1 to notify the service providing system 2 that the second expiration date is old.

The first card information indicates the expiration date of the credit card managed by the payment system. The second card information indicates the expiration date of the credit card managed by the service providing system 2. This allows the payment system 1 to determine whether the expiration date of the credit card is up to date.

6. Modifications
The present disclosure is not limited to the above-described embodiments, and can be modified as appropriate without departing from the spirit of the present disclosure.

For example, in the embodiment, a case has been described in which a user logs in to an e-commerce service and enters a new expiration date, but the user may also log in directly to the card management service provided by the card exchange system 1 and enter a new expiration date. In other words, the user may update the first expiration date without going through the e-commerce service or communication service. In this case, both the second expiration date in the e-commerce service and the second expiration date in the communication service will become outdated.

Figure 9 is a diagram showing an example of functions implemented in a modified washing system 1. The modified washing system 1 includes a second reception unit 108 and a second update unit 109. The second reception unit 108 and the second update unit 109 are implemented by the control unit 11. The second reception unit 108 receives a second update request from the user terminal 40 to update the first expiration date.

The second update request is data for requesting an update of the first expiration date. The second update request may be data in a predetermined format. For example, the second reception unit 108 accepts the second update request by receiving data in a predetermined format from the user terminal 40. In this variation, the second update request includes a user ID and a new first expiration date entered by the user. The user ID and new first expiration date may be added to the second update request as data separate from the second update request. In this variation, a case is described in which the credit card to be updated is identified by the user ID, but the credit card to be updated may also be identified by other information such as a card number or token. In this case, the other information may be pre-stored in the user terminal 40 or may be manually entered by the user.

The second update unit 109 updates the first expiration date based on the second update request. For example, the second update unit 109 updates the first expiration date by overwriting the first expiration date associated with the user ID included in the second update request, among the first expiration dates stored in the first card database DB1, with the new first expiration date included in the second update request. If the user ID and new first expiration date are separate data from the second update request, the second update unit 109 simply overwrites the first expiration date associated with the user ID, which is separate data, with the new first expiration date, which is also separate data.

In the modified example, the token acquisition unit 104 acquires the second token and second expiration date from the service providing system 2 after the first expiration date has been updated. This differs from the embodiment in that the user logs in directly to the exchange system 1 to update the first expiration date, but the exchange flow after the token acquisition unit 104 acquires the second token and second expiration date is the same as in the embodiment. In the modified example, even if exchange is requested from either the service providing system 2 for the e-commerce service or the communication service, exchange is performed in the same manner as in the embodiment.

In this modified example, the re-launching system 1 receives a second update request from the user terminal 40 to update the first expiration date. The re-launching system 1 updates the first expiration date based on the second update request. After the first expiration date is updated, the re-launching system 1 obtains a second token and a second expiration date from the service providing system. This allows the re-launching system 1 to achieve appropriate re-laundry even if the user directly logs in to the re-launching system 1 to update the first expiration date.

For example, the functions described as being realized by the refill server 10 may be shared among multiple computers in the refill system 1. In this case, each of the multiple computers can transmit its own processing results to the other computers, thereby realizing the sharing of functions. The refill system 1 may include at least one of the service provider system 2 and the card company system 3.

[7. Notes]
For example, the washing system according to the present disclosure can also be configured as follows.
(1)
a management unit that manages a first token and first card information related to a user's card in association with each other;
a token acquisition unit that acquires a second token and second card information related to the card;
a reconciliation execution unit that executes reconciliation for the card based on the first card information associated with the same first token as the second token;
a comparison unit that, when the reconciliation is performed, compares the first card information associated with the same first token as the second token with the second card information;
a processing execution unit that executes a predetermined process based on the comparison result by the comparison unit;
Washing system including.
(2)
The washing system includes:
a first receiving unit that receives a first update request for updating the first card information;
a first update unit that updates the first card information based on the first update request;
Further comprising:
the token acquisition unit acquires, after the first card information is updated, the second token and the second card information from a second service providing system different from the first service providing system among a plurality of service providing systems that provide services in which the user can use the card;
the reconciliation execution unit executes the reconciliation based on the first card information associated with the first token that is the same as the second token acquired from the second service providing system; and
the comparison unit, when the reconciliation is performed, compares the first card information associated with the first token that is the same as the second token with the second card information acquired from the second service providing system;
The washing system according to (1).
(3)
The washing system includes:
a second receiving unit that receives a second update request for updating the first card information from the user terminal of the user;
a second update unit that updates the first card information based on the second update request;
Further comprising:
the token acquisition unit acquires the second token and the second card information from a service providing system that provides a service that allows the user to use the card after the first card information is updated.
A washing system according to (1) or (2).
(4)
the reconciliation execution unit does not execute the reconciliation when the first card information is updated, and executes the reconciliation when the second token and the second card information are acquired.
A washing system according to (2) or (3).
(5)
the service providing system transmits the second token and the second card information to the reimbursement system when a reservation time for payment for the service arrives;
the token acquisition unit acquires the second token and the second card information from a service providing system that provides a service that allows the user to use the card when the reservation time arrives.
A washing system according to any one of (1) to (4).
(6)
the processing execution unit executes the predetermined processing by sending a predetermined notification to a service providing system that provides a service in which the user can use the card;
A washing system according to any one of (1) to (5).
(7)
the card is the user's credit card;
The first card information indicates the expiration date of the credit card managed by the credit card payment system,
the second card information indicates the expiration date of the credit card managed by a service providing system that provides a service in which the user can use the credit card;
A washing system according to any one of (1) to (6).

1 Refill system, 2 Service provision system, 3 Card company system, N Network, 10 Refill server, 11, 21, 31, 41 Control unit, 12, 22, 32, 42 Memory unit, 13, 23, 33, 43 Communication unit, 20 Service provision server, 30 Card company server, 40 User terminal, 44 Operation unit, 45 Display unit, 100 Data storage unit, 101 Management unit, 102 First reception unit, 103 First update unit, 104 Token acquisition unit, 105 Refill execution unit, 106 Comparison unit, 107 Processing execution unit, 108 Second reception unit, 109 Second update unit, 200 Data storage unit, 201 Token transmission unit, 202 Display control unit, 300 Data storage unit, 301 Refill execution unit, 400 Data storage unit, 401 Display control unit, B13, B51 Button, F10, F50 input form, SC1 registration screen, SC2 completion screen, SC3 order screen, SC4 confirmation screen, SC5 update screen, SC6 completion screen.

Claims (9)

a management unit that manages a first token and first card information related to a user's card in association with each other;
a token acquisition unit that acquires a second token and second card information related to the card from a service providing system that provides a service that allows the user to use the card ;
a reconciliation execution unit that transmits the first card information associated with the first token that is the same as the second token to a card company system of a card company that manages the card, and receives a reconciliation execution result for the card from the card company system ;
a comparison unit that compares the first card information associated with the same first token as the second token with the second card information when the execution result of the reconciliation received from the card company system indicates that there is no change to the card ;
a processing execution unit that executes a predetermined process by sending a predetermined notification to the service providing system, making a payment based on the card, or performing authentication based on the comparison result by the comparison unit; and
Washing system including. The washing system includes:
a first reception unit that receives a first update request for updating the first card information , the first update request including the second token and new first card information ;
a first update unit that updates the first card information by overwriting the first card information associated with the same first token as the second token included in the first update request with the new first card information included in the first update request;
Further comprising:
the token acquisition unit acquires the second token and the second card information from a second service providing system, which is different from the first service providing system into which the user logged in to transmit the first update request , among a plurality of service providing systems that provide services in which the user can use the card after the first card information is updated;
the reconciliation execution unit transmits to the card company system the first card information associated with the first token that is the same as the second token acquired from the second service providing system;
the comparison unit, when the reconciliation is performed, compares the first card information associated with the first token that is the same as the second token with the second card information acquired from the second service providing system;
The washing system of claim 1 . The washing system includes:
a second receiving unit that receives a second update request for updating the first card information from the user terminal of the user;
a second update unit that updates the first card information based on the second update request;
Further comprising:
the token acquisition unit acquires the second token and the second card information from a service providing system that provides a service that allows the user to use the card after the first card information is updated.
The washing system according to claim 1 or 2. the reconciliation execution unit does not transmit the first card information to the card company system at the timing when the first card information is updated, and transmits the first card information to the card company system when the second token and the second card information are acquired after the first card information is updated .
The washing system according to claim 2 . the service providing system transmits the second token and the second card information to the reimbursement system when a reservation time for payment for the service arrives;
the token acquisition unit acquires the second token and the second card information from the service providing system when the reservation time arrives.
The washing system according to claim 1 or 2. the processing execution unit executes the predetermined processing by transmitting the predetermined notification to the service providing system.
The washing system according to claim 1 or 2. the card is the user's credit card,
The first card information indicates the expiration date of the credit card managed by the credit card payment system,
the second card information indicates the expiration date of the credit card managed by a service providing system that provides a service in which the user can use the credit card;
The washing system according to claim 1 or 2. 1. A computer-implemented method for cleaning a surface, comprising:
a management step of associating and managing the first token and the first card information related to the user's card;
a token acquisition step of acquiring a second token and second card information related to the card from a service providing system that provides a service in which the user can use the card ;
a reconciliation execution step of transmitting the first card information associated with the first token that is the same as the second token to a card company system of a card company that manages the card, and receiving a reconciliation execution result for the card from the card company system ;
a comparison step of comparing the first card information associated with the same first token as the second token with the second card information when the execution result of the reconciliation received from the card company system indicates that there is no change to the card ;
a processing execution step of executing a predetermined process by transmitting a predetermined notification to the service providing system, making a payment based on the card, or performing authentication based on the comparison result of the comparison step;
A washing method including: a management unit that manages a first token and first card information related to a user's card in association with each other;
a token acquisition unit that acquires a second token and second card information related to the card from a service providing system that provides a service that allows the user to use the card ;
a reconciliation execution unit that transmits the first card information associated with the first token that is the same as the second token to a card company system of a card company that manages the card, and receives a reconciliation execution result for the card from the card company system ;
a comparison unit that compares the first card information associated with the same first token as the second token with the second card information when the execution result of the reconciliation received from the card company system indicates that there is no change to the card ;
a processing execution unit that executes a predetermined process by sending a predetermined notification to the service providing system, making a payment based on the card, or performing authentication based on the comparison result by the comparison unit;
A program that allows a computer to function as a