JP2024039085A - Payment management system, payment management method - Google Patents

Abstract

[Problem] To allow a payment medium manager to easily manage the use of the payment medium in real time. [Solution] In a payment management system comprising a payment terminal that accepts payments in response to requests from the payment medium, and a payment data server that is connected to the payment terminal and communicates with the payment medium manager terminal, the payment terminal accepts a payment using the payment medium and transmits a payment request including identification information that identifies the payment medium to the payment data server, and the payment data server transmits the payment request to the payment medium manager terminal that corresponds to the delivery address information that corresponds to the identification information requested from the payment terminal, and upon receiving a payment approval notice from the payment medium manager terminal that received the payment request, transmits the payment result to the payment terminal. [Selected Figure] Figure 7

Description

The present invention relates to a payment management system and a payment management method.

Conventionally, payment media such as transportation IC cards and convenience store (hereinafter also referred to as "convenience store") IC cards charge the balance of the target payment medium itself and use the balance information held in the payment medium. Payment processing is performed, and no special authentication is required when making a payment. Anyone can use it as long as the balance of the payment medium is charged. For this reason, if the card is lost with a balance charged, there is a possibility that the card will be misused by a third party who finds the card.

A technology has been proposed for a prepaid charge amount settlement system that checks the validity of the prepaid card, checks the charge amount input during the charge operation, and determines whether the transaction is approved ( For example, see Patent Document 1).

JP 2019-070932 A

However, giving children and the elderly a payment medium such as money or an IC card has a high risk of loss or theft. If the card is lost or stolen, the balance on the card can be misused.

In addition, children and elderly people who are unable to manage money can freely use the balance charged to the IC card, so there is a problem that they are unable to control the use of the payment medium.

In view of the above-mentioned problems, it is an object of the present invention to provide a payment management system that allows a payment medium administrator to easily manage the use of payment media in real time.

In order to achieve the above object, the payment management system of the present invention includes a payment terminal that accepts payments in response to a request from a payment medium, and a payment terminal that is connected to the payment terminal and communicates with a payment medium administrator terminal. A payment management system comprising: a payment data server, wherein the payment terminal receives a payment using the payment medium, transmits a payment request including identification information identifying the payment medium to the payment data server, and receives the payment data. The server transmits a payment request to the payment medium manager terminal corresponding to destination information corresponding to the identification information requested from the payment terminal, and sends the payment request from the payment medium manager terminal that received the payment request. It is characterized in that upon receiving a payment approval notification from a media administrator, the payment result is transmitted to the payment terminal.

Further, the payment management method of the present invention includes a payment terminal that accepts payments in response to a request from a payment medium, and a payment data server that is connected to the payment terminal and communicates with a payment medium administrator terminal. A payment management method executed by a payment management system comprising: the payment terminal receiving a payment using the payment medium, and transmitting a payment request including identification information identifying the payment medium to the payment data server; The payment data server transmits a payment request to the payment medium administrator terminal corresponding to destination information corresponding to the identification information requested by the payment terminal, and the payment medium administrator terminal that has received the payment request When receiving a payment approval notification from the administrator of the payment medium, the payment result is transmitted to the payment terminal.

According to the present invention, the administrator of a payment medium can easily manage the use of the payment medium in real time.

1 is a diagram showing an example of the configuration of a payment management system 1 according to the present embodiment. 1 is a diagram illustrating an overview of a payment management method executed by a payment terminal 10, a payment data server 20, and a card administrator terminal 30 that constitute the payment management system 1. FIG. FIG. 1 is a hardware configuration diagram of a payment terminal 10 according to the present embodiment. It is a hardware configuration diagram of a payment data server 20 according to the present embodiment. It is a hardware configuration diagram of a card administrator terminal 30 according to the present embodiment. 3 is a diagram showing an example of an identification information table 240 stored in the storage unit 24 of the payment data server 20. FIG. 3 is a sequence chart showing an example of a payment management process executed by the payment management system 1. FIG. 3 is a diagram showing an example of a usage content approval screen 331 displayed on the output device 33 by the card administrator terminal 30. FIG.

The payment management system 1 according to this embodiment will be described below with reference to the drawings. FIG. 1 is a diagram showing an example of the configuration of a payment management system 1 according to the present embodiment.

The payment management system 1 includes, for example, a payment terminal 10 and a payment data server 20. The payment management system 1 may include a card administrator terminal 30. Note that the payment management system 1 may include other configurations not shown in FIG. Although only one payment terminal 10 is shown in FIG. 1, the present invention is not limited to this, and a plurality of payment terminals may be provided. Although only one card administrator terminal 30 is shown in FIG. 1, the card administrator terminal 30 is not limited to this, and a plurality of card administrator terminals may be provided. The payment terminal 10, the payment data server 20, and the card administrator terminal 30 are interconnected via a network N, respectively.

The payment terminal 10 is a terminal that accepts payment based on the payment medium 40 used by the user. The payment medium includes an IC card, a magnetic card, a medium capable of displaying a QR code (registered trademark), and the like. A case where the payment medium 40 is an IC card will be described below. Hereinafter, the payment medium 40 will also be referred to as an IC card 40. When the payment medium is an IC card, the payment terminal 10 is a card payment terminal capable of reading an IC chip provided in the IC card. The payment terminal 10 is installed at a store, hotel, etc. where the payment medium 40 can be used. The payment terminal 10 may be installed in a movable taxi or the like. The payment medium 40 stores identification information that allows a plurality of payment mediums 40 to be uniquely identified. When the payment medium 40 is an IC card 40, the IC card 40 stores a card ID as identification information that can uniquely identify the plurality of IC cards 40.

The payment data server 20 is a terminal that verifies card information based on an authentication request from the payment terminal 10. The payment data server 20 is composed of a PC (Personal Computer) or the like.

The card administrator terminal 30 confirms the usage details with the administrator based on the approval request from the payment data server 20. The card administrator terminal 30 is configured by a smartphone or a tablet terminal.

Next, an overview of the payment management method executed by the payment terminal 10, payment data server 20, and card administrator terminal 30 that constitute the payment management system 1 will be explained. FIG. 2 is a diagram showing an overview of a payment management method executed by the payment terminal 10, payment data server 20, and card administrator terminal 30 that constitute the payment management system 1.

When the user P1 touches the IC card 40 on the payment terminal 10 through the store clerk P2, the payment terminal 10 reads the card ID stored in the IC card 40 as a prepaid card for family payment and makes the payment. The process starts and requests the payment data server 20 to authenticate the card information (step S11).

Upon receiving the card information authentication request from the payment terminal 10, the payment data server 20 verifies the card information and sends an approval request to the card administrator terminal 30 (step S12).

Upon receiving the approval request (step S13), the card manager terminal 30 displays a usage content approval screen to the manager P3 (step S13). Upon receiving usage authentication from the administrator P3 based on the approval screen, the card administrator terminal 30 notifies the payment data server 20 of approval (step S14).

The payment data server 20 that has received the approval OK notification notifies the payment terminal 10 of a payment completion notification (step S15). The payment terminal 10 that has received the payment completion notification completes the payment (step S16). This completes the purchase of the product by the user P1. Therefore, the payment medium administrator P3 can easily manage the use of the payment medium 40 in real time.

FIG. 3 is a hardware configuration diagram of the payment terminal 10 according to this embodiment.

As shown in FIG. 3, the payment terminal 10 includes a control section 11, an input device 12, an output device 13, a storage section 14, and an interface (I/F) 15 connected to a bus 16. Further, the payment terminal 10 may include other hardware configurations not shown in FIG. 3.

The control unit 11 controls the entire payment terminal 10 in an integrated manner, and includes a CPU (Central Processing Unit) that reads a program and executes payment management processing.

The input device 12 inputs various data and signals, such as a keyboard, joystick, light pen, mouse, touch pad, touch panel, trackball, etc. Further, the input device 12 functions as a reading device that reads identification information such as a card ID recorded on the payment medium 40. For example, when the payment medium 40 is an IC card or an MS card, the reading device is a card reader that can read the card ID recorded on the IC chip of the IC card or the card ID recorded on the MS of the MS card. Functions as a device.

The output device 13 outputs images and other information, such as various displays such as an LCD (Liquid Crystal Display) and an organic EL (electro-luminescence), a printer, and the like.

The storage unit 14 includes a RAM (Random Access Memory), a ROM (Read Only Memory), an HDD (Hard Disk Drive), an SSD (Solid State Drive), and the like. The storage unit 14 stores a program for the payment terminal 10 to execute payment management processing, a control program for controlling and executing each function of the payment terminal 10, screen data, and the like. The storage unit 14 provides a work area when the payment terminal 10 executes a program. Furthermore, the storage unit 14 may store other data. The application (program) of the payment terminal 10 is stored in the HDD or the like of the storage unit 14, loaded into the RAM of the storage unit 14, and executed.

The interface 15 is a unit for connecting to the payment data server 20, the card administrator terminal 30, and external equipment (not shown), such as a serial interface or parallel interface such as a USB (Universal Serial Bus) or a LAN (Local Area Network).

FIG. 4 is a hardware configuration diagram of the payment data server 20 according to this embodiment.

As shown in FIG. 4, the payment data server 20 includes a control section 21, an input device 22, an output device 23, a storage section 24, and an interface (I/F) 25 connected to a bus 26. Further, the payment data server 20 may include other hardware configurations not shown in FIG. 4.

The control unit 21 controls the entire payment data server 20 in an integrated manner, and includes a CPU that reads a program and executes payment management processing.

The input device 22 inputs various data and signals, such as a keyboard, joystick, light pen, mouse, touch pad, touch panel, trackball, etc.

The output device 23 outputs images and other information, such as various displays such as LCD and organic EL, and a printer.

The storage unit 24 includes RAM, ROM, HDD, SSD, and the like. The storage unit 24 stores a program for the payment data server 20 to execute payment management processing, a control program for controlling and executing each function of the payment data server 20, screen data, and the like. The storage unit 24 provides a work area when the payment data server 20 executes a program. The storage unit 24 also stores an identification information table, which will be described later. The application (program) of the payment data server 20 is stored in the HDD of the storage unit 24, and is loaded into the RAM of the storage unit 24 and executed.

The interface 25 is a unit for connecting to the payment terminal 10, the card administrator terminal 30, and external equipment (not shown), such as a serial interface or parallel interface such as a USB (Universal Serial Bus) or a LAN (Local Area Network).

FIG. 5 is a hardware configuration diagram of the card administrator terminal 30 according to this embodiment.

As shown in FIG. 5, the card administrator terminal 30 includes a control section 31, an input device 32, an output device 33, a storage section 34, and an interface (I/F) 35 connected to a bus 36. Further, the card administrator terminal 30 may include other hardware configurations not shown in FIG. 5.

The control unit 31 controls the entire card manager terminal 30 in an integrated manner, and includes a CPU that reads a program and executes payment management processing.

The input device 32 inputs various data and signals, such as a keyboard, joystick, light pen, mouse, touch pad, touch panel, trackball, etc.

The output device 33 outputs images and other information, such as various displays such as LCD and organic EL, and a printer.

The storage unit 34 includes RAM, ROM, HDD, SSD, and the like. The storage unit 34 stores a program for the card administrator terminal 30 to execute payment management processing, a control program for controlling and executing each function of the card administrator terminal 30, screen data, and the like. The storage unit 34 provides a work area when the card administrator terminal 30 executes a program.

The interface 35 is a unit for connecting to the payment data server 20 and an external device (not shown), such as a serial interface such as a USB (Universal Serial Bus) or a LAN (Local Area Network), or a parallel interface.

FIG. 6 is a diagram showing an example of the identification information table 240 stored in the storage unit 24 of the payment data server 20. The identification information table 240 includes a card ID, an administrator (authorizer), a balance, destination information, and payment details.

The card ID is identification information that can uniquely identify the payment medium 40. The administrator P3 (see FIG. 2) is a person who manages payments made by the user P1 (see FIG. 2) using the payment medium 40 in real time. The administrator P3 is associated with the card ID.

The balance is information (balance information) indicating the remaining amount of money that has been deposited in association with the payment medium 40 corresponding to the card ID. In this embodiment, the balance is stored not in the payment medium 40 but in the storage unit 24 of the payment data server 20, so even if the payment medium 40 is lost or stolen by the user P1, You can prevent the possibility of your balance running out.

The destination information is the contact information of the card administrator terminal 30 held by the administrator P3 of the payment medium 40. As the destination information, e-mail, telephone number, SMS, LINE (registered trademark), etc. can be used. The payment details include the products and services purchased by the user P1 through the payment terminal 10.

Next, with reference to FIG. 7, the payment management process executed by the payment terminal 10, payment data server 20, and card administrator terminal 30 that constitute the payment management system 1 will be described. FIG. 7 is a sequence chart showing an example of the payment management process executed by the payment management system 1. The payment management process is a part of the payment management method executed by the payment management system 1.

First, when the user P1 purchases a product or service, the payment terminal 10 accepts authentication using the IC card 40 (payment medium 40) (step S21). In this case, the payment terminal 10 reads the card ID from the IC card 40 (payment medium 40). When the payment terminal 10 receives authentication using the IC card 40 (payment medium 40) from the user P1, it requests the payment data server 20 to authenticate the card information (step S22). The card information authentication request includes information such as the card ID of the IC card 40 (payment medium 40) used by the user P1, the product purchased by the user, the amount, and the store name.

Upon receiving the card information authentication request from the payment terminal 10, the payment data server 20 performs card information verification (step S23). In the card information verification, it is determined whether the card ID included in the card information authentication request transmitted from the payment terminal 10 is included in the identification information table 240 stored in the storage unit 24.

If the card ID included in the information authentication request is not included in the identification information table 240 stored in the storage unit 24, the payment data server 20 determines that the card information verification is NG (step S23: NG). , sends an authentication NG notification to the payment terminal 10 (step S24). The payment terminal 10 that has received the authentication NG notification rejects the payment (step S25). When the payment refusal is accepted, the user P1 is refused (not allowed) to purchase the product or service using the payment medium 40.

If the card ID included in the information authentication request is included in the identification information table 240 stored in the storage unit 24, the payment data server 20 determines that the card information verification is OK (step S23: OK), A notification of payment details and a request for approval are sent to the card administrator terminal 30 (step S26). The payment data server 20 refers to the identification information table 240 stored in the storage unit 24 and requests notification and approval of payment details to the destination information of the card administrator terminal 30 corresponding to the card ID. The payment details notification includes the card ID, the name of the user P1, the name of the administrator P3, the name of the product or service purchased using the payment medium 40, and balance information.

The card administrator terminal 30, which has received the payment details notification and approval request, confirms the card usage details (step S27). To confirm the card usage details, the card manager terminal 30 displays a usage details approval screen on the display of the output device 33.

FIG. 8 is a diagram showing an example of the usage details approval screen 331 displayed on the output device 33 by the card administrator terminal 30. The usage content approval screen 331 displays a button 341 for accepting approval and a button 342 for not accepting approval.

The card administrator terminal 30 determines whether the usage details are approved (step S28). In this process, it is determined which of the button 341 that accepts approval displayed on the usage content approval screen 331 and the button 342 that does not accept approval has been selected.

If the selection of button 341 for accepting approval is accepted based on the operation of administrator P3 (step S28: OK), card administrator terminal 30 notifies payment data server 20 of approval OK (step S29).

Upon receiving the approval OK notification from the card administrator terminal 30, the payment data server 20 notifies the payment terminal 10 of completion of the payment (step S30). The payment terminal 10 that has received the payment completion notification completes the payment (step S31). When the payment completion is accepted, the user P1 completes the purchase of the product or service using the payment medium 40.

If the selection of the button 342 that does not accept approval based on the operation of the administrator P3 is accepted (step S28: NG), the card administrator terminal 30 notifies the payment data server 20 of the approval NG (step S32). .

Upon receiving the approval NG notification from the card administrator terminal 30, the payment data server 20 notifies the payment terminal 10 of the rejection of the payment (step S33). The payment terminal 10 that has received the payment rejection notification rejects the payment (step S34). When the payment refusal is accepted, the user P1 is refused (not allowed) to purchase the product or service using the payment medium 40.

As described above, upon receiving an approval request from the payment data server 20, the card administrator terminal 30 displays the usage details approval screen 331. Then, the card administrator terminal 30 transmits a payment completion notification to the payment terminal 10 via the payment data server 20 only when receiving an approval request from the administrator P3 of the payment medium 40. Therefore, it is possible to prevent the user P1 from using the payment medium 40 unnecessarily, and it is possible to allow children and the elderly to carry the payment medium 40 with peace of mind. Moreover, since a payment completion notification is sent immediately upon receiving the approval request from the administrator P3, the administrator P3 of the payment medium 40 can easily manage the use of the payment medium 40 in real time.

It should be noted that the present invention is not limited to the above-described embodiments as they are, but can be embodied by modifying the constituent elements without departing from the gist of the present invention at the implementation stage. Moreover, various inventions can be formed by appropriately combining the plurality of components disclosed in the above embodiments. For example, all the components shown in the embodiments may be combined as appropriate. Furthermore, components of different embodiments may be combined as appropriate. It goes without saying that various modifications and applications can be made without departing from the spirit of the invention.

1: Payment management system 10: Payment terminal 11: Control unit 12: Input device 13: Output device 14: Storage unit 15: Interface 16: Bus 20: Payment data server 21: Control unit 22: Input device 23: Output device 24: Storage section 25: Interface 26: Bus 30: Card administrator terminal 31: Control section 32: Input device 33: Output device 34: Storage section 35: Interface 36: Bus 40: Payment medium (IC card)
240: Identification information table 331: Usage details approval screen 341: Button 342: Button N: Network P1: User P2: Clerk P3: Administrator

Claims (4)

A payment management system comprising a payment terminal that accepts payments in response to a request from a payment medium, and a payment data server that is connected to the payment terminal and communicates with a payment medium administrator terminal,
The payment terminal accepts payment by the payment medium and transmits a payment request including identification information identifying the payment medium to the payment data server,
The payment data server transmits a payment request to the payment medium administrator terminal corresponding to the destination information corresponding to the identification information requested by the payment terminal,
A payment management system characterized in that, upon receiving a payment approval notification by a manager of the payment medium from the payment medium manager terminal that received the payment request, the payment result is transmitted to the payment terminal. The payment management system according to claim 1, wherein the payment medium is an IC card. The payment medium does not store balance information;
The payment management system according to claim 1 or 2, wherein the payment data server stores balance information corresponding to the identification information. Payment management performed by a payment management system that includes a payment terminal that accepts payments in response to requests from payment media, and a payment data server that is connected to the payment terminal and communicates with a payment media administrator terminal. A method,
The payment terminal accepts payment by the payment medium and transmits a payment request including identification information identifying the payment medium to the payment data server,
The payment data server transmits a payment request to the payment medium administrator terminal corresponding to the destination information corresponding to the identification information requested by the payment terminal,
A payment management method characterized in that, upon receiving a payment approval notification from a manager of the payment medium from the payment medium manager terminal that has received the payment request, a payment result is transmitted to the payment terminal.

Images