JP7572404B2 - Information processing program, information processing system, and information processing method - Google Patents

Description

The present invention relates to an information processing program, an information processing system, and an information processing method.

Conventionally, token payment, in which a payment is made using a token generated based on a payment-specific account (e.g., a credit card number, bank account number, etc.), is known as one of the technologies for enhancing the security of cashless payments. For example, in the system described in Non-Patent Document 1, a payment agency generates a token based on a user's credit card number, and the customer sends the token generated by the payment agency to an affiliated store. The user's payment at the affiliated store is then made based on the credit result using the token.

“What is token payment? Explaining its mechanism and effects”, [online], September 30, 2021, SB Payment Service, [Retrieved May 23, 2022], Internet, <URL: https://www.sbpayment.jp/support/ec/card_beginner/about-token-payment/>

In recent years, users have begun to use a variety of identifiers (e.g., My Number, point card numbers, health insurance card numbers, etc.) for purposes other than payment. However, from the perspective of ensuring security, users are not allowed to use these identifiers for payment, and are forced to use accounts dedicated to payment (e.g., credit card numbers, bank account numbers, etc.). To improve user convenience, it is hoped that a payment model will be realized that ensures security and uses any identifier, not just accounts dedicated to payment.

This disclosure has been made in light of these circumstances, and one of its objectives is to provide an information processing program, information processing system, and information processing method that can realize a payment model that is highly convenient for users while ensuring security.

An information processing program according to one aspect of the present disclosure causes a first information processing device connected to an identifier management entity device of an identifier management entity to function as a transmitter that transmits an issuance request for a token associated with an identifier managed by the identifier management entity to a second information processing device connected to a payment entity device of a payment entity, a receiver that receives from the second information processing device the token that is generated in the second information processing device in response to the issuance request and that is associated with a payment account used in the payment entity device, and a controller that associates the token received from the second information processing device with the identifier and stores them in a memory unit.

An information processing program according to another aspect of the present disclosure causes a computer as a second information processing device connected to a payment service provider device of a payment service provider to function as a receiver that receives, from a first information processing device connected to an identifier management subject device of an identifier management subject, a request to issue a token associated with an identifier managed by the identifier management subject, a generator that generates the token in response to the issuance request, a controller that associates the token with a payment account used by the payment service provider device and stores them in a memory unit, and a transmitter that transmits the token to the first information processing device.

An information processing system according to another aspect of the present disclosure includes a first information processing device connected to an identifier management entity device of an identifier management entity, and a second information processing device connected to a payment entity device of a payment entity, the first information processing device including a transmitter that transmits to the second information processing device a request for issuing a token associated with an identifier managed by the identifier management entity, a receiver that receives from the second information processing device the token generated in response to the issuance request, and a controller that associates the token received from the second information processing device with the identifier and stores them in a storage unit, and the second information processing device includes a generator that generates the token in response to the issuance request received from the first information processing device, and a controller that associates the token with a payment account used in the payment entity device and stores them in a storage unit.

An information processing method according to another aspect of the present disclosure is an information processing method in an information processing system including a first information processing device connected to an identifier management entity device of an identifier management entity and a second information processing device connected to a payment entity device of a payment entity, the information processing method including a step in which the first information processing device transmits to the second information processing device a request for issuance of a token associated with an identifier managed by the identifier management entity, a step in which the second information processing device generates the token in response to the issuance request, a step in which the second information processing device associates the token with a payment account used in the payment entity device and stores them in a storage unit, and a control unit in which the first information processing device associates the token with the identifier and stores them in the storage unit.

According to one aspect of the present disclosure, it is possible to realize a payment model that is highly convenient for users while ensuring security.

1 is a diagram showing a schematic configuration of an information processing system 1 according to a first embodiment. FIG. 2 is a diagram illustrating an example of a payment model according to the first embodiment. 1 is a diagram illustrating an example of a physical configuration of each device in an information processing system 1 according to a first embodiment. FIG. 2 is a diagram illustrating an example of a functional configuration of centers 40 and 50 according to the first embodiment. A figure showing an example of an association operation of an identifier, a token, and a payment account in the information processing system 1 related to the first embodiment. FIG. 2 is a diagram showing an example of a payment operation in the information processing system 1 according to the first embodiment. FIG. 13 is a diagram illustrating an example of a payment model according to the second embodiment. FIG. 11 is a diagram illustrating an example of a functional configuration of centers 40 and 50 according to the second embodiment. 13 is a diagram showing an example of a collaborative operation and a settlement operation in the information processing system 2 according to the second embodiment. FIG.

Below, a system according to one embodiment of the present invention will be described in detail with reference to the drawings. In addition, in the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

First Embodiment
Fig. 1 is a diagram showing an overview of an information processing system according to the first embodiment. As shown in Fig. 1, the information processing system 1 includes a device 10, one or more identifier management subject apparatuses _20m (1 < m < M, M is an integer equal to or greater than 1), one or more payment service provider apparatuses _30n (1 < n < N, N is an integer equal to or greater than 1), a center 40, and a center 50.

Device 10 is a device that stores an identifier for a purpose other than payment (e.g., My Number, point card number, insurance card number, etc.) or a device that can acquire such an identifier. Device 10 is, for example, a card, a key fob, a smartphone, a tablet, a personal computer, a terminal into which a card is inserted, or a terminal that acquires information from a key fob, but is not limited to these and may be any device.

The identifier management entity apparatus _20m is an apparatus used by an entity that manages identifiers stored or acquired by the device 10 (hereinafter referred to as the "identifier management entity"), and may be composed of one or more servers, etc. The identifier management entity may be, for example, an operator of My Number, an issuer of a point card, a health insurance association, a local government, etc., but is not limited to these and may be any entity that manages identifiers.

The payment service provider device _30n is a device used by a payment service provider, and may be composed of one or more servers, etc. Payment service providers are, for example, but not limited to, credit card companies, banks, fund transfer businesses, etc., and may be any business that performs payment using a payment account (hereinafter, referred to as a "payment account"). A payment account is, for example, but not limited to, a credit card number, a bank account number, or a specified account.

The center 40 is a first information processing device communicatively connected to one or more identifier management principal devices 20 _m . The center 40 has an interface (hereinafter referred to as "identifier manager I/F") with the identifier management principal device 20 _m , and is connected to the identifier management principal device 20 _m via, for example, an API (Application Programming Interface). The center 40 is communicatively connected to the device 10, and has an interface (hereinafter referred to as "user I/F") with the device 10. The center 40 may provide applications and/or data to the device 10 via the user I/F.

The center 50 is a second information processing device communicatively connected to one or more payment service provider devices 30 _n . The center 50 has an interface (hereinafter referred to as "payment service provider I/F") between the center 50 and the payment service provider devices 30 _n , and is connected to the payment service provider devices 30 _n via, for example, an API. The center 50 may be, for example, an information processing device used by a PSP (Payment Service Provider). The center 50 is communicatively connected to the device 10 and has an interface (hereinafter referred to as "user I/F") with the device 10. The center 50 may provide applications and/or data to the device 10 via the user I/F. The center 50 is communicatively connected to the center 40 and has an interface (hereinafter referred to as "center-to-center I/F") with the center 40. The center 50 is connected to the center 40 via, for example, an API.

The device 10, one or more identifier management subject apparatuses 20 _m , one or more payment service provider apparatuses 30 _n , center 40, and center 50 may each be separate information processing apparatuses, or at least two of these may be included in the same information processing apparatus. For example, the center 40 and the center 50 may be separate information processing apparatuses, or may be included in the same information processing apparatus.

Hereinafter, when there is no need to distinguish between one or more identifier management principal apparatus _20m (1≦m≦M, M is an integer equal to or greater than 1), they will be collectively referred to as identifier management principal apparatus 20. Also, when there is no need to distinguish between one or more payment service provider apparatus _30n (1≦n≦N, N is an integer equal to or greater than 1), they will be collectively referred to as payment service provider apparatus 30.

Fig. 2 is a diagram showing an example of a payment model according to the first embodiment. For example, in Fig. 2, My Number and point card numbers are shown as examples of identifiers managed by identifier management principal devices ₂₀₁ and _202. As shown in Fig. 2, the types of identifiers managed by each identifier management principal device 20 may differ. Also, bank account numbers and credit card numbers are shown as examples of payment accounts managed by payment service provider devices ₃₀₁ and _302. Note that the payment model shown in Fig. 2 is merely an example, and the configuration for realizing the payment model according to the first embodiment is of course not limited to that shown in the figure.

As shown in FIG. 2, the center 40 associates and stores the identifiers managed by the identifier management entity device 20 with the tokens issued by the center 50. For example, the center 40 holds information associating the identifiers with the tokens (hereinafter referred to as "association information") 401a. The center 50 also associates and stores the tokens with the payment accounts. For example, the center 50 holds information associating the tokens with the payment accounts (hereinafter referred to as "association information") 501a.

In the payment model shown in Fig. 2, the device 10 transmits a payment request to the center 40 using an identifier (here, My Number "A001") assigned by the identifier management principal apparatus _20-1 . The center 40 transmits a payment request to the center 50 using a token #1 associated with the identifier. The center 50 performs a process related to payment (hereinafter referred to as "payment process") between the payment service provider apparatus _30-1 corresponding to the payment account (here, bank account number "xxxxxxxxxxx3") associated with the token #1 from the center 40. The center 50 transmits the result of the payment process with the payment service provider apparatus _30-1 to the device 10.

In this way, in the information processing system 1 according to the first embodiment, an identifier and a payment account are associated with each other via a token. This enables payment by the payment service provider device 30 using a payment account associated with an identifier via a token, thereby achieving highly secure payments and improving user convenience compared to when the identifier and the payment account are directly associated with each other.

<Configuration>
Next, the physical configuration and the functional configuration of the information processing system 1 according to the first embodiment will be described.
Physical Configuration
3 is a diagram showing an example of the physical configuration of each device in the information processing system 1 according to the first embodiment. Each device in the information processing system 1 (e.g., the device 10, the identifier management entity device 20, the payment service provider device 30, the center 40, and the center 50, etc.) includes a processor 11, a storage device 12, a communication device 13 that performs wired or wireless communication, an input device that accepts various input operations, and an input/output device 14 that outputs various information. The processor 11 executes a program stored in the storage device 12 to realize at least a part of the function of the control unit of each device.

The processor 11 is, for example, a CPU (Central Processing Unit) and controls each device in the information processing system 1. The processor 11 may execute various processes described in this embodiment by reading and executing a program from the storage device 12. Each device in the information processing system 1 may be composed of one or more processors 11. Furthermore, each of the devices may be referred to as a computer.

The storage device 12 is composed of storage such as a memory, a hard disk drive (HDD) and/or a solid state drive (SSD). The storage device 12 may store various information (e.g., programs executed by the processor 11) necessary for the processor 11 to execute processing. The storage device 12 realizes at least some of the functions of the storage unit of each device.

The communication device 13 is a device that communicates over a network, and may include, for example, a network card, a communication module, a chip, an antenna, etc. The input/output device 14 includes, for example, an input device such as a keyboard, a touch panel, a mouse and/or a microphone, and an output device such as a display and/or a speaker. The communication device 13 realizes at least a portion of the functions of the transmitting unit, receiving unit, or transmitting/receiving unit of each device.

The physical configuration described above is merely one example. Each device in the information processing system 1 may omit some of the hardware shown in FIG. 3, or may include hardware not shown in FIG. 3. In addition, the hardware shown in FIG. 3 may be configured from one or more chips.

<Functional configuration>
Fig. 4 is a diagram showing an example of the functional configuration of the centers 40 and 50 according to the first embodiment. As shown in Fig. 4, the center 40 includes a storage unit 401, a token issuance control unit 402, a risk assessment unit 403, a payment control unit 404, and a transmission/reception unit 405. Note that the token issuance control unit 402, the risk assessment unit 403, and the payment control unit 404 may be collectively referred to as a control unit.

The storage unit 401 stores the identifier and the token in association with each other. Specifically, the storage unit 401 may store association information 401a (see FIG. 2, for example) that associates the identifier and the token. The storage unit 401 may also store information about the identifier (hereinafter referred to as "identifier information") 401b. The identifier information 401b may be received from the identifier management entity device 20 by the transmission/reception unit 405.

Here, the identifier information 401b may include at least one of the following: an identifier; information about the identifier management entity that manages the identifier (hereinafter referred to as "identifier management entity information"); information about authentication using the identifier (hereinafter referred to as "authentication information"); and information about the attributes of the user of the identifier (hereinafter referred to as "attribute information"). Furthermore, the identifier management entity information may include, for example, the name and/or identification information of the identifier management entity. The authentication information may be, for example, information about user authentication and/or provider connection. The attribute information may include, for example, at least one of the user's name, address, and contact information.

The token issuance control unit 402 controls the issuance of a token associated with an identifier in response to a token issuance request (hereinafter referred to as a "token issuance request") from the device 10 or the identifier management principal device 20. Specifically, when a token issuance request is received from the device 10 or the identifier management principal device 20 by the transmission/reception unit 405, the token issuance control unit 402 controls the transmission of the token issuance request to the center 50. In addition, the token issuance control unit 402 may restrict the transmission of the token issuance request to the center 50 based on the result of the risk assessment by the risk assessment unit 403.

The risk assessment unit 403 may perform risk assessment of the identifier based on the identifier information 401b stored in the storage unit 401. Specifically, the risk assessment unit 403 may assess the risk level of the identifier based on at least one of the identifier management subject information, authentication information, and attribute information of the identifier information 401b. For example, if the identifier management subject is highly reliable (for example, if it is the identifier management subject for My Number), the risk assessment unit 403 may assess the risk of the identifier at a low (i.e., high security) level. On the other hand, if the identifier management subject is unreliable (for example, if it is the identifier management subject for point card numbers), the risk assessment unit 403 may assess the risk of the identifier at a high (i.e., low security) level.

The risk assessment unit 403 may also assess the risk level of the identifier based on at least one of information from the center 50 regarding the use of the token associated with the identifier, information provided by the identifier management entity device 20, and information regarding transactions at the center 40 (hereinafter referred to as "transaction information").

The payment control unit 404 controls the payment process in response to a payment request from the device 10. Specifically, in response to a payment request using an identifier from the device 10, the payment control unit 404 may acquire a token associated with the identifier in the memory unit 401, and cause the transmission/reception unit 405 to transmit a payment request using the token. The payment control unit 404 may also restrict the execution of the payment process for the center 50 based on the result of the risk assessment by the risk assessment unit 403.

The transmission/reception unit 405 functions as at least one of a user I/F, an identifier management principal I/F, and an inter-center I/F. Specifically, the transmission/reception unit 405 may receive identifier information from the identifier management principal device 20. The transmission/reception unit 405 may also receive a token issuance request from the device 10 or the identifier management principal device 20. The transmission/reception unit 405 may also transmit a token issuance request to the center 50 in accordance with the control of the token issuance control unit 402.

The center 50 includes a memory unit 501, a token generation unit 502, a risk assessment unit 503, a payment control unit 504, and a transmission/reception unit 505. The token generation unit 502, the risk assessment unit 503, and the payment control unit 504 may be collectively referred to as a control unit.

The storage unit 501 stores the token in association with the payment account. Specifically, the storage unit 501 may store association information 501a (e.g., see FIG. 2) that associates the token with the payment account. The storage unit 501 may also store information about the payment account (hereinafter referred to as "payment account information") 501b. The payment account information 501b may be received from the payment service provider device 30 by the transmission/reception unit 505.

Payment account information 501b may include at least one of information indicating a payment account such as a card number or bank account number, information indicating an expiration date, information regarding a payment business operator using the payment account (hereinafter referred to as "payment business operator information"), and attribute information regarding attributes of a user using the payment account. Payment business operator information may be, for example, the name of the payment business operator. Furthermore, attribute information may include, for example, at least one of a user's name, address, and contact information. Furthermore, payment account information 501b may include authentication information regarding authentication using the payment account, transaction information regarding transactions using the payment account, etc.

The token generation unit 502 controls the issuance of a token associated with a payment account in the memory unit 501 in response to a token issuance request from the center 40. Specifically, when a token issuance request is received from the center 40 by the transmission/reception unit 505, the token generation unit 502 generates a token. In addition, the token generation unit 502 may restrict the generation of tokens based on the result of risk assessment by the risk assessment unit 503.

The risk assessment unit 503 may perform risk assessment for the token based on the payment account information 501b stored in the memory unit 501. The risk assessment unit 503 may also assess the level of risk for the token based on at least one of the information from the center 40, the information provided by the payment service provider device 30, and the transaction information at the center 50.

The payment control unit 504 controls the payment process in response to a payment request from the center 40. Specifically, in response to a payment request using a token from the center 40, the payment control unit 504 may acquire a payment account associated with the token in the memory unit 501, and cause the transmission/reception unit 505 to transmit a payment request using the payment account to the payment business device 30. The payment control unit 504 may also restrict the execution of payment processing for the payment business device 30 based on the result of the risk assessment by the risk assessment unit 503.

The transmission/reception unit 505 functions as at least one of a user I/F, an identifier management entity I/F, and an inter-center I/F. Specifically, the transmission/reception unit 505 may receive a token issuance request from the center 40. The transmission/reception unit 505 may also receive a payment request including a token from the center 40. The transmission/reception unit 505 may also transmit, to the device 10, information indicating the result of a payment process using a payment account associated with the token.

<Operation>
The operation of the information processing system 1 according to the first embodiment will be described with reference to Figures 5 and 6. Note that Figures 5 and 6 are merely examples, and some steps may be omitted, or steps not shown may be added. Furthermore, the order of at least two steps may be interchanged. Furthermore, in Figures 5 and 6, it is assumed that the device 10 stores or acquires an identifier managed by the identifier management subject device 20.

<Association Operation>
Fig. 5 is a diagram showing an example of an association operation of an identifier, a token, and a payment account in the information processing system 1 according to the first embodiment. As shown in Fig. 5, in step S101, the device 10 transmits a token issuance request to the center 40 via the identifier management principal apparatus 20. Note that the device 10 may transmit the token issuance request directly to the center 40 without passing through the identifier management principal apparatus 20. The center 40 receives the token issuance request from the identifier management principal apparatus 20 or the device 10. The token issuance request may include an identifier.

In step S102, the center 40 performs a risk assessment of the identifier included in the token issuance request. For example, the center 40 may perform a risk assessment based on information acquired from at least one of the identifier information 401b, the identifier management principal apparatus 20, and the device 10, and determine whether or not the result of the risk assessment satisfies a predetermined level. If the result of the risk assessment satisfies the predetermined level, the operation proceeds to step S103, and if the result of the risk assessment does not satisfy the predetermined level, the center 40 may transmit information indicating that the token issuance request has been rejected to the device 10 and/or the identifier management principal apparatus 20, although this is not shown in the figure.

In step S103, the center 40 transmits a token issuance request to the center 50. In step S104, in response to the token issuance request from the center 40, the center 50 transmits a payment account registration request (hereinafter referred to as a "payment account registration request") to the device 10.

In step S105, the device 10 transmits payment account information 501b to the center 50 in response to a payment account registration request from the center 50. The center 50 stores the payment account information 501b received from the device 10 in the storage unit 501.

In step S106, the center 50 may perform authentication processing (e.g., credit) of the payment account with the payment provider device 30 based on the payment account information 501b from the device 10. Specifically, the center 50 may receive the result of the authentication processing of the payment account in the payment provider device 30 based on the authentication information by transmitting the authentication information of the payment account acquired from the device 10 to the payment provider device 30.

In step S107, the center 50 generates a token. Specifically, the center 50 may generate a token if the authentication process for the payment account is successful in step S106. The token is generated for each identifier received by the center 40 in step S101 (e.g., FIG. 2). On the other hand, the token does not have to be generated for each payment account, and multiple tokens corresponding to multiple identifiers may correspond to the same payment account.

In step S108, the center 50 associates the token generated in step S107 with the payment account indicated by the payment account information 501b received in step S105 and stores them in the storage unit 501. For example, as shown in FIG. 2, the center 50 may associate the token with the payment account in the association information 501a and store them.

In step S109, the center 50 transmits information regarding the token generated in step S107 (hereinafter referred to as "token information") to the center 40. In step S110, the center 40 associates the identifier received from the device 10 in step S101 with the token indicated by the token information received from the center 50 in step S109, and stores them in the storage unit 401. For example, as shown in FIG. 2, the center 40 may store association information 401a that associates the identifier with the token.

<Payment Operation>
6 is a diagram showing an example of a payment operation in the information processing system 1 according to the first embodiment. As shown in FIG 6, in step S201, the device 10 transmits a payment request including an identifier to the center 40.

In step S202, the center 40 performs a risk assessment of the identifier in response to a payment request from the device 10. For example, the center 40 may perform a risk assessment based on at least one of the identifier information 401b, the information acquired from the identifier management principal device 20, and the information acquired from the device 10, and determine whether or not the result of the risk assessment satisfies a predetermined level. If the result of the risk assessment satisfies the predetermined level, the operation proceeds to step S203, and if the result of the risk assessment does not satisfy the predetermined level, the center 40 may transmit information to the device 10 indicating that the payment request has been rejected, although this is not shown.

In step S203, the center 40 refers to the association information 401a (e.g., FIG. 2) in the memory unit 401 and converts the identifier included in the payment request from the device 10 into a token. In step S204, the center 40 transmits the payment request including the token to the center 50.

In step S205, the center 50 performs risk assessment of the token in response to the payment request from the center 40. For example, the center 50 may perform risk assessment based on the payment account information 501b and/or information acquired from at least one of the payment provider device 30, the center 40, and the device 10, and determine whether the result of the risk assessment satisfies a predetermined level. If the result of the risk assessment satisfies the predetermined level, the operation proceeds to step S206, and if the result of the risk assessment does not satisfy the predetermined level, the center 50 may transmit information indicating that the payment request has been rejected to the device 10, although this is not shown. Note that the center 50 may transmit the information to the device 10 via the center 40.

In step S206, the center 50 refers to the association information 501a (e.g., FIG. 2) stored in the memory unit 501 and converts the token included in the payment request from the center 40 into a payment account. In step S207, the center 50 transmits the payment request including the payment account to the payment service provider device 30.

In step S208, the payment service provider device 30 transmits information indicating the result of the payment process using the payment account to the center 50. In step S209, the center 50 transmits information indicating the result of the payment process to the device 10. Note that the center 50 may transmit the information to the device 10 via the center 40.

As described above, according to the information processing system 1 of the first embodiment, the identifier and the token are associated at the center 40, and the token and the payment account are associated at the center 50, so that the identifier and the payment account are associated through the token. This enables payment by the payment service provider device 30 using the payment account associated with the identifier through the token, so that more secure payment can be achieved and user convenience can be improved compared to when the identifier and the payment account are directly associated.

Second Embodiment
Next, an information processing system 2 according to the second embodiment will be described, focusing on the differences from the information processing system 1 according to the first embodiment. As described in the first embodiment, the center 40 of the information processing system 2 associates an identifier with a token, and the center 50 associates a token with a payment account. The information processing system 2 according to the second embodiment differs from the information processing system 1 according to the first embodiment in that identifier information on an identifier associated with a token is transmitted from the center 40 to the center 50, and the identifier, token, and payment account are associated in the center 50.

Figure 7 is a diagram showing an example of a payment model according to the second embodiment. Note that in Figure 7, differences from the payment model shown in Figure 2 will be mainly described. As shown in Figure 7, the center 50 associates and stores not only the token and the payment account, but also the identifier linked from the center 40. For example, in the association information 501a of the center 50, the token, the payment account, and the identifier are associated with each other.

For example, in the payment model shown in FIG. 7, the device 10 transmits a token issuance request to the center 50 using an identifier (here, point card number "Y001") assigned by the identifier management entity apparatus _202. In response to the token issuance request, the center 50 transmits a token #2 associated with the identifier to the device 10. The device 10 transmits a payment request to the center 50 using the token #2. The center 50 performs a payment process with the payment service provider apparatus 302 corresponding to the payment account (here, credit card number "xxxx xxxx xxxx xxx1") associated with the token #2. The center 50 transmits the result of the payment process with the payment service provider apparatus ₃₀₂ to the device ₁₀ .

In this way, in the information processing system 2 according to the second embodiment, in addition to the token and the payment account, the center 50 associates the identifier linked from the center 40. This allows the device 10 to make a payment through the payment service provider apparatus 30 using the token associated with the identifier without going through the center 40, thereby improving user convenience.

<Configuration>
The physical configuration of each device constituting the information processing system 2 according to the second embodiment is similar to the physical configuration of each device constituting the information processing system 1 according to the first embodiment described with reference to FIG.

Figure 8 is a diagram showing an example of the functional configuration of centers 40 and 50 according to the second embodiment. In Figure 8, differences from Figure 4 will be mainly described. As shown in Figure 8, the center 40 of the information processing system 2 differs from Figure 4 in that it includes a collaboration control unit 406, and the center 50 includes a collaboration control unit 506. In addition, the center 40 does not have to include a payment control unit 404. Note that the collaboration control unit 406 may be collectively referred to as a control unit together with the token issuance control unit 402 and the risk assessment unit 403. Similarly, the collaboration control unit 506 may be collectively referred to as a control unit together with the risk assessment unit 503 and the payment control unit 504.

As shown in FIG. 8, the collaboration control unit 406 acquires identifier information regarding the identifier associated with the token from the storage unit 401. For example, the collaboration control unit 406 may acquire identifier information 401b from the storage unit 401. The transmission/reception unit 405 transmits the acquired identifier information 401b to the center 50. The identifier information 401b may include at least one of the identifier, identifier management subject information, authentication information, and attribute information, as described above.

The center 50 of the information processing system 2 differs from that of FIG. 4 in that it includes a collaboration control unit 506. The collaboration control unit 506 may be collectively referred to as a control unit together with the risk assessment unit 503 and the payment control unit 504.

The linkage control unit 506 associates the identifier indicated by the identifier information 401b from the center 40 with the token and the payment account and stores it in the memory unit 501.

The payment control unit 504 controls the payment process in response to a payment request from the center 40 or the device 10. Specifically, in response to a payment request using a token from the device 10, the payment control unit 504 may acquire a payment account associated with the token in the association information 501a, and cause the transmission/reception unit 505 to transmit a payment request using the payment account to the payment business device 30.

The transmission/reception unit 505 receives the identifier information 401b from the center 40. The transmission/reception unit 505 may also receive a token issuance request including the identifier from the device 10, and transmit a token associated with the identifier to the device 10. The transmission/reception unit 505 may also receive a payment request including the token from the device 10. The transmission/reception unit 505 may also transmit information indicating the result of the payment process using the payment account associated with the token to the device 10.

<Operation>
Fig. 9 is a diagram showing an example of a collaborative operation and a payment operation in the information processing system 2 according to the second embodiment. In Fig. 9, it is assumed that an identifier and a token are associated with each other in the center 40, and that a token and a payment account are associated with each other in the center 50, according to the operation described in Fig. 5. The following description of Fig. 9 will focus on the differences from the payment operation shown in Fig. 6.

As shown in FIG. 9, in step S301, the center 40 transmits identifier information 401b relating to the identifier associated with the token to the center 50. In step S302, the center 40 associates the identifier indicated by the identifier information 401b with the token and the payment account, and stores them in the storage unit 501 (e.g., association information 501a in FIG. 7).

In step S303, the device 10 transmits a token issuance request to the center 50. The token issuance request may include an identifier.

In step S304, the center 50 may perform a risk assessment of the identifier included in the token issuance request. For example, the center 50 may perform a risk assessment based on information acquired from at least one of the memory unit 501, the identifier management principal device 20, and the device 10, and determine whether or not the result of the risk assessment satisfies a predetermined level. If the result of the risk assessment satisfies the predetermined level, the operation proceeds to step S305, and if the result of the risk assessment does not satisfy the predetermined level, the center 50 may transmit information to the device 10 indicating that the token issuance request has been rejected, although this is not shown.

In step S305, the center 50 transmits a token associated with the identifier to the device 10. In step S306, the device 10 transmits a payment request to the center 50 using the token. Steps S307 to S311 are similar to steps S205 to S209 in FIG. 6, and therefore will not be described.

Although not shown, the device 10 may request the center 50 to confirm and/or update the payment account associated with the identifier and/or token. In response to a request from the device 10, the center 50 may refer to the storage unit 501 (e.g., association information 501a and/or payment account information 501b) and confirm and/or update the payment account.

As described above, according to the information processing system 2 of the second embodiment, the center 50 associates the token with the payment account, as well as the identifier linked from the center 40. This allows the device 10 to make a payment through the payment service provider device 30 using the token associated with the identifier without going through the center 40, thereby improving user convenience.

Other Embodiments
The above-described embodiments are intended to facilitate understanding of the present invention, and are not intended to limit the present invention. The elements of the embodiments, as well as their arrangements, materials, conditions, shapes, sizes, etc., are not limited to those shown as examples and can be changed as appropriate. In addition, configurations shown in different embodiments can be partially substituted or combined with each other.

1, 2...information processing system, 10...device, 11...processor, 12...storage device, 13...communication device, 14...input/output device, 20...identifier management entity device, 30...payment business operator device, 40...center, 50...center, 401...storage unit, 402...token issuance control unit, 403...risk assessment unit, 404...payment control unit, 405...transmission/reception unit, 406...cooperation control unit, 501...storage unit, 502...token generation unit, 503...risk assessment unit, 504...payment control unit, 505...transmission/reception unit, 506...cooperation control unit, 401a...association information, 401b...identifier information 501a...association information, 501b...payment account information

Claims (10)

A first information processing device connected to an identifier management subject device of an identifier management subject,
A transmitter that transmits a request for issuing a token associated with the identifier managed by the identifier management entity to a second information processing device connected to a payment service provider device used by a payment service provider;
a receiving unit that receives, from the second information processing device, the token that is generated in the second information processing device in response to the issuance request and that is associated with a payment account used in the payment service provider device;
a control unit that associates the token and the identifier received from the second information processing device with each other and stores them in a storage unit;
An information processing program that functions as a The transmission unit transmits information regarding the identifier associated with the token to the second information processing device so that the information regarding the identifier is associated with the token and the payment account in the second information processing device.
The information processing program according to claim 1 . The control unit limits transmission of the issuance request for the token based on a result of the risk evaluation of the identifier.
3. The information processing program according to claim 1 or 2. The control unit restricts execution of a process related to a payment in response to a payment request including the identifier or a payment request including the token associated with the identifier, based on a result of the risk assessment of the identifier.
3. The information processing program according to claim 1 or 2. A second information processing device connected to a payment service provider device of a payment service provider,
a receiving unit that receives, from a first information processing device connected to an identifier management principal device of the identifier management principal, a request for issuing a token associated with an identifier managed by the identifier management principal;
A generating unit that generates the token in response to the issuance request;
A control unit that associates the token with a payment account used in the payment service provider device and stores the token in a storage unit;
a transmitter that transmits the token to the first information processing device;
An information processing program that functions as a The receiving unit receives information regarding the identifier associated with the token from the first information processing device,
The control unit stores information about the identifier in the storage unit in association with the token and the payment account.
6. An information processing program according to claim 5. The control unit limits the generation of the token by the generation unit based on a result of risk assessment of the settlement account.
7. The information processing program according to claim 5 or 6. The control unit restricts execution of a process related to a payment in response to a payment request including the identifier or a payment request including the token associated with the identifier based on a result of the risk assessment of the token.
7. The information processing program according to claim 5 or 6. An information processing system including a first information processing device connected to an identifier management subject device of an identifier management subject, and a second information processing device connected to a payment service provider device of a payment service provider,
The first information processing device is
a transmission unit that transmits, to the second information processing device, a request for issuing a token associated with the identifier managed by the identifier management entity;
a receiving unit that receives the token generated in response to the issuance request from the second information processing device;
a control unit that causes the token received from the second information processing device and the identifier to be stored in a storage unit in association with each other;
The second information processing device is
a generation unit that generates the token in response to the issuance request received from the first information processing device;
A control unit that associates the token with a payment account used in the payment service provider device and stores the token in a storage unit;
An information processing system comprising: An information processing method in an information processing system including a first information processing device connected to an identifier management subject device of an identifier management subject, and a second information processing device connected to a payment service provider device of a payment service provider,
a step of transmitting, from the first information processing device, a request for issuing a token associated with an identifier managed by the identifier management entity to the second information processing device;
The second information processing device generates the token in response to the issuance request;
The second information processing device stores the token in a storage unit in association with a payment account used in the payment service provider device;
The first information processing device has a control unit that associates the token with the identifier and stores them in a storage unit.
Information processing methods.

Images