CN111311369A

CN111311369A - Bill transaction matching system and method

Info

Publication number: CN111311369A
Application number: CN202010102137.3A
Authority: CN
Inventors: 陈鹏
Original assignee: Rong Yi Xing Tianjin Network Technology Co ltd
Current assignee: Rong Yi Xing Tianjin Network Technology Co ltd
Priority date: 2020-02-19
Filing date: 2020-02-19
Publication date: 2020-06-19

Abstract

The application describes a system and a method for matching bill transactions. The system includes a first terminal configured for a first user to log into the system; a second terminal configured for a second user to log into the system and configured for the second user to upload an image of the ticket to be traded to the system; and a service platform, comprising: a ticketing pricing store configured to receive ticketing pricing issued by a first user; an image recognition module configured to recognize an image of a ticket to be traded uploaded by a second user; a ticketing pricing routing rule module configured to output, via the second terminal to the second user, a sponsor and an associated sponsor price matching the uploaded image of the ticket to be traded in response to receiving a query offer request from the second user; and a legitimacy determination module configured to determine legitimacy of the trade order. The system can improve the transaction real-time performance and improve the transaction success rate.

Description

Bill transaction matching system and method

Technical Field

The invention relates to the technical field of bill transaction, in particular to a bill transaction matching system and method.

Background

Since the issuance of Bill Law in 1995, the annual average increment of bill acceptance business in China exceeds 15%, the annual average increment of bill subsidence reaches more than 10%, the proportion of bill acceptance accounting for GDP is increased to more than 30% from the original less than 10%, and the national commercial draft subsidence reaches more than 100 trillion Yuan.

Currently, in the bill circulation market, there are two general transaction modes for the bill holding enterprise and the fund party: firstly, in the traditional off-line mode transaction, a ticket holding enterprise or a fund party searches for tickets or funds meeting the requirements of the own party through respective channels, both parties need to invest higher manpower, material resources and financial resources to maintain the channels, search for goods sources and other affairs, and meanwhile, the requirements of both parties on transaction safety are limited in scale and the transaction can be achieved only on the basis of mutual trust; the second one is the internet transaction platform, which solves the problem of transaction security, but both transaction parties need to complete various qualification certifications, and generally face to the fund party (consumer), and a ticket holder needs to issue goods in advance to wait for the fund party to transact.

The ticket transaction is carried out by adopting a traditional offline transaction mode or an existing internet transaction platform, so that the transaction real-time performance of a ticket holder is low. Therefore, a need exists for a ticketing matching system that improves transaction timeliness and increases transaction success rates.

Disclosure of Invention

The application aims to provide a bill transaction method and a bill transaction system, which can improve the transaction real-time performance and improve the transaction success rate.

In one aspect, the present application describes a system for ticketing trade matching, comprising a service platform, wherein the service platform comprises:

a ticketing pricing store configured to receive ticketing pricing issued by a first user;

an image recognition module configured to recognize an image of a to-be-transacted ticket uploaded by a second user;

a ticketing pricing routing rule module configured to, in response to receiving a query quote request from a second user, output to the second user a sponsor and associated sponsor price matching the uploaded image of the ticket to be traded for the second user to confirm the trade and submit a trade order; and

a legitimacy determination module configured to determine legitimacy of the trade order.

In an embodiment, the service platform is further configured to: after the image recognition module recognizes the bill to be traded, the information of the recognized bill to be traded is presented to the second user, so that the second user can confirm whether the recognized bill to be traded is correct or not.

In one embodiment, the second user may edit the trade order when determining the trade.

In one embodiment, the ticketing pricing routing rule module matches based on one or more of the following key parameters of the ticket information: bill amount, recipient, due date, and blemish condition.

In one embodiment, the legality determining module is configured to determine the legality of the transaction order, and includes determining whether a to-be-transacted bill is endorsed and whether information of the to-be-transacted bill matches with an order bill within a specified time.

In an embodiment, the service platform is further configured to: if the legality judging module determines that the bill to be traded is not endorsed or the information of the bill to be traded is not matched with the order bill, the second user is prompted that the trading fails; and if the legality judging module determines that the bill to be traded is endorsed and the information of the bill to be traded is matched with the order bill, the trading order is provided for the first user for auditing.

In an embodiment, the service platform is further configured to: prompting the transaction to complete and updating the order status if the transaction order is approved and payment processing is performed by the first user; and the service platform is further configured to: and if the trade order is not approved, prompting that the trade fails.

In one embodiment, the system further comprises a first terminal and a second terminal, wherein the first terminal is configured for a first user to log into the system; the second terminal is configured for the second user to log into the system and configured for the second user to upload an image of a ticket to be traded to the system and to obtain a sponsor and associated sponsor price matching the uploaded image of the ticket to be traded and for the second user to confirm the trade and submit a trade order.

In one embodiment, the first terminal is a ticket holder; and the second terminal is a funding side.

In one embodiment, the first user is a ticketing party and the second user is a funding party.

The application also discloses a method for matching of bill transactions, comprising the following steps:

issuing a ticket collection pricing by the first user;

uploading, by the second user, an image of the ticket to be traded;

sending a query quote request by the second user after the ticket image to be traded is identified and confirmed;

acquiring a sponsor and a related sponsor price matched with the uploaded image of the bill to be traded, and displaying the sponsor and the related sponsor price to the second user so that the second user can confirm the trade and submit a trade order;

the validity of the trade order is judged.

In one embodiment, the method is performed by a system comprising a service platform, wherein the service platform is provided with a ticket collecting pricing database, an image identification module, a ticket collecting pricing routing rule module and a legality judgment module

The ticket collecting pricing is issued to the ticket collecting pricing base by a first user;

uploading an image of a to-be-traded bill to the service platform by a second user;

the bill image identification module identifies the uploaded bill image to be traded;

presenting, by the service platform, the identified ticket image to be transacted to the second user for confirmation;

after confirming that the identified ticket image to be traded is correct, sending a request for inquiring quotation to a service platform by the second user;

in response to receiving the sent request for inquiring quotation, the ticket collecting pricing routing rule module in the service platform outputs a sponsor matched with the uploaded image of the ticket to be traded and a related sponsor price, and the sponsor and the related sponsor price are displayed to the second user through a second terminal so that the second user can confirm the trading and submit a trading order;

and judging the legality of the trading order by a legality judging module in the service platform.

In one embodiment, the matching is based on one or more of the following key parameters of the ticket information: bill amount, recipient, due date, and blemish condition.

In one embodiment, the determining the validity of the transaction order includes determining whether the ticket to be transacted is endorsed and whether the information of the ticket to be transacted matches the order ticket within a specified time.

In one embodiment, the method further comprises: if the legality judging module determines that the bill to be traded is not endorsed or the information of the bill to be traded is not matched with the order bill, the second user is prompted that the trading fails; and if the legality judging module determines that the bill to be traded is endorsed and the information of the bill to be traded is matched with the order bill, the trading order is provided for the first user for auditing.

In one embodiment, the method further comprises: prompting the transaction to complete and updating the order status if the transaction order is approved and payment processing is performed by the first user; and

and if the trade order is not approved, prompting that the trade fails.

In one embodiment, the first terminal is a ticket holder.

In one embodiment, the second terminal is a funding side.

In one embodiment, the first user is a ticketing party; and the second user is a funding party.

The bill transaction method and the bill transaction system are used for issuing the demands by a fund party, the ticket holder initiates the transaction, the system provides intelligent matching service, the traditional mode that the current bill transaction is realized by issuing commodities by the ticket holder and initiating the transaction by selecting the commodities by the fund party is changed, the fund party is helped to accurately search the bill source, and the ticket holder is helped to complete the bill transaction more actively, quickly and directly.

The intelligent matching transaction system and the method can improve the transaction efficiency, simplify the examination and approval process and the delivery procedure of the bill transaction, form a tighter bill service and trade cooperation relationship among banks, enterprises and upstream and downstream enterprises, accelerate the turnover speed of funds, further break through the limitation of the traditional region on the bill transaction in online bill transaction, form a bill market with transparent information and fair price, ensure that the posted market forms fair bidding after the information is transparentized, provide a wider selection space for the bill transaction of the enterprises, keep track of the bill assets and support the development of entity economy, thereby ensuring that the enterprises finally obtain good economic benefits and convenient market benefits in the bill transaction market.

Drawings

FIG. 1 is a system diagram of a ticketing trade matching system of the present invention.

FIG. 2 is a flow chart of a method of matching a ticket transaction of the present invention.

Detailed Description

One or more embodiments or implementations are now described with reference to the drawings. While specific configurations and arrangements are discussed, it should be understood that this is done for illustrative purposes only. A person skilled in the relevant art will recognize that other configurations and arrangements can be employed without departing from the spirit and scope of the description. It will be apparent to those skilled in the relevant art that the techniques and/or arrangements described herein may be employed in a variety of other systems and applications other than those described herein.

References in the specification to "one implementation," "an example implementation," etc., indicate that the implementation described may include a particular feature, structure, or characteristic, but every implementation may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same implementation. Further, when a particular feature, structure, or characteristic is described in connection with an implementation, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other implementations whether or not explicitly described herein.

The embodiment of the invention relates to a bill transaction matching system and a method thereof. Currently, ticket holders and funders often use traditional offline trading modes or existing internet trading platforms to conduct ticket trading, which results in low real-time performance of ticket holder trading. Therefore, the bill transaction matching system and method can improve transaction real-time performance and improve transaction success rate.

In an embodiment of the invention, the bill transaction matching system can comprise a bill holding end, a platform system and a fund end. The ticket holder can be a computer terminal used by a ticket holder or a ticket holder. The funding end may be a computer terminal for use by a funding party or consumer.

In embodiments of the present invention, the ticketing or funding end can be implemented as any computing device, including but not limited to a Personal Computer (PC), a laptop computer, an ultra-laptop computer, a tablet computer with or without multiple cameras, a touch pad, a portable computer, a handheld computer, a palmtop computer, a Personal Digital Assistant (PDA), a cellular telephone, a television, a smart device (e.g., a smart phone, a smart tablet or a smart television), a Mobile Internet Device (MID), a messaging device, a data communication device, and the like.

It should be understood that in the present application, the term "ticketing party" may also be referred to by similar expressions "ticket holder", "user", "second user", "ticketing end user", and so on. The term "principal" may also be referred to by similar expressions "principal," "user," "first user," "end-of-fund user," "consumer," and the like. The term "funder ticketing pricing repository" may also be referred to by similar expressions "funder ticketing pricing repository", "pricing repository", and the like. The term "ticket image recognition module" may also be referred to by the similar expressions "image recognition module", "pricing store", etc. The term "fund collection pricing routing rule module" may also be referred to by the similar expressions "fund collection pricing routing rule module", "receipt pricing routing rule module", "routing rule module", and the like. The term "order validity judging module" may also be referred to by the similar expressions "validity judging module", "judging module", and the like. The term "platform system" may also be referred to by the similar expressions "business platform", "trading platform", "system", "platform", etc. The term "funding side" may also be referred to by similar expressions "funding side terminal", "first terminal", and the like. The term "ticketing authority" may also be referred to by similar expressions "ticketing authority terminal", "second terminal", etc.

FIG. 1 illustrates the architecture of a clearing transaction matching system according to an embodiment of the present invention. As shown in fig. 1, the architecture of a clearing transaction matching system may include a ticketing end, a platform system, and a funding end. In an exemplary embodiment, the ticket holder can log in to the ticket holder through a wired or wireless network, so as to carry out transaction with the fund party on the platform system. Similarly, in an exemplary embodiment, the funding party may also log into the funding end through a wired or wireless network to conduct a transaction with the ticketing party on the platform system. In embodiments of the present invention, example wired or wireless networks include, but are not limited to: a wired or wireless local area network, a wired or wireless personal area network, a wired or wireless metropolitan area network, a cellular or satellite network, or the like.

A platform system:

as shown in fig. 1, the platform system (also referred to as "service platform") includes a sponsor ticketing pricing library, a ticket image identification module, a sponsor ticketing pricing routing rule module, an order validity judgment module, and the like.

In an exemplary embodiment, the sponsor ticketing pricing store is arranged to publish the ticketing pricing. In an exemplary embodiment, the fund side issues the expected ticketing pricing into the fund side ticketing pricing database after logging in the fund side and opening corresponding functional rights, such as fund enterprise qualification, market credit, performance capability and the like.

In an exemplary embodiment, the ticket image identification module is configured to identify a ticket image uploaded to the platform system by a ticket holder. In an exemplary embodiment, the uploaded ticket image may be identified by image recognition technology provided by a third party vendor. In some embodiments, document image recognition may include information recognition of the front and back of a document. In some embodiments, the ticket image identification may also include a ticket holder manual verification validation module. After the bill information is identified by the bill image identification module, the correctness of the identified bill information is checked by a bill holder manual checking and confirming module, and the bill information input into the system is ensured to be accurate. The ticket holder performs manual checking and confirmation, which is beneficial to reducing the complexity of customers, thereby improving the usability of products.

In an exemplary embodiment, the sponsor ticketing pricing routing rule module is configured to present to the ticketed carriers a qualifying quote based on predetermined rules. In some embodiments, the predetermined rule may be: the platform system may select one or more optimal offers among the queried offers that meet all requirements and present them to the ticket holder. The selection of the optimal offer may be based on a composite score for multiple dimensions. In some embodiments, the platform system may comprehensively score offers based on one or more dimensions, including but not limited to: the number of transactions of the sponsor, the number of counterparties, the transaction processing time, the number of defaults, whether invoicing is supported, whether automatic transaction processing (consignment system signing and payment) is supported, and the like. In some embodiments, the corresponding weight may be obtained based on the above-mentioned dimensions, and a score may be derived according to the weight; the offer with the highest composite score may be selected as the best offer and presented to the ticket holder.

In an exemplary embodiment, the ticketholder may send a query quote request to the platform system. In some embodiments, the query bid request may include such key parameters as the following ticket information: bill amount, recipient, due date, flaw condition, etc. Upon receiving a query quote request, the platform system may automatically look up in the quote repository quotes that fully meet all requirements in the sponsor quote. After the quotation meeting all the requirements is inquired, the platform system can display the inquired quotation and the fund party associated with the quotation to the ticket holder according to the fund party ticket collecting pricing routing rule.

In an exemplary embodiment, the order validity determination module is configured to query the ticket endorsement status and the order information matching status within a specified time. In some embodiments, after the ticket holder submits the order, it will wait for the transaction ticket to be underwritten through the internet banking endorsement. In the appointed time, the order validity judging module inquires whether the bill to be traded is endorsed and whether the bill information is matched with the order information. In some embodiments, if the order validity determination module determines that the ticket to be traded has not been endorsed or the ticket information does not match the order ticket within a specified time, the platform system will prompt the transaction to fail. If the order legality judging module determines that the bill to be traded is endorsed and the bill information is matched with the order bill within the specified time, the platform system waits for the fund party to carry out transaction verification.

In some embodiments, determining whether the ticket information matches the order ticket may include determining one or more of: i) billing information for the order (such as what the bearer states is not validated); ii) ticket uniqueness (ticket number, ticket amount, acceptor, due date); and iii) defective condition of the document.

In some embodiments, in determining whether a ticket to be traded is endorsed, the platform system may be connected to the central bank ECDS system via a financial institution at the appointed time so as to automatically verify whether the funds account has received the corresponding ticket endorsement, as well as details of the endorsed ticket (actual ticket status).

In some embodiments, the platform system may automatically compare whether the above-described key parameters of the order and the actual ticket are completely consistent. If so, the platform system transfers the order to the funder. If not, the transaction fails, and the platform system informs the ticket holder to withdraw the ticket.

A ticket holding end:

in an exemplary embodiment, a ticketing party ("bearer") may log into a ticketing authority. In some embodiments, if the ticket holder has not created a personal account, the ticket holder will prompt the ticket holder to register. If the ticket holder has registered an account on the ticket holder, the ticket holder can directly log in the ticket holder through a personal account. In some embodiments, after logging into the personal account, the ticketing authority may view one or more tabs on a "My orders" page, such as: "to endorse", "to retrieve (in trade)", and "to retrieve today", etc. In some embodiments, the "My orders" page may also include a "bank account management" tab by which the ticketing holder may manage personal and enterprise bank account information. In some embodiments, the My orders page may also include a "set" tab. If the "settings" tab is selected, the ticketing authority can make various settings.

Additionally, in some embodiments, the ticketing party may make a first account registration. The first account number is universal in first bills, first transaction and other products. In some embodiments, upon registering the first account number, the ticketing authority may be prompted to enter: the mobile phone number, the short message verification code, the 6-bit invitation code and the like. In some embodiments, the system may require that a "6-digit invite code" must be provided when registering the head account, otherwise registration is not possible.

Once the first account is registered, the ticket holder may log in to the first account by entering the cell phone number and login password. In some embodiments, the ticket holder may log in to the head account by selecting other login methods. For example, in some embodiments, the ticketing party may choose to log in using a third party such as WeChat. In some embodiments, when a ticketing party logs in through a third party, the ticketing party may be required to bind the cell phone.

In some implementations, the ticketing authority may be required to enter information such as a cell phone number, name, identification number, etc. when registering the first account number. Additionally, in some embodiments, the ticketing party may also be required to upload a picture as an avatar when registering the account number of the head. Once the head account number is registered, the ticket holder can perform bank account management. In some embodiments, bank account management includes personal account management and enterprise account management.

In an exemplary embodiment, the ticketing party can upload the ticket image to the platform system through the ticketing bureau. The bill image recognition module of the platform system can recognize the uploaded bill images. In some embodiments, the ticket holder may select a "take picture" option to activate a camera function to take a picture of the ticket for uploading to the platform system. Additionally, in some embodiments, the ticketing authority may also select an "album" option to upload to the platform system from selecting an existing ticket image. In some embodiments, validating the recognition result comprises validating: whether the frame is missing; whether the image is blurred; and whether the flash is intense, etc. And if the platform system fails to identify, presenting an identification failure prompt to the ticket holder. And if the platform system is successfully identified, presenting the identified bill information to the ticket holder for the ticket holder to confirm.

Once the bill information is confirmed to be correct, the ticket holder can immediately inquire the related quote. In an exemplary embodiment, upon receiving a query quote request from a ticketing party, the platform system may automatically look up in a quote repository a price that fully meets all requirements in the sponsor quote. Once the price meeting all the requirements is queried, the platform system presents the queried quote and the funder associated therewith to the ticket holder. In some embodiments, the queried offer may be a real-time offer.

In some embodiments, if the identified ticket information is correct, the ticket holder can click the 'confirm ticket information inquiry offer' button to make an inquiry, and the system will automatically compare the identified information with the 'sponsor ticket pricing database' information to automatically obtain the offer of the ticket without manually inputting the information.

In some embodiments, the platform system may present a real-time quote page. The real-time offer page may include, but is not limited to, one or more of the following information: the transferee, the amount of cash accrued today, the number of days spent, every hundred thousand deductions (yuan), the total deductions, the flaws accepted by the transferee, the special requirements of the transferee, the credit data of the transferee (cumulative transaction number (pen), cumulative opponent number (home), average payment time, etc.), etc.

After presenting the real-time quote, the ticketing party may not approve the quote. If the ticketed party does not approve the quote, the platform system may prompt termination of the transaction. If the ticketed-holder approves the quote, the platform system may present an order edit page to the ticketed-holder. In some embodiments, the order editing page may be a "confirm trades" page. In some embodiments, the "confirm transaction" page may include, but is not limited to, one or more of the following items of information: transaction ticket number, ticket amount, acceptor, due date, enterprise collection account, other accounts payable, today cash-in amount, etc. In some embodiments, the present cash out amount information includes, but is not limited to, one or more of: the number of days for rest, every one hundred thousand deductions, every one hundred thousand self-defined, the total deduction amount, the amount of the public payment and the amount due of other money.

In some embodiments, other due settings may also be made upon confirmation of the transaction. In some embodiments, other due settings may include settings for one or more of: every hundred thousand deductions (price quoted by the sponsor), every hundred thousand self-definition (the point of drawing a bill), other total amount due, and the like. In some embodiments, other due settings may also include settings for one or more of: other accounts payable, total amount payable, etc. In some embodiments, the number of other accounts payable may be one or more.

If a transaction is selected, the ticketed-holder may submit an order. After the ticketing authority submits the order, the platform system may prompt "order creation is successful, waiting for endorsement". In some embodiments, the endorsement may be a silver endorsement. In some embodiments, the system platform will prompt "please complete endorsement within 30 minutes of notifying the ticketing enterprise".

Additionally, in some embodiments, after the ticketing party submits the order, the platform system may present one or more of the following information to the ticketing party: a sponsor ticket collector, a to-be-endorsed ticket, and the like. In some embodiments, the sponsor ticketed subscriber may include, for example, one or more of the following information: bank account number, bank number, etc. In some embodiments, the endorsement ticket may include, for example, one or more of the following information: transaction ticket number, ticket amount, acceptor, due date, etc.

In some embodiments, the ticketholder may view the submitted orders on a "My orders" page. In some embodiments, the My orders page may include tags such as "all", "pending endorsements", "in transaction processing", "transaction success", "transaction failure", and the like. Selecting the "all" tab will display all orders. And selecting the label of 'waiting to endorse', and displaying the bill to endorse. Selecting the label of 'transaction processing' will display the bill with endorsement completed. Selecting the "trade successful" tab will display all orders that were traded successfully. Selecting the "trade failed" tab will display all orders that failed the trade.

And (4) capital end:

in some embodiments, the platform system may grant the corresponding rights to the funding party after making a contract with the funding party online based on funding party enterprise qualifications, market credit, fulfillment capabilities, and the like.

In some embodiments, a funding party ("consumer") may turn on the traffic control functions after logging on to the funding end. In some embodiments, the funder may set the ticket collector, select order processing rules, and select service status by modifying the business control functions. For example, through the service control function, the fund party can set ticket collecting conditions, such as no ticket collecting, which account is used for collecting the ticket, the amount of the ticket collecting, the ticket collecting conditions, whether the ticket is automatically collected or not, and the like.

In some embodiments, the order processing rules include human intervention, system automation (automated sign-in or automated withdrawal), and the like. The manual intervention options include ticket collection and check, ticket drawing and check and the like. System automation options include automatic sign-in, automatic withdrawal, etc.

After the service control function is activated, the funder may release ticketing pricing. The pricing for issuing the receipt can be achieved through a price setting function. In some embodiments, the funder may enter offers by selecting the "offer today" tab to make price settings. In addition, the funder may also make new offers by selecting the "new offers" column.

In some embodiments, when making a new offer, the funder may set one or more items in the "new offer" page, including but not limited to: quote title, ticket type, acceptance line (acceptance line selected by classification or imported), denomination amount, due date range, acceptable flaws, special requirements, set price (set by interest rate or set by a snap fee), whether billing is supported, service status (enabled or disabled), etc.

In some embodiments, the funder also looks at yesterday label by selecting yesterday' label. In some embodiments, the funder may switch between the "today's quote" label or the "yesterday's quote" label by selecting the two. For example, if the "today's quote" tab is selected, the new quote edit page is entered, and if the "yesterday's quote" tab is selected, the yesterday's quote page is entered for the funder to view the information.

After the price setting, the fund side issues the invoice pricing to the fund side invoice pricing base. Once the collection pricing is published into the sponsor collection pricing database, the ticket holder initiates a transaction in a subsequent flow.

In an exemplary embodiment, the ticket holder submits an order, and the order validity judging module of the platform system judges the validity of the order. If the order legality judging module inquires that the bill to be traded is endorsed by the online bank within the specified time and the information of the bill to be traded is matched with the order bill, the order is submitted to the fund side for the fund side to check the receipt.

In some embodiments, the platform system may provide a ticketing review page to the funder. The ticket collection auditing page can comprise a list to be audited. In some embodiments, the ticketing to-be-audited list may include, but is not limited to, one or more of the following items of information: order number, number of bills, billing member, billing submission time, payment (yuan) for public, payment (yuan) for other, billing source, time of failure, operation, etc.

In some embodiments, when the receipt is checked, the funder may check the receipt making details, the receipt making information, the ticket information, the my household information, the household information of the funder, and the like. The ordering details may include one or more of the following items of information: order number, order maker, phone number of order maker, order submission time, order application remark and the like. The billing information may include one or more of the following items of information: number of tickets, total amount of cash-out, request for payment (e.g., full payment), full payment due, total amount for a payout, other payable, other total amounts payable. The ticket information may include one or more of the following items of information: the method comprises the following steps of ticket number, order maker, ticket amount, acceptor, number of endorsers, last endorsement company, posting date, due date, adjustment days, interest counting days, annual interest rate, handling charge, defect condition, posting amount, every hundred thousand of postings, public payment, every hundred thousand of self-definition, other payable, receipt state, receipt time, business classification and the like. My user information may include one or more of the following: the name of the collector, the bank account, the bank opening bank, the bank affiliate number, etc. His user information may include one or more of the following: for public account name, bank account, bank opening line, bank number, other payable payee name, bank card number, bank opening line, payment amount (Yuan), etc. In some embodiments, when the ticket collection audit is completed, audit comments may be provided.

Additionally, in some embodiments, the funder may conduct offline payment operations and may view the payment records through the funding side. In some embodiments, the funding end may present a withdrawal record page to the funding party. The withdrawal record page may include one or more of the following items of information: order number, payee, type (public or private), mode (systematic or manual), amount (dollar) of the withdrawal, time of the withdrawal, operation, etc.

Fig. 2 shows a flow chart of the intelligent matching method for the internet-based bill transaction of the application. The intelligent matching method for bill transaction comprises the steps of issuing bill collecting pricing, uploading bill images, identifying the bill images, inquiring quotation, confirming transaction, submitting orders, judging the legality of the orders, processing payment and the like. The method and the system utilize the Internet technology to change a transaction mode from a traditional mode that a ticket holder releases commodities and a fund party selects the commodities to initiate transactions into a novel mode that the fund party releases demands and the ticket holder initiates transactions, so that the transaction efficiency and the success rate are improved.

As shown in fig. 2, the intelligent matching method for bill transaction of the present application includes the following steps:

s1: issuing a ticket collection pricing by a fund party;

s2: uploading the bill image to the platform system by the bill holder;

s3: identifying, by the platform system, the ticket image;

s4: querying, by the ticketing holder, the quote for the identified ticket;

s5, displaying the fund party matched with the inquired bill and the related transaction price to the bill holder by the platform system;

s6: selecting an appropriate transaction by the ticket holder;

s7: editing and submitting an order by a ticket holder;

s8: judging the order validity by the platform system;

s9: if the online banking endorsements are matched, the fund side approves and verifies the online banking endorsements; if not, the transaction fails;

s10: for the endorsed bill, if the fund party passes the verification, the payment processing is carried out; if the audit fails, the transaction is denied, whereby the transaction fails;

specifically, in an exemplary embodiment, a funding party may log on to a funding end and provision a service control function. Once the service control function is enabled, the funder may issue a ticketing pricing to the funder ticketing pricing repository at step S1. In some embodiments, the sponsor ticketing pricing library is included in the platform system. In an exemplary embodiment, the sponsor ticketing pricing library is included in the platform system. In an exemplary embodiment, the ticketing party may log into the ticketing bureau. After logging in to the ticket holder, the ticket holder may upload the held ticket image to the platform system at step S2.

After the ticket image is uploaded to the platform system, at step S3, it is recognized by the ticket image recognition module in the platform system. And if the platform system successfully identifies the uploaded bill image, presenting an identification result to the bill holder. The ticket holder can confirm the presented recognition result. In some embodiments, validating the recognition result comprises validating: whether the frame is missing; whether the image is blurred; and whether the flash is intense, etc. And if the platform system fails to identify, presenting an identification failure prompt to the ticket holder.

After confirming that the ticket information in the recognition result is correct, the ticket holder may transmit a query quotation request to the platform system in step S4.

After receiving a request for a query quote from a ticketing party, the platform system can automatically search a quote library for a price matching the requirements in the quote of the sponsor. In some embodiments, matching may be based on one or more of the following key parameters of the ticket information, such as: bill amount, acceptor, due date and flaw

Upon querying the fully requested price, the platform system presents the queried quote and the funding party associated therewith to the ticket holder at step S5.

For the presented queried offer, the ticketing party may decide whether to approve the offer at step S6. If approved, the platform system may present the order editing page to the ticketing holder for order editing. If not, the transaction may be prompted to end.

After entering the order editing page, the ticketing holder may fill out the order and submit the order at step S7. Once the order is submitted, the online banking endorsement of the bill to be traded is waited for. At step S8, an order validity determination may be made by the platform system. In some embodiments, the order validity determination may be performed by an order validity determination module in the platform system.

The legality judgment comprises inquiring whether the bill to be traded is endorsed and whether order information is matched within a specified time. If the bill to be traded is not endorsed within a specified time, or the bill information does not match the order bill, the transaction fails.

If the ticket to be traded has been endorsed and matches the order information, the funding party may review the order at step S9. If the audit is passed, the funding party may pay for the process, thereby completing the transaction and updating the order status. If the audit fails, the funder may decline payment and the transaction fails.

While the preferred embodiments of the present invention have been described in detail above, it should be understood that aspects of the embodiments can be modified, if necessary, to employ aspects, features and concepts of the various patents, applications and publications to provide yet further embodiments.

These and other changes can be made to the embodiments in light of the above detailed description. In general, in the claims, the terms used should not be construed to be limited to the specific embodiments disclosed in the specification and the claims, but should be construed to include all possible embodiments along with the full scope of equivalents to which such claims are entitled.

Claims

1. A system for matching of bill transactions, comprising a service platform, characterized in that the service platform comprises:

2. The system of claim 1, wherein the service platform is further configured to: after the image recognition module recognizes the bill to be traded, the information of the recognized bill to be traded is presented to the second user, so that the second user can confirm whether the recognized bill to be traded is correct or not.

3. The system of claim 1, wherein the legitimacy determination module is configured to determine the legitimacy of the trade order and includes determining whether a ticket to be traded is endorsed and whether information of the ticket to be traded matches an order ticket within a specified time.

4. The system of claim 3, wherein the service platform is further configured to: if the legality judging module determines that the bill to be traded is not endorsed or the information of the bill to be traded is not matched with the order bill, the second user is prompted that the trading fails; and if the legality judging module determines that the bill to be traded is endorsed and the information of the bill to be traded is matched with the order bill, the trading order is provided for the first user for auditing.

5. The system of claim 4, wherein the service platform is further configured to: prompting the transaction to complete and updating the order status if the transaction order is approved and payment processing is performed by the first user; and the service platform is further configured to: and if the trade order is not approved, prompting that the trade fails.

6. The system of claim 1, wherein the system further comprises a first terminal and a second terminal, wherein the first terminal is configured for a first user to log into the system; the second terminal is configured for the second user to log into the system and configured for the second user to upload an image of a ticket to be traded to the system and to obtain a sponsor and associated sponsor price matching the uploaded image of the ticket to be traded and for the second user to confirm the trade and submit a trade order.

7. The system of claim 6, wherein the first terminal is a ticketing end; and the second terminal is a funding side.

8. The system of claim 1, wherein the first user is a ticketing party and the second user is a funding party.

9. A method for ticketing trade matching, the method comprising:

issuing a ticket collection pricing by the first user;

uploading, by the second user, an image of the ticket to be traded;

the validity of the trade order is judged.

10. The method of claim 9, wherein the method is performed by a system comprising a service platform having a collection pricing store, an image recognition module, a collection pricing routing rule module, and a validity determination module, wherein

11. The method of claim 10, wherein determining the legitimacy of the trade order comprises determining whether a ticket to be traded is endorsed and whether information of the ticket to be traded matches an order ticket within a specified time.

12. The method of claim 11, wherein the method further comprises: if the legality judging module determines that the bill to be traded is not endorsed or the information of the bill to be traded is not matched with the order bill, the second user is prompted that the trading fails; and if the legality judging module determines that the bill to be traded is endorsed and the information of the bill to be traded is matched with the order bill, the trading order is provided for the first user for auditing.

13. The method of claim 12, wherein the method further comprises: prompting the transaction to complete and updating the order status if the transaction order is approved and payment processing is performed by the first user; and

and if the trade order is not approved, prompting that the trade fails.

14. The method of claim 9, wherein the first user is a ticketing party; and the second user is a funding party.