JP7570444B2 - Payment support program, payment support system, and payment support method - Google Patents

Description

The present invention relates to a payment support program, a payment support system, and a payment support method.

Conventionally, technology is known that uses a token corresponding to the user's payment method to process the payment of a user's transaction.

For example, the payment processing system described in Patent Document 1 includes a storage device that stores a user's identification information and biometric authentication information, and a calculation device. The calculation device executes the following processes: receiving a token issued by the payment agency system for the user's payment medium from the user's user terminal; linking the token with the user's identification information and biometric authentication information and storing it in the storage device; obtaining the user's biometric information from a specified store terminal when the user has a payment opportunity and performing biometric authentication based on the biometric information and biometric authentication information; and, if the biometric authentication is successful, extracting the token held for the user from the storage device and transmitting a payment request including the token and the payment amount at the payment opportunity to the payment agency system.

JP 2021-174298 A

In the payment processing system described in Patent Document 1, a user provides a token obtained from a payment agency system to the payment processing system in advance. Then, when the user makes a transaction at a store, the payment processing system authenticates the user's biometric information and extracts the token. However, in this payment processing system, since the biometric information is authenticated and processing is performed using the token obtained in advance from the user, user involvement is required for each payment.

The present invention aims to provide a payment support program, a payment support system, and a payment support method that can more easily process payments using tokens.

A payment assistance program according to one embodiment of the present invention causes a computer to implement the following: a dedicated token issuing unit that issues dedicated token information regarding a dedicated token used in settlement of a transaction between a user and a trader to a trader system of a trader based on first payment means information regarding a first payment means used by the user when trading with the trader; a correspondence generating unit that generates correspondence information that associates the first payment means information and the dedicated token information; a payment request acquiring unit that acquires first payment request information including the dedicated token information and payment information regarding settlement of a transaction with the user from the trader system; a payment means identifying unit that identifies the first payment means information corresponding to the dedicated token information based on the correspondence information; and a payment request providing unit that provides second payment request information including the payment information and the identified first payment means information to a payer system of a payer that processes the payment.

A payment support system according to one embodiment of the present invention includes a dedicated token issuing unit that issues dedicated token information regarding a dedicated token used in settlement of a transaction between a user and a trader to a trader system of the trader based on first payment means information regarding a first payment means used by the user when trading with the trader, a correspondence generating unit that generates correspondence information that associates the first payment means information and the dedicated token information, a payment request acquiring unit that acquires first payment request information including the dedicated token information and payment information regarding settlement of the transaction with the user from the trader system, a payment means identifying unit that identifies the first payment means information corresponding to the dedicated token information based on the correspondence information, and a payment request providing unit that provides second payment request information including the payment information and the identified first payment means information to the payer system of the payer that processes the payment.

In one aspect of the present invention, a payment support method includes a computer issuing dedicated token information regarding a dedicated token used in settlement of a transaction between a user and a trader to a trader system of the trader based on first payment method information regarding a first payment method used by a user when trading with the trader, generating correspondence information that associates the first payment method information and the dedicated token information, obtaining first payment request information including the dedicated token information and payment information regarding settlement of the transaction with the user from the trader system, identifying first payment method information that corresponds to the dedicated token information based on the correspondence information, and providing second payment request information including the payment information and the identified first payment method information to a settler system of the settler that processes the payment.

In this invention, a "part" does not simply mean a physical means, but also includes cases where the functions of the "part" are realized by software. Furthermore, the functions of one "part" or device may be realized by two or more physical means, devices, or software modules, and the functions of two or more "parts" or devices may be realized by one physical means, device, or software module.

The present invention provides a payment support program, a payment support system, and a payment support method that can more easily process payments using tokens.

FIG. 2 is a diagram showing an overview of processing in a payment support system 100 according to an embodiment of the present invention. 1 is a diagram showing a configuration of a payment support system 100 according to an embodiment of the present invention. FIG. 4 is a diagram showing an example of payment method information stored in a storage unit 105. FIG. 4 is a diagram showing an example of correspondence relationship information stored in a storage unit 105. FIG. 11 is a diagram showing an example of first payment request information stored in a storage unit 105. FIG. 11 is a diagram showing an example of payment result information stored in storage unit 105. 10A to 10C are diagrams illustrating an example of error information stored in a storage unit 105. 1 is a sequence chart showing an example of processing in payment processing system 100. 1 is a sequence chart showing an example of processing in payment processing system 100. 1 is a sequence chart showing an example of processing in payment processing system 100. FIG. 11 illustrates an example of the hardware configuration of a computer 1100.

A preferred embodiment of the present invention will be described with reference to the attached drawings. FIG. 1 is a diagram showing an overview of the processing in a payment support system 100, which is one embodiment of the present invention.

The payment support system 100 is an information processing system realized by a payment support program. The payment support system 100 issues dedicated token information to be used in settling a transaction with a trader based on payment method information relating to the payment method used by the user, and generates correspondence information that associates the payment method information with the dedicated token information. When settling a transaction between a user and a trader, the payment support system 100 acquires the dedicated token information from the trader's trader system, identifies the payment method information that corresponds to the dedicated token information, and provides the payment method information to the settler system of the settler that processes the settlement of the transaction.

First, the dedicated token issuance process in the payment support system 100 will be described. The user provides payment method information to the trader system (S111). The payment support system 100 acquires the payment method information from the trader system (S112). The payment support system 100 issues dedicated token information to the trader system based on the payment method information (S113), and generates correspondence information that associates the payment method information with the dedicated token information (S114).

Next, the payment support process using the dedicated token information in the payment support system 100 will be described. In response to a transaction between a user and a trader, the payment support system 100 acquires first payment request information including payment information related to the payment and dedicated token information from the trader system (S121). The payment support system 100 identifies payment method information corresponding to the dedicated token information. The payment support system 100 provides second payment request information including the payment information and the identified payment method information to the settler system (S122). The settler system performs payment processing in response to the second payment request information. The payment support system 100 acquires payment result information regarding the result of the payment processing in response to the second payment request information from the settler system (S123).

If the payment processing cannot be performed normally in the payer system, the payment support system 100 acquires error information from the payer system (S131). The payment support system 100 suggests to the user that they change the payment method corresponding to the error to another payment method (S132).

The payment support system 100 receives a change request from the user to change the payment method to another payment method (S141) and updates the correspondence information.

Figure 2 is a diagram showing the configuration of a payment support system 100, which is one embodiment of the present invention. The payment support system 100 is communicatively connected to a trader system 200, a user terminal 300, and a settler system 400 via a network such as the Internet. Details of the payment support system 100 will be described later.

The trader system 200 is an information processing system of a trader that conducts transactions with users.

The trader may be, for example, a specific business operator, or a specific store of a specific business operator. The trader may also be, for example, a specific organization (e.g., a shopping mall) that includes multiple stores of multiple business operators. In other words, the dedicated token described below may be a dedicated token corresponding to a specific business operator, a dedicated token corresponding to a specific store, or a dedicated token corresponding to a specific organization (e.g., a shopping mall). Note that traders are not limited to these.

The trader may be, for example, a trader who conducts continuous transactions with a user. Here, a continuous transaction may be, for example, a transaction for a certain amount (for example, a fixed amount, or a per-use amount according to the degree of use of the user's product or service) that is settled at regular intervals (for example, monthly). In conventional continuous transactions, the trader system 200 may register the user and the user's payment method information in advance. Therefore, the trader system 200 may perform payment processing at regular intervals (for example, monthly) without obtaining payment method information from the user.

A continuous transaction may be, for example, at least one of a so-called recurring transaction and a so-called subscription transaction. A recurring transaction is a type of transaction in which a user and a trader continuously trade, for example, consumables or pay-as-you-go services. A subscription transaction is a type of transaction in which a user and a trader continuously trade, for example, goods or services of a predetermined amount.

The user terminal 300 is a computer used by a user who conducts transactions with a trader, and may be a smartphone, tablet terminal, personal computer, etc.

The payer system 400 is a payer information processing system that processes the settlement of transactions between a user and a transactor. The payer may be, for example, a business entity that corresponds to the user's payment method. That is, if the user's payment method is a credit card, the payer may be the issuer of the credit card, and if the user's payment method is electronic money, the payer may be a funds transfer business entity that manages the electronic money.

Note that in FIG. 2, one trader system 200, one user terminal 300, and one settler system 400 are shown, but there may be multiple trader systems 200, user terminals 300, and settler systems 400.

Next, the details of the payment support system 100 will be described. The payment support system 100 includes a memory unit 105, a payment means acquisition unit 110, a verification unit 115, a dedicated token issue unit 120, a correspondence generation unit 125, a payment request acquisition unit 130, a payment means identification unit 135, a payment request providing unit 140, a payment result acquisition unit 145, a payment result providing unit 150, an error acquisition unit 155, a change proposal unit 160, and an update unit 165. Each unit shown in FIG. 2 can be realized, for example, by using a memory area or by a processor executing a payment support program stored in the memory area.

The memory unit 105 stores information processed in the payment support system 100. The memory unit 105 can store, for example, payment method information, correspondence information, first payment request information, payment result information, and error information, which will be described later.

The payment method acquisition unit 110 acquires payment method information regarding the payment method used by the user in a transaction between the user and the trader, and stores the information in the memory unit 105.

Here, the payment method information includes first payment method information relating to a first payment method, and second payment method information relating to a second payment method different from the first payment method.

The payment method acquisition unit 110 may acquire payment method information, for example, from the trader system 200. In this case, the trader system 200 may acquire payment method information from the user in accordance with a transaction between the user and the trader, and provide the acquired payment method information to the payment support system 100.

The payment method acquisition unit 110 may also acquire payment method information from the user terminal 300.

Payment method information is information about the payment method used by the user in a transaction between the user and a transactor. The payment method may be, for example, a bank account, a credit card, electronic money, points, or a payment token. Payment method information may be, for example, a bank account number, a credit card number, an ID or account for electronic money (more specifically, an ID or account at a funds transfer service provider corresponding to electronic money), an ID or account at a business that manages points (for example, a point card number), or an ID for a payment token. Note that the "payment token" exemplified in this paragraph is a different token from the dedicated token described below.

Figure 3 is a diagram showing an example of payment method information stored in the memory unit 105. The payment method information stored in the memory unit 105 includes, for example, a payment method ID and payment method content information.

The payment method ID is information that identifies the payment method information processed in the payment support system 100. The payment method content information is information that indicates the content of the payment method, such as a bank account number, a credit card number, an electronic money ID or account, an ID or account at a business that manages points, or an ID of a payment token.

The verification unit 115 verifies that payment processing based on the payment method information (e.g., first payment method information) is performed normally.

The verification unit 115 may, for example, access the settlor system 400 corresponding to the payment method information and evaluate whether the payment method information is a legitimate payment method. The verification unit 115 may, for example, evaluate the payment method information as being a legitimate payment method when a credit card number, an electronic money ID or account, an ID or account at a business that manages points, or an ID of a payment token are properly recorded in the settlor system 400.

The verification unit 115 may, for example, access the payment provider system 400 corresponding to the payment method information, and evaluate whether or not the payment processing is performed normally based on the payment method limit indicated by the payment method information. The verification unit 115 may compare the size of the transaction between the user and the trader (e.g., the size of the transaction amount) with the payment method limit, and evaluate that the payment processing is performed normally when it is determined that the transaction between the user and the trader is performed within the payment method limit.

For example, if a transaction between a user and a trader is a recurring transaction, the size of the transaction (e.g., the size of the transaction amount) can be estimated to a certain extent depending on the product or service that is continuously traded in the recurring transaction. Therefore, the verification unit 115, for example, accesses the payer system and verifies that the payment processing based on the payment method information (e.g., the first payment method information) is performed normally.

The payer corresponding to the payment method information may be, for example, a credit card issuer, a funds transfer business that manages electronic money, or a business that manages payment tokens.

The dedicated token issuing unit 120 issues dedicated token information regarding the dedicated token used for settlement of the transaction between the user and the trader to the trader system 200 based on the payment method information (e.g., the first payment method information). The trader system 200 then stores the issued dedicated token information.

Here, the dedicated token is a token that is dedicated to settlement of transactions between a user and a trader. In other words, the dedicated token cannot be used for settlement of transactions with any other than the corresponding user, and cannot be used for settlement of transactions with any other than the corresponding trader (e.g., a specific business operator, a specific store, or a specific organization such as a shopping district). In other words, even if the dedicated token information is leaked to a third party, the third party cannot make payments using the dedicated token information. In this way, the payment support system 100 can achieve more secure payments by issuing a dedicated token to the trader system 200.

The dedicated token information may further include trader identification information that can identify the trader.

The trader identification information included in the dedicated token information may be encrypted information (e.g., a digital signature, a digital watermark, or a hash value). This enables the payment support system 100 to prevent tampering with the trader identification information included in the dedicated token information.

The dedicated token issuing unit 120 may also issue dedicated token information based on the results of the verification by the verification unit 115. That is, when the verification unit 115 evaluates that the payment processing based on the payment method indicated by the payment method information is performed normally, the dedicated token issuing unit 120 may issue dedicated token information based on the payment method information. This allows the payment support system 100 to issue a dedicated token corresponding to payment method information that can execute the payment processing normally, thereby making the issuance process of the dedicated token more efficient.

The dedicated token issuing unit 120 may also issue dedicated token information based on multiple pieces of payment method information. In this case, the dedicated token issuing unit 120 may issue multiple pieces of dedicated token information corresponding to each of the multiple pieces of payment method information, or may issue one piece of dedicated token information corresponding to the multiple pieces of payment method information.

The correspondence generation unit 125 generates correspondence information that associates payment method information (e.g., first payment method information) with dedicated token information, and stores the correspondence information in the memory unit 105.

The correspondence generation unit 125 may generate correspondence information that associates the payment method information, the dedicated token information, and the trader identification information. The trader identification information may be information that identifies the trader system 200 from which the payment method acquisition unit 110 obtained the information or the trader system 200 from which the dedicated token issuance unit 120 issues the information. This allows the payment support system 100 to match the dedicated token information acquired by the payment request acquisition unit described below with the trader system 200 that provides the dedicated token information, thereby enabling more secure payments to be realized.

Figure 4 is a diagram showing an example of correspondence information stored in the storage unit 105. The correspondence information stored in the storage unit 105 includes, for example, a payment method ID and a dedicated token ID. The dedicated token ID is information that identifies a dedicated token issued by the dedicated token issuing unit 120.

The correspondence information stored in the memory unit 105 may further include trader identification information.

The payment request acquisition unit 130 acquires first payment request information from the trader system 200, including dedicated token information and payment information regarding the settlement of the transaction between the user and the trader, and stores the information in the memory unit 105.

The first payment request information is information obtained from the trader system 200 that requests settlement of a transaction between a user and a trader. Unlike the second payment request information described below, the first payment request information is information in which payment information and dedicated token information are associated.

The trader requests payment processing from the payment support system 100 in accordance with the transaction with the user. At this time, the trader system 200 provides the first payment request information to the payment support system 100.

Payment information is information regarding the settlement of a transaction between a user and a trader, and includes, for example, payment amount information indicating the payment amount of the transaction.

The first settlement request information may further include trader identification information. For example, the settlement information may include the trader identification information, and the dedicated token information may include the trader identification information. In this way, when the correspondence information includes trader identification information, the settlement support system 100 can achieve more secure settlement by comparing the trader identification information included in the correspondence information with the trader identification information included in the first settlement request information provided by the trader system 200.

In addition, for example, the first payment request information may include trader identification information that is encrypted and generated by the dedicated token issuing unit 120 and included in the dedicated token information, and trader identification information added by the trader system 200. The trader system 200 may, for example, add the trader identification information to the payment information. In this way, even if the correspondence information does not include the trader identification information, the payment support system 100 can achieve more secure payment by comparing the encrypted trader identification information included in the dedicated token information with the trader identification information added by the trader system 200.

When a user and a trader make a transaction, the trader system 200 may, for example, obtain information indicating the user (e.g., user identification information) from the user who is the trading partner. The trader system 200 may then refer to a storage unit in which information indicating the user (e.g., user identification information) and dedicated token information are stored in association with each other, identify the dedicated token information corresponding to the user, and provide the first payment request information including the dedicated token information to the payment support system 100.

In this way, the payment support system 100 only needs to obtain the dedicated token information stored in the trader system 200 (e.g., the memory unit of the trader system 200) from the trader system 200. In other words, the trader system 200 does not need to obtain payment method information from the user, nor does it need to obtain dedicated token information. This allows the user to trade with the trader without providing payment method information or dedicated token information to the trader system 200. In particular, in continuous transactions (e.g., recurring transactions), the user can easily make payments using the dedicated token.

Figure 5 is a diagram showing an example of first payment request information stored in the memory unit 105. The first payment request information stored in the memory unit 105 includes, for example, a first payment request ID, a dedicated token ID, and payment information. The payment information further includes, for example, payment amount information. The first payment request ID is information that identifies the first payment request information processed in the payment support system 100.

The payment method identification unit 135 identifies the payment method information (e.g., the first payment method information) that corresponds to the dedicated token information included in the first payment request information based on the correspondence information.

The payment request providing unit 140 provides the payment provider system 400 with second payment request information including payment information and payment method information (e.g., first payment method information) identified by the payment method identifying unit 135.

The second payment request information is information provided to the settler system 400, requesting settlement of a transaction between a user and a trader. Unlike the first payment request information, the second payment request information is information in which payment information and payment method information (e.g., first payment method information) are associated.

In other words, through a series of processes by the payment request acquisition unit 130, the payment method identification unit 135, and the payment request provision unit 140, the payment support system 100 converts, so to speak, the dedicated token information acquired from the trader system 200 into corresponding payment method information (e.g., first payment method information) and provides it to the payer system 400. This allows the trader system 200 to process the dedicated token information without processing payment method information that would be significantly affected in the event of an information leak, thereby achieving more secure payments. Furthermore, by going through the payment support system 100, the payer system 400 can perform, so to speak, normal payment processing based on the payment method information even in payment processing with enhanced security.

In particular, when a transaction between a user and a trader is a continuous transaction (e.g., a recurring transaction), the trader may continually manage the user's payment method information. As a result, there is a risk that the user's payment method information will be leaked from the trader system 200. Therefore, by having the payment support system 100 issue dedicated token information to the trader system 200, the trader system 200 can perform processing using the dedicated token information rather than processing using the payment method information, which would be significantly affected in the event of an information leak, thereby achieving more secure payments.

In addition, when the dedicated token issuing unit 120 issues dedicated token information based on multiple payment method information (e.g., first payment method information and second payment method information), the payment request providing unit 140 can provide the payment request information including the first payment method information and the second payment request information including the second payment method information to the payment system 400.

Specifically, for example, first, the payment request providing unit 140 provides the second payment request information including the first payment means information to the settler system 400. Next, the error acquisition unit 155 described later acquires error information indicating that the payment process cannot be executed normally based on the first payment means information. Then, the payment request providing unit 140 provides the second payment request information including the second payment means information to the settler system 400. As a result, even if the payment process based on the first payment means cannot be executed normally in the settler system 400, the payment support system 100 can request the settler system 400 to execute payment process based on a payment means different from the first payment means (for example, the second payment means in this case) without requiring any additional operation by the user.

When the dedicated token issuing unit 120 issues dedicated token information based on multiple payment method information, which payment method information the payment request providing unit 140 preferentially uses to provide the second payment request information may be based on, for example, a setting determined in advance by an administrator or user of the payment support system 100.

The payment result acquisition unit 145 acquires payment result information indicating the result of the payment processing according to the second payment request information from the payer system 400, and stores the information in the memory unit 105.

The settler system 400 acquires the second payment request information from the payment support system 100, and performs the payment processing of the transaction between the user and the transactor based on the second payment request information. The settler system 400 generates payment result information indicating the result of the payment processing, and provides the payment result information to the payment support system 100. The payment result acquisition unit 145 acquires the payment result information.

Figure 6 is a diagram showing an example of payment result information stored in the memory unit 105. The payment result information stored in the memory unit 105 includes, for example, a payment result ID, a payment request ID, and payment result content information. The payment result content information further includes, for example, payment amount information.

The payment result ID is information that identifies the payment result information processed in the payment support system 100. The payment result content information is information that indicates the content of the result of the payment process. The payment amount information included in the payment result content information is information that indicates the amount paid as a result of the payment process.

The payment result providing unit 150 provides the payment result information obtained from the payment processor system 400 to the trader system 200.

The error acquisition unit 155 acquires error information from the payer system 400 indicating that the payment process based on the second payment request information cannot be executed normally, and stores the error information in the memory unit 105.

The error information may be, for example, error information indicating that the payment indicated by the payment method information included in the second payment request information (e.g., payment of the payment amount indicated by the payment amount information) cannot be processed by the payment method indicated by the payment method information included in the second payment request information. This may occur, for example, when the payment exceeds the limit of the payment method or when the payment method is disabled.

Figure 7 is a diagram showing an example of error information stored in the memory unit 105. The error information stored in the memory unit 105 includes, for example, an error ID, a payment request ID, and error content information.

The error ID is information that identifies the error information processed in the payment support system 100. The error content information is information that indicates the content of the error. The error content information may be, for example, information that indicates an error code that corresponds to the content of a specific error.

The change proposal unit 160 provides change proposal information that proposes changing the payment method indicated by the payment method information (e.g., first payment method information) included in the second payment request information corresponding to the error information to a different payment method (e.g., second payment method) based on the error information.

The change proposal unit 160 may provide the change proposal information to the trader system 200, and may also provide the change proposal information to the user terminal 300. The trader system 200 may provide the acquired change proposal information to the user terminal 300. The user terminal 300 that has acquired the change proposal information may make a change request to the payment support system 100 or the trader system 200 regarding a request for a change to the payment method based on the user's operation.

When the change suggestion unit 160 provides change proposal information to the user terminal 300, the change suggestion unit 160 may provide the change proposal information, for example, by notifying a contact that is registered in advance (for example, the user's email address or the user's SNS (Social Networking System) account).

The change suggestion unit 160 may provide change suggestion information, for example, when the payment process cannot be executed normally in the payer system 400 even if the payment request providing unit 140 provides the second payment request information based on any of the payment method information associated with the dedicated token information. This allows the payment support system 100 to receive new payment method information from the user terminal 300 and continue the payment process.

In response to a change request for a change of the payment method, the update unit 165 changes the payment method information (e.g., first payment method information) corresponding to the dedicated token information to payment method information (e.g., second payment method information) relating to a different payment method (e.g., second payment method), thereby updating the correspondence information.

The update unit 165 may perform the update process in response to a change request received from the trader system 200, or in response to a change request received from the user terminal 300. When the update unit 165 performs the update process in response to a change request received from the trader system 200, the trader system 200 may receive the change request from the user terminal 300 and provide the received change request to the payment support system 100.

The update unit 165 may also perform update processing in response to a change request received from the trader system 200 or the user terminal 300 in response to the change proposal information by the change proposal unit 160. That is, in this case, the change proposal unit 160 provides the change proposal information to the trader system 200 or the user terminal 300, and a user who has referred to the change proposal information operates the user terminal 300 to provide a change request to the payment support system 100, either via the trader system 200 or not. Then, the update unit 165 updates the correspondence information in response to the change request.

When a user changes the payment method information registered in the correspondence information to different payment method information, the payment facilitating system 100 only needs to update the correspondence information, and does not need to reissue the dedicated token information or re-provide the reissued dedicated token to the trader system 200. This allows the payment facilitating system 100 to easily change the payment method information that corresponds to the dedicated token information.

In particular, when a transaction between a user and a trader is a continuous transaction (e.g., a recurring transaction), the trader may continually manage the user's payment method information. In this case, a user who wishes to change the payment method must make a request to the trader, which is a cumbersome process for the user. In addition, when a user is trading with multiple traders, the user must make a request to each of the multiple traders, which is a cumbersome process for the user.

The payment support system 100 then generates correspondence information that associates the payment method information with the dedicated token information, and issues the dedicated token information to the trader system 200. When the payment method information is changed, the update unit 165 updates the correspondence information in response to the change request. This allows the user to easily and flexibly change the payment method used in transactions with a trader by changing the payment method information included in the correspondence information in the payment support system 100, without requesting the trader to make the change.

Figure 8 is a sequence chart showing an example of processing in the payment support system 100. The sequence chart shown in Figure 8 shows an example of a dedicated token issuance process in the payment support system 100.

First, a transaction is conducted between a user and a trader, and the trader system 200 acquires first payment method information from the user (or the user terminal 300) (S801).

The payment method acquisition unit 110 acquires the first payment method information from the trader system 200 (S802). The verification unit 115 verifies that the payment process based on the first payment method information can be executed normally (S803).

The dedicated token issuing unit 120 issues dedicated token information based on the first payment method information (S804) and provides it to the trader system 200 (S805). The correspondence generating unit 125 generates correspondence information (S806).

Figure 9 is a sequence chart showing an example of processing in payment support system 100. The sequence chart shown in Figure 9 shows an example of payment support processing using dedicated token information in payment support system 100.

First, the payment request acquisition unit 130 acquires first payment request information including payment information and dedicated token information in accordance with a transaction between a user and a trader (S901). The payment method identification unit 135 identifies first payment method information corresponding to the dedicated token information included in the first payment request information based on the correspondence information (S902). The payment request provision unit 140 provides second payment request information including the payment information and the identified first payment method information to the settler system 400 (S903).

The settler system 400 performs settlement processing based on the second settlement request information. The settlement result acquisition unit 145 acquires settlement result information from the settler system 400 (S904). The settlement result provision unit 150 provides the settlement result information to the trader system 200 (S905).

The transaction in the dedicated token issuance process and the transaction in the payment assistance process may be the same transaction or may be different transactions.

In other words, when a transaction is made between a user and a transactor, the payment support system 100 may issue dedicated token information and use the dedicated token information to perform the payment support process for the transaction. This allows the payment support system 100 to process the transaction using the dedicated token, and therefore allows the transaction to be processed with high security.

Furthermore, the payment facilitating system 100 may first issue dedicated token information in a first transaction between a user and a trader, and then perform a payment facilitating process using the dedicated token information in a second transaction that is carried out after the first transaction. In this case, the payment of the first transaction may be a payment that does not use the dedicated token information. This allows the payment facilitating system 100 to efficiently issue a dedicated token without separately acquiring payment method information from the user or the trader system 200. Furthermore, the user can easily use the payment facilitating process of the payment facilitating system 100 without separately providing payment method information.

Figure 10 is a sequence chart showing an example of processing in the payment support system 100. The sequence chart shown in Figure 10 shows an example of processing in the payment support system 100 when the payment process cannot be executed normally in the settler system 400.

The error acquisition unit 155 acquires error information from the settler system 400 indicating that the settlement process based on the second settlement request information cannot be executed normally (S1001). The change proposal unit 160 provides the change proposal information to the trader system 200 or the user terminal 300 (S1002a or S1002b). In response to the change request acquired from the trader system 200 or the user terminal 300 (S1003a or S1003b), the update unit 165 changes the payment method to a different payment method and updates the correspondence information (S1004).

Next, referring to FIG. 11, an example of a hardware configuration for implementing the payment support system 100 using a computer 1100 will be described. FIG. 11 is a diagram showing an example of the hardware configuration of the computer 1100.

As shown in FIG. 11, the computer 1100 includes, for example, a processor 1101, a memory 1102, a storage device 1103, an input I/F unit 1104, a data I/F unit 1105, a communication I/F unit 1106, and a display device 1107.

Computer 1100 may be, for example, a server computer, a personal computer (e.g., desktop, laptop, tablet, etc.), a media computing platform (e.g., cable, satellite set-top box, digital video recorder, etc.), a handheld computing device (e.g., PDA, email client, etc.), or any other type of computer or communications platform.

The processor 1101 is a control unit that controls various processes in the computer 1100 by executing programs stored in the memory 1102.

The memory 1102 is a storage medium such as a RAM (Random Access Memory). The memory 1102 temporarily stores the program code of the program executed by the processor 1101 and data required when the program is executed.

The storage device 1103 is a non-volatile storage medium such as a hard disk drive (HDD) or flash memory. The storage device 1103 stores an operating system and various programs for implementing the above configurations.

The input I/F unit 1104 is a device for receiving input from a user. The input I/F unit 1104 is, for example, a keyboard, a mouse, a touch panel, various sensors, a wearable device, etc. The input I/F unit 1104 may be connected to the computer 1100 via an interface such as a USB (Universal Serial Bus).

The data I/F unit 1105 is a device for inputting data from outside the computer 1100. The data I/F unit 1105 is, for example, a drive device for reading data stored in various storage media. The data I/F unit 1105 may be provided outside the computer 1100. When the data I/F unit 1105 is provided outside the computer 1100, the data I/F unit 1105 is connected to the computer 1100 via an interface such as a USB.

The communication I/F unit 1106 is a device for performing data communication with devices external to the computer 1100 via a network such as the Internet, either wired or wirelessly. The communication I/F unit 1106 may be provided outside the computer 1100. When the communication I/F unit 1106 is provided outside the computer 1100, the communication I/F unit 1106 is connected to the computer 1100 via an interface such as a USB, for example.

The display device 1107 is a device for displaying various types of information. The display device 1107 is, for example, a liquid crystal display, an organic EL (Electro-Luminescence) display, a display of a wearable device, or the like. The display device 1107 may be provided outside the computer 1100. When the display device 1107 is provided outside the computer 1100, the display device 1107 is connected to the computer 1100 via, for example, a display cable. Furthermore, when a touch panel is adopted as the input I/F unit 1104, the display device 1107 may be configured as an integral part of the input I/F unit 1104.

The above describes one embodiment of the present invention. The payment support system 100 issues to the trader system 200 dedicated token information used for settlement of a transaction between a user and a trader based on the first payment method information used by the user, generates correspondence information that associates the first payment method information and the dedicated token information, obtains from the trader system 200 first payment request information including the dedicated token information and payment information, identifies the first payment method information that corresponds to the dedicated token information based on the correspondence information, and provides to the settler system 400 second payment request information including the first payment method information and payment information. This allows the payment support system 100 to more easily process payments using tokens.

The payment support system 100 can also provide the trader system 200 with payment result information obtained from the settler system 400. This allows the payment support system 100 to act as an intermediary between the trader system 200 and the settler system 400 and perform payment support processing, allowing the trader system 200 to obtain the results of the payment.

In addition, in response to a change request, the payment support system 100 can change the first payment method information corresponding to the dedicated token information to the second payment method information and update the correspondence information. This allows the payment support system 100 to change the payment method corresponding to the dedicated token without performing the dedicated token issuance process again, and allows the user to easily and flexibly change the payment method corresponding to the dedicated token.

The payment support system 100 can also update the correspondence information in response to a change request made through the user terminal 300. This allows the user to easily and flexibly change the payment method that corresponds to the dedicated token.

The payment support system 100 can also obtain error information from the payer system 400, and provide change proposal information that proposes changing the first payment means information included in the second payment request information corresponding to the error information to the second payment means information based on the error information, based on the error information. This allows the user to change to the second payment means information different from the first payment means information and continue the payment process, even if the payment process based on the first payment means information corresponding to the dedicated token information cannot be executed normally.

The payment support system 100 can also verify that the payment processing based on the first payment method information is performed normally, and issue dedicated token information based on the results of the verification. This allows the payment support system 100 to issue a dedicated token corresponding to the payment method information that can execute the payment processing normally, and can make the process of issuing the dedicated token more efficient.

The payment support system 100 can also issue dedicated token information based on the first payment method information used in the first transaction, and obtain first payment request information including the dedicated token information and payment information related to the payment of the second transaction made after the first transaction from the trader system 200. This allows the user to receive payment using the dedicated token without providing the payment method information to the trader system 200 after the first transaction.

Note that the present embodiment is intended to facilitate understanding of the present invention, and is not intended to limit the interpretation of the present invention. The present invention may be modified or improved without departing from the spirit of the present invention, and equivalents thereof are also included in the present invention.

100 Payment support system, 105 Memory unit, 110 Payment method acquisition unit, 115 Verification unit, 120 Dedicated token issuance unit, 125 Correspondence generation unit, 130 Payment request acquisition unit, 135 Payment method identification unit, 140 Payment request provision unit, 145 Payment result acquisition unit, 150 Payment result provision unit, 155 Error acquisition unit, 160 Change proposal unit, 165 Update unit, 200 Trader system, 300 User terminal, 400 Payment system, 1100 Computer, 1101 Processor, 1102 Memory, 1103 Storage device, 1104 Input I/F unit, 1105 Data I/F unit, 1106 Communication I/F unit, 1107 Display device

Claims (9)

On the computer,
a dedicated token issuing unit that issues dedicated token information regarding a dedicated token used for settlement of a transaction between the user and the trader to a trader system of the trader based on first payment means information regarding a first payment means used by the user when trading with the trader;
a correspondence generation unit that generates correspondence information that associates the first payment method information and the dedicated token information;
A payment request acquisition unit that acquires first payment request information from the trader system, the first payment request information including the dedicated token information and payment information regarding the payment of the transaction with the user;
a payment means identification unit that identifies the first payment means information corresponding to the dedicated token information included in the first payment request information based on the correspondence relationship information;
a payment request providing unit that provides second payment request information, including the payment information and the specified first payment means information, to a payment entity system of a payment entity that processes the payment;
A payment support program to make this a reality. The payment support program according to claim 1, further comprising a payment result providing unit that provides the trader system with payment result information obtained from the settler system and indicating the result of the payment processing in accordance with the second payment request information. The payment support program according to claim 1 or 2, further comprising an update unit that updates the correspondence information by changing the first payment means information corresponding to the dedicated token information to second payment means information related to a second payment means different from the first payment means in response to a change request for a change of the payment means. The payment support program according to claim 3, wherein the update unit updates the correspondence information in response to the change request made through the user terminal of the user. The computer includes:
an error acquisition unit that acquires, from the settler system, error information indicating that the process of the settlement based on the second settlement request information cannot be normally executed;
a change proposal unit that provides, based on the error information, change proposal information that proposes changing the first payment means indicated by the first payment means information included in the second payment request information corresponding to the error information to a second payment means different from the first payment means;
The payment support program according to claim 1 or 2, further realizing the above. The computer further includes a verification unit that verifies that a payment process based on the first payment means information is performed normally,
The dedicated token issuing unit issues the dedicated token information based on a result of the verification.
The payment support program according to claim 1 or 2. The dedicated token issuing unit issues the dedicated token information based on the first payment means information acquired from the trader system regarding the first payment means used in the first transaction between the user and the trader;
The payment request acquisition unit acquires the first payment request information including the dedicated token information and the payment information regarding the payment of a second transaction performed after the first transaction.
The payment support program according to claim 1 or 2. a dedicated token issuing unit that issues dedicated token information regarding a dedicated token used for settlement of a transaction between the user and the trader to a trader system of the trader based on first payment means information regarding a first payment means used by the user when trading with the trader;
a correspondence generation unit that generates correspondence information that associates the first payment method information and the dedicated token information;
A payment request acquisition unit that acquires first payment request information from the trader system, the first payment request information including the dedicated token information and payment information regarding the payment of the transaction with the user;
a payment means identification unit that identifies the first payment means information corresponding to the dedicated token information based on the correspondence relationship information;
a payment request providing unit that provides second payment request information, including the payment information and the specified first payment means information, to a payment entity system of a payment entity that processes the payment;
A payment support system comprising: The computer
Based on first payment means information regarding a first payment means used by a user when trading with a trader, issue dedicated token information regarding a dedicated token used for settlement of the transaction between the user and the trader to a trader system of the trader;
generating correspondence information that associates the first payment method information with the dedicated token information;
Obtaining first payment request information from the trader system, the first payment request information including the dedicated token information and payment information regarding a payment for a transaction with the user;
Identifying the first payment means information corresponding to the dedicated token information based on the correspondence information;
providing second payment request information, including the payment information and the specified first payment means information, to a payment processor system of a payment processor that processes the payment;
Payment assistance methods.

Images