JP7750800B2 - Transaction cancellation program, transaction cancellation system, and transaction cancellation method - Google Patents

Description

The present invention relates to a transaction cancellation program, a transaction cancellation system, and a transaction cancellation method.

Conventionally, there is known technology for canceling a transaction based on a receipt that a customer brings to a store and that indicates that the customer has made a transaction with the store.

For example, the terminal described in Patent Document 1 requests a terminal that stores sales information to cancel a payment based on sales information read from the receipt issued at the time of the payment to be canceled.

JP 2009-32036 A

However, the terminal described in Patent Document 1 requires customers to request payment cancellation based on a receipt that they bring to the store. This means that customers must keep the receipt issued at the time of the payment to be canceled and bring it to the store, and the store must refer to the receipt to process the cancellation, which is inconvenient.

Therefore, the present invention aims to provide a more convenient transaction cancellation program, transaction cancellation system, and transaction cancellation method.

A transaction cancellation program according to one embodiment of the present invention implements a transaction inquiry unit that inquires about the existence of a transaction based on proof-of-transaction data, which is generated in response to a customer's transaction and certifies the details of the transaction, and information indicating the customer's request to cancel the transaction, which is obtained through a specified device, on a computer; and a cancellation request sending unit that, depending on the inquiry results and based on the proof-of-transaction data, sends payment cancellation request data, which requests the cancellation of the payment corresponding to the transaction, to an external business system of an external business that processes payment cancellations.

A transaction cancellation system according to one aspect of the present invention includes a transaction inquiry unit that inquires about the existence of a transaction based on proof-of-transaction data, which is generated in response to a customer's transaction and certifies the details of the transaction, and information indicating the customer's request to cancel the transaction, which is obtained through a specified device; and a cancellation request sending unit that, in response to the inquiry results and based on the proof-of-transaction data, sends payment cancellation request data, which requests the cancellation of the payment corresponding to the transaction, to an external business system of an external business that handles payment cancellation.

In one aspect of the present invention, a transaction cancellation method involves a computer inquiring about the existence of a transaction based on proof-of-transaction data, which is generated in response to a customer's transaction and certifies the details of the transaction, and information indicating the customer's request to cancel the transaction, which is obtained through a specified device. Depending on the results of the inquiry, the computer sends payment cancellation request data, which requests the cancellation of the payment corresponding to the transaction based on the proof-of-transaction data, to an external business system of an external business that processes payment cancellations.

In this invention, the term "unit" does not simply mean physical means, but also includes cases where the functions of that "unit" are realized by software. Furthermore, the functions of a single "unit" or device may be realized by a combination of two or more physical means, devices, or software modules, or the functions of two or more "units" or devices may be realized by a single physical means, device, or software module.

The present invention makes it possible to provide a more convenient transaction cancellation program, transaction cancellation system, and transaction cancellation method.

FIG. 1 is a diagram showing an overview of processing in a transaction cancellation system 100 according to an embodiment of the present invention. 1 is a diagram showing a configuration of a transaction cancellation system 100 according to an embodiment of the present invention. FIG. 2 is a diagram showing an example of transaction content data stored in the storage unit 111. FIG. 10 is a diagram showing an example of proof-of-transaction data stored in the storage unit 111. 10 is a flowchart illustrating an example of processing in the transaction cancellation system 100.

A preferred embodiment of the present invention will be described with reference to the accompanying drawings. Figure 1 is a diagram showing an overview of the processing in a transaction cancellation system 100, which is one embodiment of the present invention.

The transaction cancellation system 100 is an information processing system implemented by a transaction cancellation program, and performs processing to request cancellation of the payment corresponding to a transaction based on transaction proof data that is generated in response to a customer's transaction and certifies the content of the transaction.

First, a customer conducts a transaction with an affiliated store (S101). The customer purchases, for example, a product or service at the affiliated store. Note that the term "affiliated store" may be interpreted as meaning a store or business, as appropriate. Next, the transaction cancellation system 100 acquires transaction content data indicating the details of the transaction from at least one of the affiliated store, customer, and external business, depending on the transaction between the affiliated store and the customer (S102a, b, c). The transaction cancellation system 100 generates proof-of-transaction data that certifies the details of the transaction based on the transaction content data (S103).

Next, the transaction cancellation system 100 accepts a request to cancel a transaction from an affiliated store or a customer (S104a, b). The transaction cancellation system 100 queries the transaction related to the request for cancellation and provides the query results to the affiliated store (S105). The affiliated store references the query results and makes a cancellation request to the transaction cancellation system 100, requesting that the transaction be canceled (S106).

Then, the transaction cancellation system 100 generates payment cancellation request data requesting cancellation of the payment corresponding to the transaction based on the proof-of-transaction data (S107) and sends it to the external business operator (S108).

Note that the following description assumes that a customer cancels a transaction with a member store in person as a preferred embodiment of the present invention, but the embodiments to which the present invention can be applied are not limited to this. Furthermore, there are no particular restrictions on the payment method used by the customer when making a transaction, and it may be, for example, payment using a credit card or electronic money card, or payment using the customer's online wallet (a payment account managed on a network) using wallet access information (e.g., a URL or QR code (registered trademark)) installed at the member store.

Figure 2 shows the configuration of a transaction cancellation system 100, one embodiment of the present invention. The transaction cancellation system 100 is communicably connected to an affiliated store device 200, a customer device 300, and an external business system 400 via a network such as the Internet. Details of the transaction cancellation system 100 will be described later.

The affiliated store device 200 is a device of the affiliated store that conducts transactions with customers. Through the affiliated store device 200, the affiliated store can provide transaction content data, apply for cancellation, and request cancellation based on the inquiry results obtained from the transaction cancellation system 100 to the transaction cancellation system 100.

The affiliated store device 200 may be, for example, a terminal installed in the affiliated store for processing payments, and may include, for example, a cash register terminal or other terminal for reading information (e.g., barcode information or tag information attached to a product) for registering product-related information (e.g., product number, price, etc.) when making a payment. In other words, the affiliated store device 200 may each be equipped with a reading device for reading product barcode information or tag information, and an acquisition device for acquiring information from the customer device 300, which will be described later.

The affiliated store device 200 may also be equipped with a staff member device (e.g., equipment for acquiring the staff member's ID, fingerprint, or signature) for acquiring staff member approval information, which will be described later.

Customer device 300 is a device used by customers who visit affiliated stores, and may be, for example, an information terminal such as a smartphone, tablet, or personal computer, or a payment device such as a credit card or electronic money card. Through customer device 300, customers can provide transaction content data and apply for cancellation to transaction cancellation system 100.

The external business system 400 is an information processing system of an external business that performs processing related to payment cancellation. The external business that performs processing related to payment cancellation may be, for example, a payment business (e.g., a payment card business or a funds transfer service provider) that corresponds to the payment method used by the customer in the transaction.

The external business system 400 obtains the payment cancellation request data from the transaction cancellation system 100 and performs payment cancellation processing based on the payment cancellation request data.

Note that while Figure 2 shows one each of the affiliated store device 200, customer device 300, and external business system 400, there may be multiple each of the affiliated store device 200, customer device 300, and external business system 400.

Next, the details of the transaction cancellation system 100 will be explained. The transaction cancellation system 100 comprises a memory unit 111, a transaction content acquisition unit 112, a transaction proof-of-transaction data generation unit 113, a cancellation request acquisition unit 121, a transaction inquiry unit 122, an inquiry result transmission unit 123, a cancellation request acquisition unit 131, a person in charge approval acquisition unit 132, and a cancellation request transmission unit 133. Each unit shown in FIG. 2 can be realized, for example, by using a memory area or by a processor executing a transaction cancellation program stored in the memory area.

The memory unit 111 stores information processed by the transaction cancellation system 100. The memory unit 111 can store, for example, transaction content data and transaction proof data, which will be described below.

The transaction content acquisition unit 112 acquires transaction content data indicating the content of the transaction in accordance with the transaction between the affiliated store and the customer, and stores this data in the memory unit 111.

Transaction content data indicates the details of transactions between affiliated stores and customers. Transaction content data includes, for example, a transaction ID, customer identification information, transaction amount information, transaction product information, transaction date and time information, and an external business ID.

The transaction ID is information that identifies the transaction content data stored in the memory unit 111.

Customer identification information may be any information that can identify the customer who conducted the transaction, and may be, for example, information that identifies the customer device 300 used by the customer in the transaction (e.g., payment card number, electronic money account information, or information that identifies the customer's information terminal), or information that identifies the customer's online wallet.

Transaction amount information is information that indicates the transaction amount in a transaction between a member store and a customer. Transaction product information is information that indicates the products, etc., traded in a transaction between a member store and a customer. Transaction date and time information is information that indicates the date and time when a transaction between a member store and a customer was conducted.

The external business ID is information that identifies the external business system 400 that processes payments for transactions between affiliated stores and customers.

The transaction content acquisition unit 112 may acquire transaction content data from at least one of the affiliated store device 200, the customer device 300, and the external business system 400.

The transaction detail acquisition unit 112 may acquire transaction detail data from the affiliated store device 200, for example, when a customer makes a payment using a payment card as the customer device 300. In this case, the affiliated store device 200 reads information about the payment card as the customer device 300, as well as information about the product the customer is attempting to purchase, and generates transaction detail data. The affiliated store device 200 then provides the generated transaction detail data to the transaction cancellation system 100.

The transaction content acquisition unit 112 may acquire transaction content data from the customer device 300, for example, when a customer makes a payment using an information terminal as the customer device 300. In this case, for example, the customer accesses a specified site from the information terminal as the customer device 300 or makes a payment using their own online wallet through a specified application. Then, using the information terminal as the customer device 300, the customer provides the transaction content data corresponding to the payment to the transaction cancellation system 100 via their own online wallet.

The transaction detail acquisition unit 112 may acquire transaction detail data from the external business system 400, for example, when the external business system 400 processes the settlement of a transaction between an affiliated store and a customer. In this case, for example, the affiliated store device 200 or the customer device 300 provides information about the transaction to the external business system 400 when settling the transaction. The external business system 400 then approves the settlement of the transaction and provides the approval result to the affiliated store device 200 or the customer device 300, thereby completing the settlement of the transaction between the affiliated store and the customer. At this time, the external business system 400 also provides the transaction detail data to the transaction cancellation system 100.

When the transaction content acquisition unit 112 acquires transaction content data from the affiliated store device 200, the transaction cancellation system 100 can perform subsequent processing based on the transaction content data managed by the affiliated store. Furthermore, when the transaction content acquisition unit 112 acquires transaction content data from the customer device 300, the customer can use the transaction cancellation system 100 through the customer device 300. Furthermore, when the transaction content acquisition unit 112 acquires transaction content data from the external business system 400, the transaction cancellation system 100 can perform subsequent processing based on transaction content data managed by a third party different from the affiliated store and the customer.

The transaction cancellation system 100 may also be configured to perform subsequent processing when the transaction content data acquired by the transaction content acquisition unit 112 from two or more of the affiliated store device 200, the customer device 300, and the external business system 400 match each other. This allows the transaction cancellation system 100 to perform subsequent processing based on authentic transaction content data.

Figure 3 shows an example of transaction content data stored in the memory unit 111. The transaction content data stored in the memory unit 111 includes, for example, a transaction ID, customer identification information, transaction amount information, transaction product information, transaction date and time information, and an external business ID.

The proof-of-transaction data generation unit 113 generates proof-of-transaction data that certifies the content of the transaction based on the transaction content data and stores it in the memory unit 111. Here, the proof-of-transaction data may be an electronic certificate that certifies the content of the transaction.

The proof-of-transaction data generation unit 113 can, for example, perform a specified process on at least one item included in the transaction content data to generate proof-of-transaction data. Here, the specified process may be a process for proving that some or all of the transaction content indicated by the proof-of-transaction data has not been tampered with, and more specifically, it may be, for example, a process of adding a timestamp or a process of hashing at least one item included in the transaction content data. This makes it possible to prevent abuse of the transaction cancellation process by affiliated stores, customers, or third parties.

The predetermined process may also be an encryption process that stores all or part of the transaction details indicated by the proof-of-transaction data in a format that cannot be accessed by unauthorized persons. This prevents confidential information (e.g., customer identification information) contained in the transaction details data from being leaked to unauthorized persons (e.g., unauthorized affiliated store staff, customers, or third parties).

In other words, the proof-of-transaction data may include, in addition to information about the transaction details, certification information, for example. The certification information is information that certifies that the transaction details indicated by the proof-of-transaction data have not been tampered with. The proof-of-transaction data may also be information that has been encrypted in a specific manner.

The proof-of-transaction data generated by the proof-of-transaction data generation unit 113 may also be stored in a memory unit provided in the affiliated store device 200. This allows the authenticity of the proof-of-transaction data to be guaranteed by comparing the proof-of-transaction data stored in the memory unit 111 with the proof-of-transaction data stored in the memory unit provided in the affiliated store device 200. The proof-of-transaction data stored in the memory unit provided in the affiliated store device 200 may also be proof-of-transaction data generated by an information processing system different from the transaction cancellation system 100.

The transaction cancellation system 100 performs subsequent processing using the transaction proof data rather than the transaction content data to determine the transaction details. This allows transaction cancellation processing to be achieved in an information processing system (e.g., transaction cancellation system 100) that is different from the information processing system of the business that settles transactions between affiliated stores and customers (e.g., external business system 400), while preventing tampering or leakage of content, errors in the transaction cancellation processing by affiliated stores or customers, or malicious transaction cancellation processing by affiliated stores or customers with a vested interest in the transaction cancellation.

Figure 4 shows an example of proof-of-transaction data stored in the memory unit 111. The proof-of-transaction data stored in the memory unit 111 includes, for example, a transaction ID, customer identification information, transaction amount information, transaction date and time information, transaction product information, transaction date and time information, external business ID, and certification information.

In the example shown in Figure 4, the proof-of-transaction data is not encrypted, but the memory unit 111 may store proof-of-transaction data that is partially or completely encrypted.

The cancellation request acquisition unit 121 acquires cancellation request information indicating a customer's request to cancel a transaction from a specified device (e.g., the affiliated store device 200 or the customer device 300).

Here, the cancellation request information may be, for example, information indicating that the customer wishes to cancel a transaction, and may also include information indicating that the customer wishes to inquire about proof-of-transaction data corresponding to the transaction that the customer wishes to cancel.

The cancellation request information may also include information (e.g., information contained in the proof-of-transaction data) that allows the transaction inquiry unit 122, described below, to identify the transaction that the customer wishes to cancel. In this case, the transaction inquiry unit 122 identifies the transaction that the customer wishes to cancel, for example, based on the information contained in the proof-of-transaction data.

The affiliated store device 200 can provide cancellation request information to the transaction cancellation system 100, for example, based on the operation of an affiliated store staff member. Specifically, the affiliated store staff member may operate the affiliated store device 200 and provide cancellation request information to the transaction cancellation system 100, for example, in response to a customer's request to cancel a transaction. At this time, the affiliated store device 200 may obtain information contained in the proof-of-transaction data from the customer or customer device 300, and provide the information contained in the obtained proof-of-transaction data to the transaction cancellation system 100.

More specifically, for example, an affiliated store may request that a customer provide customer identification information (e.g., information about the payment card or online wallet used for payment), and the affiliated store device 200 may read the customer's payment card or customer's information terminal to obtain the customer identification information. Also, for example, an affiliated store may request that a customer provide information about the transaction amount, transaction item, etc., or transaction date and time of the transaction that the customer wishes to cancel, and the affiliated store device 200 may obtain the corresponding transaction amount information, transaction item, etc. information, and transaction date and time information.

The customer device 300 can provide cancellation application information to the transaction cancellation system 100, for example, based on the customer's operation. At this time, the customer may operate the customer device 300 in accordance with the affiliated store's instructions. That is, for example, the customer may use the customer device 300 to read a URL or QR code (registered trademark) set for the cancellation process.

Specifically, for example, a customer may provide customer identification information, transaction amount information, transaction product information, or transaction date and time information to the transaction cancellation system 100 via a URL or QR code (registered trademark) set up for the cancellation process.

The transaction inquiry unit 122 inquires about the existence of a transaction corresponding to the cancellation request based on the transaction proof data and the cancellation request.

The transaction inquiry unit 122, for example, identifies the transaction proof data corresponding to the cancellation request from among the transaction proof data stored in the memory unit 111, and generates inquiry result information.

The transaction inquiry unit 122 may, for example, extract and identify proof-of-transaction data for a transaction by a customer corresponding to the customer identification information based on the customer identification information included in the cancellation request information. The transaction inquiry unit 122 may also extract and identify proof-of-transaction data for a corresponding transaction based on, for example, transaction amount information, transaction product information, or transaction date and time information included in the cancellation request information.

The transaction inquiry unit 122 may generate inquiry result information based on one identified proof-of-transaction data, or may generate inquiry result information indicating multiple inquiry results based on multiple identified proof-of-transaction data.

Here, the inquiry result information is data in a format that can be referenced by the affiliated store device 200, indicating whether or not a transaction corresponding to the cancellation request exists, and may be, for example, part or all of the proof-of-transaction data.

The inquiry result sending unit 123 sends the inquiry result information to the affiliated store device 200.

The cancellation request acquisition unit 131 acquires a transaction cancellation request from the affiliated store device 200, requesting the cancellation of a transaction.

The affiliated store device 200, for example, references the inquiry result information to identify the transaction to be canceled and provides the transaction cancellation system 100 with a transaction cancellation request requesting cancellation of the identified transaction.

At this time, the affiliated store device 200 may compare the proof-of-transaction data stored in the memory unit of the affiliated store device 200 with the inquiry result information, and if the two match, provide a transaction cancellation request to the transaction cancellation system 100. This allows the affiliated store device 200 to provide a transaction cancellation request after confirming that the transaction to be canceled was processed at the affiliated store.

Depending on the results of the inquiry, the person in charge approval acquisition unit 132 acquires person in charge approval information indicating approval for the transaction cancellation from the person in charge device responsible for the transaction cancellation.

Here, the staff member device may be, for example, a device provided in the affiliated store device 200 for acquiring staff member approval information (e.g., the staff member's ID, fingerprint, or signature). The staff member approval information may be any information that indicates that an authorized staff member has approved the transaction, and may be, for example, the staff member's ID, fingerprint, or signature.

Depending on the results of the inquiry and based on the proof-of-transaction data, the cancellation request sending unit 133 sends payment cancellation request data requesting cancellation of the payment corresponding to the transaction to the external business operator system 400 of the external business operator that performs processing related to the cancellation of the payment.

Here, the payment cancellation request data is information requesting an external business to cancel the payment corresponding to a transaction. The payment cancellation request data includes, for example, information for identifying the transaction to be canceled. The information for identifying the transaction to be canceled may be, for example, information corresponding to some or all of the items in the proof-of-transaction data.

The cancellation request sending unit 133 sends payment cancellation request data to, for example, the external business system 400 corresponding to the external business ID included in the proof-of-transaction data. The external business system 400 can cancel the payment based on the payment cancellation request data it obtains.

In addition, the cancellation request sending unit 133 can send payment cancellation request data to the external business system 400 in response to a transaction cancellation request received from the affiliated store device 200. This allows the transaction cancellation system 100 to perform transaction cancellation processing based on the affiliated store's transaction cancellation request.

In addition, the cancellation request sending unit 133 can send payment cancellation request data based on the person in charge approval information acquired by the person in charge approval acquisition unit 132.

In this case, for example, the transaction cancellation system 100 stores in advance the person in charge approval information of the person in charge who has the authority to approve the cancellation of a transaction. Then, if the pre-stored person in charge approval information of the authorized person in charge matches the person in charge approval information acquired by the person in charge approval acquisition unit 132, the cancellation request sending unit 133 can send the payment cancellation request data, assuming that the person in charge has approved it.

Figure 5 is a flowchart showing an example of processing in the transaction cancellation system 100.

First, the transaction content acquisition unit 112 acquires transaction content data from at least one of the affiliated store device 200, the customer device 300, and the external business system 400 (S501). The transaction proof data generation unit 113 generates transaction proof data that certifies the content of the transaction based on the transaction content data (S502).

Next, the cancellation request acquisition unit 121 acquires information indicating a cancellation request, and the transaction inquiry unit 122 inquires about the existence of the transaction to be canceled based on the transaction proof data (S503). In response to the inquiry results sent by the inquiry result transmission unit 123, the cancellation request acquisition unit 131 acquires a cancellation request from the affiliated store device 200, and the person in charge approval acquisition unit 132 acquires person in charge approval information (S504). The cancellation request transmission unit 133 then transmits payment cancellation request data to the external business system 400 (S505).

The above describes one embodiment of the present invention. The transaction cancellation system 100 can inquire about the existence of a transaction based on proof-of-transaction data and information indicating an application to cancel the transaction, and depending on the results of the inquiry, can send payment cancellation request data to the external business system 400 based on the proof-of-transaction data. This allows for more convenient transaction cancellation processing for member stores and customers, without the need for complicated processing by the customer and member store.

The transaction cancellation system 100 can also acquire transaction content data in accordance with the transaction and generate proof-of-transaction data based on the transaction content data. This allows for more convenient payment cancellation processing based on the proof-of-transaction data generated by the transaction cancellation system 100.

The transaction cancellation system 100 can also obtain staff approval information indicating approval for transaction cancellation from the staff device of the staff member responsible for canceling the transaction, and can send payment cancellation request data based on the staff approval information. This allows the payment cancellation process to be carried out with the approval of an authorized staff member at the affiliated store.

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

100 Transaction cancellation system, 111 Storage unit, 112 Transaction content acquisition unit, 113 Proof-of-transaction data generation unit, 121 Cancellation request acquisition unit, 122 Transaction inquiry unit, 123 Enquiry result transmission unit, 131 Cancellation request acquisition unit, 132 Personnel approval acquisition unit, 133 Cancellation request transmission unit, 200 Member store device, 300 Customer device, 400 External business system

Claims (6)

On the computer,
a transaction content acquisition unit that acquires transaction content data indicating the content of a transaction in accordance with the transaction of a customer;
a proof-of-transaction data generation unit that generates proof-of-transaction data based on the transaction content data, the proof-of-transaction data including information indicating the content of the transaction and proof information that proves that the content of the transaction has not been tampered with;
a transaction inquiry unit that inquires about the existence of the transaction based on the proof-of-transaction data and information indicating an application by the customer to cancel the transaction, the information being acquired through a predetermined device;
an inquiry result sending unit that sends inquiry result information indicating the result of the inquiry to a trading partner device used by a trading partner who traded with the customer in the transaction;
a cancellation request acquisition unit that acquires a transaction cancellation request from the transaction counterparty device, the transaction cancellation request requesting cancellation of the transaction;
a cancellation request sending unit that, in response to the inquiry result, sends payment cancellation request data requesting cancellation of the payment corresponding to the transaction based on the proof-of-transaction data and the transaction cancellation request to an external business system of an external business that performs processing related to the cancellation of the payment;
A transaction cancellation program that achieves this. the information indicating the content of the transaction includes customer identification information that identifies the customer;
the information indicating the cancellation request includes the customer identification information;
the transaction inquiry unit inquires about the existence of the transaction further based on the customer identification information;
2. The transaction cancellation program according to claim 1. A transaction cancellation program as described in claim 1 or 2, wherein the cancellation request acquisition unit acquires the transaction cancellation request transmitted based on the inquiry result information and transaction proof data that certifies the content of the transaction stored in the transaction partner device. The computer further implements a person in charge approval acquisition unit that acquires person in charge approval information indicating approval for the cancellation of the transaction from a person in charge device of the person in charge of the cancellation of the transaction according to the result of the inquiry,
The cancellation request transmission unit transmits the payment cancellation request data further based on the person in charge approval information.
3. The transaction cancellation program according to claim 1 or 2. a transaction content acquisition unit that acquires transaction content data indicating the content of a transaction in accordance with the transaction of a customer;
a proof-of-transaction data generation unit that generates proof-of-transaction data based on the transaction content data, the proof-of-transaction data including information indicating the content of the transaction and proof information that proves that the content of the transaction has not been tampered with;
a transaction inquiry unit that inquires about the existence of the transaction based on the proof-of-transaction data and information indicating an application by the customer to cancel the transaction, the information being acquired through a predetermined device;
an inquiry result sending unit that sends inquiry result information indicating the result of the inquiry to a trading partner device used by a trading partner who traded with the customer in the transaction;
a cancellation request acquisition unit that acquires a transaction cancellation request from the transaction counterparty device, the transaction cancellation request requesting cancellation of the transaction;
a cancellation request sending unit that, in response to the inquiry result, sends payment cancellation request data requesting cancellation of the payment corresponding to the transaction based on the proof-of-transaction data and the transaction cancellation request to an external business system of an external business that performs processing related to the cancellation of the payment;
A transaction cancellation system comprising: The computer
a transaction content acquisition unit that acquires transaction content data indicating the content of a transaction in accordance with the transaction of a customer;
a proof-of-transaction data generation unit that generates proof-of-transaction data based on the transaction content data, the proof-of-transaction data including information indicating the content of the transaction and proof information that proves that the content of the transaction has not been tampered with;
inquiring whether the transaction has taken place based on the proof-of-transaction data and information indicating a request by the customer to cancel the transaction, the information being obtained through a predetermined device;
transmitting inquiry result information indicating the result of the inquiry to a trading partner device used by a trading partner who traded with the customer in the transaction;
receiving a transaction cancellation request from the transaction counterparty device, the transaction cancellation request requesting cancellation of the transaction;
In response to the result of the inquiry, based on the proof-of-transaction data and the transaction cancellation request , transmit payment cancellation request data requesting cancellation of the payment corresponding to the transaction to an external business system of an external business that performs processing related to the cancellation of the payment.
How to cancel a transaction.