System, program, and method

Abstract

To provide a system for making payment through account transfer smoothly.MEANS FOR SOLVING THE PROBLEM: A program causes a processor to execute the steps of: acquiring business operator information and user information; applying for registration of account transfer to a receipt proxy server managed by a receipt agency, using the user information and the business operator information; receiving an expense claim to a user, from a business operator terminal used by a business operator; transmitting schedule information indicating a schedule of withdrawal from a transfer account to a user terminal used by the user, based on the expense claim; applying for execution of the withdrawal, based on the schedule information, to the receipt proxy server; and transmitting result information indicating an actual result of the withdrawal, received from the receipt proxy server, to the user terminal.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] The present disclosure relates to a system, a program, and a method. [Background technology]

[0002] BACKGROUND ART Conventionally, it has been common for users who receive goods or services from businesses to pay for the goods or services by account transfer.

[0003] For example, Patent Document 1 discloses a system for performing administrative processing associated with an account transfer contract. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2001-350916 Summary of the Invention [Problem to be solved by the invention]

[0005] However, with conventional account transfers, users sometimes forget the details of the withdrawals they had set up, which can result in the transfer account not being able to be debited due to the balance being too low, which can cause delays in account transfer payments. Furthermore, to know whether the scheduled withdrawals had been made properly, the user had to check their balance, which was a time-consuming process.

[0006] The present disclosure aims to provide a system that is highly convenient for users and allows them to make payments by account transfer without delay. [Means for solving the problem]

[0007] A program according to one aspect of the present disclosure is a program used in a computer having a processor that supports the use of direct debit, and causes the processor to execute the following steps: acquiring business information about a business and user information including information on a transfer account to be used for direct debit, for direct debit used by a user to make payments for the costs of the business's goods or services; using the user information and the business information to submit an application for registration of direct debit to a collection agency server managed by a collection agency; accepting a bill for expenses from the user from a business terminal used by the business; notifying a user terminal used by the user of schedule information indicating a schedule for debits from the transfer account based on the bill for expenses; requesting the collection agency server to execute the debit based on the schedule information; and notifying the user terminal of performance information indicating the actual debit performance received from the collection agency server. [Effects of the Invention]

[0008] The system of the present disclosure allows payments by direct debit to be made without delay. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram showing an overview of an account transfer support system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram showing the hardware configuration of the user terminal shown in FIG. [Figure 3] FIG. 2 is a block diagram showing a hardware configuration of the management server shown in FIG. [Figure 4] 2 is a block diagram showing the functional configuration of the user terminal shown in FIG. 1. FIG. [Figure 5] 2 is a block diagram showing a functional configuration of the management server shown in FIG. 1. FIG. [Figure 6] FIG. 2 is a diagram illustrating an example of a data structure of a business operator database. [Figure 7] FIG. 2 is a diagram illustrating an example of a data structure of a user database. [Figure 8]FIG. 2 is a diagram illustrating an example of a data structure of a billing database. [Figure 9] FIG. 10 is a diagram illustrating an example of a data structure of a deposit database. [Figure 10] FIG. 1 is a diagram illustrating an overview of the present embodiment. [Figure 11] FIG. 10 is a diagram showing the flow of the first type of processing in the account transfer support system. [Figure 12] FIG. 10 is a diagram showing the flow of second-class processing in the account transfer support system. [Figure 13] FIG. 10 is a diagram showing the flow of third-class processing in the account transfer support system. [Figure 14] FIG. 10 is a diagram showing the flow of fourth type processing in the account transfer support system. [Figure 15] FIG. 10 is a diagram showing the flow of the fifth type of processing in the account transfer support system. [Figure 16] FIG. 10 is a block diagram showing a functional configuration of a management server according to a modified example. [Figure 17] 10A and 10B are diagrams illustrating an example of the data structure of a billing database and a schedule database according to a modified example. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In the drawings for explaining the embodiment, the same components are generally designated by the same reference numerals, and repeated description thereof will be omitted.

[0011] FIG. 1 is a diagram illustrating an outline of an account transfer support system 1 (hereinafter simply referred to as system 1) of the present invention. As shown in Figure 1, system 1 is a system that supports account transfers used for payments from users for the costs of goods or services of businesses. In the following explanation, we will first explain the configuration of system 1, and then provide a detailed description of the processing using system 1.

[0012] <1. Overall configuration and hardware configuration of each device> The overall configuration of the system 1 according to this embodiment will be described. As shown in FIG. 1, the system 1 includes a user terminal 10 and a management server 20. The user terminal 10 and the management server 20 can communicate with each other via a network 80, and are communicatively connected to the collection agency server 30, the business operator terminal 40, and the financial institution server 50. The network 80 is configured by a wired or wireless network.

[0013] Here, a business operator refers to an organization that operates some kind of business. Business operators include entities that provide goods or services to users, such as nurseries, kindergartens, after-school care centers, elementary schools, cram schools, various extracurricular activities, adult schools, and training gyms. System 1 is used by multiple businesses. A user is someone who receives some kind of product or service from a business and pays the business a fee in exchange for the product or service.

[0014] The user terminal 10 is a device operated by each user. The user terminal 10 includes, for example, a mobile terminal such as a smartphone compatible with a mobile communication system, or a tablet terminal. The user terminal 10 may also be a desktop personal computer (PC), a laptop PC, or the like.

[0015] The user terminal 10 is communicably connected to the management server 20 via a network 80. The user terminal 10 is connected to the network 80 by communicating with communication devices such as a wireless base station 81 that complies with communication standards such as 5G and LTE (Long Term Evolution), and a wireless LAN router 82 that complies with wireless LAN (Local Area Network) standards such as IEEE (Institute of Electrical and Electronics Engineers) 802.11.

[0016] FIG. 2 is a diagram showing the hardware configuration of the user terminal 10. As shown in FIG. As shown in FIG. 2, the user terminal 10 includes a communication IF (Interface) 12, an input device 13, an output device 14, a memory 15, a storage unit 16, and a processor 19.

[0017] The communication IF 12 is an interface for inputting and outputting signals so that the user terminal 10 can communicate with external devices. The input device 13 is an input device (for example, a keyboard, a touch panel, a touch pad, a pointing device such as a mouse, etc.) for receiving input operations from a user.

[0018] The output device 14 is an output device (such as a display or speaker) for presenting information to the user. The memory 15 is for temporarily storing programs and data to be processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0019] The storage unit 16 is a storage device for saving data, such as a flash memory or a hard disk drive (HDD). The processor 19 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, a register, a peripheral circuit, and the like.

[0020] 1 is a device that supports the use of account transfers by applying for account transfers using information about users and businesses and notifying related parties of information about account transfer processing. The management server 20 is a computer connected to a network 80.

[0021] FIG. 3 is a diagram showing the hardware configuration of the management server 20. As shown in FIG. As shown in FIG. 3, the management server 20 includes a communication IF 22, an input / output IF 23, a memory 25, a storage 26, and a processor 29.

[0022] The communication IF 22 is an interface for inputting and outputting signals so that the management server 20 can communicate with external devices. The input / output IF 23 functions as an interface with an input device for receiving input operations from the user and an output device for presenting information to the user.

[0023] The memory 25 is for temporarily storing programs and data to be processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory). The storage 26 is a storage device for saving data, such as a flash memory or a hard disk drive (HDD). The processor 29 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

[0024] The collection agency server 30 shown in Fig. 1 is a server device managed by a collection agency. The collection agency server 30 is a computer connected to a network 80. The receiving agency server 30 has the same hardware configuration as the management server 20. That is, the receiving agency server 30 has a communication IF (Interface), an input device, memory, a storage unit, and a processor. These configurations are the same as those of the user terminal 10, so illustrations and detailed explanations will be omitted.

[0025] The collection agency server 30 is connected to the collection agency's operating terminal for communication, and has the main function of coordinating information regarding account debits with financial institutions, receiving debit results from financial institutions, and transmitting them to the management server 20.

[0026] 1 is a terminal used by a business operator to manage accounting information for the business, and is, for example, a desktop personal computer (PC), a laptop PC, etc. The business operator terminal 40 may also be a mobile terminal such as a smartphone, or a tablet terminal.

[0027] The provider terminal 40 has the same hardware configuration as the user terminal 10. That is, the provider terminal 40 has a communication IF (Interface), an input device, an output device, a memory, a storage unit, and a processor. These configurations are the same as those of the user terminal 10, so illustrations and detailed explanations will be omitted.

[0028] 1 is a server device managed by a financial institution such as a bank. The financial institution server 50 is a computer connected to a network 80. The financial institution server 50 has the same hardware configuration as the management server 20. That is, the collection agency server 30 has a communication IF (Interface), an input device, memory, a storage unit, and a processor. These configurations are the same as those of the user terminal 10, so illustrations and detailed explanations will be omitted.

[0029] The collection agency server 30 is connected to the operation terminal of the financial institution in a communication manner, and has the main function of executing account debits based on the information regarding debits sent from the collection agency server 30, and sending the results to the collection agency server 30.

[0030] <2. Functional Configuration of User Terminal 10> FIG. 4 is a block diagram showing the functional configuration of the user terminal 10 that constitutes the system 1. As shown in FIG. As shown in FIG. 4, the user terminal 10 includes multiple antennas (antenna 111, antenna 112), wireless communication units corresponding to each antenna (first wireless communication unit 121, second wireless communication unit 122), an input receiving unit 130 (including a keyboard 131 and a display 132), an audio processing unit 140, a microphone 141, a speaker 142, a camera 150, a memory unit 160, and a control unit 170.

[0031] The user terminal 10 also has functions and configurations (for example, a battery for storing power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.) that are not specifically shown in Fig. 4. As shown in Fig. 4, each block included in the user terminal 10 is electrically connected by a bus or the like.

[0032] The antenna 111 emits a signal emitted by the user terminal 10 as a radio wave. The antenna 111 also receives a radio wave from space and provides the received signal to the first radio communication unit 121.

[0033] The antenna 112 emits a signal emitted by the user terminal 10 as a radio wave. The antenna 112 also receives a radio wave from space and provides the received signal to the second radio communication unit 122.

[0034] The first wireless communication unit 121 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 111 so that the user terminal 10 can communicate with other wireless devices. The second wireless communication unit 122 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 112 so that the user terminal 10 can communicate with other wireless devices. The first wireless communication unit 121 and the second wireless communication unit 122 are communication modules including a tuner, a received signal strength indicator (RSSI) calculation circuit, a cyclic redundancy check (CRC) calculation circuit, a high-frequency circuit, etc. The first wireless communication unit 121 and the second wireless communication unit 122 perform modulation / demodulation and frequency conversion of wireless signals transmitted and received by the user terminal 10, and provide the received signals to the control unit 170.

[0035] The input receiving unit 130 has a mechanism for receiving input operations from the user. Specifically, the input receiving unit 130 includes a keyboard 131 and a display 132. Note that the input receiving unit 130 may be configured as a touch screen that detects the position of the user's contact on the touch panel, for example, by using a capacitive touch panel.

[0036] The keyboard 131 accepts input operations by the user of the user terminal 10. The keyboard 131 is a device for inputting characters, and outputs input character information to the control unit 170 as an input signal.

[0037] Display 132 displays data such as images, videos, and text under the control of control unit 170. That is, display 132 also functions as an output unit that outputs information to the user. Display 132 is realized by, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display.

[0038] The audio processing unit 140 modulates and demodulates audio signals. The audio processing unit 140 modulates a signal provided from a microphone 141 and provides the modulated signal to the control unit 170. The audio processing unit 140 also provides the audio signal to a speaker 142. The audio processing unit 140 is realized by, for example, a processor for audio processing. The microphone 141 receives audio input and provides an audio signal corresponding to the audio input to the audio processing unit 140. The speaker 142 converts the audio signal provided by the audio processing unit 140 into audio and outputs the audio to the outside of the user terminal 10.

[0039] The camera 150 is a device that receives light with a light receiving element and outputs the received light as a captured image. The camera 150 is, for example, a depth camera that can detect the distance from the camera 150 to a subject being photographed.

[0040] Storage unit 160 is configured with, for example, a flash memory, and stores data and programs used by user terminal 10. In one aspect, storage unit 160 stores user information 161.

[0041] The user information 161 is information about a user who uses the system 1 by using the user terminal 10. The user information 161 includes information for identifying the user (user ID), the user's name, account information for a messaging app used by the user, information about the user's contact information such as an email address, and the like.

[0042] The control unit 170 reads a program stored in the storage unit 160 and executes instructions included in the program to control the operation of the user terminal 10. The control unit 170 is, for example, an application program that is pre-installed in the user terminal 10. The control unit 170 operates according to a program to fulfill the functions of an operation reception unit 171, a transmission / reception unit 172, a data processing unit 173, and a display processing unit 174.

[0043] The operation receiving unit 171 performs processing to receive input operations by the user via the input device 13 such as the keyboard 131 .

[0044] The transmitting / receiving unit 172 performs processing for the user terminal 10 to transmit and receive data to and from external devices such as the management server 20 in accordance with a communication protocol.

[0045] The data processing unit 173 performs calculations on the data received by the user terminal 10 according to a program, and outputs the calculation results to a memory or the like.

[0046] The display processing unit 174 performs processing to present information to the user. The display processing unit 174 performs processing to display a display image on the display 132, processing to output audio to the speaker 142, processing to cause the camera 150 to generate vibrations, etc.

[0047] <3. Functional configuration of management server 20> 5 is a diagram showing the functional configuration of the management server 20 that constitutes the system 1. As shown in FIG. 5, the management server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0048] The communication unit 201 performs processing for the management server 20 to communicate with external devices.

[0049] The storage unit 202 stores data and programs used by the management server 20. The storage unit 202 stores at least a business operator database 2021, a user database 2022, a billing database 2023, and a deposit database 2024.

[0050] The business database (DB) 2021 is a database that stores information about businesses that use the system 1. The data structure of the business DB 2021 will be described later.

[0051] The user database (DB) 2022 is a database that stores information about users who use the system 1. The data structure of the user DB 2022 will be described later.

[0052] The billing database (DB) 2023 is a database that stores information (billing information) relating to billing from businesses to users for expenses paid by account transfer via the system 1. The data structure of the billing DB 2023 will be described later.

[0053] The deposit database 2024 is a database that stores deposit information for depositing to the business the fees debited by account transfer via the system 1. The data structure of the deposit DB 2024 will be described later.

[0054] The control unit 203 shown in Figure 5 functions as functional modules, such as a receiving control module 2031, a sending control module 2032, a registration application module 2033, a billing summary module 2034, a withdrawal application module 2035, an actual results summary module 2036, a notification module 2037, and a deposit module 2038, as a result of the processor 29 of the management server 20 performing processing according to a program.

[0055] <3-1. Functions of the control unit 203> The reception control module 2031 controls the process by which the management server 20 receives signals from external devices in accordance with a communication protocol.

[0056] The transmission control module 2032 controls the process in which the management server 20 transmits a signal to an external device in accordance with a communication protocol.

[0057] The registration application module 2033 uses the user information recorded in the user DB 2022 and the business information recorded in the business DB 2021 to apply to the collection agency server 30 for registration of a new account transfer.

[0058] The billing summary module 2034 sums up the billing information recorded in the billing DB 2023 and generates schedule information indicating the withdrawal schedule.

[0059] The withdrawal application module 2035 uses the created schedule information to apply for withdrawal to the collection agency server 30.

[0060] The performance tallying module 2036 updates the status of the withdrawal in the billing DB 2023 using information on the performance of the withdrawal sent from the collection agency server 30 .

[0061] The notification module 2037 notifies the user terminal 10 and the provider terminal 40 of the scheduled withdrawal information and actual withdrawal information. The actual withdrawal information includes the following information. Information indicating that the withdrawal was successful Information indicating that the withdrawal was not successful Furthermore, for bills that could not be debited, the notification module 2037 notifies the user of a notice of additional collection as a payment request along with alternative payment methods. Examples of alternative payment methods include credit card payments and online payment systems that link with payment agent systems for payments at convenience stores.

[0062] The online payment system prompts the user to select either credit card payment or payment at a convenience store as the payment method for the additional payment, following instructions displayed on the user terminal 10. The online payment system provides an input form for inputting credit card information to be used for the additional payment, or information such as a payment number to be used when paying at a convenience store. The online payment system may also be linked to other payment systems, such as those using two-dimensional bar codes.

[0063] The deposit module 2038 creates a deposit DB 2024 based on the withdrawal record information. The deposit module 2038 sends a transfer instruction for depositing money to the business to the financial institution server 50 based on the deposit information recorded in the deposit DB 2024. As a result, the deposit module 2038 deposits money to the business in an amount equivalent to the debited expense claim. If multiple deposits to the business are scheduled, the deposit module 2038 adds up the multiple deposit amounts and requests a lump-sum deposit. Details of the processing of the deposit module 2038 will be described later. The deposit module 2038 updates the deposit DB 2024 based on the fact that a deposit has been made.

[0064] <3-2. Structure of each database> Next, an example of the structure of each database stored in the storage unit 202 will be described.

[0065] <3-2-1. Business DB2021> FIG. 6 is a diagram showing an example of the data structure of the business operator DB 2021. As shown in FIG. 6, each record in the business DB 2021 includes an item “business ID,” an item “business name,” an item “address,” an item “representative name,” and an item “contact information.” The business DB 2021 may also include columns corresponding to other management items.

[0066] The item "Provider ID" is information for identifying a provider. A provider ID is assigned to each provider.

[0067] The item "business name" is information indicating the name of the business corresponding to the business ID.

[0068] The item "location" is information indicating the location of the business corresponding to the business ID.

[0069] The item "representative name" is information indicating the representative of the business corresponding to the business ID.

[0070] The item "contact information" is information indicating the contact information of the business corresponding to the business ID.

[0071] The item "Deposit Account" is information about the account used when depositing money to the business corresponding to the business ID.

[0072] Each record in business operator DB2021 is recorded based on information entered by the business operator when the business operator adopts the procedure for registering an account transfer using system 1. Note that each record in business operator DB2021 can be changed as needed by the business operator.

[0073] <3-2―2. User DB2022> FIG. 7 is a diagram showing an example of the data structure of the user DB 2022. As shown in FIG. 7, each record in the user DB 2022 includes an item “User ID,” an item “User Name,” an item “Address,” an item “Contact Information,” and an item “Transfer Account.” The user DB 2022 may also include columns corresponding to other management items.

[0074] The item "User ID" is information for identifying the user who will be paying the fee to the business by bank transfer. A user ID is assigned to each user.

[0075] The "contact information" item is information about the contact information of the user corresponding to the user ID. The contact information includes a phone number, an email address, account information for a messaging system or SNS, and the like.

[0076] The item "Transfer Account" is information about an account at a financial institution opened in the name of the user corresponding to the user ID, and is information about the account that will be used as the source of funds for the account transfer. Multiple transfer accounts may be set for one user.

[0077] Each record in the user DB 2022 is recorded based on information input by a user when registering a new user who will use a transfer account. Each record in the user DB 2022 can be changed according to the needs of the user. The user DB 2022 may also include the following management items, for example: Other information about your origins, such as your age, gender, date of birth, and nationality Information that suggests your ability to pay, such as your occupation, place of employment, and proof of income - Publicly assigned numbers that identify users, such as My Number or driver's license numbers

[0078] <3-2-3. Billing DB2023> FIG. 8 is a diagram showing an example of the data structure of the billing DB 2023. As shown in FIG. As shown in Figure 8, each record in billing DB2023 includes the following items: "Billing ID," "Billing Month," "Billing Business ID," "Billing User ID," "Billing Amount," "Debit Date," "Transfer Status," "Additional Collection Status," and "Deposit ID." The billing DB 2023 may also have columns corresponding to other management items.

[0079] The item "billing ID" is information for identifying the billing of the user from the business operator.

[0080] The item "billing month" is information indicating the month in which the invoice for the billing corresponding to the billing ID was issued.

[0081] The item "billing business ID" is information that identifies the business that is the billing source of the bill corresponding to the billing ID.

[0082] The item "billing destination user ID" is information for identifying the user to whom the billing corresponding to the billing ID is to be billed.

[0083] The item "billing amount" is information indicating the billing amount of the bill corresponding to the billing ID.

[0084] The item "Debit Date" is information that indicates the date on which the fee for the invoice corresponding to the invoice ID will be debited. The debit date is set, for example, to the 26th of each month. The debit date can be set as desired.

[0085] The item "Transfer Status" is information that indicates the withdrawal status for the billing corresponding to the billing ID. The transfer status includes, for example, the following: ·Not yet: The scheduled withdrawal date has not yet arrived Completed: The scheduled withdrawal date has arrived and the withdrawal has been completed successfully. · Unable: The scheduled withdrawal date has arrived, but the withdrawal could not be made normally due to insufficient balance, etc.

[0086] The "Additional Collection Status" field indicates the status of additional collection by an alternative payment method when a withdrawal is not possible for a bill corresponding to a billing ID. Examples of additional collection status include the following: N / A: The withdrawal has been completed successfully and no alternative payment method is required. · Completed: The necessary payment has already been made by alternative means. · Not yet: The necessary alternative payment has not yet been made.

[0087] The item "Deposit ID" is identification information for the procedure when depositing money to a business operator after debiting for the invoice corresponding to the invoice ID. In this embodiment, the deposit ID is issued for each business operator. In other words, for example, if there are multiple invoices for expenses from one business operator in the same month, the total amount of the debits for those multiple invoices will be deposited using a single deposit procedure.

[0088] Each record in the billing DB 2023 is recorded based on billing information issued by the business operator.

[0089] <3-2―4. Deposit DB2024> FIG. 9 is a diagram showing an example of the data structure of the deposit DB 2024. As shown in Figure 9, each record in the deposit DB2024 includes the following items: "Deposit ID," "Deposit Destination Business ID," "Deposit Destination Account," "Deposit Amount," and "Deposit Date." The deposit DB2024 may also have columns corresponding to other management items. For example, the deposit DB2024 may manage fees related to the use of the system 1, i.e., fees related to account transfer intermediation.

[0090] The item "Deposit ID" indicates the identification information of the deposit procedure for paying the debit result to the business operator.

[0091] The item "Payment recipient business ID" is identification information of the business to which the payment is to be made in the payment procedure corresponding to the payment ID.

[0092] The item "Deposit Account" is account information of the business entity to which the payment is to be made in the deposit procedure corresponding to the deposit ID.

[0093] The item "deposit amount" is information indicating the deposit amount of the deposit procedure corresponding to the deposit ID.

[0094] The item "Deposit Date" is information indicating the date on which the deposit procedure corresponding to the deposit ID was actually carried out.

[0095] New records are recorded in each record of the deposit DB 2024 by tallying up the actual withdrawal information by the deposit module 2038.

[0096] <4. System 1 Processing> Next, we will explain the processing of the system 1. First, we will explain the scheme of the service that uses the system 1. Figure 10 is a diagram that explains the scheme of the service provided by the system 1.

[0097] <4-1. Overview of services provided by System 1> As shown in Figure 10, the services provided by System 1 can be broadly divided into the following five processes, covering a series of processes from new registration for direct debit to the payment of fees deducted by direct debit to the business operator. Category 1 processing: Processing related to new account transfer registration applications Category 2 processing: Processing to notify scheduled withdrawals based on requests from businesses Category 3 processing: Processing to apply for withdrawal and receive the results Category 4 processing: Processing to notify users of withdrawal results (including additional collection) Category 5 processing: Processing to deposit funds to a business based on withdrawal records By executing these processes, the system 1 improves convenience for users and businesses and supports the use of account transfers. The details of the processes that fall into each of these broad categories will be described in order below.

[0098] <4-2. Class 1 Processing> In the first type of processing, processing related to a new account transfer registration application is carried out. Figure 11 is a flow chart showing the first type of processing. As shown in FIG. 11, in a new account transfer registration application, first, user information is entered into the user terminal 10 (step S111). Specifically, the user inputs user information including information about the transfer account to the user terminal 10. The user terminal 10 transmits the input user information to the management server 20.

[0099] After step S111, the management server 20 acquires user information (step S121). Specifically, the reception control module 2031 of the management server 20 acquires the received user information and stores it in the storage unit 202 as a new record in the user DB 2022.

[0100] After step S121, business operator information is input to the user terminal 10 (step S112). Specifically, the user inputs information about the business to which payment is to be made by account transfer into the user terminal 10. At this time, for example, the user may input the business information into the user terminal 10 by photographing a two-dimensional code containing the business information presented by the business with the camera 150 of the user terminal 10. The user terminal 10 transmits the input information about the other business to the management server 20.

[0101] After step S112, the management server 20 acquires business operator information (step S122). Specifically, the reception control module 2031 of the management server 20 acquires the received business information and stores it in the storage unit 202 as a new record in the business DB 2021.

[0102] After step S122, the management server 20 applies for account transfer registration (step S123). Specifically, the registration application module 2033 of the management server 20 uses the user information stored in the user DB 2022 and the business information stored in the business DB 2021 to send application information regarding the registration of account transfer to the collection agency server 30. The application information includes the user information and business information, as well as information regarding the monthly transfer date and information regarding the time to start account transfer.

[0103] After step S123, the collection agency server 30 receives the account transfer registration application information sent from the management server 20 (step S131). Specifically, the collection agency server 30 acquires the user information and business information contained in the application information.

[0104] After step S132, the collection agency server 30 registers the account transfer (step S132). Specifically, the collection agency server 30 registers a new account transfer contract in response to the determination that there are no deficiencies or defects in the user information and business information included in the application information.

[0105] After step S132, the collection agency server 30 notifies the completion of registration (step S133). Specifically, the collection agency server 30 transmits to the management server 2030 a message that a new account transfer contract has been registered.

[0106] After step S133, the management server 20 receives a registration notification (step S124). Specifically, the reception control module 2031 of the management server 20 acquires the notification of completion of registration sent from the collection agency server 30 .

[0107] After step S124, the management server 20 notifies the user terminal 10 of the registration (step S125). Specifically, the management server 20 transmits the notification of completion of registration transmitted from the collection agency server 30 to the user terminal 10.

[0108] After step S125, the user terminal 10 receives a registration notification (step S114). Specifically, the user terminal 10 receives a notification that a new account transfer contract has been registered, and displays this on the display 132 to present it to the user. This completes the process for registering a new account transfer.

[0109] <4-3. Class 2 Processing> In the second type of processing, a process of notifying the user of the scheduled withdrawal based on a bill from the business operator is carried out. Figure 12 shows the flow of the second type of processing. As shown in FIG. 12, in the process of notifying the scheduled withdrawal based on a bill from the business operator, first, the business operator terminal 40 bills the management server 20 for the cost (step S41). Specifically, the business operator terminal 40 transmits billing information relating to the billing of expenses from the business operator to the user to the management server 20. The billing information may be transmitted to the management server 20 at a preset frequency (for example, once a month).

[0110] After step S241, the management server 20 receives the expense claim (step S222). Specifically, the reception control module 2031 of the management server 20 acquires the claim information transmitted from the business operator terminal 40, and stores it in the storage unit 202 as a new record in the claim DB 2023.

[0111] After step S222, the management server 20 creates schedule information (step S222). Specifically, the billing tallying module 2034 of the management server 20 refers to the billing DB 2023 and creates schedule information, which is a deduction schedule, for each billing information item.

[0112] After step S222, the management server 20 notifies the schedule information (step S223). Specifically, the notification module 2037 of the management server 20 transmits the created schedule information to the user terminal 10. The schedule information includes information about the business operator, information about the withdrawal amount, and information about the withdrawal time. The schedule information may also be notified to the business operator terminal 40.

[0113] After step S223, the user terminal 10 receives the schedule information (step S211). Specifically, the user terminal 10 receives schedule information transmitted from the notification module 2037 of the management server 20. The user terminal 10 presents the user with information regarding upcoming scheduled withdrawals by displaying the received schedule information on the display 132. This allows the user to check the balance of their transfer account in preparation for upcoming scheduled withdrawals, and to check whether there are any unexpected scheduled withdrawals. This completes the process of notifying the customer of a scheduled withdrawal based on a bill from the business operator.

[0114] <4-4. Class 3 Processing> The third type of processing involves applying for a withdrawal and receiving the result. Figure 13 is a flow chart showing the third type of processing. As shown in FIG. 13, in the process of applying for a withdrawal and receiving the result, first, the management server 20 applies for a withdrawal (step S321). Specifically, the withdrawal application module 2035 of the management server 20 transmits a withdrawal application to the collection agency server 30 based on the schedule information for which a withdrawal is scheduled.

[0115] After step S321, the collection agency server 30 receives a withdrawal application (step S331). Specifically, the collection agency server 30 acquires the schedule information included in the withdrawal application.

[0116] After step S331, the collection agency server 30 sends the withdrawal request information (step S332). Specifically, the collection agency server 30 confirms that there is no discrepancy between the debit application information and the registered account transfer, and then transmits debit request information including information about the debit to the financial institution server 50. The debit request information includes the scheduled debit date, the debit amount, transfer account information, account information of the collection agency, etc.

[0117] After step S332, the financial institution server 50 receives the debit request information (step S351). Specifically, the financial institution server 50 receives various data included in the debit request information.

[0118] After step S351, the financial institution server 50 executes the withdrawal (step S352). Specifically, the financial institution server 50 uses various information contained in the withdrawal request information to transfer funds equivalent to the specified invoice amount from the designated transfer account to the collection agent. If there are no funds equivalent to the invoice amount in the transfer account, the withdrawal will not be possible.

[0119] After step S352, the financial institution server 50 notifies the collection agency server 30 of the result of the withdrawal (step S353). Specifically, if the withdrawal is successful, the financial institution server 50 notifies the collection agency server 30 of this, along with information regarding the date and time the withdrawal was made. On the other hand, if the withdrawal is not possible, the financial institution server 50 notifies the collection agency server 30 of this, along with information regarding the date and time the withdrawal was attempted. Note that if the withdrawal is not possible, the financial institution server 50 may also notify the collection agency server 30 of the amount claimed for the withdrawal and the balance in the transfer account.

[0120] After step S353, the collection agency server 30 receives the result of the withdrawal (step S333). Specifically, the collection agency server 30 receives information transmitted from the financial institution server 50 as to whether the withdrawal has been completed normally.

[0121] After step S333, the collection agency server 30 transmits the result of the withdrawal to the management server 20 (step S334). Specifically, the collection agency server 30 transmits to the management server 20 information transmitted from the financial institution server 50 as to whether the withdrawal has been completed normally.

[0122] After step S334, the management server 20 receives the result of the withdrawal (step S322). Specifically, the reception control module 2031 of the management server 20 acquires information as to whether the withdrawal has been completed normally, and updates the transfer status in the billing DB 2023 . This completes the process of applying for a withdrawal and receiving the result.

[0123] <4-5. Processing of Category 4> The fourth type of processing involves notifying the user of the results of the withdrawal. Figure 14 is a flow chart showing the fourth type of processing. As shown in FIG. 14, in the process of notifying the user of the withdrawal results, the management server 20 first tallyes up the results information (step S421). Specifically, the performance tallying module 2036 of the management server 20 refers to the billing DB 2023 and tally information on the transfer status for each bill.

[0124] In step S421, if the transfer status is "completed" and the withdrawal is not impossible (No in step S422), the management server 20 notifies the user terminal 10 of the withdrawal record (step S423). Specifically, the notification module 2037 of the management server 20 transmits to the user terminal 10 a notification that the withdrawal related to the billing ID has been successfully executed. At this time, if multiple withdrawals are scheduled, the notification module 2037 transmits to the user terminal 10 the results of the multiple withdrawals for each billing ID.

[0125] After step S423, the user terminal 10 receives the withdrawal record (step S411). Specifically, the user terminal 10 receives the information that the withdrawal has been successfully executed, which is sent from the notification module 2037 of the management server 20. The user terminal 10 presents the received information to the user by displaying it on the display 132.

[0126] On the other hand, if the transfer status is determined to be impossible in step S421 (Yes in step S422), the management server 20 calculates the additional amount (step S424). Specifically, the performance calculation module 2036 of the management server 20 calculates the cost of the additional collection for the scheduled withdrawal corresponding to the billing ID for which the withdrawal could not be executed. When calculating the cost, the module refers to information about the additional collection fee that is applied to the additional collection amount that is set in advance between the business operator and the user.

[0127] After step S424, the management server 20 notifies the customer that the withdrawal is not possible (step S425). Specifically, the notification module 2037 of the management server 20 transmits the following information to the user terminal 10: - The withdrawal corresponding to the billing ID was not possible The difference between the balance of the transfer account and the amount to be debited - The amount of additional payment calculated by the performance calculation module 2036 and the payment deadline · Request payment using alternative payment methods

[0128] After step S425, the user terminal 10 receives a notification that the withdrawal is not possible (step S412). Specifically, the user terminal 10 acquires various information contained in the notification of the non-payment of the withdrawal sent from the management server 20. The user terminal 10 displays the various information contained in the notification of the non-payment of the withdrawal on the display 132, thereby presenting it to the user.

[0129] After step S412, the user terminal 10 executes payment using the alternative payment method (step S413). Specifically, the user terminal 10 accepts user input to an online payment system included in the alternative payment method, and thereby executes payment of the additional fee via the online payment system. This completes the process of notifying the user of the withdrawal results.

[0130] <4-6. Processing of Category 5> In the fifth type of processing, a process of depositing money to the business operator is carried out based on the withdrawal record. Figure 15 is a flow chart showing the fifth type of processing. As shown in FIG. 15, in the process of depositing money to a business based on the withdrawal record, first, the collection agency server 30 transfers the amount to be withdrawn (step S531). Specifically, the receiving agent server 30 manages and operates the management server 20 and transfers the funds withdrawn by debit to the account of the system administrator who operates the account transfer support business.

[0131] After step S531, the management server 20 receives the transferred payment (step S521). Specifically, the management server 20 acquires the amount of the withdrawal sent from the collection agency server 30 and checks it against the billing amount in the billing ID.

[0132] After step S531, the management server 20 calculates the deposit amount (step S522). Specifically, the deposit module 2038 of the management server 20 creates the deposit DB 2024 based on the deposit ID assigned to each business operator by referring to the billing DB 2023. When there are multiple bills from the same business operator, the deposit module 2038 creates a lump-sum deposit information that integrates the billing amounts.

[0133] For example, the following deposit IDs are set in the billing DB 2023 shown in FIG. Payment ID: N0001...Bill from business B0001 (C0001, C0003) Payment ID: N0002...Bill from business B0002 (C0002, C0004) Payment ID: N0003...Bill from business B0003 (C0005) Payment ID: N0004...Bill from business B0004 (C0006)

[0134] For this reason, when creating the deposit DB 2024, the deposit module 2038 uses the deposit ID as the primary key, as shown in Figure 9, and adds up the amount of expense claims corresponding to the same deposit ID, setting this as the deposit amount corresponding to the deposit ID. In Figure 9, the deposit amount is calculated as follows: Deposit ID: N0001...Deposit amount P+R (total amount of C0001 and C0003) Deposit ID: N0002...Deposit amount Q+S (total amount of C0002 and C0004) Deposit ID: N0003...Deposit amount T (invoice amount for C0005) Deposit ID: N0004...Deposit amount U (invoice amount for C0006) In other words, if there is one invoice corresponding to the same deposit ID, the invoice amount for that invoice will be treated as the deposit amount.

[0135] The deposit module 2038 may add up all or part of the expenses related to multiple expense claims. The deposit module 2038 can add up the deposit amounts related to multiple expense claims, for example, according to the following rules: - Add up the billing costs for common items designated by the business operator. · Combine charges specified by the business.

[0136] The deposit module 2038 also references the billing DB 2023 and determines the billing amount to be added together based on the values ​​of the transfer status and additional collection status. Specifically, for billing ID: C0004 shown in FIG. 8, the transfer status is "unable" and the additional collection status is "paid." In other words, although payment for the expenses related to billing ID: C0004 could not be made by direct debit, it is confirmed that the user (U0003) subsequently made the appropriate payment within the specified period using an alternative payment method. In this case, the deposit module 2038 adds up the additional collection amount paid using the alternative payment method as expenses related to multiple bills from the same business.

[0137] On the other hand, if the transfer status is not possible and the additional collection status is unpaid, the deposit module 2038 assumes that the withdrawal related to the billing ID has not yet been completed, and calculates the deposit amount without adding up the billing amount corresponding to the billing ID.

[0138] After step S522, the management server 20 notifies the deposit (step S522). Specifically, the deposit module 2038 of the management server 20 refers to the deposit DB 2024 and transmits the deposit schedule to the business operator terminal 40. In addition, the deposit module 2038 transmits the transfer of the expenses related to the deposit to the financial institution server 50 based on the deposit schedule stored in the deposit DB 2024.

[0139] After step S523, the business operator terminal 40 receives a payment notification (step S541). Specifically, the business operator terminal 40 acquires the deposit schedule transmitted from the deposit module 2038 of the management server 20. The business operator terminal 40 displays the deposit schedule on an output device to present it to the business operator. This completes the process of depositing money to the business operator based on the withdrawal record.

[0140] <5.Summary> As described above, the system 1 according to this embodiment notifies the user of scheduled withdrawal information, allowing the user to check the funds in the transfer account in accordance with the scheduled withdrawal. Furthermore, the system 1 notifies the user of the actual withdrawal information, so that the user can know that the withdrawal has been carried out according to the registered details. In this way, the system 1 notifies the user of both scheduled and actual withdrawals, which is highly convenient for the user and allows payments by account transfer to be made smoothly.

[0141] Furthermore, in System 1, when depositing debited expenses, if there are multiple expense claims from the same business, at least a portion of the expenses relating to the multiple expense claims is added together and deposited with the business. This reduces the number of transactions relating to deposits compared to depositing multiple claims individually, thereby reducing the burden of fees required for deposit procedures. Furthermore, because the payment is made for the total amount of multiple claims, the business can reduce the workload of confirming the settlement of deposits.

[0142] In addition, in the step of depositing the debited fees, the additional amount paid using the alternative payment method is added up as the fees related to multiple invoices from the same business. Therefore, even if some of the scheduled debits cannot be debited, if the user subsequently makes payment using the alternative payment method, the additional fees can be collected and deposited in one lump sum.

[0143] <6. Variations> Next, a modification of the system 1 will be described. In the modified system 2, the creation of scheduled withdrawal information differs from the embodiment described above. Specifically, in the case where there are multiple expense claims for the same user, the system 2 consolidates at least a portion of the amounts of the multiple expense claims and applies for withdrawal. The system 1 according to this modified example will be described in detail below.

[0144] Fig. 16 is a block diagram showing the functional configuration of the management server 20 in the system 2. Fig. 17 is a diagram showing an example of the data structure of the billing DB 2023 and the schedule DB 2025 of the system 2. Note that in the following explanation, explanations of the same configuration as in the above-mentioned embodiment will be omitted.

[0145] 16, the management server 20 in the system 2 further includes a schedule database (DB) 2025. The schedule database 2025 is a database that stores information related to withdrawal schedules applied for based on billing information. The data structure of the schedule DB 2025 will be described later.

[0146] As shown in FIG. 17, the billing DB2023B further includes an item "Scheduled ID." The scheduled ID is an identification number assigned to each user for withdrawals during the same period. In the billing DB2023B, if there are multiple expense bills to the same user for withdrawals during the same period, the same scheduled ID is registered for that user. Here, the multiple expense bills to the same user may be multiple bills for different expense items from the same business operator, or multiple bills from different business operators.

[0147] For example, in the example of billing DB 2023B in FIG. 17, the schedule IDs are set as follows: - Schedule ID: S0001 for user with user ID: U0001 Schedule ID: S0002 for user with user ID: U0002 Schedule ID: S0003 for user with user ID: U0003 In addition, the item "transfer status" and the item "additional collection status" are not managed in the billing DB2023B.

[0148] 17, each record in the schedule DB 2025 includes an item “Schedule ID,” an item “Transfer Account,” an item “Withdrawal Amount,” an item “Scheduled Transfer Date,” an item “Transfer Status,” and an item “Additional Collection Status.” The schedule DB 2025 may also include columns corresponding to other management items.

[0149] The item "Schedule ID" is identification information for identifying a schedule for withdrawal by account transfer. A unique value is assigned to the schedule ID for each withdrawal process performed through the system 1.

[0150] The item "Transfer Account" indicates the account information of the transfer account that will be the source of funds for the withdrawal corresponding to the scheduled ID.

[0151] The item "withdrawal amount" is information indicating the amount of withdrawal corresponding to the schedule ID.

[0152] The item "transfer status" is information indicating the withdrawal status for the bill corresponding to the schedule ID.

[0153] The item "Additional Collection Status" is information indicating the status of additional collection by an alternative payment method when the withdrawal for the bill corresponding to the scheduled ID is not possible.

[0154] In the system 2, when the billing summary module 2034 creates schedule information (step S222 shown in FIG. 12), it references the schedule ID in the billing DB 2023, integrates the billing amounts for multiple bills with the same schedule ID, sets the withdrawal amount, and creates the schedule DB 2025. In the example shown, the withdrawal amounts are as follows: For schedule ID: S0001, the billing amount P (C0001) is the sum of the billing amount Q (C0002) and the billing amount T (C0005), which is the billing amount P+Q+T. For schedule ID: S0002, the billing amount R+U is the sum of the billing amount R (C0003) and the billing amount U (C0006). · Plan ID: S0003, billing amount S (C0004)

[0155] The billing aggregation module 2034 may combine all or some of the multiple expense claims for the same user. For example, the billing aggregation module 2034 may combine only the expense claims that share a preset withdrawal date among multiple expense claims issued in the same month. In addition, the billing aggregation module 2034 can add up the amounts of multiple expense claims according to the following rules. - Combine bills from multiple providers specified by the user - Combine charges specified by the business · Add up different expenses from the same business

[0156] In system 2, the schedule information includes multiple scheduled withdrawals, and therefore the schedule information notified to user terminal 10 also includes information about multiple bills as a breakdown, along with the total withdrawal amount. Then, the withdrawal application module 2035 of the management server 20 executes the above-mentioned withdrawal application process (step S321 in FIG. 13) using the schedule information related to withdrawals integrated for each user.

[0157] As explained above, when multiple expense claims are filed against the same user, at least a portion of the amounts of the multiple claim claims are consolidated and a debit request is submitted. This reduces the number of debit transactions compared to scheduling a debit for each claim, thereby reducing the fees required for deposit procedures. Furthermore, because the debit schedule can be notified with the combined amount of multiple claims, the convenience of the user checking the schedule information is ensured.

[0158] <7. Other Modifications> Next, other modifications of System 1 and System 2 will be described. For example, in systems 1 and 2, user information related to an account transfer that has already been registered can be carried over to a newly registered account transfer. In this case, by applying for an account transfer to another business using a user ID, the user information already registered in the user DB 2022 can be reused.

[0159] In addition, in Systems 1 and 2, a business operator already registered for account transfer can be inherited for a newly registered account transfer. In this case, by applying for account transfer to another user using the business operator ID, the business operator information already registered in the business operator DB2021 can be reused.

[0160] Furthermore, in Systems 1 and 2, a user can use multiple transfer accounts. For example, a user may register information about multiple transfer accounts in advance as user information, and select the transfer account to be used for the transfer related to the application prior to applying for account transfer registration. In this case, the assignment of planned IDs in System 2 will be such that a common ID is assigned to the same transfer account of the same user.

[0161] Furthermore, in Systems 1 and 2, businesses can use multiple deposit accounts. For example, a business may register information about multiple deposit accounts in advance as business information, and select the deposit account to be used for the deposit related to the application prior to applying for account transfer registration. In this case, deposit IDs in Systems 1 and 2 will be assigned in a common manner to the same deposit account of the same business.

[0162] Furthermore, systems 1 and 2 can be linked with other services. Specifically, systems 1 and 2 may obtain existing billing data from other services to create billing DB2023. In this case, it is also possible to create a bill that combines billing from the business and billing from other services. Specifically, when a parent uses a childcare support tool introduced in a nursery school, it is possible to create billing information that combines the cost of the childcare support tool and the cost of the nursery school. This reduces the number of bills and the hassle of payment for the payer.

[0163] Furthermore, in each of the above embodiments, the management server 20 is configured to accept information input from the user terminal 10, perform the necessary calculations, and then display the information on the user terminal 10, but this configuration is not limited to this. For example, some or all of the above functions may be configured to receive input at the user terminal 10, process the program within the user terminal 10, and display the program on the display 132 of the user terminal 10. To achieve such a configuration, the user may access the management server 20 via the user terminal 10, install a program provided by the management server 20 into the user terminal 10, and perform the processing within the user terminal 10. In this case, the management server 20 may not have some or all of the functional modules provided in the control unit 203 as its functions.

[0164] While the preferred embodiments of the present disclosure have been described above, the present disclosure is not limited to the same embodiments, and includes the inventions set forth in the claims and their equivalents. Furthermore, the configurations of the devices described in the above embodiments and modifications can be partially omitted or combined as long as no technical contradiction occurs.

[0165] <8. Notes> The matters described in the above embodiments will be supplemented below.

[0166] (Appendix 1) A program for use in a computer having a processor and supporting the use of account transfer, The processor A step of acquiring business information about the business and user information including information about a transfer account used for a direct debit payment from a user for the cost of the business's goods or services (steps S121 and S122); A step of submitting an application for account transfer registration to a collection agency server managed by the collection agency using the user information and business information (step S123); A step of accepting a bill to the user from a business operator terminal used by the business operator (step S221); a step of notifying a user terminal used by the user of schedule information indicating a schedule of withdrawals from the transfer account based on the expense claim (step S223); A step of requesting the collection agent server to execute a withdrawal based on the schedule information (step S321); A program that executes the steps of notifying the user terminal of the performance information indicating the performance of withdrawals received from the collection agency server (steps S423, S425).

[0167] (Appendix 2) The processor further Execute a step of depositing an amount of the expense corresponding to the debited expense claim to the business operator based on the performance information; In the step of paying the fee, 2. The program according to claim 1, wherein, when there are multiple expense claims from the same business, at least a portion of the expenses relating to the multiple expense claims is added together and paid to the business.

[0168] (Appendix 3) In the step of notifying the user terminal of the performance information (step S425), If the withdrawal is not possible, notify the user terminal of this fact together with a request to make payment using an alternative payment method; In the step of paying the fee, 3. The program of claim 2, wherein the additional amount paid using an alternative payment method is added together as the cost relating to multiple invoices from the same business.

[0169] (Appendix 4) In the step of requesting execution of withdrawal (step S321), 2. The program according to claim 1, wherein when there are multiple expense claims for the same user, at least a portion of the amounts of the multiple expense claims are consolidated and a withdrawal request is made.

[0170] (Appendix 5) 1. A method for use in a computer having a processor for facilitating the use of credit transfers, the method comprising: The processor: A step of acquiring business information about the business and user information including information about a transfer account used for a direct debit payment from a user for the cost of the business's goods or services (steps S121 and S122); A step of submitting an application for account transfer registration to a collection agency server managed by the collection agency using the user information and business information (step S123); A step of accepting a bill to the user from a business operator terminal used by the business operator (step S221); a step of notifying a user terminal used by the user of schedule information indicating a schedule of withdrawals from the transfer account based on the expense claim (step S223); A step of requesting the collection agent server to execute a withdrawal based on the schedule information (step S321); and a step of notifying the user terminal of the record information indicating the record of withdrawals received from the collection agent server (steps S423, S425).

[0171] (Appendix 6) A system including a computer having a processor and supporting the use of account transfers, The processor: A means for acquiring business information relating to a business and user information including information on a transfer account used for a direct debit to be used for payment from a user for the cost of the business's goods or services; A means for submitting an application for account transfer registration to a collection agency server managed by the collection agency using user information and business information; A means for receiving a bill for a user from a business operator terminal used by the business operator; means for notifying a user terminal used by the user of schedule information indicating a schedule of withdrawals from the transfer account based on the expense claim; A means for requesting the collection agent server to execute a withdrawal based on the schedule information; The system also includes a means for notifying a user terminal of performance information indicating the performance of withdrawals received from the collection agency server. [Explanation of symbols]

[0172] 1. Direct Debit Support System 10 User terminal 20 Management Server 202 Storage section 203 Control Unit 2031 Receiving Control Module 2032 Transmission Control Module 2033 Registration Application Module 2034 Billing Summary Module 2035 Withdrawal Application Module 2036 Performance Summary Module 2037 Notification Module 2038 Deposit Module 30 Collection Agent Server 40 Operator terminal 50 Financial institution servers

Claims

1. A program for use in a computer having a processor and supporting the use of payments from users, comprising: the processor, acquiring business information relating to the business and user information including information on a financial institution account used for the payment from the user for the cost of goods or services of the business; a step of submitting an application for registration of the account of the financial institution to a collection agency server managed by the collection agency using the user information and the business information; receiving a bill to the user from a business operator terminal used by the business operator; a step of notifying a user terminal used by the user of information related to the expense claim based on the expense claim; a step of requesting the collection agency server to execute a withdrawal from the account of the financial institution based on the expense claim based on the information related to the expense claim; and notifying the user terminal of performance information received from the collection agency server, the performance information indicating the actual deductions from the account of the financial institution based on the expense claim.

2. The processor further comprises:

2. The program according to claim 1, further comprising a step of depositing an amount of the fee equivalent to the debited fee claim to the business operator based on the performance information.

3. In the step of depositing the expenses, 3. The program according to claim 2, wherein, when there are a plurality of expense claims from the same business, at least a portion of the expenses relating to the plurality of expense claims is added together and paid to the business.

4. In the step of notifying the user terminal of the performance information, If the withdrawal is not possible, notify the user terminal of this fact together with a request to make payment using an alternative payment method; In the step of depositing the expenses, The program according to claim 3, wherein the additional amount paid using the alternative payment method is added up as expenses relating to multiple invoices from the same business.

5. In the step of requesting execution of the withdrawal, 2. The program according to claim 1, wherein, when there are a plurality of billings for the same user, at least a portion of the amounts of the billings are integrated and the deduction is requested.

6. 1. A computer-implemented method for facilitating the receipt of payments from a user, the computer-implemented method having a processor, the method comprising: the processor: acquiring business information relating to the business and user information including information on a financial institution account used for the payment from the user for the cost of goods or services of the business; a step of submitting an application for registration of the account of the financial institution to a collection agency server managed by the collection agency using the user information and the business information; receiving a bill to the user from a business operator terminal used by the business operator; a step of notifying a user terminal used by the user of information related to the expense claim based on the expense claim; a step of requesting the collection agency server to execute a withdrawal from the account of the financial institution based on the expense claim based on the information related to the expense claim; and notifying the user terminal of performance information received from the collection agency server, the performance information indicating the actual debits from the account of the financial institution based on the expense claim.

7. 1. A system comprising a computer having a processor and facilitating the utilization of payments from users, the processor: A means for acquiring business information regarding the business and user information including information on a financial institution account used for the payment from the user for the cost of goods or services of the business; A means for submitting an application for registration of the account of the financial institution to a collection agency server managed by a collection agency using the user information and the business information; means for receiving a bill for the user from a business operator terminal used by the business operator; means for notifying a user terminal used by the user of information relating to the expense claim based on the expense claim; a means for requesting the collection agency server to execute a withdrawal from the account of the financial institution based on the expense claim, based on the information related to the expense claim; A system comprising: a means for notifying the user terminal of performance information received from the collection agency server, the performance information indicating the performance of deductions from the account of the financial institution based on the expense claim.

Images