Transaction processing system and transaction processing method

Abstract

To reduce the time and effort of a person who settles a payment for a transaction using an electronic receipt service when biometric authentication is used for authenticating the person.SOLUTION: A transaction processing system includes acquisition means, determination means, settlement means, and management means. The acquisition means acquires biometric information of a person who settles a payment for a transaction. The determination means determines an identifier associated with the biometric information acquired by the acquisition means. The settlement means settles a payment for the transaction by using settlement information associated with the identifier when the determination means determines the identifier. The management means manages receipt information related to the transaction settled by the settlement means in association with the identifier determined by the determination means.SELECTED DRAWING: Figure 14

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE The present invention relates to a transaction processing system and a transaction processing method. [Background technology]

[0002] When the settlement of a transaction is to be performed by biometric authentication, the settlement person is required to perform an operation for inputting his / her own biometric information. In addition, a payer who wished to apply the electronic receipt service to the above-mentioned transaction was required to display a barcode representing the identifier of the user of the electronic receipt service on an information terminal such as a smartphone and have it read. This made the operation of the settlement person troublesome. For these reasons, it has been desirable to reduce the burden on a settlor when biometric authentication is used to authenticate the settlor in a transaction that uses an electronic receipt service. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2018-60278 A [Patent Document 2] Patent No. 5739046 Summary of the Invention [Problem to be solved by the invention]

[0004] The problem to be solved by the present invention is to provide a transaction processing system and a transaction processing method that can reduce the burden on a settlor when biometric authentication is used to authenticate the settlor in a transaction that uses an electronic receipt service. [Means for solving the problem]

[0005] The transaction processing system according to the embodiment includes an acquisition unit, a determination unit, and a settlement unit. , conversion means, management measures and granting meansThe acquisition means acquires biometric information of a person who settles a transaction. The determination means determines whether or not the biometric information acquired by the acquisition means is associated with 1. The identifier is determined by the determination means. 1. If the identifier can be determined, 1. The transaction price is settled using payment information associated with the identifier and predefined to use the payment service. The conversion means converts the first identifier determined by the determination means into a second identifier for the receipt and a second identifier for the bonus, respectively. The management means stores receipt information relating to transactions settled by the payment means, A second number for the receipt obtained by the conversion means Manage by associating with an identifier. The granting means grants a benefit related to the transaction settled by the payment means to a user associated with the identifier determined by the determination means or the second identifier for the benefit obtained by the conversion means. [Brief description of the drawings]

[0006] [Figure 1] 1 is a block diagram showing a schematic configuration of a transaction processing system according to a first embodiment. [Diagram 2] 2 is a block diagram showing a main circuit configuration of the user terminal shown in FIG. 1; [Diagram 3] FIG. 2 is a block diagram showing a main circuit configuration of the sales server shown in FIG. 1; [Figure 4] FIG. 2 is a block diagram showing a main circuit configuration of the proxy server shown in FIG. [Diagram 5] FIG. 5 is a diagram showing a schematic configuration of a data record included in the payment information database shown in FIG. 4. [Figure 6] 2 is a block diagram showing a main circuit configuration of the authentication server shown in FIG. 1; [Figure 7] FIG. 7 is a diagram showing a schematic configuration of a data record included in the authentication database shown in FIG. 6. [Figure 8] FIG. 2 is a block diagram showing a main circuit configuration of the payment server shown in FIG. [Figure 9] 2 is a block diagram showing the main circuit configuration of the receipt server shown in FIG. 1. [Figure 10] 10 is a diagram showing a schematic configuration of a data record included in the receipt database shown in FIG. 9. [Figure 11] FIG. 2 is a block diagram showing a main circuit configuration of the privilege server 7 shown in FIG. [Figure 12]FIG. 12 is a diagram showing a schematic configuration of a data record included in the point database shown in FIG. 11. [Figure 13] FIG. 13 is a diagram showing a sequence relating to user registration for a transaction processing service. [Figure 14] FIG. 13 is a diagram showing a sequence when a transaction processing service is used for payment related to the purchase of a product at a store. [Figure 15] FIG. 5 is a diagram showing a schematic configuration of a data record included in the payment information database shown in FIG. 4. [Figure 16] FIG. 7 is a diagram showing a schematic configuration of a data record included in the authentication database shown in FIG. 6. [Figure 17] 10 is a diagram showing a schematic configuration of a data record included in the receipt database shown in FIG. 9. [Figure 18] FIG. 12 is a diagram showing a schematic configuration of a data record included in the point database shown in FIG. 11. [Figure 19] FIG. 11 is a diagram showing a sequence related to user registration for an electronic receipt service. [Figure 20] FIG. 13 is a diagram showing a sequence relating to user registration for a points service. [Figure 21] FIG. 1 is a diagram showing a sequence relating to ID association. [Figure 22] FIG. 13 is a diagram showing a sequence when a transaction processing service is used for payment related to the purchase of a product at a store. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] Hereinafter, an embodiment will be described with reference to the drawings. [First embodiment] FIG. 1 is a block diagram showing a schematic configuration of a transaction processing system 100 according to the first embodiment. The transaction processing system 100 includes a user terminal 1, a sales server 2, an agency server 3, an authentication server 4, a payment server 5, a receipt server 6, and a bonus server 7. The user terminal 1, the sales server 2, the agency server 3, the authentication server 4, the payment server 5, the receipt server 6, and the bonus server 7 can communicate with each other via a communication network 200. The communication network 200 may be the Internet, a virtual private network (VPN), a local area network (LAN), a public communication network, a mobile communication network, a dedicated line, or the like, either alone or in combination as appropriate. The transaction processing system 100 includes a plurality of user terminals 1 and payment servers 5, but only one is shown in FIG. 1. The transaction processing system 100 may also include a plurality of sales servers 2. The transaction processing system 100 may also include a plurality of bonus servers 7.

[0008] User terminal 1 is an information terminal used by a user who will be the settler of a transaction to be processed by transaction processing system 100. User terminal 1 is typically dedicated to an individual user. Note that the transaction to be processed by transaction processing system 100 may be any transaction that involves the settlement of a price, but in this embodiment it is the sale of a product.

[0009] The sales server 2 is a server device that performs information processing for sales, such as registering products for sale and calculating the prices of the products for sale. The sales server 2 is, for example, a point-of-sale (POS) server. The sales server 2 is managed, for example, by a product seller.

[0010] The agency server 3 is a server device that performs information processing to provide a payment agency service that enables easy use of multiple payment services provided by multiple payment servers 5. The agency server 3 is managed, for example, by a provider of the payment agency service.

[0011] Authentication server 4 is a server device that performs information processing to authenticate whether or not a settler has been registered as a user of the transaction processing service provided by transaction processing system 100. Authentication server 4 is managed, for example, by a provider of the authentication service.

[0012] The payment server 5 is a server device that performs information processing for payment in response to a request from the agency server 3. The multiple payment servers 5 included in the transaction processing system 100 include those that apply different payment methods. For example, one of the payment servers 5 performs credit card payment. For example, another of the payment servers 5 performs code payment. The multiple payment servers 5 included in the transaction processing system 100 also include those that apply the same payment method but have different vendors or brands. For example, two of the payment servers 5 perform credit card payments for different brands of credit cards. The agency server 3 is managed, for example, by a provider of a payment agency service. The payment server 5 is managed, for example, by a provider of a payment service.

[0013] The receipt server 6 is a server device that performs information processing to provide the electronic receipt service to registered users. The receipt server 6 is managed, for example, by a provider of the electronic receipt service.

[0014] The reward server 7 is a server device that performs information processing to provide a reward granting service to a user who has registered for use. The reward granting service is a service that gives any reward to a user. In this embodiment, the reward granting service is a point service. The reward server 7 is managed, for example, by a provider of the reward granting service. Typically, the product seller and the provider of the various services are separate entities. However, some or all of the product seller and the provider of the various services may be the same business entity.

[0015] FIG. 2 is a block diagram showing the main circuit configuration of the user terminal 1. As shown in FIG. The user terminal 1 is typically a portable information processing device such as a smartphone, a mobile phone, or a tablet terminal.

[0016] The user terminal 1 includes a processor 11, a main memory 12, an auxiliary storage unit 13, a touch panel 14, an input unit 15, a communication unit 16, and a transmission path 17. The processor 11, the main memory 12, the auxiliary storage unit 13, the touch panel 14, the input unit 15, and the communication unit 16 are capable of communicating with each other via the transmission path 17. The processor 11, the main memory 12, and the auxiliary storage unit 13 are connected by the transmission path 17 to constitute a computer that performs information processing for controlling the user terminal 1.

[0017] The processor 11 corresponds to the central part of the computer. The processor 11 controls each part to realize various functions of the user terminal 1 according to information processing programs such as an operating system and application programs. The processor 11 is, for example, a CPU (central processing unit).

[0018] The main memory 12 corresponds to the main storage portion of the computer. The main memory 12 includes a nonvolatile memory area and a volatile memory area. The main memory 12 stores an operating system and application programs in the nonvolatile memory area. The main memory 12 may also store data required for the processor 11 to execute processes for controlling each part in the nonvolatile or volatile memory area. The main memory 12 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 11. The nonvolatile memory area is, for example, a ROM (read only memory). The volatile memory area is, for example, a RAM (random access memory).

[0019] The auxiliary storage unit 13 corresponds to the auxiliary storage portion of the computer. The auxiliary storage unit 13 is, for example, an EEPROM (electric erasable programmable read-only memory). A hard disk drive (HDD), a solid state drive (SSD), or other well-known storage devices may be used as the auxiliary storage unit 13. The auxiliary storage unit 13 stores data used by the processor 11 in performing various processes and data generated by the processes in the processor 11. The auxiliary storage unit 13 stores application programs.

[0020] One of the application programs stored in auxiliary memory unit 13 is an information processing program (hereinafter referred to as a client application) APA for using a transaction processing service provided by transaction processing system 100. Typically, however, the client application APA is downloaded, for example, via the Internet, in response to an operation by a user of user terminal 1, and written to auxiliary memory unit 13. In other words, the user terminal 1 is transferred to the user of the user terminal 1 in a state in which the client application APA is not stored in auxiliary memory unit 13. However, the user terminal 1 in a state in which the client application APA is stored in auxiliary memory unit 13 may be transferred to the user of user terminal 1.

[0021] The touch panel 14 functions as an input device and a display device for the user terminal 1. The input unit 15 inputs biometric information. The biometric information is information that represents characteristics such as fingerprints, veins, irises, and faces. For example, the biometric information may be information similar to that used in known biometric authentication technology. If, for example, fingerprint characteristics are used as the biometric information, an existing fingerprint sensor may be used as the input unit 15. If, on the other hand, facial characteristics are used as the biometric information, an existing camera may be used as the input unit 15.

[0022] The communication unit 16 performs communication processing for data communication via the communication network 200. As the communication unit 16, for example, a well-known communication device for performing data communication via a mobile communication network or the Internet can be used. The transmission path 17 includes an address bus, a data bus, and control signal lines, and transmits data and control signals between the connected components.

[0023] FIG. 3 is a block diagram showing the main circuit configuration of the sales server 2. As shown in FIG. The sales server 2 includes a processor 21, a main memory 22, an auxiliary storage unit 23, a communication unit 24, and a transmission path 25. The processor 21, the main memory 22, the auxiliary storage unit 23, and the communication unit 24 are capable of communicating with each other via the transmission path 25. The processor 21, the main memory 22, and the auxiliary storage unit 23 are connected by the transmission path 25 to configure a computer for controlling the sales server 2.

[0024] The processor 21 corresponds to the central part of the computer. The processor 21 executes information processing for realizing various functions of the sales server 2 in accordance with an operating system and information processing programs such as application programs. The processor 21 is, for example, a CPU.

[0025] The main memory 22 corresponds to the main storage portion of the computer. The main memory 22 includes a nonvolatile memory area and a volatile memory area. The main memory 22 stores the information processing program in the nonvolatile memory area. The main memory 22 may store data required for the processor 21 to execute information processing in a nonvolatile or volatile memory area. The main memory 22 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 21. The nonvolatile memory area is, for example, a ROM. The volatile memory area is, for example, a RAM.

[0026] The auxiliary storage unit 23 corresponds to the auxiliary storage portion of the computer. As the auxiliary storage unit 23, for example, a storage unit using a well-known storage device such as an EEPROM, HDD, or SSD can be used. The auxiliary storage unit 23 stores data used by the processor 21 when performing various processes, or data created by the processes in the processor 21. The auxiliary storage unit 23 may also store the information processing program.

[0027] The communication unit 24 performs communication processing for data communication via the communication network 200. As the communication unit 24, for example, a well-known communication device for performing data communication via a mobile communication network or the Internet can be used. The transmission path 25 includes an address bus, a data bus, and control signal lines, and transmits data and control signals between the connected components.

[0028] The auxiliary storage unit 23 stores a sales application APB, which is one of the information processing programs. The sales application APB is an application program in which information processing for realizing the functions of the sales server 2 is described.

[0029] FIG. 4 is a block diagram showing the main circuit configuration of the proxy server 3. As shown in FIG. The proxy server 3 includes a processor 31, a main memory 32, an auxiliary storage unit 33, a communication unit 34, and a transmission path 35. The processor 31, the main memory 32, the auxiliary storage unit 33, and the communication unit 34 are capable of communicating with each other via the transmission path 35. The processor 31, the main memory 32, and the auxiliary storage unit 33 are connected by the transmission path 35 to configure a computer for controlling the proxy server 3. The functions of the processor 31, the main memory 32, the auxiliary storage unit 33, the communication unit 34, and the transmission path 35 are generally the same as those of the processor 21, the main memory 22, the auxiliary storage unit 23, the communication unit 24, and the transmission path 25, and therefore a description thereof will be omitted.

[0030] However, the auxiliary storage unit 33 stores an agency application APC instead of the sales application APB. The agency application APC is an application program, and describes information processing for realizing the functions of the agency server 3. A part of the storage area of ​​the auxiliary storage unit 33 is used as a payment information database DBA.

[0031] FIG. 5 is a diagram showing a schematic configuration of a data record DRA contained in the payment information database DBA. The payment information database DBA is a collection of data records DRA associated with users of the transaction processing service. The data record DRA includes fields FAA and FAB. A user ID (identifier) ​​that is an identifier for the user is set in the field FAA. Payment information previously declared by the user is set in the field FAB. The payment information is information for using the payment services provided by the payment server 5. The payment information is various data, such as a credit number, that is predetermined for using various other payment services such as credit payment, electronic money payment, or code payment. The data record DRA may include other fields, and any information may be set in those fields.

[0032] FIG. 6 is a block diagram showing the main circuit configuration of the authentication server 4. As shown in FIG. The authentication server 4 includes a processor 41, a main memory 42, an auxiliary storage unit 43, a communication unit 44, and a transmission path 45. The processor 41, the main memory 42, the auxiliary storage unit 43, and the communication unit 44 are capable of communicating with each other via the transmission path 45. The processor 41, the main memory 42, and the auxiliary storage unit 43 are connected by the transmission path 45 to configure a computer for controlling the authentication server 4. The functions of the processor 41, the main memory 42, the auxiliary storage unit 43, the communication unit 44, and the transmission path 45 are generally similar to those of the processor 21, the main memory 22, the auxiliary storage unit 23, the communication unit 24, and the transmission path 25, and therefore will not be described here.

[0033] However, the auxiliary storage unit 43 stores an authentication application APD instead of the sales application APB. The authentication application APD is an application program, and describes information processing for realizing the functions of the authentication server 4. A part of the storage area of ​​the auxiliary storage unit 43 is used as an authentication database DBB.

[0034] FIG. 7 is a diagram showing a typical structure of a data record DRB contained in the authentication database DBB. The authentication database DBB is a collection of data records DRB associated with users of the transaction processing service. The data record DRB includes fields FBA and FBB. A user ID is set in the field FBA. The user's biometric information is set in the field FBB. The biometric information is set in the field FBB as a hash value, for example. The data record DRB may also include another field, in which any information may be set.

[0035] FIG. 8 is a block diagram showing the main circuit configuration of the payment server 5. As shown in FIG. The payment server 5 includes a processor 51, a main memory 52, an auxiliary storage unit 53, a communication unit 54, and a transmission path 55. The processor 51, the main memory 52, the auxiliary storage unit 53, and the communication unit 54 are capable of communicating with each other via the transmission path 55. The processor 51, the main memory 52, and the auxiliary storage unit 53 are connected via the transmission path 55 to configure a computer for controlling the authentication server 4. The functions of the processor 51, the main memory 52, the auxiliary storage unit 53, the communication unit 54, and the transmission path 55 are generally the same as those of the processor 21, the main memory 22, the auxiliary storage unit 23, the communication unit 24, and the transmission path 25, and therefore will not be described here.

[0036] However, the auxiliary storage unit 53 stores a payment application APE instead of the sales application APB. The payment application APE is an application program, and information processing for realizing the functions of the payment server 5 is written in the payment application APE.

[0037] FIG. 9 is a block diagram showing the main circuit configuration of the receipt server 6. The receipt server 6 includes a processor 61, a main memory 62, an auxiliary memory unit 63, a communication unit 64, and a transmission path 65. The processor 61, the main memory 62, the auxiliary memory unit 63, and the communication unit 64 are capable of communicating with each other via the transmission path 65. The processor 61, the main memory 62, and the auxiliary memory unit 63 are connected via the transmission path 65 to form a computer for controlling the receipt server 6. The functions of the processor 61, the main memory 62, the auxiliary memory unit 63, the communication unit 64, and the transmission path 65 are generally the same as those of the processor 21, the main memory 22, the auxiliary memory unit 23, the communication unit 24, and the transmission path 25, so a description thereof will be omitted.

[0038] However, the auxiliary storage unit 63 stores an electronic receipt application APF instead of the sales application APB. The electronic receipt application APF is an application program, and describes information processing for realizing the functions of the receipt server 6. Also, a part of the storage area of ​​the auxiliary storage unit 63 is used as a receipt database DBC.

[0039] FIG. 10 is a diagram showing a schematic configuration of a data record DRC contained in the receipt database DBC. The receipt database DBC is a collection of data records DRC associated with users of the transaction processing service. The data record DRC includes fields FCA and FCB. The data record DRC may also include fields following field FCC. A user ID is set in field FCA. Receipt information relating to one transaction is set in field FCB. If multiple receipt information has been registered for a user identified by the user ID set in field FCA, receipt information relating to the second and subsequent transactions is set in each field following field FCC. The data record DRC may also include other fields, in which any information may be set.

[0040] FIG. 11 is a block diagram showing the main circuit configuration of the bonus server 7. As shown in FIG. The bonus server 7 includes a processor 71, a main memory 72, an auxiliary storage unit 73, a communication unit 74, and a transmission path 75. The processor 71, the main memory 72, the auxiliary storage unit 73, and the communication unit 74 are capable of communicating with each other via the transmission path 75. The processor 71, the main memory 72, and the auxiliary storage unit 73 are connected by the transmission path 75 to form a computer for controlling the bonus server 7. The functions of the processor 71, the main memory 72, the auxiliary storage unit 73, the communication unit 74, and the transmission path 75 are generally similar to those of the processor 21, the main memory 22, the auxiliary storage unit 23, the communication unit 24, and the transmission path 25, and therefore will not be described here.

[0041] However, the auxiliary storage unit 73 stores a point service application APG instead of the sales application APB. The point service application APG is an application program, and describes information processing for realizing the functions of the benefit server 7. Also, a part of the storage area of ​​the auxiliary storage unit 73 is used as a point database DBD.

[0042] FIG. 12 is a diagram showing a schematic configuration of a data record DRD contained in the point database DBD. The points database DBD is a collection of data records DRD associated with users of the transaction processing service. Data record DRD includes fields FDA and FDB. A user ID is set in field FDA. Point information related to the user is set in field FDB. Any information may be included in the point information, but it is assumed that it may include, for example, the current number of points held. Point information may also include history information showing the history of points being awarded and used. Note that data record DRD may also include another field, in which any information may be set.

[0043] Now, for example, a general-purpose server device can be used as the hardware of the sales server 2, the agency server 3, the authentication server 4, the payment server 5, the receipt server 6, and the benefit server 7. The sales server 2, the agency server 3, the authentication server 4, the payment server 5, the receipt server 6, or the benefit server 7 is generally transferred in a state where the sales application APB, the agency application APC, the authentication application APD, the payment application APE, the electronic receipt application APF, or the point service application APG is stored in the auxiliary storage unit 13, 23, 33, 43, 53, 63, or 73, respectively, and the payment information database DBA, the authentication database DBB, the receipt database DBC, or the point database DBD is not stored. However, the hardware in a state where the sales application APB, the agency application APC, the authentication application APD, the payment application APE, the electronic receipt application APF, or the point service application APG is not stored in the auxiliary storage unit 13, 23, 33, 43, 53, 63, or 73, or where a different version of the same application program is stored in the auxiliary storage unit 13, 23, 33, 43, 53, 63, or 73, and the sales application APB, the agency application APC, the authentication application APD, the payment application APE, the electronic receipt application APF, or the point service application APG may be transferred separately. Then, the sales server 2, the agency server 3, the authentication server 4, the payment server 5, the receipt server 6, and the benefit server 7 may be configured by writing the sales application APB, the agency application APC, the authentication application APD, the payment application APE, the electronic receipt application APF, or the point service application APG to the auxiliary storage unit 13, 23, 33, 43, 53, 63, or 73 in response to an operation by an arbitrary worker. The sales application APB, the agency application APC, the authentication application APD, the payment application APE, the electronic receipt application APF or the point service application APG can be transferred by recording it on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, a semiconductor memory, or by communication via a network.The payment information database DBA, the authentication database DBB, the receipt database DBC, or the point database DBD is configured in the auxiliary storage unit 33, 43, 63, or 73 by the processor 31, 41, 61, or 71 executing information processing.

[0044] Next, the operation of the transaction processing system 100 configured as described above will be described. Note that the contents of the various processes described below are merely examples, and it is possible to change the order of some of the processes, omit some of the processes, or add other processes as appropriate. In the following explanation, in order to easily explain the characteristic operations of this embodiment, some of the processes related to such characteristic operations will be explained, and explanations of many other processes will be omitted.

[0045] In addition, in the user terminal 1, sales server 2, agency server 3, authentication server 4, settlement server 5, receipt server 6 and bonus server 7, processors 11, 21, 31, 41, 51, 61, 71 execute information processing to realize the sequence described below based on the client application APA, sales application APB, agency application APC, authentication application APD, settlement application APE, electronic receipt application APF and point service application APG.

[0046] FIG. 13 is a diagram showing a sequence relating to user registration for a transaction processing service. In order to use the transaction processing service, the user installs the client application APA in the user terminal 1 and instructs the start of information processing based on the client application APA. The user then instructs user registration. Note that various instructions from the user terminal 1 are given by, for example, predetermined operations on the touch panel 14. In response to the start instruction, the processor 11 in the user terminal 1 starts information processing based on the client application APA.

[0047] As ACT1, the processor 11 inputs biometric information and payment information. The processor 11, for example, guides the user to input the biometric information and payment information. The user follows the guidance and performs an operation to input his / her biometric information into the input unit 15. If, for example, fingerprint features are used as the biometric information, the user places his / her fingertip on the input unit 15. If, for example, facial features are used as the biometric information, the user turns his / her face toward the input unit 15. The input unit 15 extracts predetermined features related to the fingerprint or face, etc., and generates biometric information representing the extracted features. The generation of the biometric information may be performed by the processor 11. The user follows the guidance and inputs payment information to be used for payment using the transaction processing service, for example, by a predetermined operation on the touch panel 14. The order of inputting the biometric information and the payment information is arbitrary.

[0048] As ACT2, the processor 11 requests registration from the proxy server 3. The processor 11 transmits request data including, for example, identification information for identifying that the request is for user registration, and the biometric information and payment information input in ACT1, from the communication unit 16 to the communication network 200, addressed to the proxy server 3.

[0049] When the above request data is transmitted to the proxy server 3 via the communication network 200 and received by the communication unit 34, the processor 31 in the proxy server 3 proceeds to ACT3. The various requests described below are realized by transmitting and receiving, via the communication network 200, request data including identification information for identifying the purpose of the request, in the same manner as described above.

[0050] As ACT3, the processor 31 determines a user ID to be associated with the user so that the user ID does not overlap with a user ID already associated with another user. For example, the processor 31 determines a character string determined according to a predetermined algorithm so that a character string can be determined without overlapping as the user ID. Alternatively, the processor 31 stores list data representing a list of previously determined user IDs in the auxiliary storage unit 33, and determines a user ID not included in the list as a new user ID. The processor 31 may determine a user ID by any other method.

[0051] In ACT4, the processor 31 updates the payment information database DBA. For example, the processor 31 adds to the payment information database DBA a new data record DRA in which the user ID determined in ACT3 and the payment information included in the request data are set in fields FAA and FAB, respectively.

[0052] In ACT5, the processor 31 requests registration from the authentication server 4. For example, the processor 31 includes in the request data for this request the user ID determined in ACT3 and the biometric information included in the request data sent from the user terminal 1 in ACT2.

[0053] When the processor 41 in the authentication server 4 receives the registration request, the process proceeds to ACT6. In ACT6, the processor 41 updates the authentication database DBB. For example, the processor 41 adds to the authentication database DBB a new data record DRB in which the user ID and biometric information included in the request data are set in fields FBA and FBB, respectively.

[0054] As ACT7, the processor 41 notifies the proxy server 3 of the completion of registration. For example, the processor 41 transmits notification data including identification information for identifying that the notification is a registration completion notification and the user ID set in the field FBA of the new data record DRB from the communication unit 44 to the communication network 200, addressed to the proxy server 3. Note that if it is possible to determine which registration request the completion notification is for by using a session ID or an ID for identifying each registration request, the notification data does not need to include the user ID.

[0055] When the above notification data is transmitted to the proxy server 3 via the communication network 200 and received by the communication unit 34, the processor 31 in the proxy server 3 proceeds to ACT8. At this time, the processor 31 may check whether the user ID included in the notification data matches the user ID determined in ACT3, and proceed to ACT8 only if they match. The various notifications described below are realized by transmitting and receiving, via the communication network 200, notification data including identification information for identifying the purpose of the notification, in the same manner as described above.

[0056] The processor 31 as ACT8 notifies the user terminal 1 of the completion of registration. When the above notification data is transmitted to the user terminal 1 via the communication network 200 and received by the communication unit 16, the user terminal 1 completes the process related to user registration.

[0057] FIG. 14 is a diagram showing a sequence when a transaction processing service is used for settlement related to the purchase of goods at a store. When a user who has completed user registration uses the transaction processing service for payment related to purchasing a product at a store, the user or a store clerk operates the registration device for product registration to declare the use of the transaction processing service. Upon receiving this declaration, the processor 21 in the sales server 2 proceeds to ACT21.

[0058] As ACT21, the processor 21 requests biometric information from the user terminal 1. The processor 21 establishes communication with the user terminal 1 based on connection information obtained by, for example, reading a barcode displayed on the touch panel 14 of the user terminal 1 using a scanner in a registration device such as a POS terminal.

[0059] When the processor 11 in the user terminal 1 receives a request for biometric information, the process proceeds to ACT22. As ACT22, the processor 11 inputs biometric information. For example, the processor 11 guides the user to input the biometric information. The user follows the guidance and performs an operation to input his / her biometric information into the input unit 15. As a result, the processor 11 obtains the biometric information in the same manner as described above. In this way, the processor 11 obtains the biometric information of the user who will be the settler of the transaction. In other words, the processor 11 executes information processing based on the client application APA, and the computer with the processor 11 as its central part functions as an acquisition means. The user terminal 1 corresponds to a first device equipped with an acquisition means. In ACT23, the processor 11 notifies the sales server 2 of the biometric information. The processor 11 includes the biometric information input in ACT22 in the notification data sent here.

[0060] When the product registration and the calculation of the payment amount are completed in the registration device, the processor 21 in the sales server 2 proceeds to ACT24. In ACT24, the processor 21 requests a payment from the agent server 3. The processor 21 includes in the request data sent here the payment amount calculated by the registration device and the biometric information notified in ACT23.

[0061] When the processor 31 in the agent server 3 receives the payment request, the process proceeds to ACT25. In ACT25, the processor 31 requests authentication from the authentication server 4. The processor 31 includes in the request data transmitted here the biometric information contained in the request data transmitted from the sales server 2 in ACT24.

[0062] When the processor 41 in the authentication server 4 receives the authentication request, the process proceeds to ACT26. The processor 41 performs a query process as ACT26. That is, the processor 41, for example, checks whether the biometric information included in the request data sent from the proxy server 3 in ACT25 matches any of the biometric information registered in the authentication database DBB. For example, if the matching rate of the features with the biometric information included in the request data sent from the proxy server 3 in ACT25 is equal to or higher than a predetermined rate, the processor 41 determines that the authentication is successful, and if not, determines that the authentication is unsuccessful. Then, for example, if the authentication is successful, the processor 41 selects a data record DRB including a field FBB in which the biometric information with the highest matching rate is set. Then, the processor 41 acquires a user ID set in a field FBA of the corresponding data record DRB. The query process may be another well-known process for biometric authentication. Thus, the processor 41 determines the user ID as an identifier associated with the biometric information. That is, the processor 41 executes information processing based on the authentication application APD, and the computer with the processor 41 as the central part functions as a determination means. The authentication server 4 corresponds to a second device equipped with a determination means.

[0063] In ACT27, the processor 41 notifies the proxy server 3 of the result of the authentication. The notification data sent by the processor 41 includes result information indicating whether the authentication was successful or not, and if the authentication was successful, includes the user ID acquired in ACT26. Note that ACT27 and subsequent steps in Fig. 14 show the sequence when the authentication is successful, and a description of the case when the authentication is unsuccessful will be omitted.

[0064] When the processor 31 in the proxy server 3 receives a result notification indicating successful authentication, the process proceeds to ACT28. As ACT28, the processor 31 determines the payment server 5 to be used for the payment in response to the payment request made from the sales server 2 as ACT24. For example, the processor 31 searches the payment information database DBA for a data record DRA in which the user ID included in the notification data of the result notification is set in the field FAA. Then, the processor 31 determines the payment server 5 corresponding to the payment information set in the field FAB of the corresponding data record DRA as the payment server 5 to be used for the payment.

[0065] In ACT29, the processor 31 requests payment from the payment server 5 determined in ACT28. In the request data, the processor 31 includes the payment amount included in the request data transmitted from the sales server 2 in ACT24 and the payment information used to determine the payment server 5 in ACT28.

[0066] When the processor 51 in the payment server 5 receives the payment request, the process proceeds to ACT30. As ACT30, the processor 51 performs a payment process to settle the payment amount included in the request data using the payment information. For example, the processor 51 executes a process to withdraw the payment amount from an account associated with the credit number included in the payment information. The payment process performed by the processor 51 may be the same process as that performed by an existing payment server.

[0067] In this way, the processor 51 pays the price of the transaction using the payment information notified from the agent server 3 when the user ID associated with the biometric information is determined. The processor 51 functions as a payment means by executing information processing based on the payment application APE. The payment server 5 corresponds to a third device equipped with a payment means.

[0068] In ACT31, processor 51 notifies the agent server 3 of the result of the payment process. In the notification data, processor 51 includes at least result information indicating whether or not the payment was completed normally. If there is information that is determined to be notified depending on the payment method, such as a payment number, processor 51 also includes the relevant information in the notification data. Note that ACT31 and thereafter in Figure 14 represent the sequence when the payment is completed normally in ACT30, and a description of the case when the payment fails will be omitted.

[0069] When the processor 31 in the agent server 3 receives a result notification that the settlement has been completed normally, the process proceeds to ACT 32. As ACT32, the processor 31 notifies the sales server 2 of the result of the payment process. The processor 31 includes in the notification data here the result information included in the notification data received from the payment server 5 in ACT31 and the user ID included in the notification data received from the authentication server 4 in ACT27.

[0070] When the processor 21 in the sales server 2 receives a result notification that the settlement has been completed normally, the processor 21 proceeds to ACT 33. As ACT33, the processor 21 requests the receipt server 6 to register an electronic receipt. The processor 21 includes in the request data here the user ID and receipt information included in the notification data received from the agent server 3 in ACT32. The receipt information is information that indicates the content of the transaction that was the subject of the calculation of the payment amount notified to the agent server 3 in ACT24. The type of information to be included in the receipt information may be determined arbitrarily by, for example, the creator of the sales application APB. The receipt information includes, for example, information for managing the transaction, such as the name and date of the store where the transaction was performed, or the receipt number, and information such as the product code, number, unit price, and total amount for each product that was the subject of the transaction. In other words, the receipt information is expected to include various information that is written on a paper receipt. The receipt information may also include the payment number included in the notification data sent from the payment server 5 in ACT31. The receipt information may be generated by a registration device. In this case, the processor 21 includes the receipt information acquired from the registration device in the request data.

[0071] When the processor 61 in the receipt server 6 receives the registration request, the process proceeds to ACT34. In ACT34, the processor 61 updates the receipt database DBC. For example, the processor 61 searches the receipt database DBC for a data record DRC in which the user ID included in the request data received from the sales server 2 in ACT33 is set in the field FCA. If the processor 61 finds a corresponding data record DRC, it adds a new field after the last field of the data record DRC. The processor 61 then sets the receipt information included in the request data received from the sales server 2 in ACT33 in this new field. If the processor 61 does not find a corresponding data record DRC, it adds a new data record DRC in which the user ID and receipt information included in the request data received from the sales server 2 in ACT33 are set in the fields FCA and FCB to the receipt database DBC.

[0072] Thus, the processor 61 uses the receipt database DBC to manage receipt information in association with a user identifier associated with the biometric information of the payer. Thus, the processor 61 executes information processing based on the electronic receipt application APF, and the computer with the processor 61 as its central part functions as a management means. The receipt server 6 corresponds to a fourth device equipped with a management means. In ACT35, the processor 61 notifies the sales server 2 that the receipt registration has been completed.

[0073] When the processor 21 of the sales server 2 receives a completion notification that the receipt registration is complete, the processor 21 proceeds to ACT 36. Note that in response to receiving the result notification in ACT 32, the processor 21 may proceed to ACT 36 before or after the registration request in ACT 33, without waiting for the completion notification in ACT 35. As ACT36, the processor 21 requests the privilege server 7 to perform processing related to the point service. In the request data, the processor 21 includes the user ID and point information contained in the notification data received from the agent server 3 in ACT32. FIG. 14 shows a sequence for realizing a service that adds the number of points granted according to the transaction content to the number of points owned by the payer. Therefore, the point information indicates the number of points granted according to the transaction content. What kind of point service is provided and what information is included in the point information may be determined arbitrarily by, for example, the creator of the point service application APG. The point information may be generated by a registration device. In this case, the processor 21 includes the point information acquired from the registration device in the request data.

[0074] When the processor 71 in the bonus server 7 receives the processing request, the process proceeds to ACT37. In ACT37, the processor 71 updates the point database DBD. For example, the processor 71 searches the point database DBD for a data record DRD in which the user ID included in the request data received from the sales server 2 in ACT36 is set in the field FDA. If the processor 71 finds the corresponding data record DRD, it rewrites the number of owned points represented by the point information set in the field FDB of the data record DRD to a number obtained by adding the number of owned points to the number of granted points represented by the point information included in the request data. In ACT38, the processor 71 notifies the sales server 2 that the point processing has been completed.

[0075] As described above, the transaction processing system 100 of the first embodiment determines the user ID of the settler by biometric authentication using the settler's biometric information acquired by the user terminal 1, and if the user ID can be determined, settles the price of the transaction and manages receipt information related to the transaction in association with the user ID. Therefore, the authentication of the user of the electronic receipt service can be completed by the settler's biometric authentication, and the user does not need to perform a separate operation to input an ID for the electronic receipt service. This reduces the burden on the settler when biometric authentication is used to authenticate the settler of a transaction that uses the electronic receipt service.

[0076] Furthermore, according to the transaction processing system 100 of the first embodiment, point information related to the point service is also managed in association with the user ID. Therefore, if the user properly inputs the biometric information, the user can use the point service in addition to the electronic receipt service, and the effort required of the settlor when biometric authentication is used to authenticate the settlor of a transaction using the point service can be reduced.

[0077] [Second embodiment] The schematic configuration of the transaction processing system 100 according to the second embodiment is similar to that of the first embodiment, and therefore illustration and description thereof will be omitted. The second embodiment differs from the first embodiment in the structures and sequences of various databases. FIG. 15 is a diagram showing a schematic configuration of a data record DRE included in the payment information database DBA.

[0078] In the second embodiment, the payment information database DBA is a collection of data records DRE associated with users of the transaction processing service. The data record DRE includes fields FEA, FEB, FEC, and FDD. An authentication ID, which is an identifier for a user of the transaction processing service, is set in field FEA. Payment information previously declared by the user is set in field FEB. A receipt ID, which is an identifier for a user of the electronic receipt service, is set in field FEC. A point ID, which is an identifier for a user of the point service, is set in field FED. The data record DRE may include other fields, and any information may be set in those fields.

[0079] FIG. 16 is a diagram showing a schematic configuration of a data record DRF contained in the authentication database DBB. In the second embodiment, the authentication database DBB is a collection of data records DRF associated with users of the transaction processing service. The data record DRF includes fields FFA and FFB. An authentication ID is set in the field FFA. Biometric information of the user is set in the field FFB. The data record DRF may also include other fields in which any information may be set.

[0080] FIG. 17 is a diagram showing a schematic configuration of a data record DRG contained in the receipt database DBC. In the second embodiment, the receipt database DBC is a collection of data records DRG associated with users of the electronic receipt service. The data record DRG includes fields FGA and FGB. The data record DRG may also include fields following field FGC. A receipt ID is set in field FGA. Receipt information relating to one transaction is set in field FGB. If multiple receipt information has been registered for a user identified by the receipt ID set in field FGA, receipt information relating to the second and subsequent transactions is set in each field following field FGC. The data record DRG may also include other fields, in which any information may be set.

[0081] FIG. 18 is a diagram showing a schematic configuration of a data record DRH contained in the point database DBD. In the second embodiment, the point database DBD is a collection of data records DRH associated with users of the point service. The data record DRH includes fields FHA and FHB. A point ID is set in field FHA. Point information is set in field FHB. The data record DRH may also include other fields, in which any information may be set.

[0082] Next, the operation of transaction processing system 100 of the second embodiment configured as above will be described. The authentication ID in the second embodiment is substantially the same as the user ID in the first embodiment. Therefore, the sequence related to user registration for the transaction processing service is substantially the same as that in the first embodiment. However, in the proxy server 3, the processor 31 sets the authentication ID determined as ACT3 as ACT4 in FIG. 13, for example, and the payment information included in the request data in fields FEA and FEB, respectively, and adds a new data record DRE in which predetermined invalid values ​​are set in fields FEC and FED to the payment information database DBA. The processor 31 may leave fields FEC and FED blank, or may not include fields FEC and FED in the new data record DRE.

[0083] In addition, in the registration request as ACT5 and the completion notification as ACT7, the authentication ID is included in the request data and notification data instead of the user ID. Then, in the authentication server 4, the processor 41 adds, for example, in ACT6, a new data record DRF in which the authentication ID and biometric information included in the request data are set in fields FFA and FFB, respectively, to the authentication database DBB.

[0084] FIG. 19 is a diagram showing a sequence related to user registration for the electronic receipt service. In order to start using the electronic receipt service, the user instructs the user terminal 1, in which the processor 11 is executing information processing based on the client application APA, to perform user registration for the electronic receipt service. In response to this instruction, the processor 11 in the user terminal 1 proceeds to ACT41. As ACT41, the processor 11 requests the receipt server 6 for registration.

[0085] When the processor 61 in the receipt server 6 receives the registration request, the process proceeds to ACT42. As ACT42, the processor 61 determines a receipt ID to be associated with a user so that it does not overlap with a receipt ID already associated with another user. For example, the processor 61 determines a character string determined according to a predetermined algorithm so that a character string can be determined without overlapping as the receipt ID. Alternatively, the processor 61 stores list data representing a list of receipt IDs determined in the past in the auxiliary storage unit 63, and determines a receipt ID not included in the list as a new receipt ID. Alternatively, the processor 61 determines a receipt ID that is not set in field FGA of a data record DRG included in the receipt database DBC as a new receipt ID, and adds a new data record DRG in which the receipt ID determined here is set in field FGA to the receipt database DBC. The processor 61 may determine a receipt ID by any other method.

[0086] As ACT43, the processor 61 notifies the user terminal 1 of the completion of registration. The processor 61 includes the determined receipt ID in the notification data at this time. When the processor 11 in the user terminal 1 receives the notification that registration is complete, it stores the receipt ID included in the notification data in the auxiliary storage unit 13.

[0087] FIG. 20 is a diagram showing a sequence relating to user registration for the point service. In order to start using the point service, the user instructs the user terminal 1, in which the processor 11 is executing information processing based on the client application APA, to perform user registration for the point service. In response to this instruction, the processor 11 in the user terminal 1 proceeds to ACT51. As ACT51, the processor 11 requests the bonus server 7 for registration.

[0088] When the processor 71 in the bonus server 7 receives the registration request, the process proceeds to ACT52. As ACT52, the processor 71 determines a point ID to be associated with the user so that it does not overlap with a point ID already associated with another user. For example, the processor 71 determines a character string determined according to a predetermined algorithm so that a character string can be determined without overlapping as the point ID. Alternatively, the processor 71 stores list data representing a list of point IDs determined in the past in the auxiliary storage unit 73, and determines a receipt ID not included in the list as a new receipt ID. Alternatively, the processor 71 determines a point ID that is not set in the field FHA of a data record DRH included in the point database DBD as a new point ID, and adds a new data record DRH in which the determined point ID is set in the field FHA to the receipt database DBC. The processor 71 may determine a point ID by any other method.

[0089] As ACT 53, the processor 71 notifies the user terminal 1 of the completion of registration. The processor 71 includes the determined point ID in the notification data at this time. When the processor 11 in the user terminal 1 receives the notification of the completion of registration, it stores the point ID included in the notification data in the auxiliary storage unit 13.

[0090] FIG. 21 is a diagram showing a sequence relating to ID association. After completing user registration for the transaction processing service and for at least one of the electronic receipt service and the point service, the user instructs the user terminal 1, in which the processor 11 is executing information processing based on the client application APA, to associate an ID. In response to this instruction, the processor 11 in the user terminal 1 proceeds to ACT61. As ACT61, the processor 11 inputs biometric information. For example, the processor 11 guides the user to input the biometric information. The user follows the guidance and performs an operation to input his / her biometric information into the input unit 15. Then, the processor 11 obtains the biometric information in the same manner as described above.

[0091] In ACT62, the processor 11 requests the agent server 3 to make an association. In the request data here, the processor 11 includes the receipt ID if one is stored in the auxiliary memory unit 13. In the request data here, the processor 11 includes the point ID if one is stored in the auxiliary memory unit 13. In the request data here, the processor 11 includes the biometric information entered in ACT61.

[0092] When the processor 31 in the proxy server 3 receives the association request, the process proceeds to ACT 63 . In ACT63, the processor 31 requests authentication from the authentication server 4. The processor 31 includes in the request data transmitted here the biometric information included in the request data transmitted from the user terminal 1 in ACT62.

[0093] When the processor 41 in the authentication server 4 receives the authentication request, the process proceeds to ACT65. The processor 41 performs a query process as ACT65. That is, the processor 41, for example, checks whether the biometric information included in the request data sent from the proxy server 3 in ACT64 matches any of the biometric information registered in the authentication database DBB. For example, if the matching rate of the characteristics of the biometric information included in the request data sent from the proxy server 3 in ACT64 is equal to or higher than a predetermined rate, the processor 41 determines that the authentication is successful, and if not, determines that the authentication is unsuccessful. Then, for example, if the authentication is successful, the processor 41 selects a data record DRF including a field FFB in which the biometric information with the highest matching rate is set. Then, the processor 41 acquires, for example, the authentication ID set in a field FFA of the corresponding data record DRF.

[0094] In ACT 66, the processor 41 notifies the proxy server 3 of the result of the authentication. The notification data sent by the processor 41 includes result information indicating whether the authentication was successful or not, and if the authentication was successful, includes the authentication ID acquired in ACT 65. Note that in Fig. 21, the sequence after ACT 66 is shown when the authentication is successful, and a description of the case when the authentication is unsuccessful is omitted.

[0095] When the processor 31 in the proxy server 3 receives a result notification indicating that the authentication was successful, the process proceeds to ACT 67 . In ACT67, the processor 31 updates the payment information database DBA. For example, the processor 31 searches the payment information database DBA for a data record DRE in which the authentication ID included in the notification data sent from the authentication server 4 in ACT67 is set in the field FEA. Then, if a receipt ID is included in the request data sent from the user terminal 1 in ACT62, the processor 31 sets the receipt ID in the field FEC of the corresponding data record DRE. Also, if a point ID is included in the request data sent from the user terminal 1 in ACT62, the processor 31 sets the point ID in the field FED of the corresponding data record DRE. As ACT68, the processor 31 notifies the user terminal 1 of the completion of the association.

[0096] Fig. 22 is a diagram showing a sequence when a transaction processing service is used for settlement related to the purchase of goods at a store. Note that the same operations as those in Fig. 14 are given the same reference numerals and their explanation will be omitted. ACT21 to ACT26 are the same as the sequence of the first embodiment shown in Fig. 14. However, in ACT26, if the authentication is successful, the processor 41 acquires the authentication ID set in field FGA of the data record DRF including field FFB in which the biometric information with the highest matching rate is set. After completing ACT26, the processor 41 proceeds to ACT71. Thus, the processor 41 determines the authentication ID as the first identifier associated with the biometric information. In other words, the processor 41 executes information processing based on the authentication application APD, and the computer with the processor 41 as the central part functions as a determination means.

[0097] In ACT 71, the processor 41 notifies the proxy server 3 of the result of the authentication. The notification data sent by the processor 41 includes result information indicating whether the authentication was successful or not, and if the authentication was successful, includes the authentication ID acquired in ACT 26. Note that ACT 71 and subsequent steps in Fig. 22 show the sequence when the authentication is successful, and a description of the case when the authentication is unsuccessful will be omitted.

[0098] When the processor 31 in the proxy server 3 receives a result notification indicating that the authentication was successful, the process proceeds to ACT72. As ACT72, the processor 31 determines the payment server 5 to be used for the payment in response to the payment request made from the sales server 2 as ACT24. For example, the processor 31 searches the payment information database DBA for a data record DRE in which the authentication ID included in the notification data of the result notification is set in the field FEA. Then, the processor 31 determines the payment server 5 corresponding to the payment information set in the field FEB of the corresponding data record DRE as the payment server 5 to be used for the payment.

[0099] The subsequent ACT29, ACT30, and ACT31 are the same as those in the first embodiment. Therefore, the processor 51 pays the price of the transaction using the payment information notified from the agent server 3 when the authentication ID associated with the biometric information is determined. In other words, the processor 51 functions as a payment means by executing information processing based on the payment application APE.

[0100] When the processor 31 in the agent server 3 receives a result notification that the settlement has been completed normally, the process proceeds to ACT 73. As ACT73, the processor 31 performs ID conversion on the authentication ID included in the notification data sent from the authentication server 4. For example, if a receipt ID is set in the field FEC of the data record DRE found in ACT72, the processor 31 sets the receipt ID as the converted ID. Also, for example, if a point ID is set in the field FED of the data record DRE found in ACT72, the processor 31 sets the point ID as the converted ID. In this way, the processor 31 converts the authentication ID as the first identifier into the receipt ID as the second identifier. In other words, the processor 31 executes information processing based on the proxy application APC, and the computer with the processor 31 as the central part functions as a conversion means. The proxy server 3 corresponds to a fifth device equipped with a conversion means.

[0101] In ACT74, the processor 31 notifies the sales server 2 of the result of the payment process. In the notification data here, the processor 31 includes the result information included in the notification data received in ACT31 from the payment server 5 and the ID after ID conversion in ACT73. That is, if the processor 31 obtains a receipt ID as an ID after conversion in ACT73, it includes the receipt ID in the notification data. Also, if the processor 31 obtains a point ID as an ID after conversion in ACT73, it includes the point ID in the notification data. In FIG. 22, the notification data in ACT74 is shown to include a receipt ID and a point ID, but there are cases where the notification data includes only one of the receipt ID and the point ID, or where neither the receipt ID nor the point ID is included.

[0102] The processor 21 of the sales server 2 receives a result notification that the settlement has been completed normally, and if the notification data includes a receipt ID, the processor 21 proceeds to ACT75. In ACT75, the processor 21 requests the receipt server 6 to register an electronic receipt. The processor 21 includes in the request data here the receipt ID and receipt information contained in the notification data received from the agent server 3 in ACT74.

[0103] When the processor 61 in the receipt server 6 receives the registration request, the process proceeds to ACT76. In ACT76, the processor 61 updates the receipt database DBC. For example, the processor 61 searches the receipt database DBC for a data record DRG in which the receipt ID included in the request data received from the sales server 2 in ACT75 is set in field FGA. If the processor 61 finds a corresponding data record DRG, it adds a new field after the last field of the data record DRG. The processor 61 then sets the receipt information included in the request data received from the sales server 2 in ACT75 in this new field. If the processor 61 does not find a corresponding data record DRG, it adds a new data record DRG in which the receipt ID and receipt information included in the request data received from the sales server 2 in ACT75 are set in fields FGA and FGB to the receipt database DBC.

[0104] Thus, the processor 61 uses the receipt database DBC to manage receipt information in association with a receipt identifier associated with the biometric information of the payer. Thus, the processor 61 executes information processing based on the electronic receipt application APF, and the computer with the processor 61 as its central part functions as a management means. In ACT 77, the processor 61 notifies the sales server 2 that the receipt registration has been completed.

[0105] The processor 21 in the sales server 2 receives a result notification that the settlement has been completed normally, and if the notification data includes the point ID, the processor 21 proceeds to ACT78. In ACT78, the processor 21 requests the special server 7 to perform processing related to the point service. The processor 21 includes in the request data here the point ID and point information contained in the notification data received from the proxy server 3 in ACT74.

[0106] When the processor 71 in the bonus server 7 receives the processing request, the process proceeds to ACT 79. In ACT79, the processor 71 updates the point database DBD. For example, the processor 71 searches the point database DBD for a data record DRH in which the point ID included in the request data received from the sales server 2 in ACT78 is set in the field FHA. If the processor 71 finds the corresponding data record DRH, it rewrites the number of owned points represented by the point information set in the field FHB of the data record DRH to a number obtained by adding the number of owned points to the number of granted points represented by the point information included in the request data. As a result, a user identified by the user ID is given a privilege in the form of points according to the transaction. Thus, the processor 71 executes information processing based on the point service application APG, and the computer having the processor 71 as its central part functions as a granting means. The processor 71 as ACT80 notifies the sales server 2 that the point processing has been completed.

[0107] 22 shows an example in which the notification data received from the proxy server 3 in ACT74 includes a receipt ID and a point ID. If a receipt ID is not included, ACT75, ACT76, and ACT77 will not be executed. If a point ID is not included, ACT78, ACT77, and ACT78 will not be executed. The processor 21 may also execute ACT78 before ACT75. Alternatively, the processor 21 may execute ACT78 after ACT75 and before ACT77.

[0108] As described above, the transaction processing system 100 of the second embodiment determines the authentication ID of the settlor through biometric authentication using the settlor's biometric information acquired by the user terminal 1, and if the authentication ID can be determined, settles the price of the transaction, and manages receipt information related to the transaction in association with the receipt ID associated with the authentication ID. Therefore, the authentication of the user of the electronic receipt service can also be completed through the biometric authentication of the settlor, and the user does not need to perform a separate operation to input an ID for the electronic receipt service. This reduces the burden on the settlor when biometric authentication is used to authenticate the settlor of a transaction that uses the electronic receipt service.

[0109] Furthermore, the transaction processing system 100 of the second embodiment manages point information related to a point service in association with a point ID associated with an authentication ID. Therefore, if a user properly inputs biometric information, the user can use the point service in addition to the electronic receipt service, and this reduces the burden on the settlor when biometric authentication is used to authenticate the settlor of a transaction that uses the point service.

[0110] This embodiment can be modified in various ways as follows. The user ID or authentication ID associated with the biometric information may be determined by the agent server 3. Alternatively, the sales server 2 may directly request payment to the payment server 5, and the user ID or authentication ID associated with the biometric information may be determined by the payment server. Alternatively, the receipt server 6 or the special server 7 may have a function as a determination means and may be used as the authentication server 4.

[0111] The function of the conversion means may be provided in the receipt server 6 or the bonus server 7, or in a server other than that included in the transaction processing system 100, and the corresponding server may be substituted for the authentication server 4.

[0112] It is not necessary to execute the sequence shown in Fig. 19. In addition, in the sequence shown in Fig. 21, a receipt ID determined by any other method may be input into the user terminal 1.

[0113] The sequence shown in Fig. 20 does not have to be executed. A separately registered point ID may be input in the user terminal 1. In addition, in the sequence shown in Fig. 21, a point ID determined separately by any method may be input in the user terminal 1.

[0114] The biometric information may be input into a registration device, such as a POS terminal, connected to the sales server 2, using an input device built into or external to the registration device.

[0115] The point service does not have to be provided.

[0116] Each function realized by the processors 11, 21, 31, 41, 51, 61, 71 through information processing can be realized in part or in whole by hardware that executes information processing not based on a program, such as a logic circuit, etc. Also, each of the above functions can be realized by combining the above hardware, such as the logic circuit, with software control.

[0117] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. The invention as originally claimed in the present application is set forth below. [Appendix 1] A means for acquiring biometric information of a person who settles a transaction; a determination means for determining an identifier associated with the biometric information acquired by the acquisition means; a payment means for paying for the transaction using payment information associated with the identifier when the identifier is determined by the determination means; a management means for managing receipt information relating to the transaction settled by the payment means in association with the identifier determined by the determination means; A transaction processing system comprising: [Appendix 2] A means for acquiring biometric information of a person who settles a transaction; a determination means for determining a first identifier associated with the biometric information acquired by the acquisition means; a payment means for paying for the transaction using payment information associated with the first identifier when the determination means is able to determine the first identifier; a conversion means for converting the first identifier determined by the determination means into a second identifier; a management means for managing receipt information relating to the transaction settled by the payment means in association with the second identifier obtained by the conversion means; A transaction processing system comprising: [Appendix 3] A granting means for granting a privilege related to the transaction settled by the payment means to a user associated with the identifier determined by the determination means or the second identifier obtained by the conversion means; 3. The transaction processing system of claim 1 or 2, further comprising: [Appendix 4] The conversion means converts the first identifier determined by the determination means into a second identifier for a receipt and a second identifier for a special offer, The management means uses the second identifier for the receipt obtained by the conversion means, The granting means uses a second identifier for the privilege obtained by the conversion means. 4. A transaction processing system as described in claim 3. [Appendix 5] A first device acquires biometric information of a person who makes a payment to the transaction; determining, at a second device, an identifier associated with the biometric information acquired by the first device; a third device, when the identifier is determined by the second device, settles the price of the transaction using payment information associated with the identifier; and managing, at a fourth device, receipt information relating to the transaction settled by the third device in association with the identifier determined by the second device. Transaction processing method. [Explanation of symbols]

[0118] 1...user terminal, 2...sales server, 3...agent server, 4...authentication server, 5...payment server, 6...receipt server, 7...benefit server, 11,21,31,41,51,61,71...processor, 12,22,32,42,52,62,72...main memory, 13,23,33,43,53,63,73...auxiliary memory unit, 14...touch panel, 15...input unit, 16,24,34,44,54,64,74...communication unit, 17,25,35,45,55,65,75...transmission path, 100...transaction processing system, 200...communication network.

Claims

1. A means for acquiring biometric information of a person who is settling a transaction; a determination means for determining a first identifier associated with the biometric information acquired by the acquisition means; a payment means for paying for the transaction using payment information that is associated with the first identifier and is predetermined for using a payment service when the first identifier is determined by the determination means; A conversion means for converting the first identifier determined by the determination means into a second identifier for a receipt and a second identifier for a special offer; a management means for managing receipt information relating to the transaction settled by the settlement means in association with the second identifier for receipt obtained by the conversion means; a granting means for granting a privilege related to the transaction settled by the settlement means to a user associated with the identifier determined by the determination means or a second identifier for a privilege obtained by the conversion means; A transaction processing system comprising:

2. A first device acquires biometric information of a person who is settling a transaction; determining, at a second device, an identifier associated with the biometric information acquired by the first device; a third device, when the identifier is determined by the second device, paying for the transaction using payment information that is associated with the identifier and that is predetermined for using a payment service; managing, at a fourth device, receipt information relating to the transaction settled by the third device in association with the identifier determined by the second device; granting, at the reward server, a reward for the settled transaction to a user associated with the determined identifier or a second identifier for the reward obtained by the conversion; Transaction processing method.

Images