CN117787961B - Payment ticket business integrated management method and system - Google Patents

Abstract

The embodiment of the present application provides a payment ticket integrated management method and system, the method comprising: a mobile device collects information of a first payment ticket selected by a target object, the information of the first payment ticket comprising: a ticket ID, a ticket merchant ID and a payment amount; the mobile device performs identity recognition on the target object to determine the first identity of the target object, extracts all unfinished payment tickets under the first identity from historical payment ticket data, and queries from all unfinished payment tickets whether there is a second payment ticket with the same ticket ID and ticket merchant ID; when the mobile device determines that there is a second payment ticket, extracts a bound account number of the second payment ticket, displays the bound account number and the second payment ticket and issues a prompt message, the prompt message being used to prompt the target object whether to continue to pay the first payment ticket.

Description

A payment ticket integrated management method and system

Technical Field

The present application belongs to the field of e-commerce and data technology, and specifically relates to a payment and ticketing integrated management method and system.

Background technique

Payment ticket information refers to payment ticket information related to various performances, competitions, activities, etc. It includes ticket price information, performance time, venue information, ticket purchase methods, etc. With the expansion of ticket information and the development of the Internet, some VIPs with service attributes are also planned as payment ticket categories, such as VIPs of video websites, VIP services of certain software, etc.

As the number of payment tickets increases, and payment tickets have multiple platforms, users may also have multiple accounts. Therefore, multiple platforms cannot achieve cross-platform and multi-account payment ticket management, which may result in users making duplicate payments for the same payment ticket.

Summary of the invention

The present application provides a payment ticket integrated management method and system, which can avoid the problem of users making repeated payments for the same payment ticket and improve the user experience.

In a first aspect, the present application provides a payment ticketing integrated management method, the method comprising the following steps:

The mobile device collects information of a first payment ticket selected by the target object, wherein the information of the first payment ticket includes: a ticket ID, a ticketing merchant ID, and a payment amount;

The mobile device performs identity recognition on the target object to determine the first identity of the target object, extracts all unfinished payment tickets under the first identity from the historical payment ticket data, and queries whether there is a second payment ticket with the same ticket ID and ticketing business ID from all the unfinished payment tickets;

When the mobile device determines that it has the second payment ticket, it extracts the bound account of the second payment ticket, displays the bound account and the second payment ticket, and issues a prompt message, which is used to prompt the target object whether to continue to pay the first payment ticket.

In a second aspect, a payment and ticketing integrated management system is provided, the system comprising:

A collection unit, configured to collect information of a first payment ticket selected by a target object, wherein the information of the first payment ticket includes: a ticket ID, a ticketing merchant ID, and a payment amount;

An identification unit, configured to perform identity identification on a target object to determine a first identity of the target object;

The processing unit is used to extract all unfinished payment tickets under the first identity from the historical payment ticket data, and query whether there is a second payment ticket with the same ticket ID and ticket merchant ID from all the unfinished payment tickets; when it is determined that there is a second payment ticket, extract the binding account of the second payment ticket, display the binding account and the second payment ticket, and issue a prompt information, where the prompt information is used to prompt the target object whether to continue to pay the first payment ticket.

In a third aspect, the present application provides a computer storage medium storing a computer program for electronic data exchange, wherein the computer program enables a computer to execute part or all of the steps described in the first aspect of the present application.

The embodiments of the present application have the following beneficial effects:

The technical solution provided by the present application is that the mobile device collects the information of the first payment ticket selected by the target object, and the information of the first payment ticket includes: ticket ID, ticket merchant ID and payment amount; the mobile device performs identity recognition on the target object to determine the first identity of the target object, extracts all the unfinished payment tickets under the first identity from the historical payment ticket data, and queries from all the unfinished payment tickets whether there is a second payment ticket with the same ticket ID and ticket merchant ID; when the mobile device determines that there is a second payment ticket, it extracts the binding account of the second payment ticket, displays the binding account and the second payment ticket and sends a prompt message, which is used to prompt the target object whether to continue to pay the first payment ticket. This technical solution can determine whether there is a second payment ticket that is the same as the first payment ticket by querying the information of the first payment ticket when selecting the first payment ticket. On the premise of determining that there is a second payment ticket, the target object can select and determine whether to pay the first payment ticket by sending a prompt message, so that the target object can perform the determination of the payment ticket and avoid repeated payment of the same payment ticket.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

FIG1 is a schematic diagram of a system architecture of a ticketing center provided in an embodiment of the present application;

FIG2 is a flow chart of a payment and ticketing integrated management method provided in an embodiment of the present application;

FIG3 is a schematic diagram of the structure of an integrated payment and ticketing management system provided in an embodiment of the present application.

Detailed ways

In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

The terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, systems, products or devices.

Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

The following introduces the architecture of the ticketing center system involved in the embodiment of the present application.

The present application also provides a ticketing center 10 and a mobile device 20. As shown in FIG1 , the ticketing center 10 is connected to the mobile device 20 via a wireless network. The mobile device includes at least one processor 11 and a memory 12, and may also include a communications interface 14, a display screen 16, and a bus 13. Among them, the processor 11, the memory 12, the display screen 16, and the communication interface 14 can communicate with each other through the bus 13. The communication interface 14 can transmit information, and the communication interface 14 can have a wireless communication function, and the wireless communication function can be a short-range wireless communication or a long-range communication function (such as LTE or NR mode). The processor 11 can call the logic instructions in the memory 12 to execute or support the method in the embodiment of the present application. The mobile device 20 may also include: a microphone, etc.

In addition, the logic instructions in the above-mentioned memory 12 can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product.

The memory 12, as a computer-readable storage medium, can be configured to store software programs, computer executable programs, such as program instructions or modules corresponding to the method in the embodiment of the present disclosure. The processor 11 executes functional applications and data processing by running the software programs, instructions or modules stored in the memory 12, that is, implementing or supporting the method in the embodiment of the present application.

The above-mentioned ticketing center 10 can be multiple ticketing center devices. Of course, in an optional application scenario, the above-mentioned ticketing center 10 can be a ticketing center cluster, and the above-mentioned ticketing center cluster can be a distributed ticketing center or a cloud ticketing center, etc. This application does not limit the connection relationship or functional division between ticketing centers.

The following describes the main technical application scenarios of the embodiments of this application:

There are many existing platforms for ticket payment, such as travel platforms for air tickets and tickets, shopping platforms for restaurant tickets, video platforms for film and television membership payment platforms, etc. Moreover, a natural person may have multiple accounts. For a travel platform, he may use account A, for a shopping platform he may use account B, and for a video platform he may use account C. The data of multiple platforms are not interoperable, which may result in duplicate payments for a natural person if multiple platforms sell the same product.

Let's take a video platform as an example. For example, the video platform has a customized membership service, such as short video editing VIP membership. For natural person A, he used account A to purchase the above-mentioned short video editing VIP membership on the video platform. However, one month later, when natural person A logged into the shopping platform, the shopping platform recommended the short video editing VIP membership. At this time, natural person A logged in to account B of the shopping platform. Since it is the same content, natural person A is very likely to purchase the short video editing VIP membership again for the same reason. At this time, the recorded account B has the short video editing VIP membership, and account A also has the short video editing VIP membership. Since account A and account B belong to the same natural person, for the same natural person, he paid two fees for the same service "short video editing VIP membership", and natural person A may not know it in the end. Therefore, this type of payment ticketing needs to be managed in an integrated manner, so as to facilitate the effective management of users' payment ticketing and avoid the problem of multiple payments by the same natural person for the same payment ticket.

VIP (very important person) is generally an important person or an important figure. Later, it develops into a member, member service, etc., a title with special status or specific services.

The specific methods are introduced in detail below.

Please refer to Figure 2. The present application also provides a payment ticketing integrated management method. Figure 2 is a flow chart of a payment ticketing integrated management method provided by the present application. The above method is executed. Specifically, the method shown in Figure 2 can be performed by the ticketing center and the mobile device in cooperation. The above method is shown in Figure 2 and includes the following steps:

Step S201: The mobile device collects information of a first payment ticket selected by a target object, wherein the information of the first payment ticket includes: a ticket ID, a ticketing business ID, and a payment amount;

The above-mentioned paid ticketing services include, but are not limited to: VIP services of video websites, VIP services of application software, air tickets, performance tickets, train tickets, entrance tickets, etc. This application does not limit the specific form of paid ticketing services, as long as the above-mentioned paid ticketing services are services that require payment of a certain amount of money.

Step S202: The mobile device performs identity recognition on the target object to determine the first identity of the target object, extracts all unfinished payment tickets under the first identity from the historical payment ticket data, and checks whether there is a second payment ticket with the same ticket ID and ticketing business ID from all the unfinished payment tickets;

For example, the mobile phone device may perform identity recognition on the target object in a variety of ways, such as face recognition, fingerprint recognition, vein recognition, etc. This application does not limit the above-mentioned identity recognition methods.

Specifically, if the mobile device performs identity recognition on the target object through vein recognition, it may specifically include:

The mobile device obtains a first vein image of the target object (the above-mentioned first vein image can be a vein image of a specific part of the target object, such as a palm, an index finger, etc.), extracts vein points from the first vein image to obtain a vein feature image, connects continuous vein points in the vein feature image to obtain a line segment image, collects angle values between intersecting line segments in the line segment image to obtain x angle values, obtains x intersection points corresponding to the x angle values and x pixel positions corresponding to the x intersection points from the line segment image, constructs a one-to-one mapping relationship between the x angle values and the x pixel positions of the intersecting line segments to obtain a first mapping, extracts multiple template mappings with x angle values from a preset template mapping, obtains multiple mapping relationships among the multiple template mappings, compares the multiple mapping relationships with the first mapping respectively to determine a first template mapping that is the same as the first mapping, and determines that a first identity corresponding to the first template mapping is the identity of the above-mentioned target object.

For example, the above x is an integer greater than or equal to 20.

The above identity recognition can ignore the influence of the acquisition angle, because the above x angle values are the angles between fine veins, and the positional relationship between fine veins is determined by the identity, which is also the basis for identifying the user's identity through veins. Based on this principle, after constructing the above first mapping, the identity can be recognized by comparing the mappings. The calculation method of the above angle value can adopt the existing image angle recognition method, which will not be repeated here.

Step S203: When the mobile device determines that it has the second payment ticket, it extracts the bound account of the second payment ticket, displays the bound account and the second payment ticket, and issues a prompt message, which is used to prompt the target object whether to continue to pay the first payment ticket.

The technical solution provided by the present application is that the mobile device collects the information of the first payment ticket selected by the target object, and the information of the first payment ticket includes: ticket ID, ticket merchant ID and payment amount; the mobile device performs identity recognition on the target object to determine the first identity of the target object, extracts all the unfinished payment tickets under the first identity from the historical payment ticket data, and queries from all the unfinished payment tickets whether there is a second payment ticket with the same ticket ID and ticket merchant ID; when the mobile device determines that there is a second payment ticket, it extracts the binding account of the second payment ticket, displays the binding account and the second payment ticket and sends a prompt message, which is used to prompt the target object whether to continue to pay the first payment ticket. This technical solution can determine whether there is a second payment ticket that is the same as the first payment ticket by querying the information of the first payment ticket when selecting the first payment ticket. On the premise of determining that there is a second payment ticket, the target object can select and determine whether to pay the first payment ticket by sending a prompt message, so that the target object can perform the determination of the payment ticket and avoid repeated payment of the same payment ticket.

For example, the above method may further include, before step S201:

Mobile devices build historical payment ticket data, including:

The mobile phone device monitors the payment information of the mobile phone. When it has the first payment information, it obtains the payment information and product information of the first payment information. The above payment information includes but is not limited to: the full name of the merchant and the acquiring institution. When the above product information is identified and determined to belong to the payment ticket, the full name of the merchant, the acquiring institution and the product information are determined as a payment ticket information, and the payment ticket information is added to the historical payment ticket data.

For example, the above method may further include:

The mobile device periodically extracts the effective time of all unfinished payment tickets from the historical payment ticket data, extracts at least one payment ticket whose effective time has a difference with the current time less than a time limit threshold, and generates reminder information of the at least one payment ticket.

The above method avoids the problem that the payment ticket data cannot be used after it expires by periodically counting the expiration date of the historical payment ticket data.

For example, the above method may further include:

When the mobile phone device determines that it does not have the second payment ticket, the mobile phone device classifies and identifies the product information provided by all the unfinished payment tickets to determine the corresponding multiple categories, classifies and identifies the product information of the first payment ticket to determine the first category, and queries a first quantity of payment tickets of the same category as the first category from the multiple categories. If the first quantity is greater than the quantity threshold, a prompt message is sent to the target object, and the above prompt message includes: the first category and the first quantity.

This technical solution is mainly to prevent the target object from subscribing too many payment tickets of a single category. Taking video VIP as an example, if the first identity has subscribed to VIP of platform A, VIP of platform B, VIP of platform C, and VIP of platform D, then if he wants to subscribe to VIP of platform E, he needs to remind the target object that he has already subscribed to VIP of so many video platforms, and remind him that there may be duplicate consumption, etc.

The above classification and recognition method can be implemented using existing classifiers, such as support vector machines, neural network models, etc.

At present, the proportion of complaints about tourism is relatively high, mainly because the service items of tourism payment ticketing are inconsistent with the actual items. For example, there are 10 service items in tourism payment ticketing, but only 8 items are actually provided. Another example is that there are 10 service items in tourism payment ticketing, and all 10 items are VIP charges, but the number of VIP items actually provided is 4. Especially for such VIP items, users may not be able to perceive the service. Let's take a practical example to illustrate. Taking the amusement park project as an example, there are 10 VIP items for the amusement park project in the payment ticketing, but after the user orders the payment ticketing, only 6 VIP items may be provided, and the remaining items are ordinary items. Therefore, the ticketing center needs to verify such invisible items and clean up the payment ticketing market.

For example, the above method may further include:

If the payment ticket is a travel payment ticket, the ticket center extracts the first payment ticket link of the travel payment ticket, identifies the first payment ticket link to determine multiple services corresponding to the first payment ticket link, generates a template vector of the first payment ticket link based on the multiple services, extracts all user IDs (such as ID numbers) that purchase the first payment ticket link, randomly selects n user IDs from all user IDs, obtains the actual service of each user ID among the n user IDs, generates a feature vector for each user ID based on the actual service to obtain n feature vectors corresponding to the n user IDs, calculates the difference between the template vector and the n feature vectors respectively to obtain n difference vectors, and calculates the sum of all element values of the n difference vectors to obtain a sum. If the sum is greater than a first threshold, it is determined that the payment ticket link service is abnormal, and enters a subsequent review process (such as manual verification or a more stringent verification process). If the sum is less than the first threshold, it is determined that the payment ticket link service is normal.

For example, the template vector for generating the first payment ticket link according to the multiple services may specifically include:

Extract all project services x of the first payment ticket link provider, generate an initial template vector, the initial template vector has x element values, and the initial values of the x element values are 0, match multiple services with the x service items, and modify the initial values of multiple element values corresponding to the multiple items matching the x service items to 1 to obtain a modified vector, which is the template vector.

Let's take a practical example to illustrate. Assuming that the first payment ticket link provider is an amusement park, the amusement park provides 10 service items, and the 10 service items are pass items, but all 10 items have VIP services (such as priority queuing or queuing-free), then the initial template vector can be specifically: 00000 00000; assuming that the multiple services are VIP services for 5 items, which are 1, 3, 4, 7, and 9 respectively, then the element values corresponding to 1, 3, 4, 7, and 9 of the initial template vector are modified to 1, and the others remain unchanged to determine the template vector of the first payment ticket link, which can be specifically: 10110 01010. Similarly, the above feature vector can also be generated in the above manner, except that multiple items are replaced with actual items corresponding to the user ID. For example, the actual items provided by user 1 are only 7 and 9 VIP, then the feature vector of user 1 can be: 0000 01010, and the calculated difference vector can be: 10110 00000.

In this way, it is possible to quantify the number of unserved projects. If many users are unable to actually complete the corresponding projects, it means that the link of the project provider is abnormal.

Referring to FIG. 3 , FIG. 3 provides a payment and ticketing integrated management system, the system comprising:

The collecting unit 301 is used to collect the information of the first payment ticket selected by the target object, wherein the information of the first payment ticket includes: ticket ID, ticket merchant ID and payment amount;

An identification unit 302 is used to perform identity identification on a target object to determine a first identity of the target object;

The processing unit 303 is used to extract all unfinished payment tickets under the first identity from the historical payment ticket data, and query whether there is a second payment ticket with the same ticket ID and ticket merchant ID from all the unfinished payment tickets; when it is determined that there is a second payment ticket, extract the binding account of the second payment ticket, display the binding account and the second payment ticket, and issue a prompt information, where the prompt information is used to prompt the target object whether to continue to pay the first payment ticket.

For example,

The processing unit 303 is also used to construct historical payment ticket data, specifically including:

Monitor the payment information of the mobile phone, and when the first payment information is available, obtain the payment information and product information of the first payment information, wherein the payment information includes but is not limited to: the full name of the merchant and the acquiring institution, and when the product information is identified and determined to belong to a payment ticket, the full name of the merchant, the acquiring institution and the product information are determined as one payment ticket information, and the one payment ticket information is added to the historical payment ticket data.

For example, the system further comprises:

The expiration monitoring unit 304 is used to periodically extract the validity time of all unexpired payment tickets in the historical payment ticket data, extract at least one payment ticket whose difference between the validity time and the current time is less than the expiration threshold, and generate reminder information of the at least one payment ticket.

For example,

The processing unit 303 is also used to determine that when there is no second payment ticket, the mobile device classifies and identifies the product information provided by all the unfinished payment tickets to determine the corresponding multiple categories, classifies and identifies the product information of the first payment ticket to determine the first category, and queries a first quantity of payment tickets of the same category as the first category from multiple categories. If the first quantity is greater than the quantity threshold, a prompt message is sent to the target object, and the above prompt message includes: the first category and the first quantity.

For example,

The identification unit 302 is specifically used to obtain a first vein image of the target object (the above-mentioned first vein image can be a vein image of a specific part of the target object, such as a palm, an index finger, etc.), extract vein points from the first vein image to obtain a vein feature image, connect continuous vein points in the vein feature image to obtain a line segment image, collect angle values between intersecting line segments in the line segment image to obtain x angle values, obtain x intersection points corresponding to the x angle values and x pixel positions corresponding to the x intersection points from the line segment image, construct a one-to-one mapping relationship between the x angle values and the x pixel positions of the intersecting line segments to obtain a first mapping, extract multiple template mappings with x angle values from a preset template mapping, obtain multiple mapping relationships among the multiple template mappings, respectively compare the multiple mapping relationships with the first mapping to determine a first template mapping that is the same as the first mapping, and determine that a first identity corresponding to the first template mapping is the identity of the above-mentioned target object.

The embodiment of the present application can divide the functional units of the electronic device according to the above method example. For example, each functional unit can be divided according to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units. It should be noted that the division of units in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented by software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website site, computer, ticketing center or data center to another website site, computer, ticketing center or data center by wired or wireless means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a ticketing center or data center that contains one or more available media sets. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state hard disk.

An embodiment of the present application also provides a computer storage medium, wherein the computer storage medium stores a computer program for electronic data exchange, wherein the computer program enables a computer to execute part or all of the steps of any method described in the above method embodiments, and the above computer includes an electronic device.

The present application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute some or all of the steps of any method described in the method embodiment. The computer program product may be a software installation package, and the computer includes an electronic device.

It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

In the several embodiments provided in the present application, it should be understood that the disclosed methods, devices and systems can be implemented in other ways. For example, the device embodiments described above are merely schematic; for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a ticketing center, or a network device, etc.) to perform some steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: a USB flash drive, a mobile hard disk, a magnetic disk, an optical disk, a volatile memory or a non-volatile memory. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM) and direct RAM bus RAM (DR RAM). Various media that can store program code are available.

Although the present invention is disclosed as above, the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions without departing from the spirit and scope of the present invention, and can make various changes and modifications, including the combination of the above-mentioned different functions and implementation steps, including software and hardware implementation methods, all of which are within the scope of protection of the present invention.

Claims (8)

1. An integrated management method for ticket payment, which is characterized by comprising the following steps:

the mobile phone equipment acquires information of a first payment ticket selected by a target object, wherein the information of the first payment ticket comprises the following components: ticket ID, ticket business ID, and payment amount;

The mobile phone equipment performs identity recognition on the target object to determine the first identity of the target object, extracts all the unfinished payment tickets under the first identity from the historical payment ticket data, and inquires whether the second payment ticket which is the same as the ticket ID and the ticket business ID exists in all the unfinished payment tickets;

When the mobile phone equipment determines that the second payment ticket is available, a binding account number of the second payment ticket is extracted, the binding account number and the second payment ticket are displayed, and prompt information is sent out, wherein the prompt information is used for prompting whether the target object continues to pay the first payment ticket;

When the mobile phone equipment determines that the second payment ticket is not available, the mobile phone equipment classifies and identifies all commodity information provided by the payment tickets which are not ended to determine a plurality of corresponding categories, classifies and identifies commodity information of the first payment ticket to determine a first category, inquires first quantity of the payment tickets of the same category as the first category from the plurality of categories, and sends prompt information to a target object if the first quantity is larger than a quantity threshold value, wherein the prompt information comprises: a first category and a first number.

2. The integrated payment ticket management method according to claim 1, further comprising, before the mobile phone device collects the information of the first payment ticket selected by the target object:

The mobile phone device builds historical payment ticket data, and specifically comprises the following steps:

The mobile phone equipment monitors payment information of the mobile phone, and when the mobile phone equipment has the first payment information, acquires the payment information of the first payment information and commodity information, wherein the payment information comprises but is not limited to: and when the commodity information is identified and determined to belong to the payment ticket, the merchant full scale and the commodity information are determined to be one payment ticket information, and the one payment ticket information is added into the historical payment ticket data.

3. The payment ticketing integrated management method according to claim 1, the method further comprising:

And the mobile phone equipment periodically extracts the effective time of all the unfinished payment tickets in the historical payment ticket data, extracts at least one payment ticket with the difference value smaller than the deadline threshold value from the effective time, and generates the reminding information of the at least one payment ticket.

4. The integrated payment ticket management method according to any one of claim 1 to 3,

The payment ticket comprises: VIP of video website, VIP service of application software, air ticket, presentation ticket, train ticket or entrance ticket.

5. A payment ticketing integrated management system, the system comprising:

The collecting unit is used for collecting information of first payment ticketing selected by a target object, wherein the information of the first payment ticketing comprises the following components: ticket ID, ticket business ID, and payment amount;

the identification unit is used for carrying out identification on the target object to determine the first identity of the target object;

The processing unit is used for extracting all the unexpired payment tickets under the first identity from the historical payment ticket data, and inquiring whether the unexpired payment tickets have the second payment ticket which is the same as the ticket ID and the ticket business ID; when the second payment ticket is determined, a binding account number of the second payment ticket is extracted, the binding account number and the second payment ticket are displayed, and prompt information is sent out, wherein the prompt information is used for prompting whether the target object continues to pay the first payment ticket;

The processing unit is further configured to, when it is determined that the second payment ticket does not exist, perform classification recognition on the commodity information provided by all the outstanding payment tickets to determine a plurality of corresponding categories, perform classification recognition on the commodity information of the first payment ticket to determine a first category, query a first number of payment tickets in the same category as the first category from the plurality of categories, and if the first number is greater than a number threshold, send prompt information to a target object, where the prompt information includes: a first category and a first number.

6. The payment ticket integrated management system of claim 5,

The processing unit is further configured to construct historical payment ticket data, and specifically includes:

monitoring payment information of the mobile phone, and when the mobile phone has the first payment information, acquiring the payment information of the first payment information and commodity information, wherein the payment information comprises but is not limited to: and when the commodity information is identified and determined to belong to the payment ticket, the merchant full scale and the commodity information are determined to be one payment ticket information, and the one payment ticket information is added into the historical payment ticket data.

7. The payment ticketing integrated management system of claim 5, the system further comprising:

and the time limit monitoring unit is used for periodically extracting the effective time of all the unexpired payment tickets in the historical payment ticket data, extracting at least one payment ticket with the difference value from the current time in the effective time smaller than the time limit threshold value, and generating the reminding information of the at least one payment ticket.

8. The payment ticket integrated management system according to any one of claims 5 to 7,

The payment ticket comprises: VIP of video website, VIP service of application software, air ticket, presentation ticket, train ticket or entrance ticket.