A ticket generation system, method, apparatus, storage medium and electronic device

Abstract

The embodiment of the specification discloses a kind of bill generation systems, first joint use platform judges whether the payment information corresponding in the bill generation initial request obtained is the historical payment service executed by the first payment service system corresponding to first joint use platform, if not, bill generation initial request is sent to bill service server, by bill service server determine the second payment service system of execution historical payment service, and bill generation initial request is forwarded to the second joint use platform corresponding to second payment service system, by second joint use platform, payment information in bill generation initial request is checked, and after checking, bill generation final request is sent to bill service server, by bill service server, the electronic bill corresponding to historical payment service is generated. Through the above system, merchant only needs to connect one service provider corresponding joint use platform, that is, the electronic bill corresponding to the payment service executed by any payment service system can be issued.

Description

TECHNICAL FIELD

[0001] The present specification relates to the technical field of computer technology, and in particular, to a bill generation system, method, device, storage medium and electronic equipment. BACKGROUND

[0002] With the development of computer technology, traditional paper bills have been basically replaced by electronic bills.

[0003] In the prior art, various market subjects such as merchants can install or interface the system of a bill service provider, and the bill service provider can act as an agent for the merchant to issue invoices and other bills from a bill service server. However, it is difficult to manage many bill service providers, and various irregularities such as missing invoices and false invoices often occur. In addition, in addition to normal tax payment, merchants also need to pay service fees to these bill service providers, which also seriously aggravates the burden of small and medium-sized enterprises.

[0004] With the continuous improvement of the system, in order to reduce the burden of small and medium-sized enterprises as much as possible and govern irregularities in the tax payment process, only a few service providers that can provide payment services have the qualifications of bill service providers at present. The payment services provided by these service providers are also the payment services corresponding to the most commonly used payment channels of the majority of users.

[0005] Even if there are only a few service providers that can provide bill services, merchants still need to interface the systems of multiple service providers, which not only makes the process of obtaining bill services by merchants extremely inconvenient, but also increases the cost of merchants. SUMMARY

[0006] The embodiments of the present specification provide a bill generation system, method, device, storage medium and electronic equipment to partially solve the problems existing in the prior art.

[0007] The embodiments of the present specification adopt the following technical solutions:

[0008] The bill generation system provided by the present specification comprises a bill service server, a payment service system corresponding to different service providers, and a joint platform corresponding to different service providers. Wherein:

[0009] The first joint platform is configured to obtain a bill generation initial request, determine whether the historical payment service corresponding to the payment information carried in the bill generation initial request is executed by the first payment service system corresponding to the first joint platform according to the payment information, and if not, send the bill generation initial request to the bill service server.

[0010] The bill service server is configured to receive the bill generation initial request sent by the first joint platform, determine a payment business system that executes the historical payment business as a second payment business system according to the payment information carried in the bill generation initial request, and forward the bill generation initial request to a second joint platform corresponding to the second payment business system.

[0011] The second joint platform is configured to, after receiving the bill generation initial request forwarded by the bill service server, verify the payment information according to the payment information and historical payment data stored in the second payment business system, and send a bill generation final request carrying the payment information to the bill service server after the verification is passed.

[0012] The bill service server is configured to generate an electronic bill corresponding to the historical payment business according to the payment information carried in the bill generation final request after receiving the bill generation final request.

[0013] The bill service server is configured to receive the bill generation initial request sent by the first joint platform, determine a payment business system that executes the historical payment business as a second payment business system according to the payment information carried in the bill generation initial request, and forward the bill generation initial request to a second joint platform corresponding to the second payment business system.

[0014] The bill service server is configured to receive the bill generation initial request sent by the first joint platform, determine a payment business system that executes the historical payment business as a second payment business system according to the payment information carried in the bill generation initial request, and forward the bill generation initial request to a second joint platform corresponding to the second payment business system.

[0015] The bill service server is configured to receive the bill generation initial request sent by the first joint platform, determine a payment business system that executes the historical payment business as a second payment business system according to the payment information carried in the bill generation initial request, and forward the bill generation initial request to a second joint platform corresponding to the second payment business system.

[0016] The bill service server is configured to receive the bill generation initial request sent by the first joint platform, determine a payment business system that executes the historical payment business as a second payment business system according to the payment information carried in the bill generation initial request, and forward the bill generation initial request to a second joint platform corresponding to the second payment business system.

[0017] The bill service server is configured to receive the bill generation initial request sent by the first joint platform, determine a payment business system that executes the historical payment business as a second payment business system according to the payment information carried in the bill generation initial request, and forward the bill generation initial request to a second joint platform corresponding to the second payment business system.

[0018] The bill service server is configured to receive the bill generation initial request sent by the first joint platform, determine a payment business system that executes the historical payment business as a second payment business system according to the payment information carried in the bill generation initial request, and forward the bill generation initial request to a second joint platform corresponding to the second payment business system.

[0019] The bill service server is configured to receive the bill generation initial request sent by the first joint platform, determine a payment business system that executes the historical payment business as a second payment business system according to the payment information carried in the bill generation initial request, and forward the bill generation initial request to a second joint platform corresponding to the second payment business system.

[0020] The bill service server is configured to receive the bill generation initial request sent by the first joint platform, determine a payment business system that executes the historical payment business as a second payment business system according to the payment information carried in the bill generation initial request, and forward the bill generation initial request to a second joint platform corresponding to the second payment business system.

[0021] According to the payment information carried in the initial ticket generation request, it is judged whether the historical payment business corresponding to the payment information is executed by the first payment business system corresponding to the first joint use platform;

[0022] If not, the initial ticket generation request is sent to the ticket business server, so that the ticket business server determines the second payment business system that executes the historical payment business according to the payment information carried in the initial ticket generation request, and forwards the initial ticket generation request to the second joint use platform corresponding to the second payment business system, so that the second joint use platform verifies the payment information according to the payment information and the historical payment data stored in the second payment business system, and sends a final ticket generation request carrying the payment information to the ticket business server after verification, so that the ticket business server generates an electronic ticket corresponding to the historical payment business according to the payment information carried in the final ticket generation request.

[0023] The present specification provides a ticket generation method, which is applied to a second joint use platform, and the method comprises:

[0024] receiving a ticket generation initial request forwarded by a ticket business server; wherein the ticket generation initial request is sent to the ticket business server by a first joint use platform after judging that the historical payment business corresponding to the payment information carried in the ticket generation initial request is not executed by the first payment business system corresponding to the first joint use platform, and forwarded by the ticket business server after determining that the payment business system that executes the historical payment business is the second payment business system corresponding to the second joint use platform according to the payment information;

[0025] verifying the payment information according to the payment information and the historical payment data stored in the second payment business system;

[0026] After verification, a final ticket generation request carrying the payment information is sent to the ticket business server, so that the ticket business server generates an electronic ticket corresponding to the historical payment business according to the payment information carried in the final ticket generation request.

[0027] The present specification provides a ticket generation device, which comprises:

[0028] The receiving module is configured to receive a bill generation initial request sent by a first joint platform; wherein the bill generation initial request is sent by the first joint platform according to payment information carried in the bill generation initial request, and the first joint platform determines that a historical payment service corresponding to the payment information is not executed by a first payment service system corresponding to the first joint platform;

[0029] The determining module is configured to determine, according to the payment information carried in the bill generation initial request, a payment service system that executes the historical payment service as a second payment service system;

[0030] The forwarding module is configured to forward the bill generation initial request to a second joint platform corresponding to the second payment service system, so that the second joint platform verifies the payment information according to the payment information carried in the bill generation initial request and historical payment data stored in the second payment service system;

[0031] The receiving module is further configured to receive a bill generation final request carrying the payment information sent by the second joint platform after the verification of the payment information is passed;

[0032] The generating module is configured to generate an electronic bill corresponding to the historical payment service according to the payment information carried in the bill generation final request.

[0033] The present specification provides a bill generation device, which is applied to a first joint platform, and the device comprises:

[0034] The obtaining module is configured to obtain a bill generation initial request;

[0035] The determining module is configured to determine, according to payment information carried in the bill generation initial request, whether a historical payment service corresponding to the payment information is executed by a first payment service system corresponding to the first joint platform;

[0036] The sending module is configured to, when the determination result of the determining module is no, send the bill generation initial request to a bill service server, so that the bill service server determines a second payment service system that executes the historical payment service according to the payment information carried in the bill generation initial request, and forwards the bill generation initial request to a second joint platform corresponding to the second payment service system, so that the second joint platform verifies the payment information according to the payment information and historical payment data stored in the second payment service system, and sends a bill generation final request carrying the payment information to the bill service server after the verification is passed, so that the bill service server generates an electronic bill corresponding to the historical payment service according to the payment information carried in the bill generation final request.

[0037] The present specification provides a ticket generation device, the device is applied to a second joint platform, the device comprises:

[0038] The receiving module is configured to receive a ticket generation initial request forwarded by a ticket service server; wherein the ticket generation initial request is sent to the ticket service server after the first joint platform determines that a historical payment service corresponding to payment information carried by the ticket generation initial request is not executed by a first payment service system corresponding to the first joint platform, and is forwarded by the ticket service server after determining that a payment service system executing the historical payment service is a second payment service system corresponding to the second joint platform according to the payment information;

[0039] The verification module is configured to verify the payment information according to the payment information and historical payment data stored in the second payment service system;

[0040] The sending module is configured to send a ticket generation final request carrying the payment information to the ticket service server after verification, so that the ticket service server generates an electronic ticket corresponding to the historical payment service according to the payment information carried in the ticket generation final request.

[0041] The present specification provides a computer readable storage medium, the storage medium stores a computer program, and the computer program is executed by a processor to implement the above-mentioned ticket generation method.

[0042] The present specification provides an electronic device, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, and the processor executes the program to implement the above-mentioned ticket generation method.

[0043] The above-mentioned at least one technical scheme adopted by the embodiment of the present specification can achieve the following beneficial effects:

[0044] The embodiment of the specification discloses a kind of bill generation system, first joint use platform judges the payment information in the bill generation initial request obtained corresponds Whether the historical payment service is executed by the first payment service system corresponding to the first joint use platform, if not, the bill generation initial request is sent to bill service server, by bill service server determines the second payment service system of executing the historical payment service, and the bill generation initial request is forwarded to the second joint use platform corresponding to the second payment service system, by second joint use platform, the payment information in the bill generation initial request is checked, and after checking, bill generation final request is sent to bill service server, by bill service server, the electronic bill corresponding to the historical payment service is generated.Through the above system, merchant only needs to connect one service provider corresponding joint use platform, it can issue the electronic bill corresponding to the payment service executed by any payment service system. BRIEF DESCRIPTION OF DRAWINGS

[0045] The drawings described herein are used to provide further understanding of the specification, and form part of the specification, the illustrative embodiment of the specification and its explanation are used to explain the specification, and do not constitute improper limitation on the specification.In the drawings:

[0046] Figure 1 A kind of bill generation system schematic diagram provided for the embodiment of the specification;

[0047] Figure 2 A kind of bill generation method flow chart schematic diagram provided for the embodiment of the specification;

[0048] Figure 3 The first bill generation device schematic diagram provided for the embodiment of the specification;

[0049] Figure 4 The second bill generation device schematic diagram provided for the embodiment of the specification;

[0050] Figure 5 The third bill generation device schematic diagram provided for the embodiment of the specification;

[0051] Figure 6 The structure schematic diagram of electronic equipment provided for the embodiment of the specification. DETAILED DESCRIPTION

[0052] To make the purpose, technical scheme and advantages of the specification clearer, the technical scheme of the specification will be described clearly and completely in the following with the embodiment of the specification and corresponding drawings.Obviously, the described embodiment is only a part of the embodiment of the specification, not all the embodiments.Based on the embodiment in the specification, all other embodiments obtained by those skilled in the art without making creative labor belong to the scope of the specification.

[0053] The technical solutions provided by the embodiments of the present specification are described in detail below with reference to the drawings.

[0054] At present, a service provider with the qualification of a bill service provider can not only provide a payment channel for a user through its own payment business system, so that the user uses the payment business provided by the payment business system of the service provider through the payment channel, but also provide bill services for a merchant through the service provider's own joint platform.

[0055] When the user obtains the goods and / or services of the merchant and pays for them, the user can opt for a payment channel of a service provider to make a payment, and accordingly, the payment information of the payment business performed by the user will also be stored in the payment business system of the service provider. When the merchant needs to obtain the electronic bill corresponding to the above payment business, the merchant can also opt for a joint platform of a service provider, send an invoice request to the bill business server through the joint platform, and request the bill business server to generate an electronic bill corresponding to the payment business.

[0056] However, in the above process, the joint platform needs to verify the payment information corresponding to the above payment business before sending an invoice request to the bill business server. However, it is the user's freedom to choose a payment channel of a service provider, and it is also the merchant's freedom to interface with a joint platform of a service provider. If the service provider corresponding to the payment channel selected by the user is not the same as the service provider corresponding to the joint platform interfaced by the merchant, the joint platform interfaced by the merchant has no access to the payment information stored in the payment business system of another service provider (because the payment information is sensitive information for each service provider and cannot be easily accessed by others), and thus cannot verify the payment information corresponding to the above payment business. Therefore, the merchant has no choice but to interface with the joint platforms of all service providers to cope with the above situation, and even if these service providers do not charge any fees for the bill services they provide, the merchant still needs to interface with multiple joint platforms, which greatly increases the operation and use costs.

[0057] Therefore, the embodiments of the present specification provide a bill generation system, as shown in Figure 1 The bill generation system includes a bill business server, payment business systems corresponding to different service providers, and joint platforms corresponding to different service providers. Wherein:

[0058] The bill business server is located in the backend and interfaces with the joint platforms corresponding to the service providers, and is used to generate electronic bills.

[0059] The payment service system is located at the back end and is borne by at least one server, and is used to provide a payment service for a user. The user can use the payment service through a payment channel provided by the payment service system, and meanwhile, payment information of an executed payment service is stored.

[0060] The joint platform is located at the back end and is also borne by at least one server, and is used to provide a bill service for a merchant. The joint platform is a safe and efficient digital channel directly connected to a tax department and a service provider, and is created to promote the digitalization of tax collection. The service provider can directly connect to a bill service end for generating electronic invoices and other electronic bills through a standardized interface by using an internal information system of the service provider.

[0061] For the same service provider, the corresponding joint platform has the permission to query payment information in the corresponding payment service system of the service provider. For different service providers, the joint platform corresponding to one service provider does not have the permission to query payment information in the payment service system corresponding to another service provider. Figure 1 The different service providers are service provider 1, service provider 2,..., and service provider n.

[0062] Based on the system as shown in Figure 1 , the bill generation method provided by the embodiments of the present specification is shown in Figure 2 .

[0063] Figure 2 A bill generation method flow diagram provided by the embodiments of the present specification is shown in the following steps:

[0064] S200: The first joint platform acquires a bill generation initial request.

[0065] In the embodiments of the present specification, the first and the second are used to distinguish different service providers. The first joint platform and the first payment service system correspond to the same service provider, and the second joint platform and the second payment service system correspond to another service provider.

[0066] Whether the first joint platform or the second joint platform can be borne by a server cluster including multiple servers. In the present specification, the merchant only needs to consider network delay to select the joint platform borne by the nearest server to the merchant for connection, without considering which service provider the joint platform borne by the server belongs to.

[0067] In the embodiments of the present specification, the joint platform connected by the merchant is referred to as the first joint platform, and the payment service system corresponding to the first joint platform is referred to as the first payment service system.

[0068] The first joint platform can obtain a bill generation initial request for generating an electronic bill corresponding to the payment service after a user as a payer pays a fee to a merchant as a payee.

[0069] The payment service system used by the user to perform the payment service is another service provider's payment service system, which is referred to as a second payment service system in the embodiments of the present specification, and the joint platform corresponding to the second payment service system is referred to as a second joint platform.

[0070] Generally, the first payment service system can serve as a merchant's acquirer system and receive a collection request sent by a merchant as a payee. The first payment service system can send the collection request to the second payment service system according to payment channel information specified by the user as a payer in the collection request. The second payment service system can perform a payment service corresponding to the collection request according to payment information carried in the collection request after receiving the collection request, store data of the payment service as historical payment data, and return an execution success result of the payment service to the first payment service system. This is the case of intermediate connection in the payment service process.

[0071] In order to avoid the merchant's illegal behavior of missing invoicing or false invoicing, the first payment service system can automatically generate a bill generation initial request carrying payment information of the payment service and send the bill generation initial request to the first joint platform in response to the execution success result after receiving the execution success result in the embodiments of the present specification. At this time, the first joint platform can obtain the bill generation initial request.

[0072] Of course, in addition to the above-mentioned automatic sending of the bill generation initial request to the first joint platform by the first payment service system after receiving the execution success result returned by the second payment service system, the merchant can manually send a bill generation initial request for a certain historical payment service that has been successfully executed to the first joint platform through the first payment service system, or directly send a bill generation initial request for a certain historical payment service that has been successfully executed to the first joint platform, which is not limited in the present specification.

[0073] S201: According to the payment information carried in the bill generation initial request, it is judged whether the historical payment service corresponding to the payment information is executed by the first payment service system corresponding to the first joint platform.

[0074] For the payment service that has been successfully executed, it is referred to as a historical payment service in the present specification

[0075] After receiving the initial ticket generation request, the first association platform can determine whether the historical payment service corresponding to the payment information carried in the initial ticket generation request is executed by the first payment service system according to the payment information carried in the initial ticket generation request.

[0076] Specifically, the first association platform can obtain the payment channel information contained in the payment information, and determine whether the service provider identifier corresponding to the first payment service system is contained in the payment channel information. If yes, it is determined that the historical payment service is executed by the first payment service system, otherwise, it is determined that the historical payment service is not executed by the first payment service system.

[0077] S202: If the historical payment service is not executed by the first payment service system, the initial ticket generation request is sent to the ticket service server.

[0078] When the first association platform determines that the historical payment service is not executed by the first payment service system, since the historical payment data of the historical payment service is not stored in the first payment service system, the first payment service system cannot verify the payment information carried in the initial ticket generation request, and therefore the initial ticket generation request can be directly sent to the ticket service server for generating electronic tickets.

[0079] When the first association platform determines that the historical payment service is executed by the first payment service system, that is, the payment service system corresponding to the payment channel selected by the user is the same service provider as the service provider corresponding to the association platform of the merchant, the historical payment data stored in the first payment service system can be queried, and the payment information can be verified according to the queried historical payment data and the payment information carried in the initial ticket generation request. After verification, the final ticket generation request carrying the payment information can be generated, and the final ticket generation request is sent to the ticket service server, so that the ticket service server can directly generate electronic tickets according to the payment information carried in the final ticket generation request.

[0080] The first association platform can obtain at least one of the payment order identifier, the payer information, the payee information and the payment amount contained in the payment information as to-be-verified information when verifying the payment information, query the to-be-verified information from the historical payment data stored in the first payment business system, and verify the payment information according to the query result. If the payment order corresponding to the payment order identifier is queried from the historical payment data stored in the first payment business system, and the payer information in the payment order is the same as the payer information contained in the payment information, the payee information in the payment order is the same as the payee information contained in the payment information, and the payment amount in the payment order is the same as the payment amount contained in the payment information, it is determined that the payment information is verified. If the payment order corresponding to the payment order identifier is not queried from the historical payment data stored in the first payment business system, or the payer information in the payment order is different from the payer information contained in the payment information, or the payee information in the payment order is different from the payee information contained in the payment information, or the payment amount in the payment order is different from the payment amount contained in the payment information, it is determined that the payment information is not verified.

[0081] S203: The bill business server determines a payment business system that executes the historical payment business as a second payment business system according to the payment information carried in the bill generation initial request.

[0082] When the first association platform determines that the historical payment business is not executed by the first payment business system, after sending the bill generation initial request to the bill business server, the bill business server determines a second payment business system that executes the historical payment business according to the payment information carried in the bill generation initial request.

[0083] Specifically, the bill business server can determine a service provider identifier contained in the payment channel information according to the payment channel information contained in the payment information, and determine a payment business system corresponding to the service provider identifier contained in the payment channel information as the second payment business system that executes the historical payment business.

[0084] S204: The bill generation initial request is forwarded to a second association platform corresponding to the second payment business system.

[0085] After the bill business server determines the second payment business system, the bill generation initial request can be forwarded to a second association platform corresponding to the second payment business system.

[0086] S205: The second joint platform verifies the payment information according to the payment information carried in the initial ticket generation request and the historical payment data stored in the second payment business system.

[0087] After receiving the initial ticket generation request forwarded by the ticket business server, the second joint platform can query the historical payment data stored in the second payment business system, and verify the payment information according to the historical payment data queried and the payment information carried in the initial ticket generation request.

[0088] In the verification of the payment information, the second joint platform can obtain at least one of the payment order identifier, the payer information, the payee information and the payment amount contained in the payment information as to-be-verified information, query the to-be-verified information in the historical payment data stored in the second payment business system, and verify the payment information according to the query result. If the payment order corresponding to the payment order identifier is queried in the historical payment data stored in the second payment business system, and the payer information in the payment order is the same as the payer information contained in the payment information, the payee information in the payment order is the same as the payee information contained in the payment information, and the payment amount in the payment order is the same as the payment amount contained in the payment information, it is determined that the verification of the payment information is passed. If the payment order corresponding to the payment order identifier is not queried in the historical payment data stored in the second payment business system, or the payer information in the payment order is different from the payer information contained in the payment information, or the payee information in the payment order is different from the payee information contained in the payment information, or the payment amount in the payment order is different from the payment amount contained in the payment information, it is determined that the verification of the payment information is failed.

[0089] S206: After the verification is passed, a final ticket generation request carrying the payment information is sent to the ticket business server.

[0090] After the verification of the payment information carried in the initial ticket generation request is passed, the second joint platform can generate a final ticket generation request carrying the payment information, and send the final ticket generation request to the ticket business server.

[0091] S207: The ticket business server generates an electronic ticket corresponding to the historical payment business according to the payment information carried in the final ticket generation request.

[0092] In the embodiments of the present specification, the electronic ticket includes but is not limited to an electronic invoice. Those skilled in the art should understand that, in addition to the electronic invoice, other electronic tickets can also be generated by the method shown in the figure. Figure 2 ​

[0093] When the electronic bill is an electronic invoice, after receiving the bill generation final request, the bill service server can generate the electronic invoice corresponding to the above historical payment business according to the payment information, the payee information, the payment amount and the detail line information contained in the payment information carried in the bill generation final request.

[0094] After generating the electronic bill, the bill service server can also return the generated electronic bill to the second joint platform, so that the second joint platform returns the electronic bill to the first payment business system.

[0095] Specifically, the second joint platform can return the received electronic bill directly to the first payment business system based on the communication connection between the second joint platform and the first payment business system, or the second joint platform can also return the received electronic bill to the first joint platform based on the communication connection between the second joint platform and the first joint platform, so that the first joint platform returns the electronic bill to the first payment business system.

[0096] After receiving the electronic invoice, the first payment business system can send the electronic invoice to the merchant as the payee, and provide it to the user as the payer.

[0097] Through the above method, the merchant only needs to connect to the joint platform corresponding to a service provider, for example, considering the factor of network delay, the merchant can connect to the joint platform carried by the server closest to the merchant itself, so as to issue the electronic bill corresponding to the payment business executed by any payment business system, without the need to connect to all joint platforms corresponding to service providers, which can effectively reduce the operation and use cost of the user. At the same time, the bill generation initial request is automatically generated and sent to the first joint platform by the first payment business system after receiving the execution success result of the payment business, so that whether the user as the payer needs the electronic bill or not, the issuance of the electronic bill can be bound together with the collection behavior of the merchant, which can effectively prevent the merchant from developing invoices, developing invoices, and other irregular behaviors.

[0098] In the embodiments of the present application, as described above, the selection of the payment channel depends on the user as the payer, and the connection of the joint platform depends on the merchant, and similarly, the payment business system used by the merchant as the own collection agency also depends on the merchant itself. Therefore, in theory, the payment business system corresponding to the payment channel selected by the user, the joint platform connected by the merchant, and the payment business system selected by the merchant as the own collection agency may all be the same, only partially the same, or different. Figure 2 The process shown is an example of explaining that the service provider corresponding to the joint platform connected by the merchant and the payment business system selected by the merchant as the own collection agency is the same.

[0099] If the combined platform connected by the merchant is different from the service provider corresponding to the payment business system selected by the merchant as its acquirer, then in step S200, the ticket generation initial request obtained by the first combined platform can be sent by the payment business system selected by the merchant as its acquirer (hereinafter referred to as a third payment business system). That is, after receiving the execution success result of the payment business executed for the user by the second payment business system, the third payment business system automatically generates a ticket generation initial request carrying the payment information of the payment business in response to the trigger of the execution success result, and sends the ticket generation initial request to the first combined platform. Subsequently, steps S201-S207 can be continued to generate the electronic ticket of the payment business.

[0100] In summary, in the embodiments of the present specification, the ticket generation initial request is generated by the payment business system selected by the merchant as its acquirer and sent to the combined platform connected by the merchant. If the service provider corresponding to the payment business system selected by the user to execute the payment business is the same service provider as the combined platform connected by the merchant, the combined platform can directly verify the payment information carried in the ticket generation initial request according to the historical payment data stored in the payment business system used to execute the payment business, and after verification, generate a ticket generation final request carrying the payment information and send it to the ticket business server, so that the ticket business server generates an electronic ticket. If the service provider corresponding to the payment business system selected by the user to execute the payment business is not the same service provider as the combined platform connected by the merchant, the combined platform can first route the ticket generation initial request to the ticket business server, and the ticket business server forwards the ticket generation initial request to the combined platform corresponding to the payment business system selected by the merchant as its acquirer, so that it verifies the payment information carried in the ticket generation initial request, and after verification, generates a ticket generation final request carrying the payment information and sends it to the ticket business server, so that the ticket business server generates an electronic ticket. Before the generation of the electronic ticket is realized through the above process, the merchant can first authorize on the ticket business server, and after authorization, the above method can be used to provide the merchant with a combined platform that only connects to any one service provider, so as to provide the service of issuing an electronic ticket corresponding to the payment business executed through any payment business system.

[0101] The above is a ticket generation system and method provided by the embodiments of the present specification. Based on the same idea, the present specification also provides corresponding devices, storage media and electronic equipment.

[0102] Figure 3 The first ticket generation device provided by the embodiments of the present specification is shown in the schematic diagram, which comprises:

[0103] The receiving module 301 is configured to receive a bill generation initial request sent by a first joint platform; wherein the bill generation initial request is sent by the first joint platform according to payment information carried in the bill generation initial request, and the first joint platform determines that a historical payment business corresponding to the payment information is not executed by a first payment business system corresponding to the first joint platform;

[0104] The determining module 302 is configured to determine a payment business system executing the historical payment business as a second payment business system according to the payment information carried in the bill generation initial request;

[0105] The forwarding module 303 is configured to forward the bill generation initial request to a second joint platform corresponding to the second payment business system, so that the second joint platform performs verification on the payment information according to the payment information carried in the bill generation initial request and historical payment data stored in the second payment business system;

[0106] The receiving module 301 is further configured to receive a bill generation final request carrying the payment information sent by the second joint platform after the verification on the payment information is passed;

[0107] The generating module 304 is configured to generate an electronic bill corresponding to the historical payment business according to the payment information carried in the bill generation final request.

[0108] Optionally, the generating module 304 is further configured to return the generated electronic bill to the second joint platform, so that the second joint platform returns the electronic bill to the first payment business system.

[0109] Optionally, the electronic bill includes an electronic invoice.

[0110] The generating module 304 is specifically configured to generate an electronic invoice corresponding to the historical payment business according to payment party information, a payee, a payment amount and detail line information included in the payment information.

[0111] Figure 4 A second bill generation device schematic diagram provided by an embodiment of the present specification is provided, and the device is applied to a first joint platform. The device includes:

[0112] The obtaining module 401 is configured to obtain a bill generation initial request.

[0113] The determining module 402 is configured to determine whether a historical payment business corresponding to payment information carried in the bill generation initial request is executed by a first payment business system corresponding to the first joint platform.

[0114] The sending module 403 is configured to, when the determination result of the determination module is no, send the bill generation initial request to the bill service server, so that the bill service server determines a second payment service system for executing the historical payment service according to the payment information carried in the bill generation initial request, and forwards the bill generation initial request to a second joint use platform corresponding to the second payment service system, so that the second joint use platform verifies the payment information according to the payment information and historical payment data stored in the second payment service system, and sends a bill generation final request carrying the payment information to the bill service server after the verification is passed, so that the bill service server generates an electronic bill corresponding to the historical payment service according to the payment information carried in the bill generation final request.

[0115] Optionally, the obtaining module 401 is specifically configured to receive a bill generation initial request carrying payment information of a historical payment service, which is generated and sent by the first payment service system.

[0116] The bill generation initial request is generated and sent by the first payment service system in response to a successful execution result of the historical payment service.

[0117] Optionally, the determination module 402 is specifically configured to obtain payment channel information contained in the payment information, determine whether the payment channel information contains a service provider identifier corresponding to the first payment service system, if the payment channel information contains the service provider identifier, determine that the historical payment service corresponding to the payment information is executed by the first payment service system, and if the payment channel information does not contain the service provider identifier, determine that the historical payment service corresponding to the payment information is not executed by the first payment service system.

[0118] Optionally, the apparatus further includes:

[0119] The verification module 404 is configured to, if the determination module 402 determines that the historical payment service is executed by the first payment service system, verify the payment information according to the payment information and historical payment data stored in the first payment service system, and send a bill generation final request carrying the payment information to the bill service server after the verification is passed.

[0120] Optionally, the verification module 404 is specifically configured to obtain at least one of a payment order identifier, a payer information, a payee information and a payment amount contained in the payment information as to-be-verified information, query the to-be-verified information in the historical payment data stored in the first payment service system, and verify the payment information according to a query result.

[0121] Figure 5A third ticket generation device schematic diagram provided by an embodiment of the present specification is applied to a second joint platform, and the device comprises:

[0122] The receiving module 501 is configured to receive a ticket generation initial request forwarded by a ticket service server; wherein the ticket generation initial request is sent to the ticket service server after the first joint platform determines that a historical payment service corresponding to payment information carried by the ticket generation initial request is not executed by a first payment service system corresponding to the first joint platform, and is forwarded by the ticket service server after the ticket service server determines that a payment service system executing the historical payment service is a second payment service system corresponding to the second joint platform according to the payment information;

[0123] The checking module 502 is configured to check the payment information according to the payment information and historical payment data stored in the second payment service system;

[0124] The sending module 503 is configured to send a ticket generation final request carrying the payment information to the ticket service server after the checking passes, so that the ticket service server generates an electronic ticket corresponding to the historical payment service according to the payment information carried in the ticket generation final request.

[0125] Optionally, the checking module 502 is specifically configured to obtain at least one of a payment order identifier, a payer information, a payee information and a payment amount contained in the payment information as to-be-checked information; query the to-be-checked information in the historical payment data stored in the second payment service system; and check the payment information according to a query result.

[0126] Optionally, the receiving module 501 is further configured to receive the electronic ticket sent by the ticket service server;

[0127] The sending module 503 is further configured to return the received electronic ticket to the first payment service system based on a communication connection between the first payment service system; or return the received electronic ticket to the first joint platform based on a communication connection between the first joint platform, so that the first joint platform returns the electronic ticket to the first payment service system.

[0128] The present specification also provides a computer-readable storage medium, which stores a computer program. The computer program is executed by a processor to execute the above-provided ticket generation method.

[0129] Based on Figure 2 The present specification also provides a structure schematic diagram of an electronic device as shown. Figure 6 The present specification also provides a structure schematic diagram of an electronic device as shown.Figure 6 At the hardware level, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and of course, other hardware required by the business. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs to implement the above-mentioned bill generation method.

[0130] The above only describes the embodiments of the present specification and is not intended to limit the present specification. The present specification can have various modifications and changes for those skilled in the art. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present specification shall be included in the scope of claims of the present specification.

Claims

1. A ticket generating system, the ticket generating system comprising: The bill business server, the payment business systems respectively corresponding to different service providers, and the joint platforms respectively corresponding to different service providers; wherein: The first joint platform is configured to obtain a bill generation initial request, determine whether a historical payment business corresponding to payment information carried in the bill generation initial request is executed by a first payment business system corresponding to the first joint platform according to the payment information, and send the bill generation initial request to the bill business server if the historical payment business is not executed by the first payment business system. The bill business server is configured to receive the bill generation initial request sent by the first joint platform, determine a payment business system executing the historical payment business as a second payment business system according to the payment information carried in the bill generation initial request, and forward the bill generation initial request to a second joint platform corresponding to the second payment business system. The second joint platform is configured to, after receiving the bill generation initial request forwarded by the bill business server, verify the payment information according to the payment information and historical payment data stored in the second payment business system, and send a bill generation final request carrying the payment information to the bill business server after the verification is passed. The bill business server is configured to generate an electronic bill corresponding to the historical payment business according to the payment information carried in the bill generation final request after receiving the bill generation final request.

2. The bill generation system of claim 1, wherein the first payment business system is configured to receive a collection request sent by a collection party, send the collection request to the second payment business system according to payment channel information specified by a payer in the collection request, and the second payment business system is configured to, after receiving the collection request, execute a payment business corresponding to the collection request, store data of the payment business as historical payment data after the execution of the payment business is successful, and return an execution success result of the payment business to the first payment business system. The first payment business system is further configured to generate a bill generation initial request carrying payment information of the payment business in response to triggering of the execution success result, and send the bill generation initial request to the first joint platform.

3. The bill generation system of claim 2, wherein the bill business server is further configured to return the generated electronic bill to the second joint platform. The second joint platform is further configured to return the received electronic bill to the first payment business system based on a communication connection between the first payment business system and the second joint platform, or return the received electronic bill to the first joint platform based on a communication connection between the first joint platform and the second joint platform, so that the first joint platform returns the electronic bill to the first payment business system. The first payment business system is further configured to send the electronic bill to the payer. ​ 4.The ticket generation system of claim 2, wherein the first joint platform is further configured to, if it is determined that the historical payment transaction is executed by the first payment transaction system, verify the payment information according to the payment information and historical payment data stored in the first payment transaction system, and send a ticket generation final request carrying the payment information to the ticket transaction server after the verification is passed. 5.A ticket generation method, the method comprising: receiving a ticket generation initial request sent by a first joint platform, wherein the ticket generation initial request is sent by the first joint platform after it is determined that historical payment transaction corresponding to payment information carried in the ticket generation initial request is not executed by a first payment transaction system corresponding to the first joint platform according to the payment information; determining a payment transaction system executing the historical payment transaction as a second payment transaction system according to the payment information carried in the ticket generation initial request; forwarding the ticket generation initial request to a second joint platform corresponding to the second payment transaction system, so that the second joint platform verifies the payment information according to the payment information carried in the ticket generation initial request and historical payment data stored in the second payment transaction system; receiving a ticket generation final request carrying the payment information sent by the second joint platform after the verification of the payment information is passed; generating an electronic ticket corresponding to the historical payment transaction according to the payment information carried in the ticket generation final request. 6.The method of claim 5, further comprising: returning the generated electronic ticket to the second joint platform, so that the second joint platform returns the electronic ticket to the first payment transaction system.

7. The method of claim 5, the electronic ticket comprising: an electronic invoice; generating an electronic ticket corresponding to the historical payment transaction according to the payment information carried in the ticket generation final request, specifically comprising: generating an electronic invoice corresponding to the historical payment transaction according to payer information, payee information, payment amount and detail line information contained in the payment information. 8.A ticket generation method, the method being applied to a first joint platform, the method comprising: obtaining a ticket generation initial request; determining whether a historical payment transaction corresponding to payment information carried in the ticket generation initial request is executed by a first payment transaction system corresponding to the first joint platform according to the payment information. sending, if not executed by the first payment service system, the bill generation initial request to a bill service server, so that the bill service server determines a second payment service system that executes the historical payment service according to the payment information carried in the bill generation initial request, and forwards the bill generation initial request to a second joint use platform corresponding to the second payment service system, so that the second joint use platform verifies the payment information according to the payment information and historical payment data stored in the second payment service system, and sends a bill generation final request carrying the payment information to the bill service server after verification, so that the bill service server generates an electronic bill corresponding to the historical payment service according to the payment information carried in the bill generation final request.

9. The method of claim 8, wherein the bill generation initial request is obtained, specifically comprising: receiving the bill generation initial request carrying the payment information of the historical payment service generated and sent by the first payment service system; wherein the bill generation initial request is generated and sent by the first payment service system in response to the successful execution result of the historical payment service.

10. The method of claim 8, wherein whether the payment information corresponds to the historical payment service executed by the first payment service system corresponding to the first joint use platform is determined according to the payment information carried in the bill generation initial request, specifically comprising: obtaining payment channel information contained in the payment information; determining whether the payment channel information contains a service provider identifier corresponding to the first payment service system; if yes, determining that the payment information corresponds to the historical payment service executed by the first payment service system; if no, determining that the payment information does not correspond to the historical payment service executed by the first payment service system.

11. The method of claim 8, further comprising: if it is determined that the historical payment service is executed by the first payment service system, verifying the payment information according to the payment information and historical payment data stored in the first payment service system; after verification, sending a bill generation final request carrying the payment information to the bill service server.

12. The method of claim 11, wherein the payment information is verified according to the payment information and the historical payment data stored in the first payment service system, specifically comprising: obtaining at least one of a payment order identifier, a payer information, a payee information and a payment amount contained in the payment information as to-be-verified information; querying the to-be-verified information in the historical payment data stored in the first payment service system; verifying the payment information according to the query result.

13. A bill generation method, the method being applied to a second joint use platform, the method comprising: receive a bill generation initial request forwarded by a bill service server; wherein the bill generation initial request is sent to the bill service server after the first joint platform judges that a historical payment business corresponding to payment information carried in the bill generation initial request is not executed by a first payment business system corresponding to the first joint platform, and is forwarded by the bill service server after determining that the payment business system executing the historical payment business is a second payment business system corresponding to a second joint platform according to the payment information; verify the payment information according to the payment information and historical payment data stored in the second payment business system; after verification, send a bill generation final request carrying the payment information to the bill service server, so that the bill service server generates an electronic bill corresponding to the historical payment business according to the payment information carried in the bill generation final request.

14. The method of claim 13, wherein verifying the payment information according to the payment information and historical payment data stored in the second payment business system specifically comprises: obtaining at least one of a payment order identifier, a payer information, a payee information and a payment amount contained in the payment information as to-be-verified information; querying the to-be-verified information in the historical payment data stored in the second payment business system; verifying the payment information according to the query result.

15. The method of claim 13, further comprising: receiving the electronic bill sent by the bill service server; returning the received electronic bill to the first payment business system based on a communication connection between the first payment business system, or returning the received electronic bill to the first joint platform based on a communication connection between the first joint platform, so that the first joint platform returns the electronic bill to the first payment business system.

16. A bill generation device, comprising: a receiving module configured to receive a bill generation initial request sent by a first joint platform; wherein the bill generation initial request is sent by the first joint platform after judging that a historical payment business corresponding to payment information carried in the bill generation initial request is not executed by a first payment business system corresponding to the first joint platform according to the payment information obtained from the bill generation initial request; a determining module configured to determine a payment business system executing the historical payment business as a second payment business system according to the payment information carried in the bill generation initial request; a forwarding module configured to forward the bill generation initial request to a second joint platform corresponding to the second payment business system, so that the second joint platform verifies the payment information according to the payment information carried in the bill generation initial request and historical payment data stored in the second payment business system; the receiving module is further configured to receive a bill generation final request carrying the payment information sent by the second joint platform after verification of the payment information. The generating module is configured to generate, according to the payment information carried in the final request, an electronic bill corresponding to the historical payment service. 17.A bill generating apparatus, applied to a first joint platform, comprising: an obtaining module, configured to obtain a bill generating initial request; a judging module, configured to judge, according to the payment information carried in the bill generating initial request, whether a historical payment service corresponding to the payment information is executed by a first payment service system corresponding to the first joint platform; a sending module, configured to, when the judging result of the judging module is no, send the bill generating initial request to a bill service server, so that the bill service server determines, according to the payment information carried in the bill generating initial request, a second payment service system for executing the historical payment service, and forwards the bill generating initial request to a second joint platform corresponding to the second payment service system, so that the second joint platform verifies the payment information according to the payment information and historical payment data stored in the second payment service system, and sends a bill generating final request carrying the payment information to the bill service server when the verification is passed, so that the bill service server generates an electronic bill corresponding to the historical payment service according to the payment information carried in the bill generating final request. 18.A bill generating apparatus, applied to a second joint platform, comprising: a receiving module, configured to receive a bill generating initial request forwarded by a bill service server; wherein the bill generating initial request is sent to the bill service server by a first joint platform when the first joint platform judges that a historical payment service corresponding to payment information carried in the bill generating initial request is not executed by a first payment service system corresponding to the first joint platform, and is forwarded by the bill service server when the bill service server determines that a payment service system for executing the historical payment service is a second payment service system corresponding to the second joint platform according to the payment information; a verifying module, configured to verify the payment information according to the payment information and historical payment data stored in the second payment service system; a sending module, configured to, when the verification is passed, send a bill generating final request carrying the payment information to the bill service server, so that the bill service server generates an electronic bill corresponding to the historical payment service according to the payment information carried in the bill generating final request. 19.A computer readable storage medium, storing a computer program, wherein the computer program is executed by a processor to implement the method in any one of claims 5-15. 20.An electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method in any one of claims 5-15 when executing the program.

Images