JP2025044574A - Payment processing device, method, and program - Google Patents

Abstract

To provide a subscription service by a member store providing a face-to-face service without having to provide a member management mechanism by creating a dedicated website or application.SOLUTION: A settlement processing apparatus generates a credit inquiry telegram based on a validity check request telegram and stores a card number and a contract number associated with a transaction approval when the credit inquiry result for the credit inquiry telegram indicates the transaction approval. The settlement processing apparatus receives sales data associated with a member store, reads a card number based on a contract number included in the sales data, generates a credit inquiry telegram based on the read card number, a member store identifier included in the sales data, and a charging amount, determines charging eligibility for the contract number based on a credit inquiry result for the credit inquiry telegram, acquires the card number for the contract number determined the charging eligibility and generates a sales telegram based on the card number.SELECTED DRAWING: Figure 8

Description

The present invention relates to a payment processing device, method, and program that provides affiliated stores with a mechanism for implementing subscription services.

The market for consumer (so-called B2C) subscription services is expanding rapidly. Areas where the subscription service market is expanding include "clothing and fashion rental," "dining out services," "lifestyle services such as furniture and home appliances," "multi-location living services," "digital content," and "delivery services using subscription system platforms."

In these fields, consumers receive the services they want by registering an account using a device such as a PC, smartphone, or tablet, and it is relatively easier to acquire members for subscription services in non-face-to-face transaction situations. The system described in Patent Document 1 is known as a system for supporting member acquisition in non-face-to-face transactions.

Patent No. 7291193

Meanwhile, companies that provide face-to-face services to consumers are facing the challenge of how to develop subscription services. In order for such companies to acquire members for their subscription services, they need to create a dedicated website or app to manage members, check the validity of payment methods, and prepare a system for billing, but some companies find it difficult to prepare such a system. In addition, when consumers visit a store, it is difficult to explain the service content, have them register as members, and check the payment method used by the consumer, due to not only system constraints but also time constraints.

In addition, when merchants implement subscription services, they are required to hold and properly manage card information, which places an excessive burden on them as they must comply with PCI DSS, the security standard for the credit card industry.

The present invention has been made to solve these problems, and aims to provide a payment processing device, method, and program that allows affiliated stores that offer face-to-face services to implement subscription services without having to create a dedicated website or app to set up a membership management system.

A payment processing device according to one aspect of the present invention is a payment processing device including a communication unit for communicating with an external network, a storage unit, and a control unit,
The storage unit stores a card number and a contract number associated with an affiliated store,
The control unit is
receiving sales data associated with the affiliated store via the communication unit;
reading out the card number from the storage unit based on the contract number included in the sales data, and generating a first credit inquiry message based on the read out card number, the affiliated store identifier included in the sales data, and the billing amount;
determining whether or not to charge the contract number based on a first credit inquiry result for the first credit inquiry message;
and acquiring from the storage unit the card number associated with the contract number determined to be billable, and generating a sales message based on the card number.

According to the present invention, a payment processing device can provide a subscription service mechanism to an affiliated store, so that the affiliated store can provide a subscription service to its customers without having to hold the card information of the affiliated store customers.

A more detailed understanding of the embodiments disclosed herein can be had from the following description, taken in conjunction with the accompanying drawings, in which:
1 is a configuration diagram of an entire system including a payment processing device 10 according to the present invention. 1 is a system configuration diagram of a payment processing device 10 according to the present invention. 10 is a diagram illustrating an example of the data structure of deposit billing information 106. FIG. 3 is a diagram showing an example of a data structure of payment information 108. FIG. FIG. 11 is a flow diagram illustrating a registration process for a subscription service. FIG. 11 is a flow diagram illustrating a cancellation process for a subscription service. FIG. 11 is a flow diagram illustrating a contract number inquiry process for a subscription service. FIG. 11 is a flow diagram illustrating a billing process for a subscription service.

(Overall composition)
1 is a block diagram of an entire system including a payment processing device 10 according to the present invention. Payment processing device 10 is connected to a card company system 11, an affiliated store payment terminal 12, and an affiliated store system 13 so that they can communicate with each other. Payment processing device 10 is used by an acquirer or a payment agency, and card company system 11 is used by an issuer. Note that, depending on the card, the issuer and acquirer may be the same card company.

The payment processing device 10 checks whether the card number included in the validity check request message received from the affiliated store payment terminal 12 is a card number included in the validity checklist, and requests a validity check (i.e., authorization) from the card company system 11 for card numbers that it determines can be processed further. The payment processing device 10 associates the card number information that it has received a response that it is valid with the affiliated store code and contract number, and deposits and registers it. The payment processing device 10 transmits the contract number associated with the deposited and registered card number information to the affiliated store payment terminal 12.

The payment processing device 10 receives a cancellation request including the contract number or card number from the affiliated store payment terminal 12 or affiliated store system 13, and invalidates the registered card number.

The payment processing device 10 receives a contract number inquiry request, including the card number, from the affiliated store payment terminal 12, and requests a validity check from the card company system 11. The payment processing device 10 inquires about the billing information based on the card number that is answered as valid, and transmits the obtained contract number to the affiliated store payment terminal 12.

The payment processing device 10 receives sales data including the contract number and sales amount from the affiliated store system 13, identifies the card number based on the contract number included in each sales data, and performs a credit inquiry (authorization request) to the card company system 11 based on the identified card number and sales amount. The payment processing device 10 receives the credit inquiry result from the card company system 11, and provides the contract numbers associated with the card numbers for which the credit inquiry result was NG to the affiliated store system 13 as an authorization NG target list. For card numbers for which the credit inquiry result was OK, the payment processing device 10 generates a sales message and sends it to the card company system 11.

The payment processing device 10 identifies the card company system 11 to which the credit inquiry message and sales message should be sent based on the numerical information of a certain number of digits of the card number. As is well known to those skilled in the art, the numerical information of a certain number of digits of the card number identifies the card company that is the issuer.

The payment processing device 10 calculates the usage fee for the subscription service and transmits the billing data to the affiliated store system 13.

The card company system 11 receives a credit inquiry (authorization request) including the card number and amount information from the payment processing device 10, and performs a card validity check (authorization process). The card company system 11 transmits the results of the card validity check to the payment processing device 10. The card company system 11 also receives a sales message from the payment processing device 10, records card sales, issues an invoice to the card member, and performs direct debit processing for the card member's specified account.

The affiliated store payment terminal 12 is a payment terminal that can handle various cashless payments such as credit cards, debit cards, electronic money, and two-dimensional codes, and has a touch panel display. The affiliated store payment terminal 12 can download and execute a business application for the subscription service from the payment processing device 10. The business application for the subscription service has functions such as inputting a contract number uniquely set by the affiliated store, generating a validity check request message based on card information presented by the customer, and outputting the contract number associated with the registered deposited card number received from the payment processing device 10 on the display/printing it via the printing means of the affiliated store payment terminal 12.

The affiliated store system 13 is a PC or tablet terminal used by the affiliated store. The affiliated store system 13 can register the contract number and billing information via a business application for the subscription service downloaded from the payment processing device 10, or via a specified website.

(System Configuration)
2 is a system configuration diagram of a payment processing device 10 according to the present invention. Like a general computer, the payment processing device 10 comprises a control unit 101, a main memory unit 102, an auxiliary memory unit 103, an IF unit 104, and an output unit 105, all of which are interconnected by a bus 120 or the like. The payment processing device 10 comprises deposit and billing information 106, a checklist 107, and payment information 108 in the form of storage means such as a file/database in the auxiliary memory unit 103.

The control unit 101, also called the central processing unit (CPU), controls each component of the payment processing device 10 and performs data calculations, and also reads out and executes various programs stored in the auxiliary storage unit 103 into the main storage unit 102. The main storage unit 102, also called the main memory, can store various received data, computer-executable instructions, and data after calculation processing based on those instructions. The auxiliary storage unit 103 is a storage device such as a hard disk drive (HDD), and is used for long-term storage of data and programs.

The embodiment in FIG. 2 describes an embodiment in which the control unit 101, main memory unit 102, and auxiliary memory unit 103 are provided in the same computer, but in another embodiment, the payment processing device 10 can be configured to realize parallel distributed processing by multiple computers by using multiple control units 101, main memory units 102, and auxiliary memory units 103. In another embodiment, it is also possible to install multiple servers for the payment processing device 10, and have the multiple servers share a single auxiliary memory unit 103.

The IF unit 104 acts as an interface (IF) when sending and receiving data with other systems and devices, and also provides an interface that accepts various commands and input data (various masters, tables, etc.) from the system operator. The output unit 105 provides a display screen that displays the processed data and a printing means for printing the data.

Components with functions similar to those of the control unit 101, main memory unit 102, auxiliary memory unit 103, IF unit 104, and output unit 105 also exist in the card company system 11, affiliated store payment terminal 12, and affiliated store system 13, but a description of these will be omitted in this specification.

The on-deposit billing information 106 stores the card numbers deposited from each affiliated store and the card information associated with the card numbers. FIG. 3 is a diagram illustrating an example of the data structure of the on-deposit billing information 106. The on-deposit billing information 106 can include an affiliated store ID 301, a deposited card number 302, a contract number 303, a card expiration date 304, and a security code 305, but is not limited to these data items and can also include other data items.

The affiliated store ID 301 is an identifier that identifies the affiliated store that uses the subscription service. The deposited card number 302 is the card number held by the affiliated store customer that uses the subscription service, and is a card number for which a validity check by the payment processing device 10 and the card company system 11 has been successfully completed. The contract number 303 is the subscription service contract number that the affiliated store has assigned to the affiliated store customer, or the subscription service contract number that the payment processing device 10 automatically assigns to the affiliated store customer. The card expiration date 304 is the expiration date until which payments can be made using the deposited card number. The security code 305 is a security code that can be used for payments using the deposited card number.

Returning to FIG. 2, checklist 107 stores the card number ranges and individual card numbers that are specified by the affiliated store and that the affiliated store wishes to or does not wish to register as members. The card number ranges and individual card numbers registered in checklist 107 (not shown) allow the payment processing device 10 to control the processing, such as to target only cards from specific issuers, to exclude cards issued in foreign countries, to exclude prepaid cards, etc.

Payment information 108 stores billing information charged by the affiliated store to the affiliated store customer, the deposited card number identified based on the billing information, and the results of the credit inquiry process and sales registration process based on the card number. Figure 4 is a diagram showing an example of the data structure of payment information 108. Payment information 108 can include affiliated store ID 301, deposited card number 302, contract number 303, target date 401, billing amount 402, authorization result 403, and sales registration flag 404, but is not limited to these data items and can also include other data items.

The affiliated store ID 301, the deposited card number 302, and the contract number 303 have been explained above with reference to FIG. 3, so a repeat explanation will be omitted.

The target date 401 indicates the date on which a charge will be made to a member store customer who has used the member store's subscription service. The charge amount 402 indicates the charge amount that the member store will charge to the customer. The authorization result 403 indicates the result of authorization (e.g., OK or NG) performed by the card company system 11 based on the deposited card number and the charge amount. The sales registration flag 404 is a flag that indicates whether sales registration based on the deposited card number and the charge amount has been performed in the card company system 11.

(Subscription service registration process)
5 is a flow diagram illustrating the registration process for the subscription service. This process flow is premised on the assumption that the affiliated store payment terminal 12 has downloaded and installed an application for the subscription service from the payment processing device 10, the affiliated store has explained the contents of the subscription service to the affiliated store customer, and the affiliated store customer has agreed to join the service.

In S501, the affiliated store payment terminal 12 reads the card information and generates a validity check request message. The validity check request message includes the affiliated store ID, card number, card expiration date, and security code, and may further include the contract number if the affiliated store assigns a contract number to the affiliated store customer. The contract number is entered from an application displayed on the display of the affiliated store payment terminal 12.

At S502, the affiliated store payment terminal 12 transmits the generated validity check request message to the payment processing device 10.

At S503, the payment processing device 10 queries the checklist 107 based on the card number included in the received validity check request message to determine whether the card number is eligible for registration. If it is determined that the card number is not eligible for registration, the payment processing device 10 sends a notification to the affiliated store payment terminal 12 indicating that registration is not possible (not shown). On the other hand, if it is determined that the card number is eligible for registration, the process proceeds to S504.

At S504, the payment processing device 10 generates a credit inquiry message that includes the affiliated store ID, card number, and an arbitrary amount (e.g., 0 yen) included in the validity check request message. As is known to those skilled in the art, a credit inquiry message is also called an authorization message.

At S505, the payment processing device 10 identifies the card company system 11 to which the message should be sent based on the numerical information of a predetermined number of digits of the card number in the credit inquiry message, and sends the generated credit inquiry message to the card company system 11. The card company system 11 is a system associated with the issuer that issued the card number.

At S506, the card company system 11 executes authorization processing based on the affiliated store ID, card number, and amount contained in the received credit inquiry message. The authorization processing is a process that determines whether the card transaction is approved or not approved by checking the card expiration date, the credit limit, etc. The card company system 11 generates a credit inquiry result based on the result of the authorization processing. The credit inquiry result indicates approval or disapproval of the card transaction based on the information contained in the credit inquiry message, and includes, for example, the affiliated store ID, card number, amount, and a flag indicating approval or disapproval.

At S507, the card company system 11 transmits the credit inquiry result to the payment processing device 10.

In S508, if the credit inquiry result indicates that the transaction is not approved, the payment processing device 10 transmits a notification indicating that registration is not possible to the affiliated store payment terminal 12 (not shown). On the other hand, if the credit inquiry result indicates that the transaction is approved and the validity check request message does not include a contract number, the payment processing device 10 issues a contract number associated with the affiliated store. If the credit inquiry result indicates that the transaction is approved, the payment processing device 10 stores the affiliated store ID, card number, contract number, card expiration date, and security code in the billing information 106 based on the validity check request message and the credit inquiry result. Whether the payment processing device 10 issues a new contract number can be determined depending on whether the affiliated store holds and issues a contract number. That is, in the present invention, the contract number can be one that the affiliated store has assigned and issued (one that is included in the validity check request message), or if the affiliated store does not issue one, the payment processing device 10 can use a contract number that it has issued to be associated with the affiliated store.

At S509, when the data registration to the deposit billing information 106 is completed, the payment processing device 10 sends a processing completion notification to the affiliated store payment terminal 12. The processing completion notification includes at least the affiliated store ID and contract number.

At S510, when the affiliated store payment terminal 12 receives the processing completion notification, it displays the contract number associated with the registered card number on the display, and outputs a printout (e.g., a receipt) showing the contract number via the printing means of the affiliated store payment terminal 12. The printout may be handed over to the affiliated store customer, and is also retained as a record of the affiliated store.

In S511, the affiliated store system 13 can register the contract number together with the customer information received from the affiliated store customer in the system and manage it as member information. The member information may be managed independently by the affiliated store.

(Subscription service cancellation process)
6 is a flow diagram illustrating the cancellation process of the subscription service. The cancellation process can be executed from the affiliated store system 13 (S601 to S604) or from the affiliated store payment terminal 12 (S605 to S608).

At S601, the affiliated store system 13 receives input of the contract number that is the subject of the cancellation process from an affiliated store employee or the like. At S602, the affiliated store system 13 transmits a cancellation request including the input contract number to the payment processing device 10. The input of the contract number and the transmission of the cancellation request can be performed via a business application for the subscription service or via a specified website.

In S603, the payment processing device 10 queries the deposit billing information 106 based on the received contract number, and if data for the corresponding contract number is found, executes a predetermined process on the data stored in the contract number 303 of that data. The predetermined process may be any process that prevents subsequent processes using the contract number from being executed, such as deleting the contract number itself or adding an arbitrary value to the contract number to make it unusable (for example, changing contract number "1234" to "1234-disable").

At S604, the payment processing device 10 transmits the invalidation processing result to the affiliated store system 13. The invalidation processing result may include the affiliated store ID, the contract number, and a notification indicating that the transaction has been invalidated.

The cancellation process from S601 to S604 described above is executed by the affiliated store system 13, and the necessary information is the contract number. On the other hand, the cancellation process from S605 to S608 described below is executed by the affiliated store payment terminal 12, and the necessary information is the contract number or card number.

At S605, the affiliated store payment terminal 12 receives input of a contract number or card number from an affiliated store customer or an affiliated store employee, etc. The contract number may be input from a cancellation menu on the display of the affiliated store payment terminal 12. The card number may be input from a card information reading means of the affiliated store payment terminal 12 (e.g., any means such as a contact or contactless IC card reader, a magnetic stripe reader, etc.). At S606, the affiliated store payment terminal 12 transmits a cancellation request including the input contract number or card number to the payment processing device 10.

In S607, the payment processing device 10 queries the deposited billing information 106 based on the received contract number or card number, and if data for the corresponding contract number or card number is found, executes a predetermined process on the data stored in the contract number 303 of that data. The predetermined process may be any process that makes it impossible to execute subsequent processes that use the contract number, such as deleting the contract number itself, or loading an arbitrary value onto the contract number to make it unusable (for example, changing contract number "1234" to "1234-disable").

At S608, the payment processing device 10 transmits the invalidation processing result to the affiliated store system 13. The invalidation processing result may include the affiliated store ID, the contract number or card number, and a notification indicating that the card has been invalidated.

(Subscription service contract number inquiry processing)
7 is a flow diagram for explaining the contract number inquiry process of the subscription service. This process is executed when a member store customer or the like has forgotten his/her contract number.

At S701, the affiliated store payment terminal 12 receives input of a card number. The card number may be input from a card information reading means of the affiliated store payment terminal 12 (e.g., any means such as a contact or contactless IC card reader, a magnetic stripe reader, etc.). The affiliated store payment terminal 12 generates a contract number inquiry request message based on the input card number.

At S702, the affiliated store payment terminal 12 sends a contract number inquiry request message including the input card number and affiliated store ID to the payment processing device 10.

At S703, the payment processing device 10 queries the deposited billing information 106 based on the affiliated store ID and card number included in the contract number inquiry request message to determine whether data exists. If it is determined that no data exists, the payment processing device 10 notifies the affiliated store payment terminal 12 that card information does not exist (not shown). The notification that card information does not exist is displayed on the display of the affiliated store payment terminal 12. On the other hand, if it is determined that card information exists, the data acquired by the query is stored in the main memory unit 102, and the processing from S704 onwards is executed.

At S704, the payment processing device 10 generates a credit inquiry message (authorization message) that includes the affiliated store ID and card number included in the contract number inquiry request message, as well as an arbitrary amount (e.g., 0 yen). At S705, the payment processing device 10 identifies the card company system 11 to which the credit inquiry message should be sent based on the numerical information of a predetermined number of digits of the card number, and sends the generated credit inquiry message to the card company system 11.

At S706, the card company system 11 executes authorization processing based on the affiliated store ID, card number, and amount contained in the received credit inquiry message. At S707, the card company system 11 transmits the credit inquiry result to the payment processing device 10.

At S708, the payment processing device 10 analyzes the credit inquiry result, and if the credit inquiry result indicates that the transaction is approved, generates a processing completion notification that includes at least the contract number of the data obtained by the inquiry at S703. On the other hand, if the credit inquiry result indicates that the transaction is not approved, the payment processing device 10 generates a notification indicating that the card cannot be used and sends it to the affiliated store payment terminal 12 (not shown). The notification indicating that the card cannot be used is displayed on the display of the affiliated store payment terminal 12.

At S709, the payment processing device 10 sends a processing completion notification including at least the contract number to the affiliated store payment terminal 12.

At S710, the payment processing device 10 displays the contract number included in the processing completion notification on the display, and outputs a printed matter (e.g., a receipt) showing the contract number via the printing means of the affiliated store payment terminal 12.

In another embodiment of the present invention, an affiliated store can obtain a contract number associated with the affiliated store from the payment processing device 10. The affiliated store system 13 sends a contract number acquisition request to the payment processing device 10 via a business application for the subscription service or via a specified website. In response to the contract number acquisition request, the payment processing device 10 can acquire a set of contract numbers associated with the affiliated store from the deposited billing information 106 and provide them to the affiliated store system 13.

(Subscription service billing process)
FIG. 8 is a flow diagram illustrating the billing process for the subscription service.

At S801, an affiliated store employee or the like creates sales data using the affiliated store system 13. The sales data includes the affiliated store ID, the billing date, the contract number, and the billing amount. At S802, the affiliated store system 13 transmits the sales data to the payment processing device 10.

At S803, the payment processing device 10 stores the received sales data in the payment information 108, queries the deposited billing information 106 using each of the contract numbers included in the sales data, and obtains the corresponding card numbers. The payment processing device 10 generates an authorization message based on each of the obtained card numbers and the corresponding affiliated store ID, target date, and billing amount in the received sales data.

At S804, the payment processing device 10 identifies the card company system 11 to which the credit inquiry message should be sent based on the numerical information of a predetermined number of digits of the card number in the credit inquiry message, and sends the generated credit inquiry message to the card company system 11. The card company system 11 is a system associated with the issuer that issued the card number.

At S805, the card company system 11 executes authorization processing based on the affiliated store ID, card number, and amount contained in the received credit inquiry message. At S806, the card company system 11 transmits the credit inquiry result to the payment processing device 10. The payment processing device 10 stores the result of the authorization processing indicated in the credit inquiry result in the payment information 108.

The processes of S803 to S806 are performed for each card number associated with the contract number included in the sales data.

At S807, the payment processing device 10 generates a result list indicating the determination result of whether or not billing can be performed for each contract number based on the credit inquiry result. The result list may indicate that billing can be performed for some contract numbers and that billing cannot be performed for other contract numbers. At S808, the payment processing device 10 transmits the result list to the affiliated store system 13.

In S809, the affiliated store system 13 receives the result list and displays it on its display and/or prints it via a printing means. The affiliated store may take measures such as canceling the contract with affiliated store customers who are indicated in the result list as not being billable.

At S810, the payment processing device 10 obtains from the deposited billing information 106 the card number associated with each contract number indicated as billable in the result list, and generates a sales message based on the card number. The sales message includes information on the affiliated store ID, the target date, the card number, and the billing amount. At S811, the payment processing device 10 identifies the card company system 11 to which the sales message should be sent based on the numerical information of a predetermined number of digits of the card number in the sales message, sends the generated sales message to the card company system 11, and stores in the payment information 108 a sales registration flag indicating that the sales message has been sent.

At S812, the card company system 11 records sales for each card number based on the sales message, and then performs billing processing for each card number using a predetermined payment method (e.g., the affiliated store customer's bank account).

At S813, the payment processing device 10 executes settlement processing for the affiliated store for the use of the subscription service for that month and generates billing data. At S814, the payment processing device 10 transmits the billing data to the affiliated store system 13.

At S815, the affiliated store system 13 executes the payment process using any means (e.g., bank transfer, direct debit, etc.) based on the received billing data.

The principles of the present invention have been described above with reference to exemplary embodiments, but those skilled in the art will understand that various embodiments that change the configuration and details can be realized without departing from the gist of the present invention. In other words, the present invention can be embodied, for example, as a system, device, method, program, or storage medium.

REFERENCE SIGNS LIST 10 Payment processing device 11 Card company system 12 Affiliated store payment terminal 13 Affiliated store system 101 Control unit 102 Main memory unit 103 Auxiliary memory unit 104 IF unit 105 Output unit 106 Deposited billing information 107 Checklist 108 Payment information

At S608, the payment processing device 10 transmits the invalidation processing result to the affiliated store payment terminal 12. The invalidation processing result may include the affiliated store ID, the contract number or the card number, and a notification indicating that the card has been invalidated.

Claims (8)

A payment processing device including a communication unit for communicating with an external network, a storage unit, and a control unit,
The storage unit stores a card number and a contract number associated with an affiliated store,
The control unit is
receiving sales data associated with the affiliated store via the communication unit;
reading out the card number from the storage unit based on the contract number included in the sales data, and generating a first credit inquiry message based on the read out card number, the affiliated store identifier included in the sales data, and the billing amount;
determining whether or not to charge the contract number based on a first credit inquiry result for the first credit inquiry message;
and obtaining from the memory unit the card number associated with the contract number determined to be chargeable, and generating a sales message based on the card number. The payment processing device of claim 1, wherein the control unit is further configured to generate a result list based on the determination of whether or not to charge the contract number, and transmit the result list via the communication unit. The control unit is
Identifying a card company system to which the first credit inquiry message should be sent based on the card number included in the first credit inquiry message;
3. The payment processing device of claim 2, further configured to: identify the card company system to which the sales message should be sent based on the card number included in the sales message. The control unit is
receiving a validity check request message via the communication unit;
generating a second credit inquiry message based on the validity check request message, and identifying a card company system to which the second credit inquiry message should be sent based on a card number included in the second credit inquiry message;
2. The payment processing device of claim 1, further configured to: if a second authorization result for the second authorization message indicates transaction approval, store in the memory unit a card number and a contract number associated with the transaction approval. The payment processing device of claim 4, wherein the control unit is further configured to transmit a notification including the affiliated store identifier and the contract number via the communication unit in response to storing the card number and the contract number in the memory unit. the storage unit further stores a card checklist including information on card numbers designated by the affiliated store that the affiliated store wishes to register or not register;
5. The payment processing device of claim 4, wherein the control unit is further configured to query the card check list based on the card number included in the validity check request message and determine whether the card number is a registerable card number. A method executed by a payment processing device having a communication unit for communicating with an external network, a storage unit, and a control unit, comprising:
The storage unit stores a card number and a contract number associated with an affiliated store,
the control unit receiving, via the communication unit, sales data associated with the affiliated store;
the control unit reads out the card number from the storage unit based on the contract number included in the sales data, and generates a first credit inquiry message based on the read-out card number, the affiliated store identifier included in the sales data, and the billing amount;
The control unit determines whether or not to charge the contract number based on a first credit inquiry result for the first credit inquiry message;
The control unit retrieves the card number associated with the contract number determined to be billable from the memory unit, and generates a sales message based on the card number. A program for causing a computer to execute the method according to claim 7.

Images