Method, apparatus and device for processing electronic voucher

Abstract

Embodiments of the present specification provide a processing method, device and equipment of electronic voucher, wherein the method comprises: obtaining payment voucher and ticket voucher of a user to be processed, wherein the payment voucher is a trusted voucher generated by the user to be processed through payment application for payment operation; determining a target payment voucher to be matched in the payment voucher, and performing matching processing on the target payment voucher and the ticket voucher according to a preset matching rule; and establishing an association relationship for the target payment voucher and the ticket voucher which are matched successfully, wherein the target payment voucher corresponding to the association relationship is used to prove that the associated ticket voucher is trusted.

Description

[0001] This application is a divisional application of the Chinese patent application No. CN202110573819.7, filed on May 25, 2021, entitled "Electronic voucher processing method, device and equipment". TECHNICAL FIELD

[0002] The present document relates to the technical field of data processing, and in particular to an electronic voucher processing method, device and equipment. BACKGROUND

[0003] Invoices are not unfamiliar to people. In daily life, invoices often need to be processed, such as invoice reimbursement. After employees consume on business, they submit invoices issued by merchants to the finance department for verification and reimbursement by relevant staff. However, employees may intentionally or unintentionally submit false invoices due to various factors, which not only increases the workload of staff and reduces the efficiency of reimbursement, but also causes significant adverse effects to employees and even enterprises if the staff do not timely discover. Therefore, how to prove the authenticity of invoices in the process of invoice reimbursement is a technical problem that needs to be solved urgently. SUMMARY

[0004] One or more embodiments of the present specification provide an electronic voucher processing method. The method includes obtaining payment vouchers and bill vouchers of a user to be processed. The payment vouchers are trusted vouchers generated by the user to be processed through payment application for payment operation. Determine the target payment vouchers to be matched in the payment vouchers. According to the preset matching rule, the target payment vouchers and the bill vouchers are matched. The target payment vouchers and the bill vouchers that match successfully are associated. The target payment vouchers corresponding to the association are used to prove that the associated bill vouchers are trusted.

[0005] One or more embodiments of the present specification provide an electronic voucher processing device. The device includes an obtaining module that obtains payment vouchers and bill vouchers of a user to be processed. The payment vouchers are trusted vouchers generated by the user to be processed through payment application for payment operation. The device further includes a determining module that determines the target payment vouchers to be matched in the payment vouchers. The device further includes a matching module that matches the target payment vouchers and the bill vouchers according to the preset matching rule. The device further includes an association module that establishes an association between the target payment vouchers and the bill vouchers that match successfully. The target payment vouchers corresponding to the association are used to prove that the associated bill vouchers are trusted.

[0006] The one or more embodiments of the specification provide a processing device of electronic credentials. The device comprises a processor. The device further comprises a memory arranged to store computer executable instructions. The computer executable instructions, when executed, cause the processor to acquire payment credentials and ticket credentials of a user to be processed. The payment credentials are trusted credentials generated by the user to be processed in a payment operation through a payment application. A target payment credential to be matched in the payment credentials is determined. The target payment credential and the ticket credentials are subjected to matching processing according to a preset matching rule. An association relationship is established for the target payment credential and the ticket credentials that are successfully matched. The target payment credential corresponding to the association relationship is used to prove that the associated ticket credentials are trusted.

[0007] The one or more embodiments of the specification provide a storage medium. The storage medium is used to store computer executable instructions. The computer executable instructions, when executed by a processor, acquire payment credentials and ticket credentials of a user to be processed. The payment credentials are trusted credentials generated by the user to be processed in a payment operation through a payment application. A target payment credential to be matched in the payment credentials is determined. The target payment credential and the ticket credentials are subjected to matching processing according to a preset matching rule. An association relationship is established for the target payment credential and the ticket credentials that are successfully matched. The target payment credential corresponding to the association relationship is used to prove that the associated ticket credentials are trusted. BRIEF DESCRIPTION OF DRAWINGS

[0008] In order to more clearly illustrate the technical solutions in the one or more embodiments of the specification or the prior art, the drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments described in the specification, and for those skilled in the art, other drawings can also be obtained without creative labor.

[0009] Figure 1 A scene schematic diagram of a processing method of electronic credentials provided by the one or more embodiments of the specification;

[0010] Figure 2 A first flow schematic diagram of a processing method of electronic credentials provided by the one or more embodiments of the specification;

[0011] Figure 3 A second flow schematic diagram of a processing method of electronic credentials provided by the one or more embodiments of the specification;

[0012] Figure 4 A third flow schematic diagram of a processing method of electronic credentials provided by the one or more embodiments of the specification;

[0013] Figure 5 A fourth flowchart illustrating a method for processing electronic credentials provided in one or more embodiments of this specification;

[0014] Figure 6 A fifth flowchart illustrating a method for processing electronic vouchers provided in one or more embodiments of this specification;

[0015] Figure 7 A schematic diagram of the module composition of an electronic credential processing device provided in one or more embodiments of this specification;

[0016] Figure 8 This is a schematic diagram of the structure of an electronic credential processing device provided for one or more embodiments of this specification. Detailed Implementation

[0017] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0018] Figure 1 This diagram illustrates an application scenario of an electronic voucher processing method provided in one or more embodiments of this specification. Figure 1 As shown, the scenario includes: a first terminal device for the user to be processed and a device for processing electronic credentials. The first terminal device can be a mobile phone, tablet computer, desktop computer, laptop computer, smartwatch, etc. Figure 1 (Only a mobile phone is shown in the image). The first terminal device has a payment application installed. This payment application can be a standalone application (App), a mini-program embedded in other applications, or a web-based application, etc. The electronic voucher processing device can be a standalone server or a server cluster consisting of multiple servers.

[0019] Specifically, when the user to be processed performs a payment operation on at least one transaction through a payment application in a first terminal device of the user to be processed, the payment application corresponding to a payment server generates a corresponding electronic payment voucher (hereinafter referred to as a payment voucher in the specification), and a transaction participant of the transaction can generate a corresponding ticket voucher in an electronic form or a paper form. An electronic voucher processing device acquires the payment voucher and the ticket voucher of the user to be processed, determines a target payment voucher to be matched in the acquired payment voucher, and performs matching processing on the target payment voucher and the ticket voucher according to a preset matching rule; and establishes an association relationship for the target payment voucher and the ticket voucher that are successfully matched, and the target payment voucher corresponding to the association relationship is used to prove that the associated ticket voucher is authentic. The payment voucher, such as a payment bill or a payment flow, is generated by the payment server corresponding to the payment application, and the user cannot tamper with it, so the payment voucher is authentic and is an authentic voucher. The ticket voucher can be an invoice, and can also be a train ticket, an air ticket, and the like. The electronic voucher processing device acquires the electronic ticket voucher, such as an electronic invoice, a photo or a scanned copy of a train ticket, and the like. The transaction participant can be an online merchant, an offline merchant, a service platform (such as a ticket purchase platform), and the like, and can also be other types of transaction participants.

[0020] Therefore, by performing matching processing on the payment voucher generated based on the payment application and the ticket voucher, and establishing an association relationship for the payment voucher and the ticket voucher that are successfully matched, since the payment voucher cannot be tampered with by the user and is authentic, the authenticity of the associated ticket voucher can be proved by the payment voucher corresponding to the association relationship, and the authenticity of the ticket voucher is proved. For the reimbursement scenario, not only can the relevant auditors provide authentic verification basis, reduce the workload of the auditors for verifying the authenticity of the ticket voucher, and improve the reimbursement efficiency; but also avoid the adverse effects on the enterprise and the relevant personnel caused by the existence of false ticket vouchers.

[0021] Based on the above application scenario architecture, one or more embodiments of the specification provide an electronic voucher processing method. Figure 2 A flowchart of an electronic voucher processing method provided by one or more embodiments of the specification is shown in Figure 2 The method in Figure 1 The electronic voucher processing device in Figure 2 The method includes the following steps:

[0022] In step S102, the payment voucher and the ticket voucher of the user to be processed are acquired; wherein the payment voucher is an authentic voucher generated by the user to be processed through the payment application for the payment operation;

[0023] In the embodiments of the present specification, the payment operation of the user to be processed can correspond to at least one transaction. It can be understood that the transaction includes the user to be processed and other transaction participants, such as offline entity merchants, online merchants, service platforms (such as ticket purchase platforms), and other forms of transaction participants. When the user to be processed performs a payment operation through the payment application to pay resources (such as physical currency, virtual currency, points, etc.) to the transaction participant, the payment server corresponding to the payment application can generate corresponding payment vouchers (such as payment bills, payment water flows, etc.), and the transaction participant can generate corresponding bill vouchers (such as invoices, airplane travel orders) by itself, or the transaction participant generates corresponding bill vouchers through a third-party bill agency.

[0024] In the voucher processing scenario, such as the reimbursement scenario, when the authenticity of the bill voucher needs to be evidenced to prove that the bill voucher is credible, the payment voucher and the bill voucher of the user to be processed can be obtained by the electronic voucher processing device, and subsequent processing can be performed. It should be noted that the electronic voucher processing device can be arranged in the payment server corresponding to the payment application, and can also exist independently from the payment server.

[0025] In step S104, a target payment voucher to be matched in the payment voucher is determined, and the target payment voucher and the bill voucher are matched according to a preset matching rule.

[0026] It is considered that in actual application, the payment voucher of the user to be processed can include payment vouchers of multiple payment scenarios, such as payment vouchers of business consumption scenarios and payment vouchers of private consumption scenarios. Not every payment scenario needs to be processed for reimbursement and other voucher processing. Therefore, in one or more embodiments of the present specification, the electronic voucher processing device determines a target payment voucher to be matched in the obtained payment voucher, and matches the determined target payment voucher and the obtained bill voucher according to a preset matching rule.

[0027] In step S106, an association relationship is established between the target payment voucher and the bill voucher that are successfully matched. The target payment voucher corresponding to the association relationship is used to prove that the associated bill voucher is credible.

[0028] In one or more embodiments of the specification, by matching the payment credentials generated by the payment application based payment processing with the ticket credentials, and establishing an association relationship for the payment credentials and the ticket credentials that are successfully matched, since the payment credentials cannot be tampered by the user and are credible, the credibility of the associated ticket credentials can be proved by the corresponding payment credentials of the association relationship, thereby realizing the evidence of the authenticity of the ticket credentials. For the reimbursement scenario, not only can the relevant auditors provide credible verification basis, reduce the workload of the auditors for verifying the authenticity of the ticket credentials, and improve the reimbursement efficiency, but also avoid the adverse effects on the enterprise and the relevant personnel caused by the existence of false ticket credentials.

[0029] In the specification, the reimbursement scenario is taken as an example for illustration. It is considered that the reimbursement processing procedures of different institutions may be different, wherein the institutions include enterprises, institutions, social groups, organizations, etc. In the embodiments of the specification, multiple electronic credential acquisition methods are provided. Specifically, in order to facilitate the institution to which the to-be-processed user belongs to conveniently process the reimbursement, in one or more embodiments of the specification, the institution to which the to-be-processed user belongs can pre-configure a reimbursement code for each member of the institution, and realize the integrated processing of payment and reimbursement based on the reimbursement code. The reimbursement code can identify a unique institution, and the reimbursement code can be various forms such as a two-dimensional code, a bar code, etc. Correspondingly, the payment credentials of the to-be-processed user obtained in step S102 can include:

[0030] According to the determined user information of the to-be-processed user and the reimbursement code bound to the to-be-processed user, each payment voucher associated and generated within the corresponding first time interval is obtained from the specified payment voucher library according to the preset first time interval; wherein the reimbursement code is pre-applied by the institution to which the to-be-processed user belongs and is bound to the to-be-processed user. The binding mode of the reimbursement code can be set as needed in actual application, for example, the institution to which the to-be-processed user belongs can pre-apply the reimbursement code from the payment service end corresponding to the payment application, and provide the applied reimbursement code to the member users of the institution, each member user operates the payment application to complete the binding of the reimbursement code, and the service end saves the bound reimbursement code and the user information of each member user in the specified database; correspondingly, the to-be-processed user can directly perform payment based on the bound reimbursement code of the payment application when performing payment operation. For another example, the institution to which the to-be-processed user belongs sends the user information of the member user to the payment service end corresponding to the payment application, the payment service end binds and saves the received user information and the reimbursement code to the specified database; correspondingly, the to-be-processed user can first obtain the bound reimbursement code from the payment service end when operating the payment application to perform payment operation, and perform payment based on the obtained reimbursement code. The payment service end corresponding to the payment application can save the generated payment bill and the reimbursement code in the specified payment voucher library based on the payment operation of the user. The electronic voucher processing device can obtain the user information and the bound reimbursement code of each user from the specified database, and according to the preset first time interval, obtain the associated payment vouchers generated within the corresponding first time interval from the payment voucher library according to the obtained user information and the reimbursement code of the to-be-processed user. Wherein the user information is, for example, user identification and / or user payment account information, etc.; the first time interval can be set as needed in actual application, such as 24 hours, etc.

[0031] In view of the fact that in actual application, some institutions may not have the ability to apply for reimbursement codes, or have not had time to apply for reimbursement codes. Based on this, in one or more embodiments of the present specification, after the to-be-processed user sets the institution information of the institution to which the to-be-processed user belongs through the payment application, that is, after the user information of the to-be-processed user is associated with the institution information, the full amount of payment vouchers of the to-be-processed user can be processed. Specifically, the payment vouchers of the to-be-processed user obtained in step S102 can include:

[0032] According to the preset second time interval, the user information of the to-be-processed user is determined, and each payment voucher associated and generated within the corresponding second time interval is obtained from the specified payment voucher library. Specifically, the processing device of the electronic voucher can obtain the registration information of the payment application of each user from the specified user information library, and according to the preset second time interval, the user information of the to-be-processed user is determined according to the obtained registration information of the to-be-processed user; and according to the determined user information, each payment voucher associated and generated within the corresponding second time interval is obtained from the specified payment voucher library.

[0033] Further, in order to improve the processing efficiency of the electronic voucher, in one or more embodiments of the present specification, the payment server can obtain the payment voucher every time a payment voucher is generated. Specifically, the payment voucher of the to-be-processed user obtained in step S102 can include:

[0034] If the generation prompt information of the payment voucher is obtained from the payment application of the to-be-processed user or the payment server corresponding to the payment application, the corresponding payment voucher is obtained from the specified payment voucher library according to the obtained generation prompt information. Specifically, when the to-be-processed user binds a reimbursement code, and the processing device of the electronic voucher is separated from the payment server corresponding to the payment application and exists independently, if the payment server determines that the payment operation of the to-be-processed user is based on the reimbursement code, the payment server sends the generation prompt information of the payment voucher to the processing device of the electronic voucher through the payment application after generating the payment voucher; or the payment server generates the payment voucher and sends the generation prompt information of the payment voucher to the processing device of the electronic voucher by itself, so that the processing device of the electronic voucher obtains the corresponding payment voucher according to the received generation prompt information. When the processing device of the electronic voucher is arranged in the payment server, the payment server generates the payment voucher, and the processing device of the electronic voucher can obtain the corresponding generation prompt information and obtain the corresponding payment voucher. When the to-be-processed user does not bind the reimbursement code, the payment server can send the generation prompt information to the processing device of the electronic voucher every time a payment voucher is generated.

[0035] In order to protect the rights and interests of the user, before obtaining the payment voucher of the to-be-processed user, the payment application can first display authorization inquiry information to the to-be-processed user to inquire whether the to-be-processed user grants the right to obtain the payment voucher; and after receiving the authorization confirmation information sent by the payment application based on the authorization confirmation operation of the to-be-processed user, the payment voucher of the to-be-processed user is obtained.

[0036] Further, considering that the user to be processed can have multiple different payment applications, such as a first payment application and a second payment application, and in different scenarios, the user to be processed can use different payment applications for payment operations. In order to realize the full amount of payment credential processing of the user, in one or more embodiments of the present specification, payment credentials across payment applications can also be obtained. Taking the processing device of the electronic credential associated with the first payment application as an example, the user to be processed can operate the second payment application to export the corresponding payment credential ciphertext, and operate the first payment application to upload the payment credential ciphertext, so as to send the payment credential ciphertext to the processing device of the electronic credential through the first payment application. Correspondingly, when the processing device of the electronic credential obtains the payment credential ciphertext, if the payment credential ciphertext is successfully decrypted according to the preset decryption mode, subsequent processing is performed. Thus, in the case of ensuring the credibility of the payment credential, the processing of the payment credential across the payment application is realized.

[0037] In order to realize the comprehensive acquisition of the bill credential, the present specification provides multiple acquisition methods of the bill credential. Specifically, the acquisition of the bill credential of the user to be processed in step S102 can include:

[0038] receiving the bill credential sent by the transaction participant corresponding to the payment operation; or obtaining the bill credential from a designated third-party bill institution, wherein the obtained bill credential includes the bill credential of the user to be processed; or receiving the bill credential sent by the user to be processed.

[0039] Specifically, in order to facilitate the obtaining of the bill voucher, in one or more embodiments of the present specification, the electronic voucher processing device can be pre-connected with the transaction participant to obtain the automatic ticket return service provided by the transaction participant that associates the bill voucher with the payment voucher. Whether the user to be processed is bound to a reimbursement code or not, after the user to be processed performs a payment operation through the payment application, the user to be processed can query the payment record through the payment application and operate the bill voucher application button corresponding to the payment record. Based on the operation of the bill voucher application button by the user to be processed, the payment application sends a first bill voucher application request to the second terminal device of the determined transaction participant according to the payment voucher identifier and the institution information of the determined payment voucher. The second terminal device generates an electronic bill voucher according to the first bill voucher application request and sends the generated bill voucher and the payment voucher identifier to the electronic voucher processing device, and sends the application success information to the payment application. Alternatively, the second terminal device sends the generated bill voucher and the payment voucher identifier to the payment application, so that the payment application sends the bill voucher and the payment voucher identifier to the electronic voucher processing device, thereby realizing the automatic ticket return service. When the user to be processed is bound to a reimbursement code, the payment service side can also generate a corresponding payment voucher after the user to be processed performs a payment operation based on the reimbursement code through the payment application. According to the payment voucher identifier of the payment voucher and the institution information associated with the determined reimbursement code, etc., the second terminal device of the transaction participant is sent a second bill voucher application request; the second terminal device generates an electronic bill voucher according to the second bill voucher application request, and sends the generated bill voucher and the payment voucher identifier to the payment service side, so that the payment service side provides the bill voucher and the payment voucher identifier to the electronic voucher processing device.

[0040] Further, considering that not all transaction participants have the ability to provide automatic ticket return services, for transaction participants who cannot provide automatic ticket return services, the electronic voucher processing device can obtain a direct ticket return service from the transaction participant that does not associate the bill voucher with the payment voucher. Specifically, the transaction participant can provide an application code for the bill voucher, such as a two-dimensional code, etc. After the payment operation is successful, the payment application can be operated to scan the application code and input institution information and payment amount, etc. The payment application sends a third bill voucher application request to the second terminal device of the transaction participant according to the billing information and the application identifier of the payment application. The second terminal device generates an electronic bill voucher according to the third bill voucher application request, determines the associated electronic voucher processing device according to the application identifier, and sends the bill voucher to the electronic voucher processing device, thereby realizing the direct ticket return service.

[0041] Further, considering that some transaction participants can not have the ability to issue electronic form of ticket credentials, the paper form of ticket credentials, such as paper invoices, paper train tickets, etc. can also be provided to the to-be-processed user. At this time, the to-be-processed user can obtain the corresponding electronic form of ticket credentials by photographing, scanning, etc. and operate the payment application to upload the electronic form of ticket credentials to send the electronic form of ticket credentials to the electronic voucher processing device through the payment application. Alternatively, the payment application includes a ticket voucher management module, and the to-be-processed user uploads each electronic form of ticket credentials through the ticket voucher management module. Or, each payment record of the payment application is provided with a corresponding upload button, and the to-be-processed user operates the upload button to upload the corresponding ticket credentials, and the payment application can send the obtained ticket credentials to the electronic voucher processing device in association with the determined corresponding payment voucher identifier.

[0042] In addition, the electronic voucher processing device can also be connected with a third-party ticket agency, and the electronic voucher processing device can send a ticket voucher obtaining request to a third terminal device of the third-party ticket agency according to the pre-set transaction participant information of the pre-set third time interval; the third terminal device obtains the associated electronic form of ticket credentials generated within the corresponding third time interval from its ticket voucher library according to the participant information in the ticket voucher obtaining request, and sends the obtained ticket credentials to the electronic voucher processing device. Alternatively, the third-party ticket agency opens the access permission of the ticket voucher library to the electronic voucher processing device; the electronic voucher processing device accesses the ticket voucher library according to the pre-set third time interval, and obtains the associated ticket credentials generated within the corresponding third time interval from the ticket voucher library according to the pre-set transaction participant information.

[0043] In order to manage the obtained ticket credentials, the electronic voucher processing device saves the obtained ticket credentials, or the obtained ticket credentials and the associated payment voucher identifier when obtaining the ticket credentials, or obtaining the ticket credentials and the associated payment voucher identifier.

[0044] In the embodiments of the present specification, the obtaining method of the payment voucher and the ticket voucher is not specifically limited, and other obtaining methods can also be set according to actual needs in practical application.

[0045] In order to realize the effective matching of the payment voucher and the ticket voucher, in one or more embodiments of the present specification, the information extraction processing of the obtained each voucher can be performed first to obtain the corresponding key information, and the matching processing is performed based on the key information. Specifically, as shown in Figure 3 As shown, step S102 can further include the following step S103-2:

[0046] Step S103-2, performing information extraction processing on each payment voucher and each invoice voucher according to a preset mode, to obtain corresponding first key information and second key information;

[0047] The first key information can include payment voucher identification, payment amount, participant information (such as merchant name, etc.) of a transaction participant corresponding to a payment operation, payment time of the payment operation, etc. The second key information can include invoice voucher identification, participant information of a transaction participant providing the invoice voucher, payment amount, generation time of the invoice voucher, institution information (such as enterprise name), etc. The specific mode of information extraction can be set as needed in actual application, which is not limited in the present specification. In addition, it should be pointed out that the extraction processing operation of the first key information and the extraction processing operation of the second key information can be executed simultaneously, continuously, or discontinuously. For example, the payment voucher and the invoice voucher can be acquired at different times, and the extraction processing of the first key information and the extraction processing of the second key information can be performed on the acquired payment voucher and the acquired invoice voucher, respectively, i.e., discontinuously. The extraction processing of the first key information and the extraction processing of the second key information can also be performed simultaneously on each payment voucher and each invoice voucher acquired within a corresponding fourth time interval according to a preset fourth time interval, i.e., simultaneously. The extraction processing of the first key information and the extraction processing of the second key information can also be performed on the acquired payment voucher and the acquired invoice voucher within a corresponding fifth time interval according to a preset fifth time interval, i.e., continuously. The preset time intervals in the present specification can be the same or different.

[0048] Corresponding to step S103-2, as shown in Figure 3 Step S104 can include the following step S104-2 and step S104-4, and step S106 can include the following step S106-2:

[0049] Step S104-2, determining a target payment voucher to be matched in the payment voucher according to the first key information;

[0050] Step S104-4, performing matching processing on the first key information and the second key information of the target payment voucher according to a preset matching rule.

[0051] Step S106-2, establishing an association relationship according to the first key information of the target payment voucher and the second key information of the invoice voucher matched successfully.

[0052] Further, in order to facilitate management of the key information, as shown in Figure 4 Step S103-2 can further include the following step S103-4:

[0053] Step S103-4, save the first key information and the second key information; and if it is determined that the ticket voucher exists the associated payment voucher, determine the payment voucher identifier of the associated payment voucher, and save the determined payment voucher identifier and the corresponding second key information.

[0054] Specifically, when the extraction processing of the second key information is performed every time a ticket voucher is acquired, it is determined whether the ticket voucher and the payment voucher identifier are acquired at the same time, and if so, it is determined that the ticket voucher exists the associated payment voucher, and the payment voucher identifier acquired at the same time is determined as the payment voucher identifier of the associated payment voucher, and the payment voucher identifier is saved in correspondence with the currently extracted second key information. When the extraction processing of the second key information is performed on each ticket voucher acquired within a corresponding interval according to a predetermined time interval (such as the fourth time interval or the fifth time interval described above), when the second key information is obtained, it is determined whether the corresponding ticket voucher has saved the payment voucher identifier, and if so, it is determined that the ticket voucher exists the associated payment voucher, and the saved payment voucher identifier is determined as the payment voucher identifier of the associated payment voucher, and the payment voucher identifier is saved in correspondence with the extracted second key information.

[0055] It should be noted that the first key information and the second key information can be saved in the same database, or can be saved in different databases. Since the extraction processing time of the first key information and the second key information can be different, the saving operation of the first key information and the second key information can be performed at the same time or not at the same time.

[0056] Corresponding to the above step S103-4, as shown in FIG. 4, the step S104-2 can include the following steps S104-22 to S104-28: Figure 4

[0057] Step S104-22, determine whether the corresponding transaction participant provides the automatic ticket return service according to the participant information in each first key information;

[0058] Specifically, for each first key information, the participant information is acquired therefrom; the corresponding service identifier is acquired from the specified partner information table according to the acquired participant information, and if the acquired service identifier represents that the automatic ticket return service is provided, it is determined that the corresponding transaction participant provides the automatic ticket return service; and if the acquired service identifier represents that the automatic ticket return service is not provided, it is determined that the corresponding transaction participant does not provide the automatic ticket return service.

[0059] ​Step S104-24, if the automatic ticket return service is provided and it is determined according to the saved information that the payment credential corresponding to the first key information including the participant information is in the first state, the payment credential in the first state is determined as the first target payment credential; wherein the first state represents that the automatic ticket return service has been provided;

[0060] Specifically, if it is determined according to the participant information that the transaction participant provides the automatic ticket return service, the payment credential identifier is obtained from the first key information including the participant information; the obtained payment credential identifier is matched with the saved payment credential identifier corresponding to the ticket credential, if the matching is successful, it is determined that the payment credential corresponding to the corresponding first key is in the first state; if the matching fails, it is determined that the payment credential corresponding to the corresponding first key is in the second state. Or, when the user binds the reimbursement code, the payment server obtains the corresponding ticket credential from the transaction participant according to the reimbursement code and the payment credential identifier, and after successful acquisition, the service providing identifier representing that the automatic ticket return service has been provided is associated and saved with the corresponding payment identifier; correspondingly, the electronic credential processing device also obtains the service providing identifier when obtaining the payment credential, and saves the service providing identifier corresponding to the extracted first key information. And if it is determined that the first key information corresponds to the saved service providing identifier, it is determined that the corresponding payment credential is in the first state. The second state represents that the automatic ticket return service is not provided; since the automatic ticket return service is not provided, the corresponding ticket credential has not been generated, and therefore the corresponding payment credential does not belong to the target payment credential to be matched.

[0061] Step S104-26, if the automatic ticket return service is not provided, the payment credential corresponding to the first key information including the participant information is determined as the second target payment credential;

[0062] Step S104-28, the first target payment credential and / or the second target payment credential are determined as the target payment credential.

[0063] It can be understood that when the obtained payment credentials include both the first target payment credential and the second target payment credential, the first target payment credential and the second target payment credential are determined as the target payment credential; when the obtained payment credentials include only one of the first target payment credential and the second target payment credential, the included first target payment credential or second target payment credential is determined as the target payment credential.

[0064] Since the payment credential corresponding to the automatic ticket return service and the ticket credential have a natural association, the target payment credential can be divided and matched according to the corresponding matching mode.

[0065] Specifically, when the target credential includes the first target payment credential, such as Figure 5As shown, step S104-4 can include the following steps S104-4-2 to S104-4-6:

[0066] Step S104-4-2, obtaining the payment credential identifier from the first key information of the first target payment credential;

[0067] Step S104-4-4, performing matching processing on the obtained payment credential identifier and the payment credential identifier corresponding to the saved second key information;

[0068] Step S104-4-6, if the payment credential identifier matching is successful, determining that the first target payment credential corresponding to the payment credential identifier matches the ticket credential corresponding to the second key information.

[0069] In particular, in the scenario of reimbursement, when the user to be processed does not bind the reimbursement code, since the first target payment credential can include the payment credential of the user to be processed for private consumption, the payment credential is not within the reimbursement range. Furthermore, when the user to be processed binds the reimbursement code, considering that the institution information of the institution to which the user to be processed belongs in the ticket credential can be incorrect. Based on this, in one or more embodiments of the present specification, step S104-4-4 can include:

[0070] If the payment credential identifier matching is successful, and the institution information in the second key information that matches successfully is the institution information associated with the user to be processed, it is determined that the first target payment credential corresponding to the payment credential identifier matches the ticket credential corresponding to the second key information. Wherein, determining that the institution information in the second key information that matches successfully is the institution information associated with the user to be processed includes: when the user to be processed binds the reimbursement code, obtaining the institution information associated with the reimbursement code, determining whether the obtained institution information is consistent with the institution information in the second key information that matches successfully, if consistent, determining that the institution information in the second key information that matches successfully is the institution information associated with the user to be processed. When the user to be processed does not bind the reimbursement code, obtaining the institution information associated with the saved institution information according to the user information of the user to be processed, determining whether the obtained institution information is consistent with the institution information in the second key information that matches successfully, if consistent, determining that the institution information in the second key information that matches successfully is the institution information associated with the user to be processed.

[0071] Therefore, based on the matching of the payment credential identifier, the matching of the first target payment credential and the ticket credential is realized.

[0072] Further, when the target credential includes a second target payment credential, as Figure 5 As shown, step S104-4 can include the following steps S104-4-8 to S104-4-16:

[0073] Step S104-4-8, obtaining the preset first to-be-matched information from the first key information of the second target payment voucher;

[0074] The first to-be-matched information can include a payment amount, participant information of a transaction participant corresponding to a payment operation, and the like.

[0075] Step S104-4-10, determining a target invoice voucher to be matched in the obtained invoice vouchers according to a payment time in the first key information and a generation time of the invoice voucher in the second key information.

[0076] It is considered that in the obtained invoice vouchers, the time span between the earliest generated invoice voucher and the latest generated invoice voucher can be large, for example, 10 days, and usually, a user will apply for a corresponding invoice voucher within 3 days or 5 days after a payment is successful when the user needs to perform reimbursement. Based on this, in order to improve the matching rate, in one or more embodiments of the present specification, the target invoice voucher to be matched is determined based on a first preset time length, and the first preset time length can be set as needed in actual application, such as 5 days. Specifically, step S104-4-10 can include: determining a first time period according to the payment time and the first preset time length; performing matching processing on the generation time in the second key information and the first time period to obtain a target generation time located in the first time period; and determining the invoice voucher corresponding to the second key information including the target generation time as the target invoice voucher to be matched.

[0077] Step S104-4-12, obtaining the preset second to-be-matched information from the second key information of the target invoice voucher;

[0078] The second to-be-matched information can include a payment amount, invoice issuer information, and the like, and the invoice issuer information is participant information of a transaction participant corresponding to a payment operation, such as a merchant name.

[0079] Step S104-4-14, performing matching processing on the first to-be-matched information and the second to-be-matched information to obtain a similarity of the first to-be-matched information and the second to-be-matched information.

[0080] The specific process of the matching processing can be set as needed in actual application, and the present specification does not make a specific limitation on this.

[0081] Step S104-4-16, if the similarity is not less than a preset similarity threshold, determining that the second target payment voucher and the target invoice voucher are matched successfully.

[0082] The similarity threshold value can be set and adjusted as needed in actual application. For example, when complete matching is required between the to-be-matched information, the similarity threshold value can be set to 1, when a certain error is allowed, the similarity threshold value can be set to 0.8, and the like.

[0083] In particular, in the reimbursement scenario, when the to-be-processed user is not bound to the reimbursement code, since the second target payment voucher can include the payment voucher of the private consumption of the to-be-processed user, and the target ticket voucher can include the ticket voucher that does not include the institution information of the institution to which the to-be-processed user belongs, in order to improve the reimbursement accuracy, in one or more embodiments of the present specification, the step S104-4-12 can include: obtaining the preset second to-be-matched information and the institution information from the second key information of the target ticket voucher. Correspondingly, the step S104-4-16 can include: if the similarity is greater than the preset similarity, and it is determined that the obtained institution information is the institution information associated with the to-be-processed user, it is determined that the second target payment voucher and the target ticket voucher are matched successfully.

[0084] Thus, based on the preset to-be-matched information, the matching of the second target payment voucher and the ticket voucher is realized.

[0085] It is considered that in actual application, the ticket voucher is usually generated at a certain time after the payment voucher is generated. Therefore, in the currently obtained payment voucher, there can be a payment voucher that is not matched successfully. In order to facilitate the management of the payment voucher, and in the next processing process, the payment voucher that is not matched successfully participates in the matching again. In addition, in the matching process, for the ticket voucher that is matched successfully, it does not participate in the matching of other payment vouchers, so as to improve the matching efficiency. In one or more embodiments of the present specification, the method can further include:

[0086] If it is determined that the matching processing is successful, the state information representing the associated state is saved in correspondence with the first key information and the second key information that are matched successfully, respectively.

[0087] Further, since there can be a payment voucher that is not matched successfully, the foregoing step S104-28 can include:

[0088] The first key information of each payment voucher currently obtained is determined as the current first key information, and the first key information of each payment voucher previously obtained is determined as the historical first key information. It is determined whether there is target key information in the historical first key information that is in the unassociated state. If yes, the payment voucher corresponding to the target key information is determined as the third target payment voucher, and the third target payment voucher, the first target payment voucher, and / or the second target payment voucher are determined as the target payment voucher. If no, the first target payment voucher and / or the second target payment voucher are determined as the target payment voucher.

[0089] In consideration of the fact that the institution to which the user to be processed belongs to may change its rules so that some ticket vouchers for business expenses cannot be reimbursed, and the fact that when the user to be processed is not bound to a reimbursement code, there may be payment vouchers for private expenses. Such historical payment vouchers in the unassociated state may reduce the matching efficiency if they are involved in the matching process multiple times. Based on this, in one or more embodiments of the present specification, the payment voucher corresponding to the target key information can be determined as the third target payment voucher, which can include:

[0090] According to the current time and the second preset time length, a second time period is determined; the payment time in the target key information is matched with the second time period to obtain the target payment time within the second time period; and the payment voucher corresponding to the target key information including the target payment time is determined as the third target payment voucher.

[0091] Further, when the target voucher includes the third target payment voucher, the step S104-4 further includes: matching the historical first key information and the second key information of the third target payment voucher according to a preset matching rule. The process of matching the historical first key information and the second key information is the same as the process of matching the first key information and the second key information, which can be referred to the foregoing description, and repeated description is omitted here.

[0092] Since the generation time of the ticket voucher can be later than the acquisition time of the payment voucher, multiple matching processes are performed on the payment voucher in the unmatching successful state, which greatly ensures the matching success rate of the acquired ticket vouchers.

[0093] Further, in order to ensure the accuracy of the established association relationship and to enable the institution to which the user to be processed belongs to conveniently perform the reimbursement and the like, in one or more embodiments of the present specification, as shown in Figure 6 After the step S106, the following steps S108 to S112 can be further included:

[0094] In step S108, if a query request sent by the payment application of the user to be processed is received, the association relationship is sent to the payment application so that the payment application displays the association relationship.

[0095] In step S110, if confirmation information sent by the payment application based on the confirmation operation of the user to be processed is received, the institution to which the user to be processed belongs to is determined.

[0096] In step S112, the target payment voucher matched successfully, the ticket voucher matched successfully, and the association relationship are sent to the determined institution so that the institution performs the related processing according to the received target payment voucher, ticket voucher, and association relationship.

[0097] For example, an institution performs a reimbursement process according to a received target payment credential, a bill credential, and an association relationship. It should be noted that the method for processing an electronic credential provided in the embodiments of the present specification is not limited to application in a reimbursement scenario, but can also be applied to other bill processing scenarios that require proof of the credibility of a bill credential.

[0098] In one or more embodiments of the present specification, by performing matching processing on a payment credential generated by performing a payment process based on a payment application and a bill credential, and establishing an association relationship for the payment credential and the bill credential that match successfully, since the payment credential is unforgeable by a user and has credibility, the credibility of the associated bill credential can be proved by the corresponding payment credential of the association relationship, thereby achieving proof of the authenticity of the bill credential. For a reimbursement scenario, not only can the relevant auditors be provided with a credible verification basis, thereby reducing the workload of the auditors for verifying the authenticity of the bill and improving the efficiency of the reimbursement; but also avoiding the adverse effects on the enterprise and the relevant personnel caused by the existence of false bill credentials.

[0099] Corresponding to the above-described method for processing an electronic credential, based on the same technical concept, one or more embodiments of the present specification also provide a processing device for an electronic credential. Figure 7 A schematic diagram of the module composition of the processing device for an electronic credential provided in one or more embodiments of the present specification is shown in Figure 7 As shown in the figure, the device includes:

[0100] The acquisition module 201 acquires a payment credential and a bill credential of a user to be processed; the payment credential is a trusted credential generated by a payment operation of the user to be processed through a payment application;

[0101] The determination module 202 determines a target payment credential to be matched in the payment credential;

[0102] The matching module 203 performs matching processing on the target payment credential and the bill credential according to a preset matching rule;

[0103] The association module 204 establishes an association relationship for the target payment credential and the bill credential that match successfully; the target payment credential corresponding to the association relationship is used to prove the credibility of the associated bill credential.

[0104] Optionally, the device further includes an extraction module.

[0105] The extraction module performs information extraction processing on each payment credential and each bill credential acquired according to a preset mode, to obtain corresponding first key information and second key information;

[0106] The determining module determines a target payment instrument to be matched in the payment instruments according to the first key information;

[0107] The matching module matches the first key information and the second key information of the target payment instrument according to a preset matching rule.

[0108] Optionally, the apparatus further comprises a saving module;

[0109] The saving module saves the first key information and the second key information, and if it is determined that the bill instrument is associated with the payment instrument, determines a payment instrument identifier of the associated payment instrument, and saves the payment instrument identifier in correspondence with the corresponding second key information.

[0110] The determining module determines whether the transaction participant provides an automatic return service according to the participant information in each first key information;

[0111] If the automatic return service is provided and it is determined according to the saved information that the payment instrument corresponding to the first key information including the participant information is in a first state, the payment instrument in the first state is determined as a first target payment instrument; wherein the first state represents that the automatic return service has been provided based on the payment instrument.

[0112] If the automatic return service is not provided, the payment instrument corresponding to the first key information including the participant information is determined as a second target payment instrument.

[0113] The first target payment instrument and / or the second target payment instrument are determined as the target payment instrument.

[0114] Optionally, the determining module determines the first key information of each payment instrument currently acquired as current first key information, and determines the first key information of each payment instrument previously acquired as historical first key information.

[0115] It is determined whether there is target key information in the historical first key information in an unassociated state.

[0116] If yes, the payment instrument corresponding to the target key information is determined as a third target payment instrument, and the third target payment instrument, the first target payment instrument and / or the second target payment instrument are determined as the target payment instrument.

[0117] If no, the first target payment instrument and / or the second target payment instrument are determined as the target payment instrument.

[0118] The processing device of the electronic voucher provided by one or more embodiments of the present specification can prove the authenticity of the associated ticket voucher through the corresponding payment voucher of the association relationship, because the payment voucher is tamper-proof and has credibility, and thus the authenticity of the ticket voucher is proved. For the reimbursement scenario, not only can the relevant auditors provide a reliable check basis, reducing the workload of the auditors for the ticket voucher verification, and improving the reimbursement efficiency; but also avoids the adverse effects on the enterprise and the relevant personnel caused by the existence of false ticket vouchers.

[0119] It should be noted that the embodiments of the processing device of the electronic voucher in the present specification are based on the same inventive concept as the embodiments of the processing method of the electronic voucher in the present specification, and therefore the specific implementation of the embodiments can refer to the foregoing implementation of the corresponding processing method of the electronic voucher, and the repeated parts will not be described again.

[0120] Further, corresponding to the above-described processing method of the electronic voucher, based on the same technical concept, one or more embodiments of the present specification also provide an electronic voucher processing device, which is used to execute the above-mentioned processing method of the electronic voucher, Figure 8 A structural schematic diagram of an electronic voucher processing device provided by one or more embodiments of the present specification.

[0121] As Figure 8 shown, the electronic voucher processing device can have a large difference due to different configurations or performances, and can include one or more processors 301 and memories 302, and one or more storage applications or data can be stored in the memories 302. The memory 302 can be temporary storage or persistent storage. The application stored in the memory 302 can include one or more modules (not shown in the figure), and each module can include a series of computer executable instructions in the electronic voucher processing device. Further, the processor 301 can be configured to communicate with the memory 302, and execute a series of computer executable instructions in the memory 302 on the electronic voucher processing device. The electronic voucher processing device can also include one or more power supplies 303, one or more wired or wireless network interfaces 304, one or more input and output interfaces 305, one or more keyboards 306, etc.

[0122] In one specific embodiment, the processing device of the electronic voucher includes a memory and one or more programs, wherein one or more programs are stored in the memory, and one or more programs can include one or more modules, and each module can include a series of computer executable instructions in the processing device of the electronic voucher, and the one or more programs configured to be executed by one or more processors include computer executable instructions for:

[0123] obtaining payment credentials and ticket credentials of a user to be processed; the payment credentials are trusted credentials generated by the user through a payment application for a payment operation;

[0124] determining target payment credentials to be matched in the payment credentials, and performing matching processing on the target payment credentials and the ticket credentials according to a preset matching rule;

[0125] establishing an association relationship between the target payment credentials and the ticket credentials that are successfully matched; the target payment credentials corresponding to the association relationship are used to prove that the associated ticket credentials are trusted.

[0126] Optionally, the computer executable instructions, when executed, further include, after the obtaining of the payment credentials and the ticket credentials of the user to be processed:

[0127] performing information extraction processing on the payment credentials and the ticket credentials according to a preset mode, to obtain corresponding first key information and second key information;

[0128] The determining of the target payment credentials to be matched in the payment credentials, and the performing of the matching processing on the target payment credentials and the ticket credentials according to the preset matching rule, includes:

[0129] determining the target payment credentials to be matched in the payment credentials according to the first key information, and performing matching processing on the first key information and the second key information of the target payment credentials according to the preset matching rule.

[0130] Optionally, the computer executable instructions, when executed, the first key information includes: payment credential identification of the payment credentials and participant information of a transaction participant corresponding to the payment operation;

[0131] After the obtaining of the corresponding first key information and second key information, further includes:

[0132] saving the first key information and the second key information; and if it is determined that the ticket credentials exist associated payment credentials, determining payment credential identification of the associated payment credentials, and saving the payment credential identification and the corresponding second key information;

[0133] determining the target payment instrument to be matched in the payment instruments according to the first key information comprises:

[0134] determining whether the transaction participant provides an automatic return ticket service according to the participant information in each of the first key information;

[0135] if the automatic return ticket service is provided and it is determined according to the saved information that the payment instrument corresponding to the first key information including the participant information is in a first state, determining the payment instrument in the first state as a first target payment instrument; wherein the first state represents that the automatic return ticket service has been provided based on the payment instrument;

[0136] if the automatic return ticket service is not provided, determining the payment instrument corresponding to the first key information including the participant information as a second target payment instrument;

[0137] determining the first target payment instrument and / or the second target payment instrument as the target payment instrument.

[0138] Optionally, the computer executable instructions, when executed, the determining the first target payment instrument and / or the second target payment instrument as the target payment instrument comprises:

[0139] determining the first key information of each payment instrument currently acquired as current first key information and the first key information of each payment instrument previously acquired as historical first key information;

[0140] determining whether there is target key information in the historical first key information in an unassociated state;

[0141] if yes, determining the payment instrument corresponding to the target key information as a third target payment instrument and determining the third target payment instrument, the first target payment instrument and / or the second target payment instrument as the target payment instrument;

[0142] if no, determining the first target payment instrument and / or the second target payment instrument as the target payment instrument.

[0143] The processing device of the electronic voucher provided by one or more embodiments of the present specification can prove the credibility of the associated ticket voucher through the corresponding payment voucher of the association relationship, because the payment voucher is tamper-proof and has credibility, thereby realizing the evidence of the authenticity of the ticket voucher. For the reimbursement scenario, not only can it provide the relevant auditors with a reliable check basis, reducing the workload of the auditors for checking the authenticity of the ticket voucher and improving the reimbursement efficiency, but also avoiding the adverse effects on the enterprise and the relevant personnel caused by the existence of false ticket vouchers.

[0144] It should be noted that the embodiments of the processing device of the electronic voucher in the present specification are based on the same inventive concept as the embodiments of the processing method of the electronic voucher in the present specification, and therefore the specific implementation of the embodiments can refer to the foregoing implementation of the corresponding processing method of the electronic voucher, and the repeated parts will not be described again.

[0145] Further, corresponding to the above-described processing method of the electronic voucher, based on the same technical concept, one or more embodiments of the present specification also provide a storage medium for storing computer executable instructions, in one specific embodiment, the storage medium can be a U disk, an optical disk, a hard disk, etc. The computer executable instructions stored in the storage medium can implement the following processes when executed by a processor:

[0146] Obtaining the payment voucher and the ticket voucher of the user to be processed; the payment voucher is a trusted voucher generated by the payment operation of the user to be processed through the payment application;

[0147] Determining the target payment voucher to be matched in the payment voucher, and performing matching processing on the target payment voucher and the ticket voucher according to a preset matching rule;

[0148] Establishing an association relationship between the target payment voucher and the ticket voucher that match successfully; the target payment voucher corresponding to the association relationship is used to prove that the associated ticket voucher is credible.

[0149] Optionally, the computer executable instructions stored in the storage medium, when executed by the processor, further comprise, after obtaining the payment voucher and the ticket voucher of the user to be processed:

[0150] According to a preset mode, the payment voucher and the ticket voucher are subjected to information extraction processing to obtain corresponding first key information and second key information;

[0151] The determination of the target payment voucher to be matched in the payment voucher, and the matching processing of the target payment voucher and the ticket voucher according to a preset matching rule, comprises:

[0152] determining a target payment instrument to be matched in the payment instruments according to the first key information, and performing matching processing on the first key information and the second key information of the target payment instrument according to a preset matching rule.

[0153] Optionally, the computer executable instructions stored in the storage medium, when executed by the processor, the first key information includes: payment instrument identification of the payment instrument and participant information of a transaction participant corresponding to the payment operation;

[0154] After the corresponding first key information and second key information are obtained, the method further includes:

[0155] saving the first key information and the second key information, and if it is determined that the bill instrument has an associated payment instrument, determining payment instrument identification of the associated payment instrument, and saving the payment instrument identification and the corresponding second key information;

[0156] The determining a target payment instrument to be matched in the payment instruments according to the first key information includes:

[0157] determining whether the transaction participant provides an automatic return service according to the participant information in each of the first key information;

[0158] if the automatic return service is provided and it is determined according to the saved information that the payment instrument corresponding to the first key information including the participant information is in a first state, determining the payment instrument in the first state as a first target payment instrument; wherein the first state represents that the automatic return service has been provided based on the payment instrument;

[0159] if the automatic return service is not provided, determining the payment instrument corresponding to the first key information including the participant information as a second target payment instrument;

[0160] determining the first target payment instrument and / or the second target payment instrument as the target payment instrument.

[0161] Optionally, the computer executable instructions stored in the storage medium, when executed by the processor, the determining the first target payment instrument and / or the second target payment instrument as the target payment instrument includes:

[0162] determining the first key information of each payment instrument currently acquired as current first key information, and determining the first key information of each payment instrument previously acquired as historical first key information;

[0163] determine whether the target key information in the historical first key information is in an unassociated state;

[0164] If yes, determine the payment credential corresponding to the target key information as a third target payment credential, and determine the third target payment credential, the first target payment credential and / or the second target payment credential as the target payment credential.

[0165] If no, determine the first target payment credential and / or the second target payment credential as the target payment credential.

[0166] The storage medium storing the computer executable instructions provided by one or more embodiments of the present specification, when executed by a processor, can prove the credibility of the associated ticket credential through the corresponding payment credential of the association relationship by matching the payment credential generated based on the payment application with the ticket credential and establishing an association relationship for the payment credential and the ticket credential that match successfully, since the payment credential is tamper-proof and has credibility. Therefore, the authenticity of the ticket credential is evidenced. For the reimbursement scenario, not only can the relevant auditors provide credible verification basis, reduce the workload of the auditors for verifying the authenticity of the ticket credential, and improve the reimbursement efficiency, but also avoid the adverse effects on the enterprise and the relevant personnel caused by the existence of false ticket credentials.

[0167] It should be noted that the embodiments of the storage medium in the present specification and the embodiments of the processing method of the electronic credential in the present specification are based on the same inventive concept, and therefore the specific implementation of this embodiment can refer to the foregoing implementation of the corresponding processing method of the electronic credential, and the repeated parts will not be described again.

[0168] The above describes specific embodiments of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be executed in an order different than the order in the embodiments and still achieve the desired result. In addition, the processes depicted in the figures do not necessarily require the particular order shown or sequential order to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous or possible.

[0169] In the 1990s, it was quite obvious to distinguish whether an improvement in a technology was in hardware (e.g., improvement in circuit structures of diodes, transistors, switches, etc.) or in software (improvement in method flow). However, as technology has evolved, many improvements in method flow today can be considered as direct improvements in hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structures by programming the improved method flow into hardware circuits. Therefore, it cannot be said that an improvement in a method flow cannot be implemented by hardware entity modules. For example, a programmable logic device (PLD) (e.g., a field programmable gate array (FPGA)) is an integrated circuit whose logic function is determined by user programming of the device. A digital system is "integrated" on a PLD by the designer programming it, rather than by asking a chip manufacturer to design and fabricate a custom integrated circuit chip. Moreover, instead of manually fabricating integrated circuit chips, this programming is now mostly implemented by "logic compiler" software, which is similar to software compilers used in program development, and the original code to be compiled is written in a specific programming language, which is called a hardware description language (HDL), and there are many such languages, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., and the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should be aware that, as long as the method flow is logically programmed in the above-mentioned hardware description languages and programmed into an integrated circuit, a hardware circuit implementing the logical method flow can be easily obtained.

[0170] The controller can be implemented in any suitable way, e.g. the controller can take the form of a microprocessor or processor and a computer readable medium storing computer readable program code, e.g. software or firmware, executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller and an embedded microcontroller, examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91 SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also know that in addition to being implemented in pure computer readable program code form, the controller can perfectly well be implemented by means of logic programmed into logic gates, switches, application specific integrated circuits, programmable logic controllers and embedded microcontrollers, etc. to perform the same functions. The controller can thus be considered a hardware component, and the means comprised therein for performing various functions can be considered structures within the hardware component. Alternatively, or even additionally, the means for performing various functions can be considered both software modules implementing the method and structures within the hardware component.

[0171] The systems, apparatuses, modules or units illustrated by the above embodiments can be implemented by computer chips or entities, or products with certain functions. A typical implementation device is a computer. Specifically, the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0172] For the sake of description, the above apparatuses are described in various units by functions respectively. Of course, the functions of each unit can be implemented in the same or multiple software and / or hardware in the implementation of the embodiments of the present specification.

[0173] Those skilled in the art will appreciate that one or more embodiments of the present specification can be provided as a method, a system or a computer program product. Therefore, one or more embodiments of the present specification can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present specification can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROMs, optical storage devices, etc.) containing computer usable program code.

[0174] The specification is presented with reference to flow diagrams and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the specification. It will be understood that each block of the flow diagrams and / or block diagrams, and combinations of blocks in the flow diagrams and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processing element or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flow diagrams and / or block diagrams block or blocks. Figure 1 The flow diagrams and / or block diagrams in the specification can present a method, apparatus or computer program product according to embodiments of the specification. Although the flow diagrams and / or block diagrams can present a method, apparatus or computer program product in a particular, it is understood that the method, apparatus and computer program product can include one or more additional steps, operations, or functions, and the method, apparatus and computer program product can include fewer than all of the steps, operations, or functions shown in the figures. Additionally, the steps, operations, or functions need not be implemented in the order shown in the figures. Further, the steps, operations, or functions can be implemented using additional or different steps, operations, or functions. Figure 1 These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the function specified in the flow diagrams and / or block diagrams block or blocks.

[0175] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flow diagrams and / or block diagrams block or blocks. Figure 1 The flow diagrams and / or block diagrams in the specification can present a method, apparatus or computer program product according to embodiments of the specification. Although the flow diagrams and / or block diagrams can present a method, apparatus or computer program product in a particular, it is understood that the method, apparatus and computer program product can include one or more additional steps, operations, or functions, and the method, apparatus and computer program product can include fewer than all of the steps, operations, or functions shown in the figures. Additionally, the steps, operations, or functions need not be implemented in the order shown in the figures. Further, the steps, operations, or functions can be implemented using additional or different steps, operations, or functions. Figure 1 These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the function specified in the flow diagrams and / or block diagrams block or blocks.

[0176] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flow diagrams and / or block diagrams block or blocks. Figure 1 The flow diagrams and / or block diagrams in the specification can present a method, apparatus or computer program product according to embodiments of the specification. Although the flow diagrams and / or block diagrams can present a method, apparatus or computer program product in a particular, it is understood that the method, apparatus and computer program product can include one or more additional steps, operations, or functions, and the method, apparatus and computer program product can include fewer than all of the steps, operations, or functions shown in the figures. Additionally, the steps, operations, or functions need not be implemented in the order shown in the figures. Further, the steps, operations, or functions can be implemented using additional or different steps, operations, or functions. Figure 1 These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the function specified in the flow diagrams and / or block diagrams block or blocks.

[0177] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0178] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) and / or cache memory, non-volatile memory, such as read-only memory (ROM), EPROM, and / or flash memory, etc. The memory is an example of computer-readable media.

[0179] Computer-readable media includes permanent and non-permanent, movable and non-movable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to a computing device. According to the definition herein, computer-readable media does not include transitory media such as modulated data signals and carriers.

[0180] It should also be noted that the terms "comprising", "containing", or any other variant thereof are intended to cover non-exclusive inclusion, such that processes, methods, articles or devices that include a series of elements not only include those elements, but also include other elements not explicitly listed or inherent to such processes, methods, articles or devices. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article or device that includes the element.

[0181] One or more embodiments of the present specification can be described in the general context of computer-executable instructions being executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types. One or more embodiments of the present specification can also be practiced in a distributed computing environment, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media, including storage devices.

[0182] Each embodiment in the present specification is described in a progressive manner, and the same or similar parts between each embodiment can be referred to each other, and each embodiment focuses on the difference from other embodiments. In particular, for system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and the relevant parts can be referred to the part of the method embodiment.

[0183] The above merely provides the example of the present document and is not intended to limit the present document. For those skilled in the art, the present document can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present document shall be included in the scope of claims of the present document.

Claims

1. A method for processing electronic vouchers, comprising: obtaining payment vouchers and ticket vouchers of a user to be processed; performing information extraction processing on the payment vouchers and the ticket vouchers according to a preset mode to obtain corresponding first key information and second key information; the first key information comprises a payment voucher identifier of the payment voucher and participant information of a transaction participant corresponding to a payment operation; determining whether the transaction participant provides an automatic ticket return service according to the participant information in each first key information; if the automatic ticket return service is provided and it is determined according to saved information that the payment voucher corresponding to the first key information comprising the participant information is in a first state, determining the payment voucher in the first state as a first target payment voucher, determining the first target payment voucher as a target payment voucher, and performing matching processing on the first key information of the target payment voucher and the second key information according to a preset matching rule; establishing an association relationship according to the first key information of the target payment voucher and the second key information of the ticket voucher matched successfully; the target payment voucher corresponding to the association relationship is used to prove that the associated ticket voucher is authentic.

2. The method of claim 1, wherein the payment voucher of the user to be processed is a trusted voucher generated by the user to be processed through a payment application when performing a payment operation; when the user to be processed performs a payment operation, payment is made based on a reimbursement code bound to the payment application.

3. The method of claim 1, wherein the obtaining of the payment voucher of the user to be processed comprises: according to the determined user information of the user to be processed and the reimbursement code bound to the user to be processed, obtaining, at a preset first time interval, each payment voucher associated and generated within a corresponding first time interval from a designated payment voucher library; or according to the determined user information of the user to be processed, obtaining, at a preset second time interval, each payment voucher associated and generated within a corresponding second time interval from a designated payment voucher library; or if a generation prompt information of a payment voucher is obtained from a payment application or a payment server corresponding to the payment application, obtaining a corresponding payment voucher from a designated payment voucher library according to the generation prompt information.

4. The method of claim 1, wherein the obtaining of the ticket voucher of the user to be processed comprises: receiving a ticket voucher sent by a transaction participant corresponding to the payment operation; or obtaining a ticket voucher from a designated third-party ticket agency, wherein the obtained ticket voucher comprises the ticket voucher of the user to be processed; or receiving a ticket voucher sent by the user to be processed.

5. The method of claim 1, wherein the first state represents that the automatic ticket return service has been provided based on a payment voucher; and after the obtaining of the corresponding first key information and second key information, the method further comprises: saving the corresponding first key information and second key information; and if it is determined that the ticket voucher has an associated payment voucher, determining a payment voucher identifier of the associated payment voucher and saving the payment voucher identifier and the corresponding second key information. ​ ​ The method further comprises, after the step of determining whether the transaction participant provides the automatic ticket return service according to the participant information in each first key information: If the automatic ticket return service is not provided, determining a payment credential corresponding to the first key information including the participant information as a second target payment credential; Determining the first target payment credential and / or the second target payment credential as the target payment credential.

6. The method of claim 5, wherein the target payment credential comprises the first target payment credential. The matching processing of the first key information of the target payment credential and the second key information according to the preset matching rule comprises: Obtaining a payment credential identifier from the first key information of the first target payment credential; Matching the obtained payment credential identifier with a saved payment credential identifier corresponding to the second key information; If the payment credential identifiers match successfully, it is determined that the first target payment credential corresponding to the payment credential identifier matches the ticket credential corresponding to the second key information successfully.

7. The method of claim 6, wherein the corresponding first key information comprises a payment time of the payment operation, the second key information comprises a generation time of the ticket credential, and the target payment credential comprises the second target payment credential. The matching processing of the first key information of the target payment credential and the second key information according to the preset matching rule comprises: Obtaining preset first matching information from the first key information of the second target payment credential; Determining a target ticket credential to be matched in the ticket credential according to the payment time and the generation time in the first key information of the second target payment credential; Obtaining preset second matching information from the second key information of the target ticket credential; Matching the first matching information with the second matching information to obtain a similarity between the first matching information and the second matching information; If the similarity is not less than a preset similarity threshold, it is determined that the second target payment credential matches the target ticket credential successfully.

8. The method of claim 7, wherein the determining of the target ticket credential to be matched in the ticket credential according to the payment time and the generation time in the first key information of the second target payment credential comprises: Determining a first time period according to the payment time in the first key information of the second target payment credential and a first preset time length; Matching the generation time in the first key information of the second target payment credential with the first time period to obtain a target generation time within the first time period; Determining a ticket credential corresponding to the second key information including the target generation time as the target ticket credential to be matched.

9. The method of claim 5, wherein the determining of the first target payment credential and / or the second target payment credential as the target payment credential comprises: Determining current first key information of each payment credential as current first key information and determining previous first key information of each payment credential as historical first key information. determining whether the target key information in the historical first key information is in an unassociated state; if yes, determining a payment credential corresponding to the target key information as a third target payment credential, and determining the third target payment credential, the first target payment credential and / or the second target payment credential as the target payment credential; if no, determining the first target payment credential and / or the second target payment credential as the target payment credential.

10. The method of claim 9, the corresponding first key information further comprising: a payment time of the payment operation; the determining of the payment credential corresponding to the target key information as the third target payment credential comprises: determining a second time period according to a current time and a second preset time length; matching the payment time in the target key information with the second time period to obtain a target payment time within the second time period; determining the payment credential corresponding to the target key information including the target payment time as the third target payment credential.

11. The method of claim 9, wherein the target payment credential comprises the third target payment credential. the matching of the first key information and the second key information of the target payment credential according to the preset matching rule comprises: matching the historical first key information and the second key information of the third target payment credential according to the preset matching rule.

12. The method of claim 5, further comprising: if the matching is successful, saving state information representing an associated state corresponding to the matching successful first key information and second key information, respectively.

13. The method of claim 1, after the establishing of the association relationship according to the matching successful first key information of the target payment credential and the second key information of the bill credential, further comprising: if a query request sent by the payment application of the to-be-processed user is received, sending the association relationship to the payment application to enable the payment application to display the association relationship; if confirmation information sent by the payment application based on a confirmation operation of the to-be-processed user is received, determining an institution to which the to-be-processed user belongs; sending the matching successful target payment credential, the matching successful bill credential and the association relationship to the determined institution.

14. An electronic credential processing apparatus, comprising: an acquisition module configured to acquire a payment credential and a bill credential of a to-be-processed user; determining module, according to a preset mode, performing information extraction processing on the payment voucher and the ticket voucher to obtain corresponding first key information and second key information; the first key information includes payment voucher identification of the payment voucher and participant information of a transaction participant corresponding to a payment operation; whether the transaction participant provides an automatic ticket return service is determined according to the participant information in each first key information; if the automatic ticket return service is provided and it is determined according to saved information that the payment voucher corresponding to the first key information including the participant information is in a first state, the payment voucher in the first state is determined as a first target payment voucher, the first target payment voucher is determined as a target payment voucher, and matching processing is performed on the first key information of the target payment voucher and the second key information according to a preset matching rule; an association module, according to the first key information of the target payment voucher and the second key information of the ticket voucher matched successfully, establishing an association relationship; the target payment voucher corresponding to the association relationship is used to prove that the associated ticket voucher is authentic.

15. An electronic voucher processing device, comprising: a processor; and a memory arranged to store computer executable instructions that, when executed, cause the processor to: obtain payment vouchers and ticket vouchers of users to be processed; perform information extraction processing on the payment vouchers and the ticket vouchers according to a preset mode to obtain corresponding first key information and second key information; the first key information includes payment voucher identification of the payment voucher and participant information of a transaction participant corresponding to a payment operation; determine whether the transaction participant provides an automatic ticket return service according to the participant information in each first key information; if the automatic ticket return service is provided and it is determined according to saved information that the payment voucher corresponding to the first key information including the participant information is in a first state, the payment voucher in the first state is determined as a first target payment voucher, the first target payment voucher is determined as a target payment voucher, and matching processing is performed on the first key information of the target payment voucher and the second key information according to a preset matching rule; according to the first key information of the target payment voucher and the second key information of the ticket voucher matched successfully, establish an association relationship; the target payment voucher corresponding to the association relationship is used to prove that the associated ticket voucher is authentic.

16. A storage medium for storing computer executable instructions, the computer executable instructions, when executed by a processor, implement the following processes: obtain payment vouchers and ticket vouchers of users to be processed; perform information extraction processing on the payment vouchers and the ticket vouchers according to a preset mode to obtain corresponding first key information and second key information; the first key information includes payment voucher identification of the payment voucher and participant information of a transaction participant corresponding to a payment operation; determine whether the transaction participant provides an automatic ticket return service according to the participant information in each first key information; If the automatic ticket refund service is provided and it is determined according to the saved information that the payment credential corresponding to the first key information including the participant information is in a first state, the payment credential in the first state is determined as a first target payment credential, the first target payment credential is determined as a target payment credential, and the first key information of the target payment credential and the second key information are matched according to a preset matching rule; An association relationship is established according to the first key information of the target payment credential and the second key information of the ticket credential matched successfully; and the target payment credential corresponding to the association relationship is used to prove that the associated ticket credential is authentic.

Images