Information processing method, information processing program, and information processing apparatus

Abstract

To provide an information processing method, an information processing program, and an information processing apparatus for transmitting issue information of a printable check.SOLUTION: An information processing method includes: receiving an issuance request including a drawer ID and an amount; determining whether a financial account associated with the drawer ID exists; generating check issuance information including the amount when it is determined that the financial account exists; and executing a process to transmit the issuance information in order to print a check.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present invention relates to an information processing method, an information processing program, and an information processing device for transmitting check issuance information. [Background technology]

[0002] With the spread of electronic payment systems, checks, which have traditionally been handled as paper media, are also being digitized. For example, Patent Document 1 proposes an electronic payment system that handles electronic checks. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2003-233717 Summary of the Invention [Problem to be solved by the invention]

[0004] However, electronic checks cannot be used at stores that have not introduced electronic payment systems, and it is not practical from the standpoint of convenience to require end users to use both paper checks and electronic checks.

[0005] The present invention has been made in light of these circumstances, and its purpose is to provide an information processing method, information processing program, and information processing device for transmitting printable check issuance information. [Means for solving the problem]

[0006] An information processing method according to one embodiment of the present application receives an issuance request including an issuer ID and an amount, determines whether a financial account associated with the issuer ID exists, and if it is determined that the financial account exists, generates check issuance information including the amount and executes a process of sending the issuance information to print the check. [Effects of the Invention]

[0007] In one aspect of the present invention, it is possible to transmit printable check issuance information. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is an explanatory diagram showing an example of the configuration of a payment system. [Figure 2] FIG. 2 is a block diagram illustrating an example of a hardware configuration of a server. [Figure 3] FIG. 2 is a block diagram showing an example of the hardware configuration of a store terminal. [Figure 4] FIG. 2 is a block diagram illustrating an example of the hardware configuration of a user terminal. [Figure 5] FIG. 10 is an explanatory diagram illustrating an example of a user DB; [Figure 6] FIG. 2 is an explanatory diagram illustrating an example of a store DB. [Figure 7] FIG. 10 is an explanatory diagram showing an example of a check database. [Figure 8] FIG. 10 is an explanatory diagram showing an example of a cash-out DB. [Figure 9] FIG. 10 is an explanatory diagram showing an example of a check database. [Figure 10] 10 is a flowchart illustrating an example of a procedure for a chord display process. [Figure 11] 10 is a flowchart showing an example of the check issuance process. [Figure 12] 10 is a flowchart showing an example of a procedure for cashing out. [Figure 13] FIG. 10 is an explanatory diagram showing an example of an issuance setting screen. [Figure 14] FIG. 10 is an explanatory diagram showing an example of a presentation screen. [Figure 15] FIG. 1 is an explanatory diagram showing an example of a check. [Figure 16] 10 is a flowchart illustrating an example of a procedure for issuing a history list process. [Figure 17] FIG. 10 is an explanatory diagram showing an example of an issuance history list screen. [Figure 18] 10 is a flowchart illustrating an example of a procedure for processing a receipt history list. [Figure 19]FIG. 10 is an explanatory diagram showing an example of a receipt history list screen. DETAILED DESCRIPTION OF THE INVENTION

[0009] An embodiment will be described below with reference to the drawings. Figure 1 is an explanatory diagram showing an example of the configuration of a payment system. Payment system 100 includes server 1 (information processing device), store terminal 2, user terminal 3 (issuer terminal), and accounting system 4. Server 1, store terminal 2, and user terminal 3 are communicably connected to each other via network N. Server 1 and accounting system 4 are operated by the same financial institution or the same financial group, and are communicably connected via a dedicated network or VPN (Virtual Private Network). Although only one store terminal 2 and one user terminal 3 are shown in Figure 1, there may be two or more of each.

[0010] Server 1 manages the issuing and cashing of checks. Server 1 is composed of a server computer, a workstation, a PC (Personal Computer), etc. Server 1 may also be composed of a multi-computer consisting of multiple computers, a virtual machine virtually constructed by software, or a quantum computer. Furthermore, the functions of Server 1 may be realized by a cloud service.

[0011] The store terminal 2 is a terminal installed in a store that provides products or services to consumers. The store terminal 2 is configured as a POS (Point of Sale) terminal. The store terminal 2 may also be configured as a laptop computer, tablet computer, smartphone, etc. equipped with a payment function.

[0012] A printer PRN and a code reader CR are connected to the store terminal 2. If the store terminal 2 is equipped with a receipt printer, the printer PRN is not necessary. The printer PRN prints checks. To ensure the durability of printed checks, it is preferable that the printer PRN be a thermal transfer printer, dot impact printer, inkjet printer, or laser printer rather than a thermal printer that prints on thermal paper. The code reader CR reads barcodes and two-dimensional codes and sends the information embedded in the codes to the store terminal 2.

[0013] The user terminal 3 is a computer used by a consumer, and may be a smartphone, a tablet computer, a laptop computer, or the like.

[0014] The accounting system 4 operates a deposit ledger in a financial institution and provides services to consumers who have opened accounts. The accounting system 4 also controls connections to an ATM (Automated Teller's Machine) network.

[0015] The payment system 100 is communicatively connected to the banking system 5. The banking system 5 is assumed to be operated by a financial institution separate from the financial institution that operates the server 1 and the accounting system 4. By cooperating with the payment system 100, the financial institution that operates the banking system 5 is able to issue checks described in this specification to customers. Although not shown in Figure 1, the payment system 100 may also cooperate with an electronic check clearing house or a Zengin system to handle checks.

[0016] 2 is a block diagram showing an example of the hardware configuration of the server 1. The server 1 includes a control unit 11, a main memory unit 12, an auxiliary memory unit 13, a communication unit 14, and a reading unit 15. The control unit 11, the main memory unit 12, the auxiliary memory unit 13, the communication unit 14, and the reading unit 15 are connected by a bus B.

[0017] The control unit 11 has one or more arithmetic processing devices such as a central processing unit (CPU), a micro-processing unit (MPU), a graphics processing unit (GPU), etc. The control unit 11 reads and executes a control program 1P (program, program product) stored in the auxiliary storage unit 13, thereby performing various information processing, control processing, etc. related to the server 1 and realizing various functional units.

[0018] The main memory unit 12 is a static random access memory (SRAM), a dynamic random access memory (DRAM), a flash memory, etc. The main memory unit 12 mainly temporarily stores data required for the control unit 11 to execute arithmetic processing.

[0019] The auxiliary storage unit 13 is a hard disk or SSD (Solid State Drive), etc., and stores the control program 1P and various DBs (Databases) required for the control unit 11 to execute processing. The auxiliary storage unit 13 stores a user DB 131, a store DB 132, a check DB 133, and a cashing DB 134. The auxiliary storage unit 13 may be separate from the server 1 and may be an external storage device connected externally. The various DBs, etc. stored in the auxiliary storage unit 13 may be stored in a database server or cloud storage different from the server 1.

[0020] The communication unit 14 communicates with the store terminal 2 and the user terminal 3 via the network N. The communication unit 14 also communicates with the accounting system 4 via a dedicated line or VPN. The control unit 11 may use the communication unit 14 to download the control program 1P from another computer via the network N or the like, and store it in the auxiliary storage unit 13.

[0021] The reading unit 15 reads the portable storage medium 1a including a CD (Compact Disc)-ROM and a DVD (Digital Versatile Disc)-ROM. The control unit 11 may read the control program 1P from the portable storage medium 1a via the reading unit 15 and store it in the auxiliary storage unit 13. The control unit 11 may also read the control program 1P from the semiconductor memory 1b.

[0022] 3 is a block diagram showing an example of the hardware configuration of the store terminal 2. The store terminal 2 includes a control unit 21, a main memory unit 22, an auxiliary memory unit 23, a communication unit 24, a display panel 25, an operation unit 26, and a serial communication unit 27. Each unit is connected via a bus B.

[0023] The control unit 21 has one or more arithmetic processing units such as a CPU, an MPU, a GPU, etc. The control unit 21 provides various functions by reading and executing a control program 2P (program, program product) stored in the auxiliary storage unit 23.

[0024] The main memory unit 22 is an SRAM, a DRAM, a flash memory, etc. The main memory unit 22 mainly temporarily stores data necessary for the control unit 21 to execute arithmetic processing.

[0025] The auxiliary memory unit 23 is a hard disk or SSD, and stores various data necessary for the control unit 21 to execute processing. The auxiliary memory unit 23 also stores issuance information for printing checks for a predetermined period of time. The auxiliary memory unit 23 may be an external storage device that is separate from the store terminal 2 and externally connected. The various databases and other data stored in the auxiliary memory unit 23 may also be stored on a database server or cloud storage.

[0026] The communication unit 24 communicates with the server 1 via the network N. In addition, the control unit 21 may use the communication unit 24 to download the control program 2P from another computer via the network N or the like, and store it in the auxiliary storage unit 23.

[0027] Display panel 25 can be configured with a liquid crystal panel, an organic EL (Electro Luminescence) display, or the like. Operation unit 26 can be configured with, for example, a touch panel incorporated in display panel 25, allowing a store clerk to perform predetermined operations on display panel 25. Operation unit 26 can also be used to perform operations on a software keyboard displayed on display panel 25. Operation unit 26 may also be a hardware keyboard, numeric keypad, mouse, or the like.

[0028] The serial communication unit 27 is a communications interface that performs serial communications. The serial communication unit 27 performs wired communications in accordance with the USB (Universal Serial Bus) standard, or wireless communications in accordance with the Bluetooth (registered trademark) standard. The serial communication unit 27 communicates with the printer PRN and prints checks based on the issuance information received from the server 1. The serial communication unit 27 also communicates with the code reader CR, obtaining barcode or two-dimensional code images or information embedded in the codes from the code reader CR.

[0029] 4 is a block diagram showing an example of the hardware configuration of a user terminal 3. The user terminal 3 includes a control unit 31, a main memory unit 32, an auxiliary memory unit 33, a communication unit 34, a display panel 35, and an operation unit 36. Each unit is connected via a bus B.

[0030] The control unit 31, main memory unit 32, auxiliary memory unit 33, communication unit 34, display panel 35, and operation unit 36 ​​have the same configuration as the control unit 21, main memory unit 22, auxiliary memory unit 23, communication unit 24, display panel 25, and operation unit 26 of the store terminal 2, respectively, and therefore their explanation will be omitted.

[0031] Next, the databases used in the payment system 100 will be described. Figure 5 is an explanatory diagram showing an example of a user DB. The user DB 131 stores information on financial accounts held by users. The user DB 131 includes a user ID column, a number column, a financial institution code column, a branch number column, a type column, an account number column, and an account holder name column. The user ID column stores a user ID that can uniquely identify a user. The number column stores the sequential number of the financial account. If a user has multiple financial accounts, the sequential numbers make it possible to distinguish between them. The financial institution code column stores the financial institution code of the financial institution where the financial account is opened. The branch number column stores the branch code of the branch where the financial account is opened. The type column stores the type of financial account. For example, types include ordinary, fixed-term, savings, current, etc. The account number column stores the account number of the financial account. The account holder name column stores the name of the account holder who holds the financial account. It is assumed that the account holder is the same person as the user, so the account holder's name is the user's name.

[0032] Figure 6 is an explanatory diagram showing an example of a store DB. Store DB 132 stores information on financial accounts held by stores. Store DB 132 includes a store ID column, a store name column, a number column, a financial institution code column, a branch number column, a type column, and a store account number column. The store ID column stores a store ID that can uniquely identify a store within a financial institution. The store name column stores the name of the store. The number column stores the sequential number of the financial account. If a store has multiple financial accounts, they can be distinguished by the sequential number. The financial institution code column stores the financial institution code of the financial institution where the financial account is opened. The branch number column stores the branch code of the branch where the financial account is opened. The type column stores the type of financial account. The store account number column stores the account number of the financial account.

[0033] Figure 7 is an explanatory diagram showing an example of a check DB. Check DB 133 stores information about issued checks. Check DB 133 includes a check ID column, an issue date and time column, a user ID column, a number column, a store ID column, an amount column, and an uncashed column. The check ID column stores a check ID that can uniquely identify a check. The issue date and time column stores the date and time when the issuance information for printing the check was created. This date and time corresponds to the issuance date and time for a traditional check. The user ID column stores the user ID (issuer ID) of the user who requested the issuance of the check. This user corresponds to the issuer for a traditional check. The number column stores the sequential number of the financial account specified by the user. The values ​​in the number column correspond to the values ​​stored in the number column in user DB 131. The store ID column stores the store ID of the store that will be the recipient of the check. The recipient store is the store specified by the user. The amount column stores the amount of the check. The Uncashed column stores whether the check has been cashed. For example, if the check has not been cashed, the Uncashed column stores "Not Cashed," and if the check has been cashed, the Uncashed column stores "Cashed." If the check has been cashed, the date and time of cashing may also be stored in the Uncashed column.

[0034] Figure 8 is an explanatory diagram showing an example of a cashing DB. The cashing DB 134 stores the cashing history of checks. The cashing DB 134 includes a check ID column, an amount column, a cashing date and time column, a store ID column, a financial institution code column, a store number column, a type column, and an account number column. The check ID column stores the check ID of the cashed check. The amount column stores the check amount. The cashing date and time column stores the date and time the check was cashed. The store ID column stores the store ID of the store designated as the recipient of the check. Values ​​are stored in the financial institution code column through the account number column when the recipient does not receive cash when the check is cashed, but requests that the money be deposited into a financial account. The financial institution code column stores the financial institution code of the financial institution where the received financial account is opened. The store number column stores the store number of the financial account. The type column stores the type of financial account. The account number column stores the account number of the financial account.

[0035] Figure 9 is an explanatory diagram showing an example of a check DB. The check DB 231 stores information about checks received by the store terminal 2. The check DB 231 is stored in the auxiliary memory unit 23 of the store terminal 2. The check DB 231 includes a check ID column, an issue date and time column, an amount column, a print column, a print deadline column, and an image column. The check ID column stores the check ID. The issue date and time column stores the date and time the check was issued. The amount column stores the check amount. The print column stores whether the check has been printed. For example, if the check has not been printed, the print column stores 0. If the check has already been printed, the print column stores 1. The print deadline column stores the deadline for printing. The image column stores the image of the check to be used for printing.

[0036] The print column, print deadline column, and image column are not required in the check DB 231. This is because if the store terminal 2 prints the check using the printer PRN immediately after receiving the information for printing the check (issuance information) from the server 1, this information is unnecessary. Note that if reprinting is permitted if a printed check is lost, the print column may store the number of times it has been printed. To avoid fraud and confusion, the number of times it can be printed may be limited. The print deadline sets the deadline by which the check can be printed, including reprints. Setting a deadline is also to avoid fraud and confusion. If the limit on the number of times it can be printed is reached or the print deadline has passed, the images stored in the image column may be deleted.

[0037] The check DB 231 is not required for the store terminal 2. This is because if the store terminal 2 prints the check using the printer PRN immediately upon receiving the information for printing the check (issuance information) from the server 1, there is no need to store the issuance information. If you want to check a list of checks received at the store, you can create a list from the check DB 133 stored in the server 1.

[0038] Next, the processing performed by the payment system 100 will be described. FIG. 10 is a flowchart showing an example of the procedure for the code display processing. The code display processing is processing performed when a user requests the issuance of a check. The user operates the user terminal 3 to select a financial account to use for payment and enter the check amount. The control unit 31 of the user terminal 3 accepts the sequential number and amount of the selected financial account (step S1). The sequential number of the financial account is a number stored in the number string of the user DB 131. The control unit 31 creates a two-dimensional code (step S2). The two-dimensional code includes information such as the user ID, the sequential number of the financial account, and the amount. The control unit 31 displays the created two-dimensional code on the display panel 35 (step S3). The control unit 31 ends the processing. The user informs the clerk that they will be paying by check and presents the two-dimensional code. Note that if the user holds only one financial account to use for payment, the sequential number of the financial account does not need to be embedded in the two-dimensional code.

[0039] FIG. 11 is a flowchart showing an example of the check issuance process. In the check issuance process, server 1 issues a check in accordance with a user request and provides it to store terminal 2. The store clerk operates store terminal 2 to switch to check payment mode and prepares to read the two-dimensional code. After preparation is complete, the store clerk reads the two-dimensional code presented by the user with code reader CR. Control unit 21 of store terminal 2 acquires the two-dimensional code (step S11). Control unit 21 sends a check issuance request to server 1, including the user ID, financial account sequence number and amount embedded in the two-dimensional code, and store ID (step S12). Note that if the financial account sequence number is not embedded in the two-dimensional code, the sequence number is assumed to be 1. Control unit 11 of server 1 receives the issuance request (step S13). Based on the issuance request, control unit 11 sends an inquiry to accounting system 4 (step S14). The control unit 11 searches the user DB 131 using the user ID and sequence number included in the issuance request as keys, and obtains information on the financial account specified by the user (financial institution code, branch code, type, and account number). The control unit 11 makes an inquiry including the obtained financial account information. If it is necessary to make an inquiry to another financial institution based on the financial institution code, the control unit 11 makes an inquiry to the banking system 5 operated by the other financial institution. In the following explanation, it is assumed that an inquiry is made to the accounting system 4. The accounting system 4 receives the inquiry (step S15). The accounting system 4 verifies whether the account specified by the branch code, type, and account number included in the inquiry validly exists (step S16). The accounting system 4 sends the confirmation result to the server 1 (step S17). The control unit 11 of the server 1 receives the confirmation result (step S18). The control unit 11 determines whether the financial account specified by the user validly exists based on the received confirmation result (step S19). If the control unit 11 determines that the financial account is valid and exists (YES in step S19), it issues the check (step S20). The control unit 11 issues a check ID and creates the check. The check information is stored in the check DB 133 (step S21). The issue date and time is the date and time the check information was stored in the check DB 133. The value in the uncashed column is set to a value indicating that the check has not been cashed.The control unit 11 creates issuance information including the check ID, issuance date and time, and amount, and sends it to the store terminal 2 (step S22).

[0040] If the accounting system 4 can confirm that the user's financial account exists, it may check the balance of that account. If the account balance is less than the check amount, the control unit 11 of the server 1 may not issue the check.

[0041] In the above explanation, the user DB 131 is searched using the user ID and sequence number as keys to obtain information on the financial account specified by the user (financial institution code, branch code, type, and account number), but this is not limited to this. The information on the financial account specified by the user may be embedded in the two-dimensional code created in the code display process. In this case, the financial account information is obtained by the store terminal 2 and transmitted to the server 1.

[0042] The issuing information may include a user ID. The issuing information may also include a two-dimensional code that embeds at least the check ID and additional information, such as the date and time of issue and the amount. It may also include a uniform resource locator (URL) for a website that describes how to cash the check, a URL for a website that guides or searches for ATMs or financial institution branches near the store, or a two-dimensional code that embeds these URLs. The issuing information may also include a two-dimensional code that allows the amount obtained by cashing the check to be remitted directly via online banking. For example, when the two-dimensional code is scanned into a terminal running an online banking application program, a screen appears in which the remittance destination is not set but the remittance amount is set. An image file for printing that includes the above information may also be used as the issuing information. Furthermore, a PostScript file, GPD file, or EMF (Enhanced Metafile) file that can be accepted by the printer PRN may be sent to the store terminal 2 as the issuing information. Even when sending an image file, PostScript file, GPD file, or EMF file to the store terminal 2 as issuance information, it is desirable to add text data such as the check ID, issuance date and time, amount, and user ID as file attributes.

[0043] The control unit 21 of the store terminal 2 receives the issuance information (step S23). The control unit 21 causes the printer PRN to print the check based on the issuance information (step S24), and then ends the process. If the store terminal 2 is equipped with a check DB 231, the issuance information is stored in the check DB 231. The printing deadline is a predetermined period from the date and time of issue or the date and time of receipt of the issuance information. The deadline time may be 11:59 p.m., regardless of the time of issue or receipt. It is desirable to use anti-counterfeit paper on which the word "copy" or similar appears when the check is printed.

[0044] Before transmitting the issuance information from the server 1 to the store terminal 2, all or part of the issuance information may be transmitted to the user terminal 3 for confirmation by the user. If the user confirms the content and permits transmission, the server 1 transmits the issuance information to the store terminal 2. If the user does not permit transmission, the issuance information is not transmitted to the store terminal 2, and the server 1 transmits to the store terminal 2 a message indicating that issuance is not permitted.

[0045] If the control unit 11 determines that a valid financial account does not exist (NO in step S19), it sends a notice that the check cannot be issued to the store terminal 2 (step S25). The control unit 21 of the store terminal 2 receives the notice that the check cannot be issued (step S26). The control unit 21 displays that the check cannot be issued on the display panel 25 (step S27) and ends the process. The store clerk confirms that the check cannot be issued, informs the user that payment by check is not possible, and encourages them to use another payment method.

[0046] FIG. 12 is a flowchart showing an example of the cashing process. Cashing is a process executed by the payment system 100 when a store clerk attempts to cash a printed check. In the process example shown in FIG. 12, the check is cashed using an ATM (Automated Teller Machine). The ATM is assumed to have the functionality to accept cashing. The clerk brings the check to the ATM section. The clerk operates the ATM to switch to check cashing mode. The clerk has the ATM read the two-dimensional code on the check. The ATM acquires the two-dimensional code (step S41). The ATM analyzes the two-dimensional code and restores the embedded check information (check ID, issue date and amount, and user ID) (step S42). The ATM sends a cashing request including the restored check information to the accounting system 4 (step S43). If the ATM cannot read the two-dimensional code, the clerk may input the check ID, issue date and amount, and user ID into the ATM. The accounting system 4 receives the cashing request (step S44). The accounting system 4 sends an inquiry including the check information to the server 1 (step S45). The control unit 11 of the server 1 receives the inquiry (step S46). The control unit 11 determines whether the check identified by the check information is cashable based on the check information. The control unit 11 confirms that data matching the check information is stored in the check DB 133. It also confirms whether the stored check is uncashed. The control unit 11 sends the confirmation result to the accounting system 4 (step S47). If the check is valid but uncashed, the control unit 11 sends a confirmation result indicating that cashing is permitted; otherwise, it sends a confirmation result indicating that cashing is not permitted. The accounting system 4 receives the confirmation result (step S48). Based on the confirmation result, the accounting system 4 determines whether or not to permit the withdrawal (step S49). If the confirmation result indicates that cashing is permitted, the accounting system 4 determines that the withdrawal is permitted. If the confirmation result indicates that the check is not cashable, the accounting system 4 determines that the withdrawal is not permitted. If the accounting system 4 determines that the withdrawal is permitted (YES in step S49), it sends a withdrawal instruction to the ATM (step S50). The ATM receives the withdrawal instruction (step S51). The ATM dispenses the amount of the check (step S52).The clerk withdraws cash from the ATM. The ATM sends a notification of withdrawal completion to accounting system 4 (step S53). Accounting system 4 receives the notification of completion (step S54). Accounting system 4 updates the account balance of the user corresponding to the check (step S55). Accounting system 4 sends a notification of completion to server 1 (step S56). Control unit 11 of server 1 receives the notification of completion (step S57). Control unit 11 updates the value in the uncashed column of the record in check DB133 corresponding to the cashed check to a value indicating that it has been cashed (step S58), and ends the process.

[0047] If the accounting system 4 determines that withdrawal is not permitted (NO in step S49), it sends a withdrawal denial notice to the ATM (step S59). The ATM receives the withdrawal denial notice (step S60). The ATM displays a message that the check cannot be cashed (step S61) and ends the process. If the control unit 11 of the server 1 determines that cashing is not permitted, it may send the reason for denial to the ATM via the accounting system 4 and present it to the clerk.

[0048] In the cash conversion process shown in Figure 12, cash is withdrawn from an ATM, but this is not a limitation. Cash may also be deposited into an account designated by a clerk rather than being withdrawn from the ATM. The clerk inputs the deposit account information into the ATM. Alternatively, the ATM may obtain the deposit account information by scanning a cash card or passbook. Alternatively, the two-dimensional code may be scanned by a terminal capable of online banking, and the money may be deposited into the designated account via online banking. Cash conversion may also be performed at a financial institution's counter, just like with conventional checks.

[0049] The check 133DB on the server 1 stores the store ID of the store where the check was issued, but does not verify whether the person bringing the check is a store employee or other such person during the cashing process. As with conventional checks, the bearer can cash the check. A check with a designated payee, like a registered check, may also be used. In this case, for example, the ATM can scan the bankbook or cash card of an account held by the store to verify whether the bearer is a store employee or not.

[0050] Next, examples of screens displayed on the user terminal 3 are shown. FIG. 13 is an explanatory diagram showing an example of an issuance settings screen. The issuance settings screen d01 is a screen for entering settings for the check to be issued. For example, the issuance settings screen d01 is displayed when the check issuance menu in the main menu of online banking is selected. The issuance settings screen d01 includes an amount field d011, an account display d012, a selected radio button d013, an unselected radio button d014, and a next button d015. The amount of the check to be issued is set in the amount field d011. The account display d012 stores information about the account held by the user. If the user holds multiple accounts, the account display d012 is displayed repeatedly. The account display d012 includes a deposit type d0121, a branch name d0122, an account number d0123, and a balance d0124. The deposit type d0121 displays the type of account. If the account is the same as the previous account, the deposit type d0121 is omitted. The branch name d0122 displays the name of the branch where the account is located. The account number d0123 displays the account number. The balance d0124 displays the balance of the account. The selected radio button d013 indicates that the corresponding account has been selected as the check payment account. The unselected radio button d014 indicates that the corresponding account has not been selected as the check payment account. Selecting the next button d015 will transition to the presentation screen. Note that the sequential number value stored in the number column of the user DB131 assigned to each account displayed on the issuance setting screen d01 is obtained from the server 1 when the issuance setting screen d01 is created, or is stored in advance in the user terminal 3.

[0051] FIG. 14 is an explanatory diagram showing an example of a presentation screen. Presentation screen d02 is a screen displayed by the code display process. This is an explanatory diagram showing an example of presentation screen d02. Presentation screen d02 includes type d021, account d022, amount d023, two-dimensional code d024, and close button d025. Type d021 displays the type of payment account, and account d022 displays the branch name and account number of the payment account. Amount d023 displays the face value of the check. Two-dimensional code d024 is a two-dimensional code that is read by the store terminal 2. When the close button d025 is selected, presentation screen d02 is closed and the screen returns to the main menu.

[0052] Figure 15 is an explanatory diagram showing an example of a check. The check shown in Figure 15 is an example of a check printed by a printer PRN connected to the store terminal 2. The check includes a bank name 151, a user ID 152, an amount 153, an issue date 154, a store name 155, and a two-dimensional code 156. The bank name 151 indicates the bank that issued the check. The user ID 152 indicates the user ID of the user who issued the check. The amount 153 indicates the amount to be paid if the check is cashed. The issue date 154 indicates the date the check was issued. The time may also be displayed. The store name 155 indicates the name of the store that received the check. The two-dimensional code 156 is a two-dimensional code in which information for cashing is embedded. At least the check ID is embedded in the two-dimensional code 156.

[0053] The check may be printed with the URL of a website that describes how to cash the check, the URL of a website that guides or searches for ATM corners or financial institution branches near the store, or a two-dimensional code that embeds these URLs.

[0054] The following configuration may be adopted to prevent the two-dimensional code d024 presented by the user from being misused. An expiration date may be embedded in the two-dimensional code d024 displayed on the presentation screen d02, and an error may be generated if the store terminal 2 reads an expired two-dimensional code d024. The control unit 31 of the user terminal 3 may display an encrypted two-dimensional code d024. The two-dimensional code d024 may be decrypted by the store terminal 2. The two-dimensional code d024 may be transmitted to the server 1, and the control unit 11 of the server 1 may decrypt it. The control unit 31 of the user terminal 3 may embed encrypted information in the two-dimensional code d024. The encrypted information extracted from the two-dimensional code d024 may be decrypted in the store terminal 2, or the encrypted information may be transmitted to the server 1, and the control unit 11 of the server 1 may decrypt it.

[0055] Next, the check history display function will be explained. Figure 16 is a flowchart showing an example of the procedure for issuing history listing processing. Issuance history listing processing is processing that displays a list of checks issued based on a user request. The user selects check list from the main menu. The control unit 31 of the user terminal 3 accepts the selection and sends a list request to the server 1 (step S71). The control unit 11 of the server 1 receives the request (step S72). The control unit 11 acquires the user's check information from the check DB 133 (step S73). The control unit 11 acquires cashing information corresponding to the acquired check information from the cashing DB 134 (step S74). The control unit 11 creates a list and sends it to the user terminal 3 (step S75). The control unit 31 of the user terminal 3 receives the list (step S76). The control unit 31 displays the list (step S77) and ends the processing.

[0056] The check information and cashing information sent to the user terminal 3 may be a portion of the information obtained from the check DB 133 and a portion of the information obtained from the cashing DB 134, respectively. Of the cashing information, the values ​​of the financial institution code string, branch number string, type string, and account number string are not sent to the user terminal 3.

[0057] Figure 17 is an explanatory diagram showing an example of the issuance history list screen. The issuance history list screen d03 displays information about issued checks. For each check, the issuance history list screen d03 displays the check ID d031, issue date and time d032, recipient d033, amount d034, and cashing date d035. The check ID d031 indicates the check ID. The issue date and time d032 indicates the date and time the check was issued. The recipient d033 indicates the name of the store that obtained the check issuance information. The amount d034 indicates the amount of the check. The cashing date d035 indicates the date the check was cashed.

[0058] FIG. 18 is a flowchart showing an example of the procedure for processing the receipt history list. The receipt history list process displays a list of checks received by a store. A store clerk operates the store terminal 2 to select a check list from a menu. The control unit 21 of the store terminal 2 accepts the selection and sends a list request to the server 1 (step S91). The control unit 11 of the server 1 receives the request (step S92). The control unit 11 acquires the check information sent to the store from the check DB 133 (step S93). The control unit 11 acquires the cashing information corresponding to the acquired check information from the cashing DB 134 (step S94). The control unit 11 creates the check information and cashing information and sends them to the store terminal 2 (step S95). The control unit 21 of the store terminal 2 receives the check information and cashing information (step S96). The control unit 21 creates a list (step S97). At that time, the control unit 21 also references the information stored in the check DB 231. The control unit 21 displays the created list (step S98), and ends the process.

[0059] Figure 19 is an explanatory diagram showing an example of the receipt history list screen. The receipt history list screen d04 displays information about received checks. For each check, the receipt history list screen d04 displays the issue date and time d041, user name d042, amount d043, print status d044, and cash status d045. The issue date and time d041 indicates the date and time the check was issued. The user name d042 indicates the name of the user who issued the check. The amount d043 indicates the amount of the check. The print status d044 indicates the printing status of the check. If the check was printed using the PRN printer, the print date is displayed. If the check has not yet been printed, it indicates that it is not printed, and if a printing deadline has been set, the deadline is displayed. The cash status d045 indicates the cash status. If the check has already been cashed, it indicates the cashing date. If the check has not yet been cashed, it indicates that it is not cashed and displays the cashing deadline.

[0060] On the receipt history list screen d04, when an unprinted check is selected by tapping or the like, a pull-down menu appears, and when print is selected from the menu, the check can be printed on the printer PRN. If a printed check is lost and needs to be printed again, the same operation can be used to print it again.

[0061] If multiple check printing is permitted, a sequential number or the printing date and time may be embedded in the two-dimensional code printed on the check. The sequential number or printing date and time attached to the most recent check is stored on server 1, allowing only the most recent check to be cashed. This reduces the risk of a third party cashing a lost check.

[0062] This embodiment offers the following advantages. Because users request the issuance of checks using the user terminal 3, checks can be issued without the need to carry a paper checkbook, just like with electronic checks. The issued electronic checks are printed on paper by the printer PRN connected to the store terminal 2. Because the store receives a physical item with the value of the payment amount with each payment, the payment system 100 is expected to be adopted even by stores that have reservations about the safety and stability of electronic payments and have refused to introduce electronic payments.

[0063] The technical features (constituent elements) described in each embodiment can be combined with each other, and by combining them, new technical features can be formed. The embodiments disclosed herein are illustrative in all respects and should not be considered limiting. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the meaning and scope of the claims. Furthermore, although the claims use a format in which a claim refers to two or more other claims (multiple claim format), this is not limiting. Multiple claims (multiple multiple claims) that refer to at least one other multiple claim may also be used. [Explanation of symbols]

[0064] 100: Payment system 1: Server 11: Control section 12: Main memory 13: Auxiliary storage section 131: User DB 132: Store DB 133: Check DB 134: Cashing DB 14: Communications Department 15: Reading unit 1P: Control program 1a: Portable storage medium 1b: Semiconductor memory 2: Store terminal 21: Control unit 22: Main memory 23: Auxiliary storage section 231: Check DB 24: Communications Department 25: Display panel 26:Operation section 27: Serial communication section 2P: Control program CR: Code reader PRN: Printer 3: User terminal 31: Control unit 32: Main memory 33: Auxiliary storage section 34: Communications Department 35: Display panel 36:Operation section 4: Accounting system 5: Banking System B: Bus N: Network

Claims

1. receiving an issuance request including an issuer ID and an amount; Determine whether or not a financial account associated with the issuer ID exists; If it is determined that the financial account exists, generating check issuance information including the amount; Send the issuance information to have the check printed. An information processing method that performs processing.

2. The amount is the price for the goods or services received by the issuer at the store, The issuance request is sent from the store terminal when the store terminal reads the code displayed on the issuer terminal used by the issuer. The information processing method according to claim 1.

3. The issuing information is stored in a storage unit in association with the cashing status.

3. The information processing method according to claim 1.

4. When a check cashing request including the issuer ID and the amount is received, the system determines whether the check is uncashed based on the cashing status stored in the memory unit; If it is determined that the item has not been redeemed, a redemption permit will be sent. Update the redemption status to redeemed The information processing method according to claim 3 .

5. The issuing information includes a two-dimensional code in which the issuer ID, the amount, the store ID, and the issuing date and time are embedded.

3. The information processing method according to claim 1.

6. The issuing information is transmitted to the issuer terminal corresponding to the issuer ID.

3. The information processing method according to claim 1.

7. receiving an issuance request including an issuer ID and an amount; Determine whether or not a financial account associated with the issuer ID exists; If it is determined that the financial account exists, generating check issuance information including the amount; Send the issuance information to have the check printed. An information processing program that causes an information processing device to execute processing.

8. An information processing device including a control unit, The control unit receiving an issuance request including an issuer ID and an amount; Determine whether or not a financial account associated with the issuer ID exists; If it is determined that the financial account exists, generating check issuance information including the amount; Send the issuance information to have the check printed. An information processing device that executes processing.

Images