JP7673916B2 - Payment integration device, payment integration method, and payment integration program - Google Patents

Description

The present invention relates to a payment integration device, a payment integration method, and a payment integration program.

Patent document 1 discloses a technology that links two payment application software, reads a two-dimensional code of a first application with a second application, and executes a payment process using a payment method associated with the identification information of the first application via a payment SDK.

JP 2020-57392 A

However, in the invention described in Patent Document 1, the payment entity is the second application that reads the two-dimensional code, and there is a problem in that the second application cannot function as an integrated application that mediates data to the first application.

The present invention has been made in consideration of the above problems, and aims to provide a payment integration device, a payment integration method, and a payment integration program that can determine which payment application software a scanned payment code, such as a barcode or QR code (registered trademark), belongs to, and transfer the payment to that payment application software.

In order to solve the above-mentioned problems and achieve the objective, the payment integration device of the present invention is a payment integration device equipped with a memory unit and a control unit, and the control unit is characterized in that it is equipped with a code acquisition means for acquiring code data of a payment code, a payment identification means for identifying a payment service capable of paying with the payment code based on the code data, a payment execution control means for transmitting the code data to the payment service and executing the payment of the payment code, and a result acquisition means for acquiring a payment result in the payment service.

In addition, in the payment integration device according to the present invention, the storage unit includes a payment service storage means for storing payment service identification data, and the payment specification means identifies the payment service that can be used to settle the payment code by identifying the payment service coded in the payment code based on the payment service identification data and the code data.

In addition, in the payment integration device according to the present invention, the storage unit further includes a payment service storage means for storing application software for the payment service, and the payment identification means is characterized in that, when the application software is able to read the payment code based on the code data, the payment service of the application software is identified as the payment service available for the payment.

In addition, in the payment integration device according to the present invention, the payment specification means is further characterized in that it displays a selection screen on which the payment service can be selected, and specifies the selected payment service as the payment service available for payment.

In addition, in the payment integration device according to the present invention, the payment specification means, when it is not possible to automatically specify the payment service that can be used for payment, displays a selection screen on which the payment service can be selected, and specifies the selected payment service as the payment service that can be used for payment.

In addition, in the payment integration device according to the present invention, the storage unit includes a payment service storage means for storing a proxy account of the payment service, and a user storage means for storing a user account including fund data for each user, the code acquisition means further acquires user identification data of the user who read the payment code, the payment execution control means transmits the proxy account and the code data to the payment service and executes the payment of the payment code, and the result acquisition means further executes the payment process of the user who read the payment based on the payment result, the user account, and the user identification data.

In addition, in the payment integration device according to the present invention, the payment integration device is communicatively connected to a user's terminal device, the storage unit includes a payment service storage means for storing implementation data including whether or not application software for the payment service is implemented in the terminal device, the code acquisition means acquires the code data of the payment code transmitted from the terminal device, and the payment execution control means, when it determines based on the implementation data that the application software for the payment service identified by the payment identification means is implemented in the terminal device, transmits the code data to the application software implemented in the terminal device and executes the payment of the payment code.

The payment integration method according to the present invention is a payment integration method to be executed by a payment integration device having a memory unit and a control unit, and is characterized by including a code acquisition step executed by the control unit to acquire code data of a payment code, a payment identification step to identify a payment service capable of paying with the payment code based on the code data, a payment execution control step to transmit the code data to the payment service and execute the payment of the payment code, and a result acquisition step to acquire a payment result in the payment service.

The payment integration program according to the present invention is a payment integration program to be executed by a payment integration device having a memory unit and a control unit, and is characterized in that the control unit executes a code acquisition step of acquiring code data of a payment code, a payment identification step of identifying a payment service capable of paying with the payment code based on the code data, a payment execution control step of transmitting the code data to the payment service and executing the payment of the payment code, and a result acquisition step of acquiring a payment result in the payment service.

The present invention has the effect of allowing payments to be made with other payment apps within the payment application software (payment app) implemented in the user terminal. In other words, the present invention has the effect of allowing not only the payment app itself but also the integrated app of payment apps. The present invention also has the effect of allowing the results of payments made with other payment apps to be inherited and the usage history to be displayed. The present invention also has the effect of allowing any payment app to be used by registering the payment app that the user wants to use as an integrated payment app. The present invention also has the effect of allowing information linking of the QR code (registered trademark) read when the integrated app is launched.

FIG. 1 is a diagram showing an example of a payment integration process according to the present embodiment. FIG. 2 is a diagram showing an example of the payment integration process according to the present embodiment. FIG. 3 is a diagram showing an example of the payment integration process according to the present embodiment. FIG. 4 is a block diagram showing an example of the configuration of the payment integration system according to this embodiment. FIG. 5 is a flowchart showing an example of processing of the integrated payment system according to this embodiment. FIG. 6 is a diagram showing an example of the payment integration process according to the present embodiment. FIG. 7 is a diagram showing an example of the payment integration process according to the present embodiment.

An embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment.

[1. Overview]
First, an overview of the present invention will be described with reference to Figures 1 to 3. Figures 1 to 3 are diagrams showing an example of a payment integration process in this embodiment.

As shown in FIG. 1, in this embodiment, when the PayAG barcode presented at the store (biller) is read by the PayAG app, which is a payment app and integrated app implemented on the user's (purchaser's) smartphone, a payment process is executed by bank account transfer or credit card based on the user account registered in the PayAG app, and the payment result is reflected in the PayAG history.

Also, as shown in FIG. 2, in this embodiment, when the QR code (registered trademark) for Pay1 presented at a store is read by the PayAG app implemented on the user's smartphone, it is determined to be the QR code (registered trademark) for Pay1, a message is displayed on the smartphone screen indicating that PayAG payment is not possible, payment information is linked to the automatically selected Pay1, and payment processing is performed using the Pay1 balance, or payment processing by bank account transfer or credit card based on a user account registered in the PayAG app, and the payment result is reflected in the PayAG history, allowing the user to confirm the payment result for Pay1.

Also, as shown in FIG. 3, in this embodiment, when the QR code (registered trademark) for Pay2 presented at the beauty salon is read by the PayAG app implemented on the user's smartphone, it is determined to be the QR code (registered trademark) for Pay2, and a message is displayed on the smartphone screen indicating that PayAG payment is not possible. The payment information is linked to the automatically selected Pay2, and payment processing is performed using the Pay2 balance or a combined payment processing with the communication fee payment, or a payment processing by bank account transfer or credit card based on the user account registered in the PayAG app, and the payment result is reflected in the PayAG history (payment result data can be linked to PayAG), allowing the user to confirm the payment result using Pay2.

Furthermore, in this embodiment, when a QR code (registered trademark) other than PayAG that is presented at a store is read by the PayAG app implemented on the user's smartphone, it is determined to be a QR code (registered trademark) other than PayAG, and a message is displayed on the smartphone screen indicating that PayAG payment is not possible. In addition, other payment services (payment methods) that are registered in PayAG are displayed, the payment process is executed using the payment service selected by the user, and the payment result is reflected in the PayAG history, allowing the user to confirm the payment result using that payment service.

Here, in this embodiment, it may be possible to register a payment app that links with PayAG in the PayAG app. Also, in this embodiment, it may be possible to launch a payment app that has been registered and linked from within the PayAG app while the PayAG app is running. Here, as a method for launching a payment app in this embodiment, all registered payment apps may be displayed on a screen, and a payment app selected by the user may be launched from there. Also, as a method for launching a payment app in this embodiment, it may be possible to repeatedly launch registered apps in order until a payment can be made automatically. Also, as a method for launching a payment app in this embodiment, it may be possible to automatically select a payment method that can be determined from the loaded code data from registered payment apps, and launch the selected payment app.

[2. Configuration of the integrated payment system]
An example of the configuration of a payment integrated system in which a terminal device 100, a server (payment integration device) 200, and a payment service 600 according to this embodiment are communicatively connected will be described with reference to Fig. 4. Fig. 4 is a block diagram showing an example of the configuration of the payment integrated system in this embodiment.

[Configuration of terminal device 100]
In FIG. 4, the terminal device 100 may be a mobile terminal such as a mobile phone, a smartphone, a tablet terminal, a PHS, or a PDA (Personal Digital Assistant), or an information processing device such as a commercially available desktop or notebook personal computer.

The terminal device 100 includes a control unit 102, a memory unit 106, and an input/output unit 112, and each unit of the terminal device 100 is connected to each other so as to be able to communicate with each other via any communication path.

The input/output unit 112 may have a function of inputting and outputting data (I/O). Here, the input/output unit 112 may be, for example, a key input unit, a touch panel, a control pad (for example, a touch pad and a game pad), a mouse, a keyboard, and a microphone. The input/output unit 112 may also be a display unit (for example, a display, a monitor, and a touch panel made of liquid crystal or organic EL, etc.) that displays (input/output) information of application software, etc. The input/output unit 112 may also be an audio output unit (for example, a speaker, etc.) that outputs audio information as audio. The input/output unit 112 may also be an image input unit (for example, a camera, etc.) that records images (still images and videos) captured by an imaging element such as a CCD image sensor or a CMOS image sensor as digital data. The input/output unit 112 may also be a fingerprint sensor, a camera (for example, an infrared camera, etc.) that can be used for iris authentication or face authentication, etc., and/or a biosensor such as a vein sensor.

The terminal device 100 has a function of connecting to other devices via the network 300 so that they can communicate with each other, and communicating data with the other devices. Here, the network 300 has a function of connecting the terminal device 100 to other devices so that they can communicate with each other, and is, for example, the Internet and/or a LAN (Local Area Network), etc.

The storage unit 106 stores various databases, tables, and/or files. The storage unit 106 stores computer programs that work with the OS (operating system) to give commands to the CPU (central processing unit) to perform various processes. The storage unit 106 may be, for example, a RAM (random access memory), a ROM (read only memory), a HDD (hard disk drive), and/or a SSD (solid state drive). The storage unit 106 may store image data recorded in the input/output unit 112, data received via the network 300, and/or input data input via the input/output unit 112.

The control unit 102 is a CPU or the like that performs overall control of the terminal device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs. For example, the control unit 102 may execute various processes such as obtaining image data recorded in the input/output unit 112, reading character data (URL, etc.) included in the image data, sending and receiving data via the network 300, obtaining input data input via the input/output unit 112, and displaying data (screen) on the output unit 114.

[Configuration of server 200]
4, the server 200 may be an information processing device such as a personal computer or a workstation. The server 200 includes a control unit 202 and a storage unit 206, and each unit of the server 200 is connected to each other via an arbitrary communication path so as to be able to communicate with each other. The server 200 is connected to other devices via a network 300 so as to be able to communicate with each other.

The memory unit 206 stores various databases, tables, and/or files. The memory unit 206 records computer programs that work with the OS to give instructions to the CPU to perform various processes. The memory unit 206 is a storage means such as RAM, ROM, HDD, and/or SSD, and stores various databases and tables. In terms of functional concept, the memory unit 206 includes a payment service database 206a and a user database 206b.

The payment service database 206a stores payment service data of the payment service 600. Here, the payment service database 206a may store payment service identification data. The payment service database 206a may also store application software of the payment service 600. The payment service database 206a may also store a proxy account of the payment service 600 (for example, an account in which an integrated application is set as a user of the payment service 600 (payment application)). The payment service database 206a may also store implementation data including whether or not the application software of the payment service 600 is implemented in the terminal device 100. The payment service 600 may also be a code payment service such as a two-dimensional code payment service or a barcode payment service.

The user database 206b stores user data of the user of the terminal device 100. Here, the user database 206b may store a user account including raw material data for each user. Here, the raw material data may include bank account data including a transfer bank account number, etc., and/or credit card data including a credit card number, etc. In addition, the user account may include a name, an address, a telephone number, an email address, credit card data, debit card data, bank account data, prepaid data, mobile payment data, and/or a password, etc. In addition, the user data may include user identification data of the user of the terminal device 100. In addition, the user database 206b may store a usage history such as a payment history of the user. Here, the payment history may be set in association with the user, the payment service, the payment amount, and/or the payment date and time, etc.

The control unit 202 is a CPU or the like that performs overall control of the server 200. The control unit 202 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs. In terms of functional concept, the control unit 202 includes a code acquisition unit 202a, a payment specification unit 202b, a payment execution control unit 202c, and a result acquisition unit 202d.

The code acquisition unit 202a acquires code data of a payment code. Here, the code acquisition unit 202a may acquire user identification data of the user who read the payment code. The code acquisition unit 202a may also acquire code data of the payment code transmitted from the terminal device 100. The code acquisition unit 202a may also store the code data or the user identification data in the user database 206b. Here, the payment code may be a barcode or a two-dimensional code such as a QR code (registered trademark). The code data may be image data of the payment code. The code data may be read data of the payment code read by the input/output unit 112 of the terminal device 100.

The payment specification unit 202b specifies a payment service 600 that can settle the payment code. Here, the payment specification unit 202b may specify a payment service 600 that can settle the payment code based on the code data. The payment specification unit 202b may also specify a payment service 600 that can settle the payment code by identifying the payment service 600 coded in the payment code based on the payment service identification data and the code data. The payment specification unit 202b may also specify the payment service 600 of the application software as a payment service 600 that can settle when the payment code can be read by the application software based on the code data. The payment specification unit 202b may also display a selection screen that allows the payment service 600 to be selected, and specify the selected payment service 600 as a payment service 600 that can settle. The payment specification unit 202b may also display a selection screen that allows the payment service 600 to be selected, and specify the selected payment service 600 as a payment service 600 that can settle when the payment specification unit 202b cannot automatically specify a payment service 600 that can settle.

The payment execution control unit 202c transmits the code data to the payment service 600 and executes the payment of the payment code. Here, the payment execution control unit 202c may transmit the proxy account and the code data to the payment service 600 and execute the payment of the payment code. Furthermore, when the payment execution control unit 202c determines based on the implementation data that the application software of the payment service 600 identified by the payment identification unit 202b is implemented in the terminal device 100, it may transmit the code data to the application software implemented in the terminal device 100 and execute the payment of the payment code.

The result acquisition unit 202d acquires the payment result in the payment service 600. Here, the result acquisition unit 202d may execute the payment process of the read user based on the payment result, the user account, and the user identification data. In addition, the result acquisition unit 202d may update the user's usage history stored in the user database 206b based on the payment result.

[3. Processing of payment integration system]
An example of the process of the payment integrated system according to this embodiment will be described with reference to Fig. 5 to Fig. 7. Fig. 5 is a flowchart showing an example of the process of the payment integrated system according to this embodiment.

As shown in FIG. 5, the code acquisition unit 202a of the server 200 receives and acquires the code data, which is the read data of the payment code read by the user at the input/output unit 112 of the terminal device 100, and the user identification data of the user from the terminal device 100 (step SA-1).

Then, the payment identification unit 202b of the server 200 determines whether or not a payment service 600 capable of settling the payment code can be identified based on the payment service identification data and code data stored in the payment service database 206a (step SA-2).

Then, if the payment identification unit 202b of the server 200 determines that the payment service 600 can be identified (step SA-2: Yes), it transitions the process to step SA-3.

Then, the payment specification unit 202b of the server 200 specifies a payment service 600 that can settle the payment code based on the payment service identification data and the code data stored in the payment service database 206a (step SA-3), and transitions the process to step SA-5.

On the other hand, if the payment identification unit 202b of the server 200 determines that the payment service 600 cannot be identified (step SA-2: No), it transitions the process to step SA-4.

Then, the payment identification unit 202b of the server 200 displays a selection screen on the input/output unit 112 of the terminal device 100 from which a payment service 600 can be selected, receives selection data selected by the user on the selection screen, and identifies the selected payment service 600 as an available payment service 600 based on the selection data (step SA-4), and transitions the process to step SA-5.

Then, the payment execution control unit 202c of the server 200 determines whether the application software of the payment service 600 identified by the payment identification unit 202b is implemented in the terminal device 100 based on the implementation data stored in the payment service database 206a (step SA-5).

If the payment execution control unit 202c of the server 200 determines that the application software for the payment service 600 is not installed in the terminal device 100 (step SA-5: No), it transitions the process to step SA-6.

Then, the payment execution control unit 202c of the server 200 sends the proxy account of the payment service 600 stored in the payment service database 206a and the code data to the payment service 600, and executes the payment of the payment code (step SA-6).

Then, the result acquisition unit 202d of the server 200 receives and acquires the payment result from the payment service 600 (step SA-7).

Then, the result acquisition unit 202d of the server 200 executes the user's payment process based on the payment result, the user account stored in the user database 206b, and the user identification data, updates the user's usage history stored in the user database 206b (step SA-8), and ends the process.

On the other hand, if the payment execution control unit 202c of the server 200 determines that the application software for the payment service 600 is installed in the terminal device 100 (step SA-5: Yes), it transitions the process to step SA-9.

Then, the payment execution control unit 202c of the server 200 sends the code data to the application software of the payment service 600 implemented in the terminal device 100, and executes the payment of the payment code (step SA-9).

Then, the result acquisition unit 202d of the server 200 receives and acquires the payment result from the payment service 600, updates the user's usage history stored in the user database 206b based on the payment result (step SA-10), and ends the process.

Now, a specific example of the payment integration process in this embodiment will be described with reference to Figures 6 and 7. Figures 6 and 7 are diagrams showing an example of the payment integration process in this embodiment.

As shown in FIG. 6, in this embodiment, (1) the PayAG app is launched on the user's smartphone 100, and if the barcode or QR code (registered trademark) that is read is a PayAG payment code, the payment is made by PayAG, and (2) if the QR code (registered trademark) that is read is not a PayAG payment code and a common QR code (registered trademark) is available, the payment code contains information about another payment app (e.g., Pay1 or Pay2, etc.), so the code data of the read payment code and an account in which PayAG is set as a user of the other payment AP are sent to the payment AP, and the payment is made.

Here, standardization of QR codes (registered trademark) may mean that, in the QR code (registered trademark) of a payment service affiliated with PayAG and PayAG's QR code (registered trademark), information identifying a payment application that is commonly recognized by both companies is written with a specific amount of information at a specific position in the QR code (registered trademark). In other words, standardization of QR codes (registered trademark) may mean the use of JPQR or the like, which standardizes the information arrangement, information definition, information size, and information type in the QR code (registered trademark), or, when each company's QR code (registered trademark) is different for each company, coding may be performed between affiliated companies so that a payment application can be identified at a specific position in the QR code (registered trademark). For example, in this embodiment, if PayAG and Pay1 are affiliated, and a code for Pay1 payment or PayAG payment is included in a specific position in the QR code (registered trademark) between PayAG and Pay1 as payment app information, if the read QR code (registered trademark) is for Pay1 payment, the code data of this QR code (registered trademark) may be sent to Pay1 and the payment may be executed.

In this embodiment, if the QR code (registered trademark) cannot be standardized, compatible payment apps (APs) affiliated with PayAG may be displayed on a selection screen and the user may select one. Also, in this embodiment, if the selected payment AP is not compatible, the user may be prompted to select a compatible payment AP again. Also, in this embodiment, payment APs may be automatically selected in order to confirm the payment and identify a compatible payment AP. Also, in this embodiment, if there is no compatible payment AP, a message stating "Payment cannot be made with this QR code (registered trademark)" may be displayed on the user's smartphone 100.

As shown in FIG. 6, in this embodiment, (3) a payment app that is linked to the PayAG app is launched, payment is executed in the payment app, and (4) the payment result of the app payment is linked to the PayAG app.

Also, as shown in FIG. 7, in this embodiment, (1) the PayAG app is launched, (2) if the read QR code (registered trademark) is not the PayAG payment code but the Pay1 payment code, compatible payment APs affiliated with PayAG are displayed on the screen and the user is prompted to select Pay1. Then, as shown in FIG. 7, in this embodiment, (3) the Pay1 app affiliated with PayAG is launched, the user is prompted to read the Pay1 QR code (registered trademark), payment is made with Pay1, and (4) the payment result of the Pay1 payment is linked to the PayAG app.

4. Other embodiments
The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including search conditions and other parameters, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

Furthermore, with regard to the terminal device 100, server 200, etc., each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the terminal device 100 and the server 200, etc., and in particular the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the terminal device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the terminal device 100, the server 200, etc. via an arbitrary network 300, and it is also possible to download all or part of it as needed.

In addition, the program for executing the processing described in this embodiment may be stored on a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile This includes any "portable physical media" such as a DVD (registered trademark) or Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

The various databases stored in the memory unit are storage devices such as RAM, ROM, etc., fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

The terminal device 100 and the server 200 may be configured as a known information processing device such as a personal computer or a workstation, or may be configured as the information processing device to which any peripheral device is connected. The terminal device 100 and the server 200 may be realized by implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

The present invention is useful in the financial industry, where mobile payment services are conducted.

100 Terminal device 102 Control unit 106 Storage unit 112 Input/output unit 200 Server 202 Control unit 202a Code acquisition unit 202b Payment specification unit 202c Payment execution control unit 202d Result acquisition unit 206 Storage unit 206a Payment service database 206b User database 300 Network 600 Payment service

Claims (8)

A payment integration device including a storage unit and a control unit,
The storage unit is
a payment service storage means for storing application software for a payment service;
Equipped with
The control unit is
A code acquisition means for acquiring code data of a payment code;
a payment identification means for identifying the payment service of the application software as an available payment service when the payment code can be read by the application software based on the code data;
a payment execution control means for transmitting the code data to the payment service and executing the payment of the payment code;
A result acquisition means for acquiring a payment result in the payment service;
A payment integration device comprising: The payment service storage means includes:
Store the payment service identification data;
The payment identification means is
The payment integration device described in claim 1 , further characterized in that the payment service coded in the payment code is identified based on the payment service identification data and the code data, thereby specifying the payment service that can be used to pay the payment code. The payment identification means is
The payment integration device according to claim 1 or 2 , further comprising: displaying a selection screen on which the payment service can be selected; and identifying the selected payment service as the payment-available payment service. The payment identification means is
The payment integration device described in claim 3, characterized in that if the payment service that can be used for payment cannot be automatically identified, a selection screen on which the payment service can be selected is displayed, and the payment service selected is identified as the payment service that can be used for payment. The payment service storage means includes:
Furthermore, a proxy account of the payment service is stored ;
The storage unit is
A user storage means for storing a user account including resource data for each user;
Equipped with
The code acquisition means includes:
Furthermore, the user identification data of the user who reads the payment code is obtained,
The payment execution control means
Transmitting the proxy account and the code data to the payment service to execute payment of the payment code;
The result acquisition means includes:
The payment integration device according to claim 1 , further comprising: a payment processing unit for executing a payment process for the read user based on the payment result, the user account, and the user identification data. The payment integration device includes:
communicatively connected to a terminal device of a user;
The payment service storage means includes:
Furthermore, storage of implementation data including whether or not the application software of the payment service is implemented in the terminal device;
The code acquisition means includes:
Acquire the code data of the payment code transmitted from the terminal device;
The payment execution control means
The payment integration device of claim 1, further characterized in that when it is determined based on the implementation data that the application software of the payment service identified by the payment identification means is implemented in the terminal device, the code data is sent to the application software implemented in the terminal device, and payment of the payment code is executed. A payment integration method to be executed by a payment integration device having a storage unit and a control unit,
The storage unit is
a payment service storage means for storing application software for a payment service;
Equipped with
Executed by the control unit,
a code acquisition step for acquiring code data of a payment code;
a payment identification step of identifying the payment service of the application software as an available payment service when the payment code can be read by the application software based on the code data;
a payment execution control step of transmitting the code data to the payment service and executing the payment of the payment code;
A result acquisition step of acquiring a payment result in the payment service;
A payment integration method comprising: A payment integration program to be executed by a payment integration device having a storage unit and a control unit,
The storage unit is
a payment service storage means for storing application software for a payment service;
Equipped with
In the control unit,
a code acquisition step for acquiring code data of a payment code;
a payment identification step of identifying the payment service of the application software as an available payment service when the payment code can be read by the application software based on the code data;
a payment execution control step of transmitting the code data to the payment service and executing the payment of the payment code;
A result acquisition step of acquiring a payment result in the payment service;
Payment integration program to execute the above.

Images