JP6229016B2 - Transaction apparatus, processing method, and program - Google Patents

Description

  The present invention relates to a transaction apparatus, a processing method, and a program.

  There is a transaction system that collects and distributes sales data indicating the results of transactions among credit card member stores, issuers (card issuers), and acquirers (member store contractors).

JP 2004-86580 A

  However, in the conventional transaction system as described above, there is a problem that processing is complicated when authorization is performed for each transaction (hereinafter referred to as authorization).

  This invention is made | formed in view of such a condition, and provides the transaction apparatus, processing method, and program which can reduce the grade which becomes complicated when performing authorization for every transaction.

In order to solve the above-described problem, one aspect of the present invention is a target member store information storage unit that stores target member store information indicating a member store that is a target of recurring indicating a transaction that is periodically charged, and an issuer. Issuer information storage unit for storing issuer determination information for associating information for identifying an issuer included in authorization data and issuer information for identifying the issuer. an acquisition unit that acquires, and the target member store information the target member store information storage unit stores, the issuer information storage unit based on said issuer determination information stored, re curling identifier for identifying the re curling The issuer to which the authorization data to which is added is determined is determined, and the acquisition unit acquires the authorization data acquired by the acquisition unit. The authorization data for the re-curling identifier is added corresponding to Sure a transaction device, characterized in that it comprises a transfer unit for transferring to the issuer.

Further, one aspect of the present invention is the above transaction apparatus, further comprising an issuer proxy storage unit that stores issuer proxy information indicating identification information of an issuer that performs authorization processing based on the authorization data, and the transfer unit includes: Based on the issuer proxy information stored in the issuer proxy storage unit, the target issuer that performs authorization processing is extracted, and the data for authorization among the data for authorization to which the recurling identifier that has determined the issuer to be transferred is added The authorization data corresponding to the target issuer is transmitted to an agency center acting on behalf of the authorization process.

  Further, according to one aspect of the present invention, in the transaction apparatus, the transfer unit is for an authorization specified in advance by the issuer among the issuers determined to transfer the authorization data to which the recurling identifier is added. The authorization data to which the recurling identifier is added is converted into a data format corresponding to the data transfer system, and the converted authorization data is converted into the issuer via the specified authorization data transfer system. It is characterized by transferring to.

Further, according to one aspect of the present invention, in the transaction apparatus, the transfer unit includes the authorization data acquired by the acquisition unit based on the target member store information stored in the target member store information storage unit . Of these, the recurling identifier is added to the authorization data corresponding to the issuer determined to transfer the authorization data to which the recurling identifier is added.

  Further, according to one aspect of the present invention, in the transaction apparatus, when transferring the authorization data to the issuer, the transfer amount of the authorization data is adjusted based on a predetermined rule, and the authorization data is transferred. A relay unit that relays the information to the issuer.

  Further, according to one aspect of the present invention, a concentrating step for collecting sales data from a member store, and author data for Not on-us where the issuer and acquirer are not the same are created, and the created authorization Sales data for creating sales data in which the authorization result is added to the sales data collected in the converging step, a transfer step for transferring data to each issuer, a receiving step for receiving an authorization result from each issuer The processing method includes a creation step and a distribution step of distributing the sales data to which the authorization result is given to the acquirer.

Another embodiment of the present invention includes a target member store information storage unit that stores target member store information indicating the merchant subject of re curling indicating the transaction to charge regularly met issuer determination information and determines the issuer A transaction apparatus processing method comprising: an issuer information storage unit for storing issuer determination information in which information for specifying an issuer included in authorization data and issuer information for identifying the issuer are associated with each other; an acquisition step of acquiring authorization data, and the target member store information the target member store information storage unit stores, on the basis of said issuer determination information the issuer information storage unit stores, for identifying the re curling The issuer that transfers the authorization data to which the recurling identifier is added is determined, and the asset acquired in the acquisition step is determined. Of the warp data is the authorization data for the re-curling identifier is added corresponding to the issuer processing method characterized by comprising a transfer step of transferring to the issuer.

Another embodiment of the present invention includes a target member store information storage unit that stores target member store information indicating the merchant subject of re curling indicating the transaction to charge regularly met issuer determination information and determines the issuer The authorization data is stored in the computer of the transaction apparatus comprising the issuer information storage unit for storing the issuer determination information in which the information for identifying the issuer included in the authorization data is associated with the issuer information for identifying the issuer. an acquisition step of acquiring, and the target member store information the target member store information storage unit stores, the issuer information storage unit based on said issuer determination information stored, re curling identifier for identifying the re curling The issuer to which the authorization data to which is added is transferred is determined, and the authorization acquired in the acquisition step is determined. Of Li for data, a program for causing the authorization data for the re-curling identifier is added corresponding to the issuer run a transfer step of transferring to the issuer.

  As described above, according to the present invention, it is possible to provide a transaction system that can reduce the degree of complicated processing when authorization is performed for each transaction.

It is a schematic diagram which shows the outline | summary of the transaction system in embodiment of this invention. It is a schematic diagram which shows an example of the data flow in this embodiment. It is a schematic diagram which shows the 1st modification of the data flow in this embodiment. It is a schematic diagram which shows the 2nd modification of the data flow in this embodiment. It is a schematic diagram which shows the 3rd modification of the data flow in this embodiment. It is a schematic diagram which shows the 4th modification of the data flow in this embodiment. It is a schematic diagram which shows the 5th modification of the data flow in this embodiment. It is a functional block diagram which shows an example of the transaction system by 1st Embodiment. It is a figure which shows the example of data of the acquirer information storage part in 1st Embodiment. It is a figure which shows the example of data of the issuer BIN information storage part in 1st Embodiment. It is a sequence diagram which shows an example of operation | movement of the transaction system by 1st Embodiment. It is a functional block diagram which shows an example of the transaction system by 2nd Embodiment. It is a figure which shows the example of data of the object member store information storage part in 2nd Embodiment. It is a figure which shows the example of data of the issuer information storage part in 2nd Embodiment. It is a figure which shows the example of data of the issuer proxy storage part in 2nd Embodiment. It is a 1st sequence diagram which shows an example of operation | movement of the transaction system by 2nd Embodiment. It is a 2nd sequence diagram which shows an example of operation | movement of the transaction system by 2nd Embodiment. It is a 3rd sequence diagram which shows an example of operation | movement of the transaction system by 2nd Embodiment. It is a functional block diagram which shows an example of the transaction system by 3rd Embodiment. It is a sequence diagram which shows an example of operation | movement of the transaction system by 3rd Embodiment. It is a functional block diagram which shows an example of the transaction system by 4th Embodiment.

<Embodiment>
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a schematic diagram showing an overview of a transaction system 1 according to an embodiment of the present invention. FIG. 2 is a schematic diagram illustrating an example of a data flow in the present embodiment. The outline of the transaction system 1 is as follows. (1) Collect sales data from the member store 2 at the first data center 5. (2) Create not-on-us authorization data in the first data center 5 and transmit the file to each issuer 4. Although illustration is omitted, the first data center 5 transmits a file to the acquirer 3 when the target issuer 4 cannot be identified. (3) The authorization result from each issuer 4 is received by the first data center 5. (4) The first data center 5 creates sales data in which the authorization result (approval number) is added to the collected sales data. (5) Distribute the sales data with the authorization result from the first data center 5 to the acquirer 3.

[Modification 1]
FIG. 3 is a schematic diagram showing a first modification of the data flow in the present embodiment. The outline of the transaction system 1a in this modification is as follows. (1) A recurring flag is set from the member store 2 to the second data center 6 and data is transmitted. (2) Receive and register an application form regarding the behavior when a recurring flag is transmitted from the member store 2 from each card company. (3) The card company that may relay the recurring flag is relayed as it is. (4) The card company that should not relay the recurring flag is edited and relayed at the second data center 6. (5) When the card company has a trouble transaction, a proxy response at the time of a recurring transaction is also possible. (6) The member store 2 transmits the sales for the recurring transaction together with the transaction to the first data center 5a. (7) The first data center 5a transmits to each acquirer 3 (in the present modification, a card company) as a normal sales transaction.

[Modification 2]
FIG. 4 is a schematic diagram showing a second modification of the data flow in the present embodiment. The outline of the transaction system 1b in this modification is as follows. (1) Collect sales data from the member store 2 at the first data center 5b. (2) Create data for Not-on-us for the first data center 5b and link to the second data center 6a. (3) Authorize relay from the second data center 6a to each issuer 4. Here, the number of cases set for each issuer direct and issuer 4 is relayed. (4) Create sales data with the authorization result returned from each issuer 4. (5) Distribute the sales data with the authorization result to the acquirer 3.

[Modification 3]
FIG. 5 is a schematic diagram showing a third modification of the data flow in the present embodiment. The outline of the transaction system 1c in the present modification is as follows. (1) Collect sales instruction data from the member store 2 at the third data center 8. (2) The third data center 8 creates authorization data for Not on-us and links to the data center (for example, the second data center 6a). (3) Authorize relay from the data center to each issuer 4. Here, the number of cases set for each issuer direct and issuer 4 is relayed. (4) Create sales data with the authorization result returned from each issuer 4. (5) Distribute the sales data with the authorization result to the acquirer 3.

[Modification 4]
FIG. 6 is a schematic diagram showing a fourth modification of the data flow in the present embodiment. The outline of the transaction system 1d in this modification is as follows. (1) Collect sales data from the member store 2 at the first data center 5b. (2) Create data for Not-on-us for the first data center 5b and link to the second data center 6a. (3) Authorize relay from the second data center 6a to each issuer 4. Here, the number of cases set for each issuer direct and issuer 4 is relayed. (3) -1 In the first place, the issuer 4 that cannot receive the recurring transaction message registers negative data in the fourth data center 9 in advance. (3) -2 When the transaction for the issuer 4 registered in advance in the fourth data center 9 is relayed from the member store 2, it becomes the issuer 4 and performs a negative check. (4) Create sales data with the authorization result returned from the issuer 4. (5) Distribute the sales data with the authorization result to the acquirer 3.

[Modification 5]
FIG. 7 is a schematic diagram showing a fifth modification of the data flow in the present embodiment. The outline of the transaction system 1e in the present modification is as follows. (1) A recurring flag is set from the member store 2 to the second data center 6 and data is transmitted. (2) BIN information is registered in advance from the acquirer 3. (3) When the destination of the message is the specific acquirer 3, the BIN determination is performed. (4) When it is the specific issuer 4 registered in the BIN determination, it is transmitted online to the issuer 4. Or substitute authorization response. If not registered, it is relayed to the acquirer 3. (5) The transaction result processed in the second data center 6 is returned to the card company. (6) The member store 2 transmits the sales for the recurring transaction together with the transaction to the first data center 5a. (7) The first data center 5a transmits it to each acquirer 3 as a normal sales transaction.

As described above, the transaction system according to the present embodiment and each modification has a mechanism for obtaining an authorization for each transaction. Therefore, according to the transaction system of the present embodiment and each modified example, it is possible to reduce the degree of complicated processing when performing authorization for each transaction.
4 and 5 described above, the system S1 indicates a part or all of the system in the embodiment shown in FIG. 2, and the system S2 is the system in the embodiment shown in FIG. 3 ([Modification 1]). A part or all of is shown. Further, the system S3 indicates a part that is a characteristic of the system in the embodiment ([Modification 2]) shown in FIG. The part which becomes is shown.

Next, the embodiment described above will be described in detail with reference to the drawings.
[First Embodiment]
Here, the embodiment described with reference to FIG. 2 will be described in detail as a first embodiment.
FIG. 8 is a functional block diagram showing an example of the transaction system 1 according to the first embodiment.
As shown in FIG. 8, the transaction system 1 includes a member store 2, an acquirer 3, an issuer 4, and a first data center 5.

  The member store 2 is a member store supplier that conducts transactions using a credit card. Here, the member store 2 indicates a computer device owned by the member store. The member store 2 transmits, for example, sales data including recurring indicating a transaction to be charged periodically, such as a public bill or a provider connection fee, to the first data center 5. Here, the sales data includes, for example, information for identifying a member store such as a member store number, a credit card member number, a sales date, a sales amount, and an approval number. The approval number is included in the authorization result, and the member store 2 transmits all “0” or all space to the approval number in the sales data by recurring, for example, and sends it to the first data center 5. To do.

The acquirer 3 is a member store contract company that makes a member store contract with the member store 2 for settlement by credit card. Here, the acquirer 3 is a computer device owned by a member store contract company.
Issuer 4 is a card issuing company that issues credit cards. Here, the issuer 4 indicates a computer device possessed by the card issuing company. In this embodiment, when the issuer 4 executes the authorization process, both the online process for executing the authorization process for each transaction and the batch process for performing the authorization process for a plurality of transactions by the authorization data file described later. Is executable. Here, the authorization process is, for example, an approval process for determining whether or not a transaction with a credit card is permitted. The issuer 4 transmits an authorization result including an approval number permitting the processing. When the issuer 4 performs batch processing using the authorization data file, the issuer 4 sends an authorization result file in which authorization results for a plurality of transactions are filed to the first data center 5 that is the transmission source of the authorization data file. .

  The first data center 5 (an example of a transaction apparatus) is a data center of a data transmission system such as a CDS (Credit Data Transfer System). The first data center 5 is constituted by, for example, one or a plurality of computer devices. The first data center 5 includes a sales data concentrator 51, an acquirer information storage unit 52, an issuer BIN information storage unit 53, an authorization data transmission unit 54, an authorization result reception unit 55, and sales data creation. A unit 56 and a sales data distribution unit 57 are provided.

The sales data concentrator 51 (an example of a concentrator) collects sales data from the member store 2 at the first data center 5.
The acquirer information storage unit 52 stores identification information of the acquirer 3 for each member store 2. That is, as shown in FIG. 9, the acquirer information storage unit 52 stores “member store” and “acquirer information” in association with each other. Here, “member store” is, for example, identification information for identifying the member store 2, and “acquirer information” is identification information for identifying the acquirer 3.

FIG. 9 is a diagram illustrating a data example of the acquirer information storage unit 52 in the present embodiment.
In the example illustrated in FIG. 9, the acquirer information storage unit 52 stores, for example, “A member store” of “member store” and “11111” of “acquirer information” in association with each other. That is, the example shown in FIG. 9 indicates that the acquirer 3 that contracts with the member store 2 that is the “A member store” is “11111”.

  Returning to the description of FIG. 8, the issuer BIN information storage unit 53 stores the BIN information of the issuer 4. For example, as shown in FIG. 10, the issuer BIN information storage unit 53 stores “NO.”, “BIN information”, and “Issuer information” in association with each other. Here, “BIN information” is information for specifying a credit card issuing company, and is defined as information having a predetermined range in the example shown in FIG. “Issuer information” is identification information for identifying the issuer 4.

FIG. 10 is a diagram illustrating a data example of the issuer BIN information storage unit 53 in the present embodiment.
In the example illustrated in FIG. 10, the issuer BIN information storage unit 53 stores, for example, “11111” of “Issuer information” in association with “100000XX to 19999XX” of “BIN information”. That is, it is indicated that “Issuer Information” corresponding to “BIN Information” corresponding to “100000XX to 19999XX” is “11111”.

  Returning to the description of FIG. 8 again, the authorization data transmission unit 54 (an example of the transfer unit), in the first data center 5, out of the sales data collected by the sales data concentrating unit 51, is for Not on-us. The authorization data is created, and the created authorization data is transferred to each issuer 4. Here, “Not on-us” indicates a transaction when the issuer 4 and the acquirer 3 are not the same. That is, the authorization data transmission unit 54 extracts sales data for transactions in which the issuer 4 and the acquirer 3 are not identical, and creates authorization data for the extracted sales data. Then, the authorization data transmission unit 54 transfers the created not-on-us authorization data to each issuer 4 as a file. The authorization data transmission unit 54 transfers the authorization data as a file to the acquirer 3 when the target issuer 4 cannot be identified.

For example, the authorization data transmission unit 54 uses the authorization information for the not on-us based on the identification information of the acquirer 3 acquired from the acquirer information storage unit 52 and the issuer information corresponding to the membership number included in the sales data. Create data. That is, the authorization data transmission unit 54 extracts, as Not on-us, sales data in which the identification information of the acquirer 3 does not match the issuer information.
For example, when the sales data is for “A member store”, in the example shown in FIG. 9, the “acquirer information” in which “member store” corresponds to “A member store” is “11111”. . Further, when the BIN information included in the membership number of the sales data is “15000XX”, in the example shown in FIG. 10, “Issuer information” corresponding to “15000XX” of “BIN information” is “11111”. . In this case, since “11111” of “acquirer information” matches “11111” of “issuer information”, the authorization data transmission unit 54 determines that the sales data is not Not on-us.

  Further, when the BIN information included in the membership number of the sales data is “25000XX”, in the example shown in FIG. 10, “Issuer information” corresponding to “25000XX” of “BIN information” is “22222”. . In this case, since “11111” of “acquirer information” does not match “22222” of “issuer information”, the authorization data transmission unit 54 determines that the sales data is Not on-us.

Thus, the authorization data transmission unit 54 extracts sales data for Not on-us and creates authorization data.
Further, the authorization data transmission unit 54 makes a predetermined transaction portion of the created authorization data into an authorization data file for each issuer 4 and directly transfers it to each issuer 4 without passing through the acquirer 3. The authorization data transmission unit 54 transmits the authorization data as a file to the acquirer 3 when the target issuer 4 cannot be identified.

  The authorization result receiving unit 55 (an example of a receiving unit) receives the authorization result from each issuer 4 at the first data center 5. That is, the authorization result receiving unit 55 receives the authorization result including the approval number from each issuer 4. Note that the authorization result file is received from each issuer 4 for the authorization data file sent by the authorization data transmission unit 54. The authorization result may include information indicating the date on which the authorization process was executed.

  The sales data creating unit 56 creates sales data in which the authorization result is added to the sales data collected by the sales data collecting unit 51 in the first data center 5. For example, the sales data creation unit 56 substitutes the approval number included in the authorization result received by the authorization result receiving unit 55 for the approval number of the sales data, and creates sales data to which the authorization result is given. Note that the sales data creation unit 56 may change the sales date of the sales data to the date (authorization execution date) when the authorization process was executed.

The sales data distribution unit 57 (an example of a distribution unit) distributes sales data to which the authorization result is given (sales data to which the authorization result has been assigned) to the acquirer 3 at the first data center 5. That is, the sales data distribution unit 57 distributes the sales data with the authorization result created by the sales data creation unit 56 to the target acquirer 3.
The sales data distribution unit 57 distributes the authorization result received by the authorization result receiving unit 55 to the member store 2.

Next, with reference to FIG. 11, operation | movement of the transaction system 1 by this embodiment is demonstrated.
FIG. 11 may be a sequence diagram illustrating an example of the operation of the transaction system 1 according to the present embodiment.
In this figure, first, the member store 2 transmits sales data to the first data center 5 (step S101). Here, the sales data is sales data by recurring. The sales data collecting unit 51 of the first data center 5 collects sales data from the member store 2.

  Next, the first data center 5 creates authorization data (step S102). That is, the authorization data transmission unit 54 of the first data center 5 performs the Notation based on the identification information of the acquirer 3 acquired from the acquirer information storage unit 52 and the issuer information corresponding to the membership number included in the sales data. Create on-us authorization data. Further, the authorization data transmission unit 54 creates an authorization data file (authorization data file).

  Next, the authorization data transmission unit 54 transfers the created authorization data file to the issuer 4 (step S103). The authorization data transmission unit 54 transfers the authorization data as a file to the acquirer 3 when the target issuer 4 cannot be identified.

  Next, the issuer 4 performs an authorization process (step S104). That is, the issuer 4 performs an authorization process for each transaction by a batch process using the acquired authorization data file.

  Next, the issuer 4 transmits the authorization result file to the first data center 5 (step S105). Then, the authorization result receiving unit 55 of the first data center 5 receives the authorization result file.

  Next, the sales data creating unit 56 of the first data center 5 creates sales data in which the authorization result is added to the sales data collected by the sales data collecting unit 51 (step S106). For example, the sales data creation unit 56 substitutes the approval number and the authorization execution date included in the authorization result received by the authorization result receiving unit 55 for the authorization number and the sales date of the sales data, and obtains the authorization result. Create the assigned sales data.

Next, the sales data distribution unit 57 of the first data center 5 distributes the sales data with the authorization result to the acquirer 3 (step S107). The sales data distribution unit 57 distributes the sales data with an authorization result as a file to the acquirer 3, for example.
Sales data distribution part 57 transmits an authorization result to member store 2 (Step S108).

  As described above, the transaction system 1 (or transaction apparatus) according to the present embodiment includes the sales data collecting unit 51 (collecting unit), the authorization data transmitting unit 54 (transfer unit), and the authorization result receiving unit 55 ( Receiving section), sales data creation section 56, and sales data distribution section 57 (distribution section). The sales data concentrator 51 collects sales data from the member store 2 at the first data center 5. The authorization data transmission unit 54 creates authorization data for Not on-us in the first data center 5 where the issuer 4 and the acquirer 3 are not the same. The authorization data transmission unit 54 transfers the created authorization data to each issuer 4. The authorization result receiving unit 55 receives the authorization result from each issuer 4 at the first data center 5. The sales data creating unit 56 creates sales data in which the authorization result is added to the sales data collected by the sales data collecting unit 51 in the first data center 5. Then, the sales data distribution unit 57 (distribution unit) distributes the sales data to which the authorization result is given to the acquirer 3 in the first data center 5.

  As a result, the transaction system 1 (or transaction apparatus) according to the present embodiment creates authorization data from the sales data at the first data center 5, and creates the authorization data created without using the acquirer 3. Since it transfers to the issuer 4, the process by the member store 2 and the acquirer 3 regarding the authorization process can be reduced. That is, the transaction system 1 according to the present embodiment can reduce processing by the member store 2 and the acquirer 3 even when a large amount of transactions due to recurring occurs. Therefore, the transaction system 1 according to the present embodiment can reduce the extent to which the processing becomes complicated when authorization is performed for each transaction.

Further, in the present embodiment, the authorization data transmission unit 54 acquires the identification information of the acquirer 3 acquired from the acquirer information storage unit 52 (storage unit) that stores the identification information of the acquirer 3 for each member store 2, the sales Based on the issuer information corresponding to the membership number included in the data, author data for Not on-us is created. The authorization data transmission unit 54 transfers the created authorization data as a file to each issuer 4. The authorization result receiving unit 55 receives the authorization result from each issuer 4 as a file.
Thereby, since the authorization data and the authorization result are transferred by the file, the transaction system 1 according to the present embodiment can reduce the load on the network between the first data center 5 and each issuer 4. Also, since the authorization data is made into a file and a plurality of transactions are authorized together, batch processing of the issuer 4 becomes possible, so that the transaction system 1 according to the present embodiment makes the processing of the issuer 4 complicated. The degree can be reduced.

The processing method according to the present embodiment includes a concentration step, a transfer step, a reception step, a sales data creation step, and a distribution step. In the collecting step, sales data from the member store 2 is collected at the first data center 5. In the transfer step, the first data center 5 creates not-on-us authorization data for which the issuer 4 and the acquirer 3 are not the same, and the created authorization data is transferred to each issuer 4. In the receiving step, the authorization result from each issuer 4 is received by the first data center 5. In the sales data creation step, sales data in which the authorization result is added to the sales data collected in the concentration step in the first data center 5 is created. In the distribution step, the first data center 5 distributes the sales data with the authorization result to the acquirer 3.
Thereby, the processing method by this embodiment can reduce the grade which becomes complicated when performing authorization for every transaction similarly to the transaction system 1 by this embodiment mentioned above.

Next, a transaction system according to the second embodiment will be described with reference to the drawings.
[Second Embodiment]
Here, the above-described [Modification 1] described with reference to FIG. 3 will be described in detail as a second embodiment.

FIG. 12 is a functional block diagram showing an example of a transaction system 1a according to the second embodiment.
As shown in FIG. 12, the transaction system 1a includes a member store 2, an issuer 4 (acquirer 3), a first data center 5a, a second data center 6, a proxy center 7, and a dedicated server 10. I have.
In the first embodiment described above, the first data center 5 creates the authorization data from the sales data and transfers the created authorization data to the issuer 4 without passing through the acquirer 3. In the embodiment, the second data center 6 relays the authorization data to the issuer 4 without going through the acquirer 3.

The member store 2 according to the present embodiment generates Not-on-us authorization data from the sales data, and transmits the generated authorization data to the second data center 6. The member store 2 generates authorization data with a recurling flag (hereinafter referred to as R flag) that is an identifier for identifying whether or not the transaction is a recurring transaction.
Further, the member store 2 gives an authorization result to the sales data and transmits it to the first data center 5a.
The first data center 5 a receives the sales data with the authorization result assigned from the member store 2 and transfers the sales data with the authorization result assigned to the acquirer 3.

The second data center 6 (an example of a transaction apparatus) is a data center of an integrated card payment system (authorization transfer system) such as CAFIS (Credit And Finance Information System). The second data center 6 is constituted by, for example, one or a plurality of computer devices. Further, the second data center 6 determines whether or not to relay the authorization data to which the R flag is added according to the issuer 4, and to the issuer 4 corresponding to the R flag, The authorization data with the flag added is relayed.
Further, the second data center 6 relays the authorization data without the R flag added to the issuer 4 that does not support the R flag. Further, the second data center 6 transmits the authorization data to the proxy center 7 to the issuer 4 (target issuer) corresponding to the proxy processing proxy.

Further, the second data center 6 converts the authorization data into the format for the authorization transfer system TS1 when the issuer 4 desires the authorization data transfer system TS1 other than CAFIS, for example. To do. The second data center 6 transfers the converted authorization data to the issuer 4 by the authorization transfer system TS1 via the dedicated server 10 of the authorization transfer system TS1.
Further, the second data center 6 receives the authorization result and transmits the received authorization result to the member store 2.
The second data center 6 includes an authorization data acquisition unit 61, a target member store information storage unit 62, an issuer information storage unit 63, an issuer proxy storage unit 64, and an authorization relay unit 65.

  The authorization data acquisition unit 61 (an example of an acquisition unit) acquires authorization data from the member store 2 at the second data center 6. Here, as an example, the authorization data acquisition unit 61 acquires authorization data with an R flag from the member store 2.

  The target member store information storage unit 62 stores target member store information indicating the member store 2 to be recurred. For example, as shown in FIG. 13, the target member store information storage unit 62 stores “target member store”, “member store identification information”, and “relay destination information when issuer determination is impossible” in association with each other. Here, “target member store” indicates a member store to be recurred, and “member store identification information” indicates identification information for identifying the target member store. The “relay destination information when issuer determination is impossible” is the issuer 4 (for example, contracting with a target member store if the transfer destination issuer 4 cannot be determined by the issuer determination process described later). Identification information of the acquirer 3).

FIG. 13 is a diagram illustrating a data example of the target member store information storage unit 62 in the present embodiment.
In the example illustrated in FIG. 13, the target member store information storage unit 62 includes, for example, “A member store” of “target member store”, “XXXX” of “member store identification information”, and “relay when issuer determination is not possible”. "11111" of "Previous information" is stored in association with each other. That is, the example shown in FIG. 13 indicates that “member store identification information” of “A member store” to be recurled is “XXXX”, and the acquirer 3 to be contracted is “11111”.

  Returning to the description of FIG. 12, the issuer information storage unit 63 stores issuer determination information for determining the issuer 4. For example, as illustrated in FIG. 14, the issuer information storage unit 63 stores “NO.”, “BIN information”, and “issuer information” in association with each other as issuer determination information. Here, “BIN information” is information for specifying a credit card issuing company, and is defined as information having a predetermined range in the example shown in FIG. “Issuer information” is identification information for identifying the issuer 4 to which the R flag is added. The issuer determination information is stored in advance in the issuer information storage unit 63 by an application from the acquirer 3.

FIG. 14 is a diagram illustrating a data example of the issuer information storage unit 63 in the present embodiment.
In the example illustrated in FIG. 14, the issuer information storage unit 63 stores, for example, “11111” of “Issuer information” in association with “100000XX to 19999XX” of “BIN information”. That is, it is indicated that “Issuer Information” corresponding to “BIN Information” corresponding to “100000XX to 19999XX” is “11111”.

  Returning to the description of FIG. 12 again, the issuer proxy storage unit 64 stores issuer proxy information indicating identification information of the issuer 4 performing proxy processing. For example, as shown in FIG. 15, the issuer proxy storage unit 64 stores “NO.” And “Issuer information” in association with each other. Here, the “issuer information” is identification information of a target issuer that performs authorization processing. In other words, the issuer proxy storage unit 64 stores a list of identification information of the target issuer that performs authorization processing.

FIG. 15 is a diagram illustrating a data example of the issuer proxy storage unit 64 in the present embodiment.
In the example illustrated in FIG. 15, the issuer proxy storage unit 64 indicates that, for example, the list of “Issuer information” of the target issuer that performs the authorization process is “11111”, “22222”,. .

  Returning to the description of FIG. 12 again, the authorization relay unit 65 (an example of a transfer unit), in the second data center 6, the target member store information stored in the target member store information storage unit 62 and the issuer information storage unit 63. The issuer 4 to which the authorization data to which the R flag (recurring identifier) is added is transferred is determined based on the issuer determination information stored in FIG. The authorization relay unit 65 forwards the authorization data to which the R flag corresponding to the determined issuer 4 is added to the issuer 4 out of the authorization data acquired by the authorization data acquisition unit 61.

  For example, the authorization relay unit 65 determines whether or not the member store identification information included in the authorization data is registered as a target member store in the target member store information storage unit 62. The authorization relay unit 65 executes the next issuer determination process when it is registered as a target member store. Further, when the authorization relay unit 65 is not registered as a target member store, the authorization relay unit 65 relays the authorization data as it is without editing it.

  Further, the authorization relay unit 65 changes the “BIN information” in the issuer determination process according to whether or not the BIN information included in the authorization data matches the “BIN information” stored in the issuer information storage unit 63. The corresponding “issuer information” is determined. When there is the corresponding “BIN information”, the authorization relay unit 65 executes a proxy determination process for the issuer 4 indicated by the corresponding “issuer information”. In addition, when there is no corresponding “BIN information”, the authorization relay unit 65 searches the target member store information storage unit 62 again, and the “relay destination when issuer determination is impossible” corresponding to the corresponding member store identification information. The authorization data is relayed to the issuer 4 (acquirer 3) corresponding to “information”.

Further, the authorization relay unit 65 determines whether or not the “issuer information” determined in the issuer determination process exists in the issuer storage unit 64 in the proxy determination process. The authorization relay unit 65 relays the authorization data to which the R flag is added to the proxy center 7 when the corresponding “issuer information” exists in the issuer proxy storage unit 64. That is, the authorization relay unit 65 extracts the target issuer that performs the authorization process based on the issuer proxy information stored in the issuer proxy storage unit 64, and sends the authorization data corresponding to the target issuer to the proxy center 7. Send.
Further, the authorization relay unit 65 sets the R flag so as to relay directly to the issuer 4 determined in the proxy determination process when the corresponding “issuer information” does not exist in the issuer proxy storage unit 64 in the proxy determination process. The added authorization data is edited and relayed to the issuer 4.

In addition, the authorization relay unit 65, when the issuer 4 of the transmission destination (destination) desires to transfer the authorization data by another authorization transfer system TS1, the authorization relay unit 65 puts the authorization data in the format for the authorization transfer system TS1. Convert. The authorization relay unit 65 transfers the converted authorization data to the issuer 4 via the dedicated server 10 by the authorization transfer system TS1. Note that the authorization relay unit 65 determines whether or not it is desired to transfer the authorization data by another authorization transfer system TS1, and requests the transfer by the authorization transfer system TS1 stored in advance in a storage unit (not shown). The determination is made based on the list of issuers 4.
As described above, the authorization relay unit 65 uses a data format corresponding to the authorization transfer system TS1 for the authorization data designated in advance by the issuer 4 out of the issuers 4 determined to transfer the authorization data to which the R flag is added. The authorization data to which the R flag is added is converted. The authorization relay unit 65 transfers the converted authorization data to the issuer 4 via the designated authorization data authorization transfer system TS1.

The proxy center 7 performs authorization processing. The proxy center 7 performs an authorization process based on the authorization data relayed from the second data center 6 and transmits the authorization result to the second data center 6. In addition, the proxy center 7 transmits the authorization result that has been subjected to authorization processing to the issuer 4.
Each issuer 4 executes an authorization process based on the authorization data relayed from the second data center 6 and transmits the authorization result to the second data center 6.

Next, with reference to FIGS. 16-18, operation | movement of the transaction system 1a by this embodiment is demonstrated.
FIG. 16 is a first sequence diagram illustrating an example of the operation of the transaction system 1a according to the present embodiment. The example shown in this figure shows an example in which the second data center 6 relays the authorization data corresponding to the authorization data to which the R flag is added to the authorization data.

In FIG. 16, first, the member store 2 transmits authorization data with an R flag to the second data center 6 (step S201). In response to this, the authorization data acquisition unit 61 of the second data center 6 acquires authorization data from the member store 2 at the second data center 6.
Next, the authorization relay unit 65 of the second data center 6 acquires the acquired authorization data, the target member store information stored in the target member store information storage unit 62, and the issuer determination information stored in the issuer information storage unit 63. Based on the above, the issuer 4 that transfers the authorization data with the R flag is determined (step S202).

Next, the authorization relay unit 65 transmits the authorization data with the R flag to the issuer 4 determined as the issuer (step S203).
Next, the issuer 4 performs an authorization process (step S204). That is, the issuer 4 executes the authorization process using the acquired authorization data with R flag. In the case of a transaction by recurring, generally, an authorization process different from the normal one is performed in the authorization process, without determining the expiration date of the credit card. The issuer 4 determines whether or not to determine the expiration date of the credit card in the authorization process based on the R flag.

Next, the issuer 4 transmits the authorization result to the second data center 6 (step S205), and the second data center 6 relays the received authorization result to the member store 2 (step S206).
Next, the member store 2 creates sales data in which the authorization result is added to the sales data (step S207). Then, the member store 2 transmits the sales data with the authorization result to the first data center 5a (step S208), and the first data center 5a distributes the sales data with the authorization result to the acquirer 3 (step S209).

  FIG. 17 is a second sequence diagram showing an example of the operation of the transaction system 1a according to the present embodiment. The example shown in this figure shows an example in which the second data center 6 relays the authorization data to which the R flag is added to the proxy center 7.

In FIG. 17, the member store 2 first transmits authorization data with an R flag to the second data center 6 (step S301). In response to this, the authorization data acquisition unit 61 of the second data center 6 acquires authorization data from the member store 2 at the second data center 6.
Next, the authorization relay unit 65 of the second data center 6 executes issuer determination and proxy determination processing (step S302). That is, the authorization relay unit 65 adds an R flag based on the acquired authorization data, the target member store information stored in the target member store information storage unit 62, and the issuer determination information stored in the issuer information storage unit 63. The issuer 4 to which the authorization data is transferred is determined. In the example shown in this figure, the authorization relay unit 65 further performs proxy determination processing based on the issuer proxy information stored in the issuer proxy storage unit 64 and determines to relay to the proxy center 7.

Next, the authorization relay unit 65 transmits authorization data with an R flag to the proxy center 7 (step S303).
Next, the agency center 7 performs authorization processing (step S304), transmits the authorization result to the second data center 6 (step S305), and the second data center 6 sends the received authorization result to the member store 2. Relay (step S306).

  Since the subsequent processing from step S307 to step S309 is the same as the processing from step S207 to step S209 in FIG. 16, the description thereof is omitted here.

  FIG. 18 is a third sequence diagram illustrating an example of the operation of the transaction system 1a according to the present embodiment. The example shown in this figure shows an example in which the second data center 6 relays the authorization data to the issuer 4 via the authorization data authorization transfer system TS1.

In FIG. 18, first, the member store 2 transmits authorization data with an R flag to the second data center 6 (step S401). In response to this, the authorization data acquisition unit 61 of the second data center 6 acquires authorization data from the member store 2 at the second data center 6.
Next, the authorization relay unit 65 of the second data center 6 executes issuer determination and conversion processing (step S402). That is, the authorization relay unit 65 adds an R flag based on the acquired authorization data, the target member store information stored in the target member store information storage unit 62, and the issuer determination information stored in the issuer information storage unit 63. The issuer 4 to which the authorization data is transferred is determined. The authorization relay unit 65 further determines whether or not the issuer 4 is designated for transfer by the authorization transfer system TS1. In the example shown in this figure, the authorization relay unit 65 shows a case where the issuer 4 is designated for transfer by the authorization transfer system TS1. Therefore, the authorization relay unit 65 converts the authorization data into a format for the authorization transfer system TS1.

Next, the authorization relay unit 65 transmits the converted authorization data to the dedicated server 10 (step S403).
Next, the dedicated server 10 transmits the authorization data to the issuer 4 via the authorization transfer system TS1 (step S404).

  Next, the issuer 4 performs an authorization process (step S405), and transmits an authorization result to the dedicated server 10 via the authorization transfer system TS1 (step S406). Then, the dedicated server 10 relays the authorization result to the second data center 6 (step S407), and the second data center 6 relays the received authorization result to the member store 2 (step S408).

  The subsequent processing from step S409 to step S411 is the same as the processing from step S207 to step S209 shown in FIG. 16, and therefore the description thereof is omitted here.

In the example of the present embodiment described above, the example in which the member store 2 adds the R flag to the authorization data and transmits it to the second data center 6 has been described. However, the authorization relay unit 65 of the second data center 6 has been described. May add an R flag. In this case, the authorization relay unit 65 adds the R flag to the authorization data and relays it to the issuer 4 determined to transfer the authorization data to which the R flag is added. Further, although the example in which the member store 2 generates Not-on-us authorization data from the sales data has been described, the second data center 6 may generate Not-on-us authorization data.
Further, in the transaction system 1a of the present embodiment, the case where the member store 2 adds the R flag and the case where the second data center 6 adds the R flag are mixed according to the member store 2. Good.

  As described above, the transaction system 1a (or transaction apparatus) according to the present embodiment includes the authorization data acquisition unit 61 (acquisition unit), the target member store information storage unit 62, the issuer information storage unit 63, and the authorization relay unit. 65 (transfer unit). The target member store information storage unit 62 stores target member store information indicating the target member store 2. The issuer information storage unit 63 stores issuer determination information for determining the issuer 4. The authorization data acquisition unit 61 acquires authorization data from the member store 2 at the second data center 6. The authorization relay unit 65 periodically charges the second data center 6 based on the target member store information stored in the target member store information storage unit 62 and the issuer determination information stored in the issuer information storage unit 63. The issuer 4 to which the authorization data to which the R flag identifying the recurring indicating the transaction to be added is added is determined. The authorization relay unit 65 forwards the authorization data to which the R flag corresponding to the determined issuer 4 is added to the issuer 4 out of the authorization data acquired by the authorization data acquisition unit 61.

  As a result, the transaction system 1a (or transaction apparatus) according to the present embodiment relays the authorization data to which the R flag is added to the corresponding issuer 4, so that the issuer 4 performs recurring based on the R flag. The authorization processing for the transaction can be appropriately executed. Therefore, the transaction system 1a according to the present embodiment can reduce the processing load due to the authorization process for the recurring transaction of the issuer 4. Further, since the second data center 6 directly relays the authorization data and the authorization result with each issuer 4 without going through the acquirer 3, processing by the acquirer 3 can be reduced. Therefore, the transaction system 1a according to the present embodiment can reduce the extent to which the processing becomes complicated when authorization is performed for each transaction.

The transaction system 1a according to the present embodiment includes an issuer proxy storage unit 64 that stores issuer proxy information indicating identification information of an issuer that performs authorization processing based on the authorization data. The authorization relay unit 65 extracts a target issuer that performs authorization processing based on the issuer proxy information stored in the issuer proxy storage unit 64. The authorization relay unit 65 transmits the authorization data corresponding to the target issuer among the authorization data acquired by the authorization data acquisition unit 61 to the proxy center 7 acting as an authorization process.
Thereby, the transaction system 1a by this embodiment can further reduce the processing load by the authorization process of the issuer 4. FIG.

In this embodiment, the authorization relay unit 65 corresponds to the authorization data authorization transfer system TS1 designated in advance by the issuer 4 among the issuers 4 determined to transfer the authorization data to which the R flag is added. The authorization data with the recurling identifier added to the data format is converted. The authorization relay unit 65 transfers the converted authorization data to the issuer 4 via the designated authorization data authorization transfer system TS1.
The transaction system 1a according to the present embodiment can select a transfer system from a plurality of transfer systems according to the request of the issuer 4. Moreover, since it becomes possible to respond | correspond to various transfer systems, the transaction system 1a by this embodiment can improve the convenience.

Further, in the present embodiment, the authorization relay unit 65 uses the authorization data corresponding to the issuer 4 determined to transfer the authorization data to which the R flag is added, among the authorization data obtained by the authorization data obtaining unit 61. Add a recurring identifier to the data.
Thereby, the transaction system 1a according to the present embodiment can cope with the case where the R flag is not added. Moreover, the transaction system 1a according to the present embodiment can reduce the processing by the member store 2.

The processing method according to the present embodiment is a processing method of the transaction system 1a including the target member store information storage unit 62 and the issuer information storage unit 63 described above, and includes an acquisition step and a transfer step. . In the acquisition step, authorization data is acquired from the member store 2 at the second data center 6. In the transfer step, transactions that are charged periodically at the second data center 6 based on the target member store information stored in the target member store information storage unit 62 and the issuer determination information stored in the issuer information storage unit 63 The issuer 4 to which the authorization data to which the recurling identifier for identifying the recurling is added is transferred. Further, in the relay step, the authorization data to which the recurling identifier corresponding to the issuer 4 is added among the authorization data acquired in the acquisition step is transferred to the issuer 4.
Thereby, the processing method by this embodiment can reduce the grade which becomes complicated when performing authorization for every transaction similarly to the transaction system 1a by this embodiment mentioned above.

Next, a transaction system according to a third embodiment will be described with reference to the drawings.
[Third Embodiment]
Here, the above-mentioned [Modification 2] described with reference to FIG. 4 will be described in detail as a third embodiment.

FIG. 19 is a functional block diagram showing an example of a transaction system 1b according to the third embodiment.
As shown in FIG. 19, the transaction system 1b includes a member store 2, an issuer 4, an acquirer 3, a first data center 5b, and a second data center 6a.
In this figure, the same components as those shown in FIG.

  In the present embodiment, the second data center 6a is provided between the first data center 5b and the issuer 4, and the authorization data and the authorization result are transferred by online processing via the second data center 6a. Different from the first embodiment.

The basic function of the first data center 5b is the same as that of the first data center 5 in the first embodiment. However, instead of the authorization data file, authorization data for each transaction is sent to the second data center 6a. The transfer point is different.
The first data center 5b includes a sales data concentrator 51, an acquirer information storage unit 52, an issuer BIN information storage unit 53, an authorization data transmission unit 54a, an authorization result reception unit 55, and sales data creation. Part 56.

  The authorization data transmission unit 54a creates authorization data for Not on-us among the sales data collected by the sales data collection unit 51 in the first data center 5, and creates the authorization data thus created. The data is transferred to each issuer 4 via the second data center 6a.

The second data center 6a (an example of a relay center) has the same basic function as the second data center 6 in the second embodiment, but a predetermined rule is used when transferring authorization data to the issuer 4. Is different in that the transfer amount of the authorization data is adjusted and the authorization data is relayed to the issuer 4. Here, the predetermined rule is, for example, relaying data from the second data center 6a to the issuer 4 in a time zone where the network has a margin (for example, at night), or authorizing data according to the response time of the authorization result. For example, changing the relay interval to issuer 4. Based on a predetermined rule, the second data center 6a adjusts the relay of the authorization data so that the network load with the issuer 4 and the processing load of the issuer 4 do not exceed a predetermined value.
The second data center 6a also includes an authorization data acquisition unit 61, a target member store information storage unit 62, an issuer information storage unit 63, an issuer proxy storage unit 64, and an authorization relay unit 65a.

  The authorization relay unit 65a has the same function as the authorization relay unit 65 in the second embodiment, and adjusts the relay of authorization data based on the predetermined rule described above. The authorization relay unit 65a may relay the authorization data according to the number of cases set for each issuer 4, for example.

In the present embodiment, the R flag may be added to the authorization data as in the second embodiment. When the R flag is added to the authorization data, the first data center 5b may add the R flag to the authorization data, or the second data center 6a adds the R flag to the authorization data. You may make it add.
Although not shown, the second data center 6a may correspond to the proxy center 7 as in the second embodiment, or may be authorized to the issuer 4 via another authorization transfer system TS1. The data for use may be transmitted.

Next, with reference to FIG. 20, the operation of the transaction system 1b according to the present embodiment will be described.
FIG. 20 is a sequence diagram showing an example of the operation of the transaction system 1b according to the present embodiment. The example shown in this figure shows an example in which the second data center 6a relays the authorization data corresponding to the authorization data to which the R flag is added to the authorization data.

  In FIG. 20, first, the member store 2 transmits sales data to the first data center 5b (step S501). Here, the sales data is sales data by recurring. The sales data concentrator 51 of the first data center 5b collects sales data from the member store 2.

  Next, the first data center 5b creates authorization data (step S502). That is, the authorization data transmission unit 54 of the first data center 5b creates authorization data for Not on-us.

Next, the authorization data transmission unit 54 transfers the created authorization data to the second data center 6a (step S503).
The second data center 6a adds the R flag to the authorization data, adjusts the transfer amount of the authorization data, and relays the authorization data with the R flag to the issuer 4 (step S504).

Next, the issuer 4 executes an authorization process (step S505), and transmits an authorization result to the second data center 6a (step S506).
Next, the second data center 6a relays the received authorization result to the first data center 5b (step S507).

  The subsequent processing from step S508 to step S510 is the same as the processing from step S105 to step S107 shown in FIG.

As described above, when the transaction system 1b according to the present embodiment transfers the authorization data to the issuer 4, the transaction system 1b adjusts the transfer amount of the authorization data based on a predetermined rule, and the authorization data is transferred to the issuer 4. Is provided with a second data center 6a (relay center).
As a result, the transaction system 1b according to the present embodiment does not require the issuer 4 to perform batch processing using the authorization data file as in the first embodiment. Therefore, for example, the transaction system 1b according to the present embodiment does not require the issuer 4 to make a change to accept the authorization data file. Further, for example, the second data center 6a can relay the authorization data to the issuer 4 during the time when the processing is free, such as at night. Therefore, the transaction system 1b according to the present embodiment can execute the processing of the issuer 4. Can be reduced. Further, the transaction system 1b according to the present embodiment can further reduce the load on the network between the first data center 5 and each issuer 4. Therefore, the transaction system 1b according to the present embodiment can reduce the extent to which the processing becomes complicated when performing authorization for each transaction, as in the first and second embodiments described above.

  In the above-described embodiment, the first data center 5b may include a part or all of the second data center 6a. For example, when the first data center 5 b transfers the authorization data to the issuer 4, the authorization relay unit that adjusts the transfer amount of the authorization data based on a predetermined rule and relays the authorization data to the issuer 4. You may make it provide 65a (relay part).

Next, a transaction system according to a fourth embodiment will be described with reference to the drawings.
[Fourth Embodiment]
Here, the above-mentioned [Modification 3] described with reference to FIG. 5 will be described in detail as a fourth embodiment.

FIG. 21 is a functional block diagram showing an example of a transaction system 1c according to the third embodiment.
As shown in FIG. 21, the transaction system 1c includes a member store 2, an issuer 4, an acquirer 3, a first data center 5a, a second data center 6a, and a third data center 8. .
In this figure, the same components as those shown in FIG.

  The third data center 8 is a storage agency center, for example, and provides a service for easily generating sales data from sales instruction data. The third data center 8 is constituted by, for example, one or a plurality of computer devices. The third data center 8 includes a sales instruction data concentrator 81, an acquirer information storage unit 82, an issuer BIN information storage unit 83, an authorization data transmission unit 84a, an authorization result reception unit 85, and sales data. A creation unit 86 and a sales data distribution unit 87 are provided.

In the present embodiment, a third data center 8 is provided instead of the first data center 5b in the third embodiment described above. The third data center 8 performs the same process as the first data center 5b described above. A sales instruction data concentrator 81, an acquirer information storage unit 82, an issuer BIN information storage unit 83, an authorization data transmission unit 84a, an authorization result reception unit 85, and a sales data creation unit 86 in the third data center 8. The sales data distribution unit 87 includes a sales data concentrating unit 51 in the first data center 5b, an acquirer information storage unit 52, an issuer BIN information storage unit 53, an authorization data transmission unit 54a, and an authorization result reception. This corresponds to the section 55, the sales data creation section 56, and the sales data distribution section 57.
The sales instruction data concentrator 81 collects sales instruction data from the member store 2 and generates sales data based on the sales instruction data.

  Since the first data center 5a in this embodiment is the same as the first data center 5a in the second embodiment, the description thereof is omitted here.

As described above, the transaction system 1c according to the present embodiment includes the third data center 8 that performs the same processing as the first data center 5a in the second embodiment, and the first data center 5a.
Thereby, the transaction system 1c according to the present embodiment has the same effect as that of the third embodiment by adding the third data center 8 without changing the first data center 5a which is an existing system. . Therefore, similarly to the third embodiment described above, the transaction system 1c according to the present embodiment can reduce the degree of complexity of processing when performing authorization for each transaction.

The present invention is not limited to the above embodiments, and can be modified without departing from the spirit of the present invention.
For example, each of the above embodiments has been described as an independent embodiment, but may be a combination of a plurality of embodiments.
In addition, a plurality of systems in which the above embodiments are implemented are mixed, and, for example, depending on the request of the member store 2, the acquirer 3, and the issuer 4, the member store 2, the acquirer 3, and the issuer 4 are different. The system may be implemented.

In the first embodiment, the example including the transfer using the authorization data file has been described. However, instead of the authorization data file, individual authorization data may be processed online.
Further, the second embodiment described above may not include the correspondence to the proxy center 7 and does not include the correspondence to be transferred to the issuer 4 by the authorization transfer system TS1 via the dedicated server 10. Form may be sufficient.

  It should be noted that a program for realizing each processing function of transaction system 1 (1a to 1e) in the present invention is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into the computer system. , Transaction processing may be performed by executing. Here, the “computer system” includes an OS and hardware such as peripheral devices. The “computer system” includes a WWW system having a homepage providing environment (or display environment). The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Further, the “computer-readable recording medium” refers to a volatile memory (RAM) in a computer system that becomes a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. In addition, those holding programs for a certain period of time are also included.

  The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, what is called a difference file (difference program) may be sufficient.

1, 1a, 1b, 1c, 1d, 1e Transaction system 2 Member store 3 Acquirer 4 Issuer 5, 5a, 5b First data center 6, 6a Second data center 7 Proxy center 8 Third data center 9 Fourth data center 10 Dedicated server 51 Sales data concentrator 52, 82 Acquirer information storage unit 53, 83 Issuer BIN information storage unit 54, 54a, 84a Authorization data transmission unit 55, 85 Authorization result reception unit 56, 86 Sales data creation unit 57, 87 Sales data distribution unit 61 Authorization data acquisition unit 62 Target member store information storage unit 63 Issuer information storage unit 64 Issuer proxy storage unit 65, 65a Authorization relay unit 81 Sales instruction data collection unit TS1 Authorization transfer system

Claims (7)

A target member store information storage unit for storing target member store information indicating a member store subject to recurring indicating a transaction to be charged periodically ;
An issuer information storage unit for storing issuer determination information, which is issuer determination information for determining an issuer, and associates information for specifying an issuer included in the authorization data with issuer information for identifying the issuer ;
An acquisition unit for acquiring authorization data;
It said target member store information the target member store information storage unit stores, the issuer information storage unit based on said issuer determination information stored, authorization data for re curling identifier is added to identify the Li curling A transfer unit that determines the issuer to transfer the authorization data, and transfers the authorization data to which the recurring identifier corresponding to the issuer is added, of the authorization data acquired by the acquisition unit, to the issuer. A transaction apparatus characterized by that. An issuer proxy storage unit that stores issuer proxy information indicating identification information of an issuer that performs authorization processing based on the authorization data;
The transfer unit is
Based on the issuer proxy information stored in the issuer proxy storage unit, the target issuer that performs authorization processing is extracted, and the data for authorization among the data for authorization to which the recurling identifier that has determined the issuer to be transferred is added The transaction apparatus according to claim 1, wherein the authorization data corresponding to the target issuer is transmitted to an agency center acting as an authorization process. The transfer unit is
Among the issuers determined to transfer the authorization data to which the recurling identifier is added, the authorization having the recurling identifier added to a data format corresponding to the authorization data transfer system designated in advance by the issuer. 3. The transaction apparatus according to claim 1, wherein the authorization data is converted, and the converted authorization data is transferred to the issuer via the designated authorization data transfer system. . The transfer unit is
Based on the target member store information stored in the target member store information storage unit, it is determined to transfer the authorization data to which the recurling identifier is added, among the authorization data acquired by the acquisition unit. The transaction apparatus according to any one of claims 1 to 3, wherein the recurling identifier is added to the authorization data corresponding to the issuer. A relay unit configured to adjust a transfer amount of the authorization data based on a predetermined rule and relay the authorization data to the issuer when transferring the authorization data to the issuer. The transaction apparatus according to any one of claims 1 to 4. A target member store information storage unit for storing target member store information indicating a member store subject to recurring indicating a transaction to be charged periodically, and issuer determination information for determining an issuer , which is included in the authorization data A transaction apparatus processing method comprising: an issuer information storage unit for storing issuer determination information in which information for specifying the issuer is associated with issuer information for identifying the issuer ,
An acquisition step of acquiring authorization data;
It said target member store information the target member store information storage unit stores, the issuer information storage unit based on said issuer determination information stored, authorization data for re curling identifier is added to identify the Li curling And transferring the authorization data to which the recurling identifier corresponding to the issuer is added from the authorization data acquired in the acquisition step to the issuer. A processing method characterized by the above. A target member store information storage unit for storing target member store information indicating a member store subject to recurring indicating a transaction to be charged periodically, and issuer determination information for determining an issuer , which is included in the authorization data A computer of a transaction apparatus comprising: an issuer information storage unit for storing issuer determination information in which information for specifying the issuer and issuer information for identifying the issuer are associated with each other ;
An acquisition step of acquiring authorization data;
It said target member store information the target member store information storage unit stores, the issuer information storage unit based on said issuer determination information stored, authorization data for re curling identifier is added to identify the Li curling And transferring the authorization data to which the recurling identifier corresponding to the issuer is added, out of the authorization data acquired in the acquisition step, to the issuer. Program to let you.

Images