JP7063963B2 - Payment support system, payment support method and payment support program - Google Patents

Description

The present invention relates to a payment support system, a payment support method, and a payment support program for supporting accurate payment.

When remittances are made in transactions such as product purchases, techniques for detecting fraud and fraudulent remittances and calling attention are being studied (for example, Patent Documents 1 to 3).
The technology described in Patent Document 1 accepts transfer destination information, and there is a high possibility that the transfer destination account is a deposit account used for transfer fraud based on the transaction history of the transfer destination account included in the transfer destination information. Determine if.

In the technique described in Patent Document 2, a fraud information database storing a damage information file containing the account information used for the transfer fraud and the damage information consisting of the damage contents is connected to the host computer.

In the technique described in Patent Document 3, the account information of the transfer destination in the transaction information is obtained based on the transaction information in which the customer, the account information indicating the information of the transfer destination account, and the transaction history in this account are associated with each other. Determine if the indicated account is a suspicious account.

Japanese Unexamined Patent Publication No. 2007-27410 Japanese Unexamined Patent Publication No. 2009-157594 Japanese Unexamined Patent Publication No. 2014-206771

However, when a transaction is made, payment is made through processes such as quotation, delivery, and billing. It takes time and effort to manage a plurality of transaction forms used in such a process and make payments.

A payment support system that solves the above problems includes a transaction information storage unit that stores information related to transactions using forms, and a control unit that is connected to a user terminal. Then, the control unit acquires the form image of the transaction form used for payment, and by character recognition of the form image, acquires the form description information including the form type and transaction content of the transaction form, and the transaction information storage unit. From, the related form related to the transaction form is specified based on the form description information, and the payment using the transaction form is made based on the comparison between the form description information of the transaction form and the form description information of the related form. Is determined, and the transaction result using the transaction form is recorded in the transaction information storage unit.

According to the present invention, it is possible to support a transaction while accurately and efficiently managing the forms used for payment.

Explanatory drawing of the payment support system of 1st Embodiment. Explanatory drawing of the hardware configuration of 1st Embodiment. It is explanatory drawing of the storage part of 1st Embodiment, (a) is the user information storage part, (b) is the explanatory drawing of the transaction information storage part. Explanatory drawing of the processing procedure of 1st Embodiment. Explanatory drawing of the form information storage part of 2nd Embodiment. Explanatory drawing of the processing procedure of 2nd Embodiment. Explanatory drawing of the processing procedure of another embodiment.

(First Embodiment)
Hereinafter, an embodiment in which the payment support system, the payment support method, and the payment support program are embodied will be described with reference to FIGS. 1 to 4. In this embodiment, it is assumed that the payment of the user is supported.
In the service that supports this payment, as shown in FIG. 1, a user terminal 10, a support server 20, and a host system 30 connected via a network (Internet) are used.

(Hardware configuration example)
FIG. 2 is a hardware configuration example of an information processing apparatus H10 that functions as a user terminal 10, a support server 20, a host system 30, and the like.

The information processing device H10 includes a communication device H11, an input device H12, a display device H13, a storage device H14, and a processor H15. Note that this hardware configuration is an example, and may have other hardware.

The communication device H11 is an interface that establishes a communication path with another device and executes data transmission / reception, such as a network interface card or a wireless interface.

The input device H12 is a device that receives input from a user or the like, and is, for example, a mouse, a keyboard, or the like. The display device H13 is a display, a touch panel, or the like that displays various information.

The storage device H14 is a storage device (for example, a user information storage unit 22 and a transaction information storage unit, which will be described later) for storing data and various programs for executing various functions of the user terminal 10, the support server 20, and the host system 30. 23 mag). An example of the storage device H14 is a ROM, RAM, hard disk, or the like.

The processor H15 controls each process in the user terminal 10, the support server 20, and the host system 30 by using the programs and data stored in the storage device H14. Examples of the processor H15 include a CPU, an MPU, and the like. The processor H15 expands a program stored in a ROM or the like into a RAM and executes various processes corresponding to various processes. For example, when the application programs of the user terminal 10, the support server 20, and the host system 30 are started, the processor H15 operates a process for executing each process described later.

The processor H15 is not limited to the one that performs software processing for all the processing executed by itself. For example, the processor H15 may include a dedicated hardware circuit (for example, an integrated circuit for a specific application: ASIC) that performs hardware processing for at least a part of the processing executed by the processor H15. That is, the processor H15 is (1) one or more processors that operate according to a computer program (software), (2) one or more dedicated hardware circuits that execute at least a part of various processes, or ( 3) It can be configured as a circuitry including a combination thereof. The processor includes a CPU and a memory such as a RAM and a ROM, and the memory stores a program code or a command configured to cause the CPU to execute a process. Memory or computer readable media includes any available medium accessible by a general purpose or dedicated computer.

(Function of payment support system)
Next, the function of the payment support system will be described with reference to FIG.
The user terminal 10 is a computer terminal used by a user who uses this service.

The support server 20 is a computer system that supports payment based on transaction forms such as invoices. The support server 20 includes a control unit 21, a user information storage unit 22, and a transaction information storage unit 23.

The control unit 21 performs processes described later (each process such as a payment support stage, an analysis stage, an evaluation stage, etc.). By executing the payment support program for that purpose, the control unit 21 functions as the payment support unit 211, the analysis unit 212, and the evaluation unit 213.

The payment support unit 211 executes a process of supporting payment to the payee.
The analysis unit 212 executes the character recognition process using the form image. Then, the analysis unit 212 executes a process of acquiring form description information (form type, issue date, business partner, transaction content, etc.) from the form image by character recognition processing.

The evaluation unit 213 executes a process of confirming the validity of the transaction based on the character recognition result and the related form. The evaluation unit 213 holds necessary form information in which the form type of the related form required for payment is recorded according to the transaction content. This required form information includes, for example, the required form type (“quote, invoice”, “quotation, invoice, invoice” according to the product name and product code of the product to be paid included in the transaction content. , "Invoice only", etc.) are recorded.

As shown in FIG. 3A, a user management record 220 for a user of a financial institution is recorded in the user information storage unit 22. The user management record 220 is recorded when a user opens an account at a financial institution. The user management record 220 records data related to a user code, a user name, a password, an account identifier, and a contact.

In the user code data area, data regarding an identifier for identifying each user of a financial institution is recorded.
In the user name data area, the user's name and data related to the name are recorded.

In the password data area, authentication information (password) used for personal authentication when logging in to the support server 20 is recorded.
In the account identifier data area, data related to an identifier (head office code, type code, account number, etc.) for identifying an account held by this user is recorded.
Data related to the user's contact information (for example, an e-mail address) is recorded in the contact data area.

As shown in FIG. 3B, the transaction information storage unit 23 records a transaction management record 230 for managing a form image acquired from a user. The transaction management record 230 is recorded when the form image is acquired from the user terminal 10. Data related to the registration date, user code, form image, form description information (form type, issue date, business partner, transaction content), and status are recorded in the transaction management record 230.

In the registration date data area, data related to the date and time (date and time) when the form image was acquired is recorded.
In the user code data area, data regarding an identifier for identifying the user who sent the form image is recorded.

In the form image data area, an image of a payment-related form acquired from the user terminal 10 is recorded. By character recognition of this image, it is possible to acquire information on the form type, issue date, business partner, and transaction content.

Data related to the type of payment-related form (for example, quotation, purchase order, invoice, invoice, etc.) is recorded in the form type data area.
In the issue date data area, data regarding the issue date of this payment-related form is recorded.

Data for identifying the issuer (customer) of this payment-related form is recorded in the customer data area.
Data for specifying the transaction content is recorded in the transaction content data area. As the transaction content, a transaction number, a product name, a product code, the number of transactions, an amount of money, etc. can be used.

In the status data area, data for specifying the transaction status (transaction result) of this payment-related form is recorded. If payment is completed for this transaction, an end flag is recorded.

A host system 30 of a financial institution is connected to the support server 20. The host system 30 is a computer system of a bank that manages an account opened in a bank and provides a payment service. Therefore, the host system 30 includes an account storage unit that stores information about the account to be managed.

(Payment support processing)
Next, the processing procedure of the payment support processing in this payment support system will be described with reference to FIG.

First, the user who pays based on the form accesses the support server 20 via the network by using the user terminal 10.
In this case, the control unit 21 of the support server 20 executes the login process (step S1-1). Specifically, the payment support unit 211 of the control unit 21 outputs a login screen to the user terminal 10. This login screen is provided with input fields for a user code and a password. The payment support unit 211 acquires the user code and password entered on the login screen from the user terminal 10 and confirms whether or not they are registered in the user information storage unit 22. If there is no registration in the user information storage unit 22, the payment support unit 211 refuses to log in.

Next, when the registration of the user code and the password can be confirmed, the control unit 21 of the support server 20 executes the acquisition process of the form image (step S1-2). Specifically, the payment support unit 211 of the control unit 21 outputs a form upload screen to the user terminal 10. In this case, the user captures a photographed or scanned form image of a transaction form to be paid (for example, a quotation, an order form, an invoice, an invoice, etc.) into the user terminal 10. Then, the captured form image is specified on the form upload screen. In this case, the payment support unit 211 acquires the form image (process target form) specified on the form upload screen from the user terminal 10. Then, the payment support unit 211 generates a transaction management record 230 in which the registration date (image acquisition date), the user code, and the form image are recorded for the processing target form, and records the transaction information storage unit 23.

Next, the control unit 21 of the support server 20 executes the image analysis process (step S1-3). Specifically, the analysis unit 212 of the control unit 21 performs character recognition of characters included in the form image acquired from the user terminal 10. Next, the analysis unit 212 acquires the form description information (form type, issue date, business partner, transaction content) based on the character recognition result. Then, the analysis unit 212 records the form description information (form type, issue date, business partner, transaction content) in association with the form image of the transaction management record 230.

Next, the control unit 21 of the support server 20 executes the search process of the related form (step S1-4). Specifically, the evaluation unit 213 of the control unit 21 identifies the transaction management record 230 in which the end flag is not recorded in the status data area in the transaction information storage unit 23. Further, the evaluation unit 213 extracts the transaction management record 230 in which the processing target form and the business partner are common. In this case, the transaction management record 230 in which the date before the issue date of the form to be processed is recorded as the issue date is extracted.

Next, the control unit 21 of the support server 20 executes the consistency confirmation process (step S1-5). Specifically, when a plurality of related forms are specified, the evaluation unit 213 of the control unit 21 compares the transaction contents of the processing target form with the transaction contents of other related forms. For example, when the form to be processed is a delivery note and the other related form is a purchase order, the match of the transaction number, product name, product code, and number of transactions is confirmed. If the form to be processed is an invoice and the other related forms are quotations, the match of transaction number, product name, product code, number of transactions, and amount is confirmed.

If no other related form is extracted in the related form search process (step S1-4), the control unit 21 of the support server 20 skips the consistency confirmation process (step S1-5). do.

Next, the control unit 21 of the support server 20 executes a determination process as to whether or not it is a payment target (step S1-6). Specifically, the evaluation unit 213 of the control unit 21 confirms the form type of the transaction management record 230 of the form to be processed. If "invoice" is recorded as the form type, it is determined to be a payment target.

If it is determined that the payment is not applicable (in the case of "NO" in step S1-6), the payment support process is terminated.
On the other hand, when it is determined that the payment is to be made (when "YES" in step S1-6), the control unit 21 of the support server 20 executes a process for specifying the type of required form according to the billing target (step S1-7). ). Specifically, the evaluation unit 213 of the control unit 21 specifies a necessary related form by using the transaction content (product name, product code) and the necessary form information of the transaction management record 230.

Next, the control unit 21 of the support server 20 executes a determination process as to whether or not there is a missing form (step S1-8). Specifically, the evaluation unit 213 of the control unit 21 confirms whether or not the necessary related form can be specified when the form to be processed is an invoice. Here, if the required related form cannot be specified, it is determined that there is a missing form. On the other hand, if other necessary related forms can be identified, it is determined that there is no missing form.

When it is determined that there is no insufficient form (when "NO" in step S1-8), the control unit 21 of the support server 20 executes the status recording process (step S1-9). Specifically, the evaluation unit 213 of the control unit 21 records the related form confirmation flag as a status in the transaction management record 230.

On the other hand, when it is determined that there is a shortage form (when "YES" in step S1-8), the control unit 21 of the support server 20 executes the alerting process (step S1-10). Specifically, the payment support unit 211 of the control unit 21 outputs a warning screen to the user terminal 10. This alert screen includes a message indicating that there is a missing form and information on the form type of the missing form. In this case, the user confirms the missing form. For example, if the missing form is forgotten to be registered, the form image of the missing form is specified on the alert screen. In this case, the control unit 21 records the insufficient form in the transaction information storage unit 23 by the form image acquisition process (step S1-2) and the image analysis process (step S1-3). Then, the evaluation unit 213 records the related form confirmation flag as the status in the transaction management record 230.

If the missing form is unnecessary, a confirmation input indicating that the related form is unnecessary is input on the alert screen. Also in this case, the payment support unit 211 records the related form confirmation flag as the status in the transaction management record 230.

Next, the control unit 21 of the support server 20 executes a determination process as to whether or not it has been confirmed (step S1-11). Specifically, the evaluation unit 213 of the control unit 21 determines that the transaction management record 230 has been confirmed when the related form confirmation flag is recorded as the status.

When it is determined that the confirmation has been completed (when "YES" in step S1-11), the control unit 21 of the support server 20 executes the payment process (step S1-12). Specifically, the payment support unit 211 of the control unit 21 generates payment data in which the payee and the payment amount (billing amount) are set based on the invoice form description information. In this case, the account identifier of the user management record 220 is set in the payment source. Then, the payment support unit 211 provides the payment data to the host system 30. In this case, the host system 30 deducts the payment amount from the payment source account and remits the payment to the payment destination account based on the payment data. Then, the payment support unit 211 records the end flag as the status in the transaction management record 230 of the form to be processed and all the related forms.

On the other hand, if it is determined that the confirmation has not been completed (in the case of "NO" in step S1-11), the payment support process is terminated.

As described above, according to the present embodiment, the following effects can be obtained.
(1-1) In the present embodiment, the control unit 21 of the support server 20 executes a form image acquisition process (step S1-2) and an image analysis process (step S1-3). As a result, payment can be made using the contents included in the form image.

(1-2) In the present embodiment, the control unit 21 of the support server 20 executes a search process for related forms (step S1-4). This makes it possible to identify other forms related to the form to be processed.

(1-3) In the present embodiment, the control unit 21 of the support server 20 performs a consistency confirmation process (step S1-5) and a required form type identification process (step S1-7) according to the request target. Run. As a result, it is possible to determine the shortage of a predetermined required form by business practice or the like.

Then, when it is determined that there is a shortage form (when "YES" in step S1-8), the control unit 21 of the support server 20 executes the alerting process (step S1-10). As a result, if the required forms are insufficient, confirmation can be urged.

(1-4) In the present embodiment, when it is determined that the payment is to be made and the confirmation is confirmed (when “YES” in steps S1-6 and S1-11), the control unit 21 of the support server 20 pays. The process is executed (step S1-12). As a result, it is possible to confirm the existence of a series of forms and make an accurate payment.

(Second Embodiment)
Next, a second embodiment for determining appropriateness based on the form of the form will be described with reference to FIGS. 5 and 6. In the first embodiment, the control unit 21 of the support server 20 executes the consistency confirmation process (step S1-5). In the second embodiment, in addition to the consistency confirmation process (step S1-5), a form confirmation process using the form form of the form to be processed is executed.

As shown in FIG. 5, the support server 20 is provided with a form information storage unit 24. The form information storage unit 24 records a form management record 240 relating to the morphological characteristics of payment-related forms for making payments. The form management record 240 is recorded when a new business partner is registered, and is updated when the form image analysis process is performed. In this form management record 240, data regarding a business partner code, a business partner name, a form type, and form feature information are recorded. Here, the form feature information includes font information (font type and font size), shape feature information (imprint, form layout), and the like.

In the account code data area, data regarding an identifier for identifying an account to make a payment is recorded.
Data related to the name of this business partner is recorded in the business partner name data area.

In the form type data area, data related to the type of payment-related form used by this business partner is recorded.
Data related to the font type used in this form and data related to the font size are recorded in the font type data area and the font size data area, respectively.

In the imprint data area, data regarding the feature amount of the imprint shape stamped on the form is recorded.
In the form layout data area, data related to the feature amount of the form layout (arrangement shape) is recorded. Here, in the payment-related form, the feature amount related to the arrangement of the user name column, the product name column, the amount column, the claimant column, etc. is recorded excluding the content whose description is changed according to the transaction. The contents that are changed according to the transaction include, for example, an invoice number, an address, an invoice date, a subject, a payment deadline, a product name, a quantity / unit, a unit price, an invoice amount, and the like.

(Form confirmation process)
As shown in FIG. 6, the control unit 21 of the support server 20 executes the form specifying process (step S2-1). Specifically, the analysis unit 212 of the control unit 21 specifies the font information in the form image. Here, at the time of character recognition, the font type and font size are specified based on the shape of the character.

Further, the analysis unit 212 identifies the imprint by pattern recognition of the form image as the shape feature information, and calculates the feature amount of the imprint shape.
Further, the analysis unit 212 specifies the layout of the form by pattern recognition as the shape feature information. Specifically, the feature amount indicating the description position and shape of the claimant column, payee column, product column, amount column, etc. in the form, and the positional relationship (arrangement shape) of each column is calculated. Here, the image of the content whose description is changed according to the transaction is ignored.

Then, the control unit 21 of the support server 20 executes the collation process of the form form (step S2-2). Specifically, the analysis unit 212 of the control unit 21 extracts the form management record 240 recorded as the business partner name by the claimant in the payee information. Then, the analysis unit 212 calculates the form feature information based on the form feature information (font information such as font type and font size, shape feature amount such as imprint and layout) recorded in the form management record 240, and the form feature information calculated based on the image. And compare.

Next, the control unit 21 of the support server 20 executes a determination process as to whether or not confirmation is required (step S2-3). Specifically, the payment support unit 211 of the control unit 21 determines that confirmation is required when there is a large difference between the form feature information of the form management record 240 and the form feature information of the form image. For example, if the font type and font size are different, it is determined that confirmation is required. Also, if there is a difference between the imprint feature amount and the layout feature amount that is greater than or equal to the confirmation reference value, it is determined that confirmation is required.

When it is determined that confirmation is unnecessary (when "NO" in step S2-3), the control unit 21 of the support server 20 executes the status update process (step S2-4). Specifically, the evaluation unit 213 of the control unit 21 records the form confirmed flag as the status in the transaction management record 230. Then, when the form confirmed flag is recorded, the control unit 21 of the support server 20 executes the payment process (step S1-12).

On the other hand, when it is determined that confirmation is required (when "YES" in step S2-3), the control unit 21 of the support server 20 executes the alerting process (step S2-5). Specifically, the payment support unit 211 of the control unit 21 outputs a warning screen to the user terminal 10. This alert screen includes a message indicating that the form is different from the pattern of the business partner.

Next, the control unit 21 of the support server 20 executes a determination process as to whether or not it has been confirmed (step S2-6). Specifically, the user confirms the transaction content by using the user terminal 10, and inputs the confirmation result on the alert screen. If you have any concerns, select the Stop Payment button, and if you have no concerns, select the Confirmation Complete button. The payment support unit 211 of the control unit 21 acquires the confirmation result based on the selected button.

When it is determined that the confirmation has been completed (when "YES" in step S2-6), the control unit 21 of the support server 20 executes the data update process (step S2-7). Specifically, the analysis unit 212 of the control unit 21 is a registration from the transaction information storage unit 23, which is a transaction management record 230 related to the same customer name and form type, and is included in a predetermined period (evaluation target period) from the latest. Extract records with recorded days. Then, the analysis unit 212 calculates the statistical values (for example, average values) of the font information and the shape feature information recorded in each transaction management record 230, and obtains the form management record 240 recorded in the form information storage unit 24. Update.
On the other hand, if it is determined that the confirmation has not been completed (in the case of "NO" in step S2-6), the control unit 21 of the support server 20 executes the payment cancellation process (step S2-8). Specifically, the evaluation unit 213 of the control unit 21 records a non-payable flag as a status in the transaction management record 230.

As described above, according to the second embodiment, the following effects can be obtained in addition to the effects of the first embodiment.
(2-1) In the second embodiment, the control unit 21 of the support server 20 executes the form specifying process (step S2-1) and the form form collation process (step S2-2). As a result, since there is a concern about fraud using the image information of the form, it is possible to detect the form that needs to be confirmed and call attention to it.

This embodiment can be modified and implemented as follows. The present embodiment and the following modified examples can be implemented in combination with each other within a technically consistent range.
-In each of the above embodiments, an example in which the support server 20 and the host system 30 are separated is shown, but the hardware configuration is not limited to this, and both can be configured as one.

-In the first embodiment, the control unit 21 of the support server 20 executes a process for specifying the type of required form according to the billing target (step S1-7). Here, using the required form information, other necessary related forms are specified according to the product name and the product code. The specification of the required form is not limited to the case where the product name or product code is used. For example, the form type of the required form may be specified according to the amount of money. Here, when the payment amount is more than the predetermined amount, "estimate, invoice, invoice" is set as the required form, and the required form is increased more than when the payment amount is less than the predetermined amount.

In addition, the required form may be specified according to the transaction frequency. For example, when the transaction frequency is high, the number of required forms may be reduced.
Further, the required form may be specified according to the transaction history. For example, the used form is recorded in the transaction history. Then, the form type used in the transaction history is specified as the required form.

-In the second embodiment, the control unit 21 of the support server 20 executes the form specifying process (step S2-1). The form of the form is not limited to the statistical value of the characteristic information. For example, the image itself may be used for deep learning. In this case, deep learning is performed using the form image in which payment is canceled, the form image in which fraud is performed (abnormal image), the form image in which there is no problem (normal image), and the like as teacher information. As a result, a trained model that predicts the certainty of the presence or absence of fraud is generated. Then, the form image of the form to be processed is input to the trained model, and the certainty of the presence or absence of fraud is predicted.

-In the second embodiment, the control unit 21 of the support server 20 executes the collation process of the form form (step S2-2). Here, the transaction management record 230 for which payment has been canceled may be extracted from the transaction information storage unit 23, and the feature amount of the form image having a fear of fraud may be calculated based on these form images. In this case, the feature information of the form image for which payment was canceled in the data update process (step S2-7) is recorded in the form information storage unit 24. Then, in the analysis process, it is determined whether the feature amount of the form image to be analyzed is close to either the feature amount of the form image having no problem or the feature amount of the form having fear of fraud.

-In the second embodiment, the control unit 21 of the support server 20 executes the collation process of the form form (step S2-2). Here, the authenticity may be determined based on the form form of the form to be processed and the form form of the related form. In this case, the form feature amounts (font information, shape feature information) of the form form of the form to be processed and the related form are compared, and if the degree of matching is equal to or more than the reference value, it is determined to be appropriate. On the other hand, if the degree of coincidence is equal to or higher than the reference value, it is determined that confirmation is required (“YES” in step S2-3), and the control unit 21 of the support server 20 executes an alert process (step S2-5). .. For example, if it is the same business partner, it is assumed that a series of forms (quotations to invoices) have a common form, and the authenticity of the business partner can be confirmed by the commonality of this form. ..

-In the first embodiment, the control unit 21 of the support server 20 executes the consistency confirmation process (step S1-5). In addition to this, external information may be used to determine the appropriateness of the transaction content of each form.

For example, the support server 20 can be connected to a trading site via the Internet. This trading site is a computer system that manages online transactions with users. This trading site includes not only the payee's business, but also the trading sites of other businesses that offer the same type of goods. It is assumed that each trading site publishes the products to be sold and the selling price via the Internet.

Then, as shown in FIG. 7, the control unit 21 of the support server 20 executes the product information search process (step S3-1). Specifically, the evaluation unit 213 of the control unit 21 searches the seller's transaction site based on the character-recognized claimant information. Then, when the transaction site of the claimant can be specified, the evaluation unit 213 searches the transaction site for the product to be paid based on the character-recognized product information.

Next, the control unit 21 of the support server 20 executes a determination process as to whether or not the product can be confirmed (step S3-2). Specifically, the evaluation unit 213 of the control unit 21 determines that the product actually exists and the product can be confirmed when the product to be paid can be specified on the transaction site of the payee.

When it is determined that the product can be confirmed (when "YES" in step S3-2), the control unit 21 of the support server 20 executes a determination process as to whether or not the price is appropriate (step S3-3). Specifically, the payment support unit 211 of the control unit 21 searches for a transaction site dealing with the product to be traded from the product information, and acquires the price at each transaction site. Next, the payment support unit 211 calculates a statistical value (for example, an average value) of the acquired price. Then, the payment support unit 211 compares the statistical value calculated from the transaction site with the invoice amount. If the difference between the calculated statistical value and the billed amount is equal to or greater than the judgment standard amount, it is judged that the price is not appropriate.

When it is determined that the price is appropriate (when "YES" in step S3-3), the control unit 21 of the support server 20 executes the status update process (step S3-4). Specifically, the evaluation unit 213 of the control unit 21 records an externally confirmed flag as a status in the transaction management record 230. Then, when the externally confirmed flag is recorded, the control unit 21 of the support server 20 executes the payment process (step S1-12).

On the other hand, when it is determined that the product cannot be confirmed or the price is not appropriate (when "NO" in steps S3-2 and S3-3), the control unit 21 of the support server 20 performs a warning process. Execute (step S3-5). Specifically, the payment support unit 211 of the control unit 21 outputs a warning screen to the user terminal 10. This alert screen contains a message indicating that the product cannot be confirmed and that the price difference is large.

As a result, it is possible to identify the possibility that there is no substance in handling the product and call attention to it. In addition, it is possible to detect a situation in which the billed amount is free from the general price and call attention.

10 ... user terminal, 20 ... support server, 21 ... control unit, 211 ... payment support unit, 212 ... analysis unit, 213 ... evaluation unit, 22 ... user information storage unit, 23 ... transaction information storage unit, 30 ... host system.

Claims (10)

A transaction information storage unit that stores information related to transactions using forms,
It is a payment support system equipped with a control unit connected to the user terminal.
The control unit
Get the form image of the transaction form used for payment,
By character recognition of the form image, the form description information including the form type and transaction contents of the transaction form is acquired.
In the transaction information storage unit , based on the form description information, a form used in a series of processes in the transaction of the transaction form and related to the transaction form is specified.
Based on the comparison between the form description information of the transaction form and the form description information of the related form, it is determined whether or not payment using the transaction form is possible.
A payment support system characterized in that a transaction result using the transaction form is recorded in the transaction information storage unit. The payment support system according to claim 1, wherein the control unit identifies a necessary related form based on the form type and transaction content of the transaction form. The control unit
Calculate the form feature amount of the transaction form,
The payment support system according to claim 1 or 2 , wherein it is determined whether or not payment is possible based on the morphological feature amount and the morphological feature amount of the related form. The payment support system according to claim 3 , wherein the font information included in the form image is used as the form feature amount of the transaction form. The payment support system according to claim 3 or 4, wherein layout information included in the form image is used as the form feature amount of the transaction form. The payment support system according to any one of claims 3 to 5 , wherein an imprint included in the form image is used as the form feature amount of the transaction form. By character recognition of the form image, the payment target product included in the form image is specified.
Search for public information about the payment target product and
The payment support system according to any one of claims 1 to 6 , wherein when the public information of the payment target product cannot be obtained, a warning is output to the user terminal. By character recognition of the form image, the billing amount included in the form image is specified, and the billing amount is specified.
Obtain the published price information for the payment target product and
The payment support system according to claim 7 , wherein a warning is output to the user terminal based on a comparison between the billed amount and a statistical value of price information. A transaction information storage unit that stores information related to transactions using forms,
It is a method for providing payment support using a payment support system equipped with a control unit connected to a user terminal.
The control unit
Get the form image of the transaction form used for payment,
By character recognition of the form image, the form description information including the form type and transaction contents of the transaction form is acquired.
In the transaction information storage unit , based on the form description information, a form used in a series of processes in the transaction of the transaction form and related to the transaction form is specified.
Based on the comparison between the form description information of the transaction form and the form description information of the related form, it is determined whether or not payment using the transaction form is possible.
A payment support method comprising recording a transaction result using the transaction form in the transaction information storage unit. A transaction information storage unit that stores information related to transactions using forms,
It is a program for providing payment support using a payment support system equipped with a control unit connected to a user terminal.
The control unit
Get the form image of the transaction form used for payment,
By character recognition of the form image, the form description information including the form type and transaction contents of the transaction form is acquired.
In the transaction information storage unit , based on the form description information, a form used in a series of processes in the transaction of the transaction form and related to the transaction form is specified.
Based on the comparison between the form description information of the transaction form and the form description information of the related form, it is determined whether or not payment using the transaction form is possible.
A payment support program characterized in that it functions as a means for recording a transaction result using the transaction form in the transaction information storage unit.

Images