Aggregate payment page jump method, device, electronic device and storage medium

Abstract

The present disclosure relates to a method, device, electronic device and storage medium for jumping to an aggregate payment page. The method includes responding to a target payment terminal's code scanning instruction for a target aggregate code, decoding the aggregate code information sent by the target payment terminal, obtaining a target code parameter, the target code parameter including an application tag domain value of an application tag domain corresponding to at least one payment application, determining the corresponding target application tag domain value from the target code parameter based on the acquired target application tag domain corresponding to the target payment application, obtaining preset jump information or address information of a joint payment page based on the target application tag domain value, and sending it to the target payment terminal so that the target payment terminal jumps to the joint payment page. The embodiments of the present disclosure can be used to aggregate existing payment QR codes and self-contained payment QR codes in certain regions, thereby improving the versatility of existing aggregate codes, greatly increasing payment efficiency and collection efficiency, and improving transaction flexibility and convenience.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a method, device, electronic device and storage medium for aggregate payment page jump. Background Art

[0002] With the improvement of people's living standards and the acceleration of globalization, consumers' demand for aggregated payment is also growing. However, the payment QR codes in some regions are self-contained. How to integrate the commonly used international payment QR codes with the payment QR codes in these regions has become the focus of improving the payment experience.

[0003] In the related art, a single aggregated QR code can often be used to scan and pay using multiple payment software. However, in the related art, the various payment QR codes in certain regions are self-contained systems, and can only be used to scan and pay using their own payment software. It is impossible to aggregate the existing payment QR codes, resulting in the dispersion of payment resources, the low versatility of the existing aggregated codes, the low payment efficiency and the low collection efficiency, which in turn leads to low transaction flexibility and convenience. Summary of the invention

[0004] The present disclosure provides a method, device, electronic device and storage medium for jumping to an aggregated payment page, so as to at least solve the problems in the related art that the existing payment QR codes and the payment QR codes of certain regions that are independent of each other cannot be aggregated, resulting in the dispersion of payment resources, the low universality of the existing aggregated codes, the low payment efficiency and the low collection efficiency, and thus the low flexibility and convenience of transactions. The technical solution of the present disclosure is as follows:

[0005] According to a first aspect of an embodiment of the present disclosure, a method for jumping to an aggregated payment page is provided, including:

[0006] In response to a target payment terminal's code scanning instruction for a target aggregation code, receiving aggregation code information sent by the target payment terminal; the target aggregation code is a joint payment code corresponding to at least one payment application;

[0007] Decode the aggregation code information to obtain a target code parameter; the target code parameter includes an application tag domain value corresponding to the application tag domain of each of the at least one payment application; the preset application tag domain value corresponding to the preset payment application in the at least one payment application includes address information of the joint payment page corresponding to the at least one payment application, and the application tag domain value corresponding to each of the payment applications other than the preset payment application in the at least one payment application includes preset jump information, and the preset jump information is used for the target payment terminal to jump to the joint payment page;

[0008] Obtaining a target application tag field corresponding to a target payment application; the target payment application is any one of the at least one payment application;

[0009] Based on the target application tag domain, determine the target application tag domain value corresponding to the target payment application from the target code parameter;

[0010] Based on the target application tag domain value, the preset jump information or the address information of the joint payment page is obtained, and the preset jump information or the address information of the joint payment page is sent to the target payment terminal, so that the target payment terminal jumps to the joint payment page based on the preset jump information or the address information of the joint payment page.

[0011] In an optional embodiment, when the target application tag field value does not include the address information of the joint payment page, acquiring the preset jump information or the address information of the joint payment page based on the target application tag field value, and sending the preset jump information or the address information of the joint payment page to the target payment terminal includes:

[0012] Acquire the preset jump information based on the target application tag domain value, and send the preset jump information to the target payment terminal so that the target payment terminal jumps to a preset intermediate page;

[0013] In response to the address acquisition instruction triggered based on the preset intermediate page, the target code parameter is sent to the preset server corresponding to the preset intermediate page, so that the preset server parses the target code parameter, obtains the address information of the joint payment page, and sends it to the target payment terminal.

[0014] In an optional embodiment, when the target application tag field value includes the address information of the joint payment page, acquiring the preset jump information or the address information of the joint payment page based on the target application tag field value, and sending the preset jump information or the address information of the joint payment page to the target payment terminal includes:

[0015] The address information of the joint payment page is obtained based on the target application tag domain value, and the address information of the joint payment page is sent to the target payment terminal.

[0016] In an optional embodiment, the method further includes:

[0017] Receive an aggregation code generation request for the target payment application sent by the target account, obtain the target payment information and the target application label field corresponding to the target payment application, and send them to the aggregation server, so that the aggregation server generates the target application label field value based on the target payment information and the target application label field, and generates the target aggregation code based on at least one application label field value;

[0018] In the case where the at least one payment application is a plurality of payment applications, the at least one application tag domain value is a tag domain value corresponding to the plurality of payment applications;

[0019] In the case where the at least one payment application is one payment application, the at least one application tag domain value is the target application tag domain value.

[0020] In an optional embodiment, the method further includes:

[0021] In response to the authorization instruction triggered based on the joint payment page, the authorization request sent by the target payment terminal is received, the target payment application is authorized, and the target authorization code is obtained and sent to the target payment terminal, so that the target payment terminal performs payment processing based on the target authorization code.

[0022] In an optional embodiment, when the two-dimensional code type of the target aggregation code is a dynamic two-dimensional code, the dynamic two-dimensional code includes transaction information, and the method further includes:

[0023] Receiving a payment request sent by the target payment terminal, obtaining target transaction information corresponding to the target aggregation code, and sending the target transaction information to the target payment terminal;

[0024] receiving a payment request sent by the target payment terminal when a payment confirmation operation triggered based on the target transaction information is detected, performing payment processing, and obtaining a first payment confirmation result;

[0025] When the first payment confirmation result shows that the payment is successful, the address information of the preset payment success page is sent to the target payment terminal, so that the target payment terminal jumps to the payment success page.

[0026] In an optional embodiment, when the two-dimensional code type of the target aggregate code is a static two-dimensional code, the static two-dimensional code includes merchant information, and the method further includes:

[0027] Receive the payment request sent by the target payment terminal, obtain the target merchant information corresponding to the target aggregation code, and send the target merchant information to the target payment terminal;

[0028] receiving a payment request sent by the target payment terminal when detecting an amount input confirmation operation triggered by the target merchant information, performing payment processing, and obtaining a second payment confirmation result;

[0029] When the second payment confirmation result shows that the payment is successful, the address information of the preset payment success page is sent to the target payment terminal, so that the target payment terminal jumps to the payment success page.

[0030] According to a second aspect of an embodiment of the present disclosure, a device for jumping to an aggregated payment page is provided, including:

[0031] The aggregation code information receiving module is used to receive the aggregation code information sent by the target payment terminal in response to the target aggregation code scanning instruction of the target payment terminal; the target aggregation code is a joint payment code corresponding to at least one payment application;

[0032] a target code parameter acquisition module, configured to decode the aggregation code information to obtain a target code parameter; the target code parameter includes an application tag domain value of an application tag domain corresponding to each of the at least one payment application; a preset application tag domain value corresponding to a preset payment application in the at least one payment application includes address information of a joint payment page corresponding to the at least one payment application, and an application tag domain value corresponding to each of the payment applications other than the preset payment application in the at least one payment application includes preset jump information, and the preset jump information is used for the target payment terminal to jump to the joint payment page;

[0033] A target application label domain acquisition module, used to acquire a target application label domain corresponding to a target payment application; the target payment application is any one of the at least one payment application;

[0034] A target application tag domain value determination module, used to determine the target application tag domain value corresponding to the target payment application from the target code parameter based on the target application tag domain;

[0035] An information sending module is used to obtain the preset jump information or the address information of the joint payment page based on the target application tag domain value, and send the preset jump information or the address information of the joint payment page to the target payment terminal, so that the target payment terminal jumps to the joint payment page based on the preset jump information or the address information of the joint payment page.

[0036] In an optional embodiment, when the target application tag field value does not include the address information of the joint payment page, the information sending module includes:

[0037] A preset jump information sending unit, used for acquiring the preset jump information based on the target application tag domain value, and sending the preset jump information to the target payment terminal, so that the target payment terminal jumps to a preset intermediate page;

[0038] The target code parameter sending unit is used to respond to the address acquisition instruction triggered based on the preset intermediate page, and send the target code parameters to the preset server corresponding to the preset intermediate page, so that the preset server can parse the target code parameters, obtain the address information of the joint payment page, and send it to the target payment terminal.

[0039] In an optional embodiment, when the target application tag field value includes the address information of the joint payment page, the information sending module includes:

[0040] An address information sending unit is used to obtain the address information of the joint payment page based on the target application tag field value, and send the address information of the joint payment page to the target payment terminal.

[0041] In an optional embodiment, the device further comprises:

[0042] An acquisition module is used to receive an aggregation code generation request for the target payment application sent by a target account, obtain the target payment information and the target application label field corresponding to the target payment application, and send them to an aggregation server, so that the aggregation server generates the target application label field value based on the target payment information and the target application label field, and generates the target aggregation code based on at least one application label field value;

[0043] In the case where the at least one payment application is a plurality of payment applications, the at least one application tag domain value is a tag domain value corresponding to the plurality of payment applications;

[0044] In the case where the at least one payment application is one payment application, the at least one application tag domain value is the target application tag domain value.

[0045] In an optional embodiment, the device further comprises:

[0046] The authorization processing module is used to respond to the authorization instruction triggered based on the joint payment page, receive the authorization request sent by the target payment terminal, perform authorization processing on the target payment application, obtain the target authorization code and send it to the target payment terminal, so that the target payment terminal performs payment processing based on the target authorization code.

[0047] In an optional embodiment, when the two-dimensional code type of the target aggregation code is a dynamic two-dimensional code, the dynamic two-dimensional code includes transaction information, and the device further includes:

[0048] A target transaction information sending module, used to receive the payment request sent by the target payment terminal, obtain the target transaction information corresponding to the target aggregation code, and send the target transaction information to the target payment terminal;

[0049] A first payment confirmation result acquisition module is used to receive a payment request sent by the target payment terminal when a payment confirmation operation triggered by the target transaction information is detected, perform payment processing, and obtain a first payment confirmation result;

[0050] The first address information sending module is used to send the address information of a preset payment success page to the target payment terminal when the first payment confirmation result shows that the payment is successful, so that the target payment terminal jumps to the payment success page.

[0051] In an optional embodiment, when the two-dimensional code type of the target aggregate code is a static two-dimensional code, the static two-dimensional code includes merchant information, and the device further includes:

[0052] A target merchant information sending module, used to receive the payment request sent by the target payment terminal, obtain the target merchant information corresponding to the target aggregation code, and send the target merchant information to the target payment terminal;

[0053] A second payment confirmation result acquisition module is used to receive a payment request sent by the target payment terminal when detecting an amount input confirmation operation triggered by the target merchant information, perform payment processing, and obtain a second payment confirmation result;

[0054] The second address information sending module is used to send the address information of the preset payment success page to the target payment terminal when the second payment confirmation result shows that the payment is successful, so that the target payment terminal jumps to the payment success page.

[0055] According to a third aspect of an embodiment of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement a method as described in any one of the above-mentioned first aspects.

[0056] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute any method described in the first aspect of the embodiment of the present disclosure.

[0057] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:

[0058] Receive the aggregation code information sent by the target payment terminal in response to the scan code instruction for the target aggregation code, decode the aggregation code information, obtain the target code parameters including the application tag domain value of the application tag domain corresponding to at least one payment application, obtain the target application tag domain corresponding to the target payment application, the target payment application is any one of the at least one payment application, based on the target application tag domain, determine the target application tag domain value corresponding to the target payment application from the target code parameters, obtain the preset jump information or the address information of the joint payment page based on the target application tag domain value, send the preset jump information or the address information of the joint payment page to the target payment terminal, so that the target payment terminal jumps to the joint payment page based on the preset jump information or the address information of the joint payment page, and can aggregate the existing payment QR code and the self-contained payment QR code in some regions, thereby improving the versatility of the existing aggregation code, greatly increasing the payment efficiency and collection efficiency, and improving the flexibility and convenience of transactions.

[0059] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0061] Figure 1 is a schematic diagram of an application environment according to an exemplary embodiment;

[0062] Figure 2 is a flow chart of a method for jumping to an aggregated payment page according to an exemplary embodiment;

[0063] Figure 3 is a schematic diagram of target code parameter disassembly according to an exemplary embodiment;

[0064] Figure 4 is a flow chart of scanning a target aggregation code according to an exemplary embodiment;

[0065] Figure 5 is a block diagram of a device for jumping to an aggregated payment page according to an exemplary embodiment;

[0066] Figure 6 It is a block diagram of an electronic device for payment page jump according to an exemplary embodiment. DETAILED DESCRIPTION

[0067] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0068] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar different contents, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the attached claims.

[0069] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties.

[0070] See also Figure 1 , Figure 1 is a schematic diagram of an application environment according to an exemplary embodiment. Figure 1 As shown, the application environment may include a terminal 100, a target application server 200, a preset server 300 and an aggregation server 400. Specifically, the target application server 200 is a server deployed on the data processing system side of the target payment application, and the preset server 300 is a server deployed on the data processing system side of the third-party service provider.

[0071] In an optional embodiment, the terminal 100 can be used to provide payment services to users. Specifically, the terminal 100 can jump to the joint payment page based on the preset jump information sent by the target application server 200 or the address information of the joint payment page. The terminal 100 may include but is not limited to electronic devices such as smart phones, desktop computers, tablet computers, laptops, smart speakers, digital assistants, augmented reality (AR) / virtual reality (VR) devices, smart wearable devices, etc., and may also be software running on the above electronic devices, such as applications. Optionally, the operating system running on the electronic device may include but is not limited to Android system, IOS system, Linux, Windows, etc.

[0072] In an optional embodiment, the target application server 200 may provide background support for the terminal 100, and send information for jumping to the aggregation code page to the terminal 100. Optionally, the target application server 200 may decode the aggregation code information sent by the terminal 100 to obtain the target code parameters. Accordingly, the preset jump information or the address information of the joint payment page may be sent to the terminal 100 in combination with the target code parameters. The preset server 300 may be used to parse the target code parameters, obtain the address information of the joint payment page, and send it to the terminal 100. The aggregation server 400 generates the target application tag domain value in advance based on the target payment information and the target application tag domain corresponding to the target payment application, and generates the target aggregation code based on at least one application tag domain value. Specifically, the target application server 200, the preset server 300 and the aggregation server 400 can be independent physical servers, or a server cluster or distributed system composed of multiple physical servers. They can also be cloud servers that provide basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), as well as big data and artificial intelligence platforms.

[0073] In addition, it should be noted that Figure 1 What is shown is only one application environment provided by the present disclosure. In actual application, other application environments may also be included.

[0074] In the embodiments of this specification, the terminal 100 and the target application server 200, the preset server 300 and the aggregation server 400 may be directly or indirectly connected via wired or wireless communication, which is not limited in this disclosure.

[0075] Figure 2 is a flow chart of a method for redirecting an aggregated payment page according to an exemplary embodiment. Figure 2 As shown, the aggregate payment page jump method is used in the target application server and includes the following steps.

[0076] In step S201, in response to a scan code instruction of a target payment terminal for a target aggregation code, aggregation code information sent by the target payment terminal is received.

[0077] In a specific embodiment, the target payment terminal may be a device that has a target payment application installed for scanning code payment, the target aggregation code may be a joint payment code corresponding to at least one payment application, and the aggregation code information may be the QR code information contained in the target aggregation code obtained after the target payment terminal scans the target aggregation code.

[0078] In an optional embodiment, the above method may further include:

[0079] Receive an aggregation code generation request for a target payment application sent by a target account, obtain target payment information and a target application tag field corresponding to the target payment application, and send the target payment information and the target application tag field to an aggregation server, so that the aggregation server generates a target application tag field value based on the target payment information and the target application tag field, and generates a target aggregation code based on at least one application tag field value;

[0080] In the case where the at least one payment application is multiple payment applications, the at least one application tag domain value is a tag domain value corresponding to the multiple payment applications;

[0081] In the case where the at least one payment application is a payment application, the at least one application tag field value is a target application tag field value.

[0082] In a specific embodiment, the target payment application can be a software program used to handle various payment transaction activities, which can use the target payment terminal to realize the transfer and settlement of funds, etc. The target payment information can be the information required for the target payment application to participate in the generation of the target aggregation code, including target account (receiving account) information, target payment application access parameters, fixed transaction amount related information, order number generation rules, etc.

[0083] In a specific embodiment, the target application tag domain may be a tag domain corresponding to the target payment application. The tag domain may be an area or a field used to identify at least one payment-related parameter obtained according to set classification and identification rules. For example, the tag domain may be used to identify the currency type used in the transaction, the payment amount of the transaction (dynamic QR code), the type of payment method used (main scan or scanned), etc. The tag domain value refers to the specific content or value assigned to the tag domain. It is a specific value assigned to the tag domain according to the classification and identification rules set for the tag domain, so that the system can accurately execute corresponding business logic and data processing operations based on these specific values. For example, the tag domain may be a Tag domain, and the tag domain value may be the specific content or value assigned to the Tag domain.

[0084] Figure 3 is a schematic diagram of target code parameter disassembly according to an exemplary embodiment. Figure 3As shown, the target application tag domain may be Tag39, and based on the target payment information (application identifier information, acquirer identifier information, user main scan, address information of the joint payment page, etc.), the target application tag domain value 0016A900000000000000 0103240 0203CsB 0353https: / / app-h5.zhangsanpay-inc.com / s / sqr905913635ae79 0402110503 008 may be obtained, wherein the target application tag domain may include at least one sub-tag domain Tag00, Tag01, Tag02, Tag03, Tag04 and Tag05, specifically, it may include Tag00 (used to store application identifier (AID) information, clarifying the application associated with the payment operation), the corresponding Tag00 domain value may be A900000000000000, Tag01 (used to store acquirer identifier (Acquirer The corresponding Tag01 domain value can be 240, Tag02 (used to mark the usage type of the payment method (Usage Type), main scan or scanned), the corresponding Tag02 domain value can be CsB (user main scan), Tag03 (used to store information related to the specific value of the payment code, such as the address information of the joint payment page), the corresponding Tag03 domain value can be https: / / app-h5.zhangsanpay-inc.com / s / sqr905913635ae79, Tag04, the corresponding Tag04 domain value can be 11, Tag05 (used to store the information of the suffix identifier (Suffix ID) assigned by each payment application), the corresponding Tag05 domain value can be 008.

[0085] In the above embodiment, a target application tag domain value is generated based on the target payment information and the target application tag domain corresponding to the target payment application, and a target aggregation code is generated based on at least one application tag domain value. An aggregation code can be implemented to support users to choose multiple payment methods to complete payment without switching between different payment applications or methods, thereby improving user experience and payment efficiency. At the same time, for merchants, they only need to display one aggregation code to receive payments of multiple payment methods, without having to prepare payment collection devices for different payment channels or perform complicated reconciliation operations, thereby improving the merchant's collection efficiency.

[0086] In step S203, the aggregation code information is decoded to obtain target code parameters.

[0087] In a specific embodiment, the target code parameters may include the application tag domain value of the application tag domain corresponding to at least one payment application. Specifically, the preset application tag domain value corresponding to the preset payment application in the at least one payment application includes the address information of the joint payment page corresponding to the at least one payment application. The preset payment application is one of the at least one pre-selected payment applications. The application tag domain value corresponding to each payment application other than the preset payment application in the at least one payment application includes preset jump information, and the preset jump information is used for the target payment terminal to jump to the joint payment page.

[0088] In a specific embodiment, Figure 3 As shown, the target code parameters include at least one payment application, and the corresponding application tag domains may be Tag29, Tag39, and Tag49. For the application tag domain Tag29, the corresponding application tag domain value may be 0016A000000677010111 0213 1670500200598. For the application tag domain Tag39, the corresponding application tag domain value may be 0016A9000000000000000 0103 240 0203CsB 0353https: / / app-h5.zhangsanpay-inc.com / s / sqr905913635ae79 0402 11 0503 008. For the application tag domain Tag49, the corresponding application tag domain value may be 0017com.qq.WX.pay 0109 114475940. 0202JS, the preset application tag domain value corresponding to the preset payment application can be the application tag domain value corresponding to the application tag domain Tag39. Specifically, the sub-tag domain Tag03 in the application tag domain value corresponding to Tag39 may include the address information of the joint payment page corresponding to at least one payment application: https: / / app-h5.zhangsanpay-inc.com / s / sqr905913635ae79, and the sub-tag domain Tag00 in the application tag domain value corresponding to Tag49 may include the preset jump information for jumping to the joint payment page: com.qq.WX.pay.

[0089] In a specific embodiment, at least one payment application's corresponding application tag field may include at least one sub-tag field, and at least one sub-tag field has a corresponding sub-tag field value, such as Figure 3As shown, Tag39 may include sub-tag domains Tag00, Tag01, Tag02, Tag03, Tag04 and Tag05, and the corresponding sub-tag domain values ​​may be A9000000000000000, 240, CsB, https: / / app-h5.zhangsanpay-inc.com / s / sqr905913635ae79, 11 and 008, respectively.

[0090] In step S205, the target application tag field corresponding to the target payment application is obtained.

[0091] In a specific embodiment, the target payment application may be any one of the at least one payment application, and the target application tag field may be a tag field corresponding to the target payment application.

[0092] In step S207, based on the target application tag field, the target application tag field value corresponding to the target payment application is determined from the target code parameters.

[0093] In a specific embodiment, Figure 3 As shown, when the target application tag domain is Tag29, the target application tag domain value corresponding to the target payment application is 0016A000000677010111 0213 1670500200598.

[0094] In step S209, the preset jump information or the address information of the joint payment page is obtained based on the target application tag domain value, and the preset jump information or the address information of the joint payment page is sent to the target payment terminal, so that the target payment terminal jumps to the joint payment page based on the preset jump information or the address information of the joint payment page.

[0095] In a specific embodiment, the preset application tag domain value corresponding to the preset payment application includes the address information of the joint payment page, and the application tag domain value corresponding to each payment application other than the preset payment application includes preset jump information. Specifically, the preset jump information is used for the target payment terminal to jump to the joint payment page.

[0096] In an optional embodiment, when the target application tag field value does not include the address information of the joint payment page, the above-mentioned obtaining the preset jump information or the address information of the joint payment page based on the target application tag field value, and sending the preset jump information or the address information of the joint payment page to the target payment terminal includes:

[0097] Acquire preset jump information based on the target application tag domain value, and send the preset jump information to the target payment terminal so that the target payment terminal jumps to the preset intermediate page;

[0098] In response to the address acquisition instruction triggered by the preset intermediate page, the target code parameters are sent to the preset server corresponding to the preset intermediate page, so that the preset server parses the target code parameters, obtains the address information of the joint payment page, and sends it to the target payment terminal.

[0099] In a specific embodiment, the preset intermediate page can be a static page configured by a preset organization. For example, when the target application tag domain is Tag49, the target application tag domain value can be 0017com.qq.WX.pay 01091144759400202JS. Based on the preset jump information com.qq.WX.pay, the address information of the preset intermediate page can be obtained, and the address information of the preset intermediate page can be sent to the target payment terminal, so that the target payment terminal jumps to the preset intermediate page based on the address information of the preset intermediate page.

[0100] In a specific embodiment, the preset server can parse the target code parameter to obtain the address information of the joint payment page corresponding to at least one payment application in the preset application tag field value. Specifically, the preset server can parse the following: Figure 3 The target code parameters shown in the figure obtain the address information of the joint payment page in the preset application tag domain value corresponding to the preset application tag domain Tag39 corresponding to the preset payment application https: / / app-h5.zhangsanpay-inc.com / s / sqr905913635ae79, and send https: / / app-h5.zhangsanpay-inc.com / s / sqr905913635ae79 to the target payment terminal.

[0101] In the above embodiment, in the case where the target application tag domain value does not include the joint payment page address information, by jumping to the preset intermediate page and parsing the target code parameters, the address information of the joint payment page is obtained, which can adapt to various payment scenarios. For example, when a new payment application participates in the aggregation or the payment business rules change, it is only necessary to adjust the logic of parsing the target code parameters of the preset intermediate page without re-modifying the target application tag domain itself, thereby improving the adaptability of the target aggregation code, and all logic for parsing the target code parameters to obtain the joint payment page address information can be concentrated on the preset intermediate page for processing, greatly improving the convenience and efficiency of maintenance.

[0102] In an optional embodiment, when the target application tag field value includes the address information of the joint payment page, the above-mentioned obtaining the preset jump information or the address information of the joint payment page based on the target application tag field value, and sending the preset jump information or the address information of the joint payment page to the target payment terminal includes:

[0103] The address information of the joint payment page is obtained based on the target application tag domain value, and the address information of the joint payment page is sent to the target payment terminal.

[0104] In a specific embodiment, when the target application tag domain is a preset application tag domain, specifically, the target application tag domain can be the preset application tag domain Tag39, and the address information of the joint payment page https: / / app-h5.zhangsanpay-inc.com / s / sqr905913635ae79 can be directly obtained from the preset application tag domain value and sent to the target payment terminal.

[0105] In the above embodiment, when the target application tag domain value includes the address information of the joint payment page, that is, the target application tag domain is a preset application tag domain, the address information of the joint payment page is obtained directly from the corresponding preset application tag domain value, which can achieve rapid information acquisition and reduce processing links, making the entire process of obtaining the address information of the joint payment page more efficient and reducing system complexity.

[0106] In an optional embodiment, the above method may further include:

[0107] In response to the authorization instruction triggered based on the joint payment page, the authorization request sent by the target payment terminal is received, the target payment application is authorized, and the target authorization code is obtained and sent to the target payment terminal, so that the target payment terminal performs payment processing based on the target authorization code.

[0108] In a specific embodiment, the target authorization code can be an authorization code, which can be a one-time code returned by the target payment application to confirm the legitimacy of the payment transaction. For example, in the aggregate code payment scenario, when the user uses the target payment application to scan the code to jump to the joint payment page, the target payment application is authorized, and the target application server generates a target authorization code (such as auth_code) and returns it to the target payment application.

[0109] In a specific embodiment, the target payment terminal can obtain an access token (access_token) and a user identifier (user_id) based on the target authorization code, so as to carry out the subsequent payment process of creating a bill.

[0110] In the above embodiment, by performing authorization processing on the target payment application and returning the target authorization code of the target payment terminal, so that the target payment terminal performs payment processing based on the target authorization code, the security of payment can be enhanced. During the authorization processing, the information interaction between the target payment application and the target payment terminal will use encryption technology to ensure that the target authorization code and target payment information are not tampered with during the transmission process. If the information is tampered with, the target payment terminal will find an abnormality when verifying the authorization code, and thus refuse to pay, thereby ensuring the integrity and accuracy of the payment data.

[0111] In an optional embodiment, when the QR code type of the target aggregation code is a dynamic QR code, the dynamic QR code includes transaction information, and the above method may further include:

[0112] Receive the payment request sent by the target payment terminal, obtain the target transaction information corresponding to the target aggregation code, and send the target transaction information to the target payment terminal;

[0113] receiving a payment request sent by a target payment terminal when a payment confirmation operation triggered based on target transaction information is detected, performing payment processing, and obtaining a first payment confirmation result;

[0114] When the first payment confirmation result shows that the payment is successful, the address information of the preset payment success page is sent to the target payment terminal so that the target payment terminal jumps to the payment success page.

[0115] In a specific embodiment, the target transaction information may include information of both parties to the transaction, transaction amount, product information, payment method, etc. Specifically, the dynamic QR code is generated corresponding to a specific transaction amount, and the transaction amount in the target transaction information may be the specific amount of the transaction.

[0116] In a specific embodiment, the first payment confirmation result may be a payment processing result after the user confirms the payment. Specifically, it may be a payment confirmation page displayed by the user triggered by the target transaction information, and the payment processing result corresponding to the payment confirmation operation may be payment success or payment failure.

[0117] In the above embodiment, when the target aggregation code is a dynamic QR code, the payment confirmation page is triggered based on the target transaction information. When the first payment confirmation result shows that the payment is successful, the address information of the preset payment success page is sent to the target payment terminal so that the target payment terminal jumps to the payment success page. The payment progress can be clarified, unnecessary payment disputes or financial losses due to misoperation can be avoided, and the accuracy and security of the payment are guaranteed.

[0118] In an optional embodiment, when the QR code type of the target aggregate code is a static QR code, the static QR code includes merchant information, and the above method may further include:

[0119] Receive the payment request sent by the target payment terminal, obtain the target merchant information corresponding to the target aggregation code, and send the target merchant information to the target payment terminal;

[0120] receiving a payment request sent by a target payment terminal when an amount input confirmation operation triggered by target merchant information is detected, performing payment processing, and obtaining a second payment confirmation result;

[0121] When the second payment confirmation result shows that the payment is successful, the address information of the preset payment success page is sent to the target payment terminal so that the target payment terminal jumps to the payment success page.

[0122] In a specific embodiment, the target merchant information may be the payment account information corresponding to the static QR code. Specifically, the static QR code is generated corresponding to a specific payment account.

[0123] In a specific embodiment, the second payment confirmation result may be a payment processing result after the user enters the amount. Specifically, the user triggers the displayed amount input page through the target merchant information, and the corresponding payment processing result after the amount input operation is performed may be payment success or payment failure.

[0124] In the above embodiment, when the target aggregation code is a static QR code, based on the amount input page triggered by the target merchant information, when the second payment confirmation result shows that the payment is successful, the address information of the preset payment success page is sent to the target payment terminal, so that the target payment terminal jumps to the payment success page. The user can accurately enter the specific amount to be paid, avoiding the problem of payment amount mismatch caused by setting a fixed amount, and improving the accuracy and flexibility of payment.

[0125] Figure 4 is a flow chart of scanning a target aggregation code according to an exemplary embodiment. Figure 4As shown, a certain payment application is a payment system launched by a certain region's central bank. Its payment QR code is a self-contained system. By scanning the target aggregation code through a certain region's bank APP, the target code parameters can be decoded, and the corresponding label domain can be identified to directly jump to the transaction page to perform transaction confirmation operations or amount input operations. At this time, the target application label domain value corresponding to the target payment application can be a preset application label domain value. The user uses the target payment application to scan the target aggregation code. The target application server decodes the aggregation code information sent by the target payment terminal to obtain the target code parameters and sends it to the target payment terminal. The target payment terminal (target payment application) decodes the target code parameters to obtain the joint payment page address information in the preset application label domain value. The target payment terminal (target payment application) jumps to the joint payment page (aggregation code front end) based on the joint payment page address information, triggering the target application server to perform authorization processing. After the authorization processing is completed, the target authorization code is obtained and sent to the target payment terminal (aggregation code front end), so that the target payment terminal (aggregation code front end) performs payment processing based on the target authorization code.

[0126] It can be seen from the technical solutions provided by the above embodiments of this specification that this specification receives the aggregation code information sent by the target payment terminal in response to the scan code instruction for the target aggregation code, decodes the aggregation code information, obtains the target code parameters including the application tag domain value of the application tag domain corresponding to at least one payment application, obtains the target application tag domain corresponding to the target payment application, the target payment application is any one of the at least one payment application, based on the target application tag domain, determines the target application tag domain value corresponding to the target payment application from the target code parameters, obtains the preset jump information or the address information of the joint payment page based on the target application tag domain value, sends the preset jump information or the address information of the joint payment page to the target payment terminal, so that the target payment terminal jumps to the joint payment page based on the preset jump information or the address information of the joint payment page, can aggregate the existing payment QR code and the self-contained payment QR code of some regions, improves the versatility of the existing aggregation code, greatly increases the payment efficiency and collection efficiency, and improves the flexibility and convenience of transactions.

[0127] Figure 5 1 is a block diagram of a device for jumping to an aggregated payment page according to an exemplary embodiment. Figure 5 , the device comprises:

[0128] The aggregation code information receiving module 510 is used to receive the aggregation code information sent by the target payment terminal in response to the target aggregation code scanning instruction of the target payment terminal; the target aggregation code is a joint payment code corresponding to at least one payment application;

[0129] The target code parameter acquisition module 530 is used to decode the aggregation code information to obtain the target code parameters; the target code parameters include the application tag domain value of the application tag domain corresponding to at least one payment application; the preset application tag domain value corresponding to the preset payment application in at least one payment application includes the address information of the joint payment page corresponding to at least one payment application, and the application tag domain value corresponding to each payment application other than the preset payment application in at least one payment application includes the preset jump information, and the preset jump information is used for the target payment terminal to jump to the joint payment page;

[0130] A target application tag domain acquisition module 550 is used to acquire a target application tag domain corresponding to a target payment application; the target payment application is any one of at least one payment application;

[0131] A target application tag domain value determination module 570 is used to determine a target application tag domain value corresponding to a target payment application from a target code parameter based on the target application tag domain;

[0132] The information sending module 590 is used to obtain the preset jump information or the address information of the joint payment page based on the target application tag domain value, and send the preset jump information or the address information of the joint payment page to the target payment terminal, so that the target payment terminal jumps to the joint payment page based on the preset jump information or the address information of the joint payment page.

[0133] In an optional embodiment, when the target application tag field value does not include the address information of the joint payment page, the information sending module 590 includes:

[0134] A preset jump information sending unit, used to obtain preset jump information based on the target application tag domain value, and send the preset jump information to the target payment terminal so that the target payment terminal jumps to the preset intermediate page;

[0135] The target code parameter sending unit is used to respond to the address acquisition instruction triggered by the preset intermediate page, and send the target code parameters to the preset server corresponding to the preset intermediate page, so that the preset server can parse the target code parameters, obtain the address information of the joint payment page, and send it to the target payment terminal.

[0136] In an optional embodiment, when the target application tag field value includes address information of the joint payment page, the information sending module 590 includes:

[0137] The address information sending unit is used to obtain the address information of the joint payment page based on the target application tag field value, and send the address information of the joint payment page to the target payment terminal.

[0138] In an optional embodiment, the above device further includes:

[0139] An acquisition module is used to receive an aggregation code generation request for a target payment application sent by a target account, obtain target payment information and a target application label field corresponding to the target payment application, and send them to an aggregation server, so that the aggregation server generates a target application label field value based on the target payment information and the target application label field, and generates a target aggregation code based on at least one application label field value;

[0140] In the case where the at least one payment application is multiple payment applications, the at least one application tag domain value is a tag domain value corresponding to the multiple payment applications;

[0141] In the case where the at least one payment application is a payment application, the at least one application tag field value is a target application tag field value.

[0142] In an optional embodiment, the above device further includes:

[0143] The authorization processing module is used to respond to the authorization instruction triggered by the joint payment page, receive the authorization request sent by the target payment terminal, perform authorization processing on the target payment application, obtain the target authorization code and send it to the target payment terminal, so that the target payment terminal performs payment processing based on the target authorization code.

[0144] In an optional embodiment, when the QR code type of the target aggregation code is a dynamic QR code, the dynamic QR code includes transaction information, and the above-mentioned device further includes:

[0145] A target transaction information sending module is used to receive a payment request sent by a target payment terminal, obtain target transaction information corresponding to a target aggregation code, and send the target transaction information to the target payment terminal;

[0146] A first payment confirmation result acquisition module is used to receive a payment request sent by a target payment terminal when a payment confirmation operation triggered based on target transaction information is detected, perform payment processing, and obtain a first payment confirmation result;

[0147] The first address information sending module is used to send the address information of the preset payment success page to the target payment terminal when the first payment confirmation result shows that the payment is successful, so that the target payment terminal jumps to the payment success page.

[0148] In an optional embodiment, when the QR code type of the target aggregate code is a static QR code, the static QR code includes merchant information, and the above-mentioned device further includes:

[0149] The target merchant information sending module is used to receive the payment request sent by the target payment terminal, obtain the target merchant information corresponding to the target aggregation code, and send the target merchant information to the target payment terminal;

[0150] A second payment confirmation result acquisition module is used to receive a payment request sent by a target payment terminal when an amount input confirmation operation triggered by target merchant information is detected, perform payment processing, and obtain a second payment confirmation result;

[0151] The second address information sending module is used to send the address information of the preset payment success page to the target payment terminal when the second payment confirmation result shows that the payment is successful, so that the target payment terminal jumps to the payment success page.

[0152] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0153] Figure 6 is a block diagram of an electronic device for payment page jump according to an exemplary embodiment. The electronic device may be a terminal, and its internal structure diagram may be as shown in FIG. Figure 6 As shown. The electronic device includes a processor, a memory, a network interface, a display screen and an input device connected via a system bus. Among them, the processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the electronic device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for jumping to an aggregated payment page is implemented. The display screen of the electronic device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the electronic device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the housing of the electronic device, or an external keyboard, touchpad or mouse, etc.

[0154] Those skilled in the art will understand that Figure 6 The structure shown in the figure is merely a block diagram of a partial structure related to the scheme of the present disclosure, and does not constitute a limitation on the electronic device to which the scheme of the present disclosure is applied. The specific electronic device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0155] In an exemplary embodiment, an electronic device is also provided, including: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the aggregate payment page jump method as in the embodiment of the present disclosure.

[0156] In an exemplary embodiment, a computer-readable storage medium is also provided. When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device can execute the aggregate payment page jump method in the embodiment of the present disclosure.

[0157] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0158] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method for jumping to an aggregated payment page, characterized in that: include: In response to a scanning instruction of a target payment terminal for a target aggregation code, receiving aggregation code information sent by the target payment terminal; The target aggregation code is a joint payment code corresponding to at least one payment application; Decode the aggregation code information to obtain a target code parameter; the target code parameter includes an application tag domain value corresponding to the application tag domain of each of the at least one payment application; the preset application tag domain value corresponding to the preset payment application in the at least one payment application includes address information of the joint payment page corresponding to the at least one payment application, and the application tag domain value corresponding to each of the payment applications other than the preset payment application in the at least one payment application includes preset jump information, and the preset jump information is used for the target payment terminal to jump to the joint payment page; Obtaining a target application tag field corresponding to a target payment application; the target payment application is any one of the at least one payment application; Based on the target application tag domain, determine the target application tag domain value corresponding to the target payment application from the target code parameter; Based on the target application tag domain value, the preset jump information or the address information of the joint payment page is obtained, and the preset jump information or the address information of the joint payment page is sent to the target payment terminal, so that the target payment terminal jumps to the joint payment page based on the preset jump information or the address information of the joint payment page.

2. A method for redirecting an aggregated payment page according to claim 1, characterized in that: In a case where the target application tag field value does not include the address information of the joint payment page, the acquiring the preset jump information or the address information of the joint payment page based on the target application tag field value, and sending the preset jump information or the address information of the joint payment page to the target payment terminal includes: Acquire the preset jump information based on the target application tag domain value, and send the preset jump information to the target payment terminal so that the target payment terminal jumps to a preset intermediate page; In response to the address acquisition instruction triggered based on the preset intermediate page, the target code parameter is sent to the preset server corresponding to the preset intermediate page, so that the preset server parses the target code parameter, obtains the address information of the joint payment page, and sends it to the target payment terminal.

3. A method for redirecting an aggregated payment page according to claim 1, characterized in that: In a case where the target application tag field value includes the address information of the joint payment page, the acquiring the preset jump information or the address information of the joint payment page based on the target application tag field value, and sending the preset jump information or the address information of the joint payment page to the target payment terminal includes: The address information of the joint payment page is obtained based on the target application tag domain value, and the address information of the joint payment page is sent to the target payment terminal.

4. A method for redirecting an aggregated payment page according to claim 1, characterized in that: The method further comprises: Receive an aggregation code generation request for the target payment application sent by the target account, obtain the target payment information and the target application label field corresponding to the target payment application, and send them to the aggregation server, so that the aggregation server generates the target application label field value based on the target payment information and the target application label field, and generates the target aggregation code based on at least one application label field value; In the case where the at least one payment application is a plurality of payment applications, the at least one application tag domain value is a tag domain value corresponding to the plurality of payment applications; In the case where the at least one payment application is one payment application, the at least one application tag domain value is the target application tag domain value.

5. The method for redirecting an aggregated payment page according to claim 1, characterized in that: The method further comprises: In response to the authorization instruction triggered based on the joint payment page, the authorization request sent by the target payment terminal is received, the target payment application is authorized, and the target authorization code is obtained and sent to the target payment terminal, so that the target payment terminal performs payment processing based on the target authorization code.

6. A method for redirecting an aggregated payment page according to any one of claims 1 to 5, characterized in that: In the case where the two-dimensional code type of the target aggregation code is a dynamic two-dimensional code, the dynamic two-dimensional code includes transaction information, and the method further includes: Receiving a payment request sent by the target payment terminal, obtaining target transaction information corresponding to the target aggregation code, and sending the target transaction information to the target payment terminal; receiving a payment request sent by the target payment terminal when a payment confirmation operation triggered based on the target transaction information is detected, performing payment processing, and obtaining a first payment confirmation result; When the first payment confirmation result shows that the payment is successful, the address information of the preset payment success page is sent to the target payment terminal, so that the target payment terminal jumps to the payment success page.

7. A method for redirecting an aggregated payment page according to any one of claims 1 to 5, characterized in that: In the case where the two-dimensional code type of the target aggregation code is a static two-dimensional code, the static two-dimensional code includes merchant information, and the method further includes: Receive the payment request sent by the target payment terminal, obtain the target merchant information corresponding to the target aggregation code, and send the target merchant information to the target payment terminal; receiving a payment request sent by the target payment terminal when detecting an amount input confirmation operation triggered by the target merchant information, performing payment processing, and obtaining a second payment confirmation result; When the second payment confirmation result shows that the payment is successful, the address information of the preset payment success page is sent to the target payment terminal, so that the target payment terminal jumps to the payment success page.

8. A device for jumping to an aggregated payment page, characterized in that: include: The aggregation code information receiving module is used to receive the aggregation code information sent by the target payment terminal in response to the target payment terminal's scanning instruction for the target aggregation code; The target aggregation code is a joint payment code corresponding to at least one payment application; a target code parameter acquisition module, configured to decode the aggregation code information to obtain a target code parameter; the target code parameter includes an application tag domain value of an application tag domain corresponding to each of the at least one payment application; a preset application tag domain value corresponding to a preset payment application in the at least one payment application includes address information of a joint payment page corresponding to the at least one payment application, and an application tag domain value corresponding to each of the payment applications other than the preset payment application in the at least one payment application includes preset jump information, and the preset jump information is used for the target payment terminal to jump to the joint payment page; A target application tag domain acquisition module is used to acquire the target application tag domain corresponding to the target payment application; The target payment application is any one of the at least one payment application; A target application tag domain value determination module, used to determine the target application tag domain value corresponding to the target payment application from the target code parameter based on the target application tag domain; An information sending module is used to obtain the preset jump information or the address information of the joint payment page based on the target application tag domain value, and send the preset jump information or the address information of the joint payment page to the target payment terminal, so that the target payment terminal jumps to the joint payment page based on the preset jump information or the address information of the joint payment page.

9. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; Wherein, the processor is configured to execute the instructions to implement the aggregate payment page jump method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the aggregate payment page jump method as described in any one of claims 1 to 7.

Images