Aggregate payment method and system

Abstract

The present invention relates to an aggregate payment method and system. The aggregate payment method comprises the following steps: receiving a first access request corresponding to payment information from a user terminal; generating redirection address information based on the first access request; and sending the redirection address information to the user terminal; wherein the redirection address information comprises jump target information and order information corresponding to the paid transaction order. The aggregate payment system comprises: a receiving unit configured to receive a first access request from a user terminal; a redirection address information generating unit configured to generate redirection address information based on the first access request; and a sending unit configured to send the redirection address information to the user terminal; wherein the redirection address information generating unit is further configured to encapsulate the order information and transaction amount information corresponding to the transaction order in the redirection address information.

Description

Technical Field

[0001] The present invention relates to the field of mobile payment, and more particularly to a user-side and system-side aggregate payment method and an aggregate payment system. Background Art

[0002] Traditional cash payment requires change, which not only affects the transaction speed, but also reduces the user's consumption and payment experience. At present, in the daily transaction process, mobile payment through the user's device has become more and more accepted and popular among consumers. There are many ways to make mobile payments for transactions, among which the most common is the payment operation by scanning a QR code (scan code payment).

[0003] However, in the process of scanning code payment, the following situations often occur: users use different third-party applications on their devices to scan codes, which requires merchants to present the QR code corresponding to the third-party application used by users; the payment collector needs to go to the corresponding account to confirm whether the payment is successful; in particular, when the merchant provides a certain type of QR code, users can only use third-party application software that is connected to the issuer of the QR code to scan code payment, which results in poor user experience and may even lead to payment failure.

[0004] Moreover, during the payment process, the system needs to frequently obtain order information related to the transaction order from the merchant, resulting in a large amount of signaling consumption between the merchant, user, system and acquiring institution. Summary of the invention

[0005] Therefore, there is a need for an aggregate payment method and system that can support multiple third-party software to scan QR codes for payment. With this aggregate payment method and system, when a certain QR code is presented on the merchant side, users can freely choose their favorite third-party application software to scan the code for payment (the third-party application software may not be connected to the QR code provider), thereby effectively ensuring the user's consumption and payment experience. At the same time, key transaction information is specifically configured to save signaling overhead during the transaction process.

[0006] To achieve one or more of the above purposes, the present invention provides the following technical solutions.

[0007] According to a first aspect of the present invention, an aggregate payment method is provided, which includes: receiving a first access request corresponding to payment information from a user terminal; generating redirection address information based on the first access request; and sending the redirection address information to the user terminal; wherein the redirection address information includes jump target information and order information corresponding to the paid transaction order.

[0008] According to the aggregate payment method of an embodiment of the present invention, the order information includes one or more information of the order number and / or order details.

[0009] According to the aggregate payment method of one embodiment of the present invention or any one of the above embodiments, the redirection address information is generated through a proxy service.

[0010] According to the aggregate payment method of one embodiment of the present invention or any one of the above embodiments, the first access request includes user-side information, merchant-side information, a code issuing institution classification code and an acquiring institution identification (ID).

[0011] According to the aggregate payment method of one embodiment of the present invention or any of the above embodiments, the redirection address information also includes acquiring institution information.

[0012] According to the aggregate payment method of one embodiment of the present invention or any one of the above embodiments, generating redirection address information includes: obtaining information for generating redirection address information by table lookup based on merchant terminal information and acquiring institution ID.

[0013] According to the aggregate payment method of one embodiment of the present invention or any one of the above embodiments, sending the redirection address information to the user terminal includes: sending the redirection address information to the user terminal via the merchant terminal; or sending the redirection address information to the user terminal via the acquiring institution.

[0014] According to a second aspect of the present invention, an aggregate payment method is provided, which includes: obtaining payment information of an order from a merchant side; generating a first access request based on the payment information; receiving redirection address information generated based on the first access request; generating a second access request based on the redirection address information; receiving a payment request based on the second access request; and making payment according to the payment request; wherein the redirection address information includes jump target information and order information corresponding to the paid transaction order.

[0015] According to the aggregate payment method of an embodiment of the present invention, the order information includes one or more information of the order number and / or order details.

[0016] According to the aggregate payment method of one embodiment of the present invention or any one of the above embodiments, the redirection address information is generated through a proxy service.

[0017] According to the aggregate payment method of one embodiment of the present invention or any one of the above embodiments, the first access request includes user-side information, merchant-side information, code issuing institution classification code and acquiring institution ID.

[0018] According to the aggregate payment method of one embodiment of the present invention or any of the above embodiments, the redirection address information also includes acquiring institution information.

[0019] According to the aggregate payment method of one embodiment of the present invention or any one of the above embodiments, obtaining payment information of an order from a merchant side includes: obtaining order information by obtaining QR code information.

[0020] According to the aggregate payment method of one embodiment of the present invention or any of the above embodiments, making payment according to the payment request includes: making payment by calling a payment control.

[0021] According to a third aspect of the present invention, an aggregate payment system is provided, comprising: a receiving unit configured to receive a first access request from a user terminal; a redirection address information generating unit configured to generate redirection address information based on the first access request; and a sending unit configured to send the redirection address information to the user terminal; wherein the redirection address information generating unit is further configured to encapsulate the jump target information and the order information corresponding to the paid transaction order in the redirection address information.

[0022] According to the aggregate payment method of an embodiment of the present invention, the order information includes one or more information of the order number and / or order details.

[0023] According to the aggregate payment system of one embodiment of the present invention or any of the above embodiments, the redirection address information generating unit is further configured to generate the redirection address information through a proxy service.

[0024] According to the aggregate payment system of one embodiment of the present invention or any one of the above embodiments, the first access request also includes user-side information, merchant-side information, code issuing institution classification code and acquiring institution identification ID.

[0025] According to the aggregate payment system of one embodiment of the present invention or any one of the above embodiments, the redirection address information also includes acquiring institution information.

[0026] According to the aggregate payment system of one embodiment of the present invention or any one of the above embodiments, the redirection address information generation unit is further configured to: obtain information for generating the redirection address information by table lookup based on the merchant terminal information and the acquiring institution ID.

[0027] According to the aggregate payment system of one embodiment of the present invention or any of the above embodiments, the sending unit is further configured to: send redirection address information to the user terminal via the merchant terminal; or send redirection address information to the user terminal via the acquiring institution. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The above and / or other aspects and advantages of the present invention will become clearer and easier to understand through the following description in conjunction with the accompanying drawings, in which the same or similar elements are represented by the same reference numerals. The accompanying drawings include:

[0029] Figure 1 A schematic flow chart of an aggregate payment method executed by a user terminal according to an embodiment of the present invention;

[0030] Figure 2 A schematic diagram of steps for generating redirection address information by a proxy service according to an embodiment of the present invention;

[0031] Figure 3 A schematic flow chart of an aggregate payment method executed by a system end according to an embodiment of the present invention;

[0032] Figure 4 According to an embodiment of the present invention Figure 3 A schematic flow chart of the steps of generating redirect address information in;

[0033] Figure 5 A schematic diagram of various connection relationships between a system end, a merchant end, a third party and an acquiring institution according to an embodiment of the present invention;

[0034] Figure 6 is an overall timing diagram of an aggregate payment method according to an embodiment of the present invention; and

[0035] Figure 7 A schematic block diagram of an aggregate payment system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0036] In this specification, the present invention is more fully described with reference to the accompanying drawings in which exemplary embodiments of the present invention are illustrated. However, the present invention may be implemented in different forms and should not be construed as being limited to the embodiments given herein. The embodiments given are intended to make the disclosure herein comprehensive and complete, so as to more fully convey the scope of the present invention to those skilled in the art.

[0037] Terms such as "comprising" and "including" indicate that in addition to the units and steps directly and clearly stated in the specification and claims, the technical solution of the present invention does not exclude the situation of having other units and steps that are not directly or clearly stated. Terms such as "first" and "second" do not indicate the order of units in terms of time, space, size, etc., but are only used to distinguish each unit.

[0038] The present invention is described below with reference to the flowchart illustration, block diagram and / or flow chart of the method and system according to an embodiment of the present invention. It will be understood that each frame of these flowchart illustrations and / or block diagrams, and the combination of flowchart illustrations and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to form a machine, so that these instructions executed by the processor of a computer or other programmable data processing device create parts for implementing the functions / operations specified in these flowcharts and / or frames and / or one or more flowcharts.

[0039] These computer program instructions can be loaded onto a computer or other programmable data processor so that a series of operating steps are performed on the computer or other programmable processor to form a computer-implemented process so that these instructions performed on the computer or other programmable data processor provide steps for implementing the functions or operations specified in one or more frames of this flow chart and / or block diagram. It should also be noted that in some alternative implementations, the functions / operations shown in the frames may not occur in the order shown in the flow chart. For example, the two frames shown in sequence can actually be performed substantially simultaneously or these frames can sometimes be performed in reverse order, depending on the functions / operations involved.

[0040] refer to Figure 1 , which shows a schematic flow chart of an aggregate payment method 100 for a user terminal according to an embodiment of the present invention.

[0041] First, in step 110, the user obtains the payment information associated with his order, and the user generally refers to a consumer who uses a mobile device to make a consumption payment. Among them, the payment information may include the number of the order, the number of the user terminal and the merchant terminal associated with the order, the transaction amount information for this transaction order, etc. in a specific case. Generally, the operation of obtaining payment information can be achieved by scanning a QR code using a user terminal (hereinafter referred to as the user terminal) of a third-party application software (such as WeChat, Alipay), or by voiceprint recognition and other technologies. In the following, the present invention is mainly described by taking the payment method of scanning a QR code as an example. The QR code includes but is not limited to QR (Quick Response) Code, Code 49, Code 16K, Code One, etc. In this article, third-party application software refers to software that plays a role in the transaction to facilitate the transaction process between the merchant and the user, in addition to the merchant and the user, which can be installed on the merchant terminal and the user terminal at the same time, and can be designed differently for the merchant terminal and / or the user terminal.

[0042] In one embodiment, the merchant applies for a constant payment QR code from a third-party application software that the user may use. The QR code is usually printed on paper for the user to scan using the corresponding third-party application software. Since such a payment QR code is fixed, the user end can only obtain the code issuing agency classification code and merchant end information by scanning the QR code. Therefore, the merchant or user needs to enter the information associated with the transaction order in the merchant end (hereinafter referred to as the merchant end) or the user end of the third-party application software when paying. The most common information is the payment amount, payment account (i.e. the acquiring institution mentioned later), etc.

[0043] In another embodiment, when collecting payment, the merchant applies for a variable payment QR code from a third-party application software that the user may use, and the QR code is usually displayed to the user on an electronic screen. Such a QR code is generated based on the transaction-related information entered by the merchant when applying for the QR code from the third-party application software, so when the user scans the QR code to pay, the payment amount and other information can be directly obtained and confirmed without the need for manual input by the user.

[0044] Continue to refer Figure 1 After the user uses a third-party application to scan the QR code to obtain payment information, the user terminal generates a first access request to the system based on the payment information (step 120). The first access request may include user terminal information such as user institution parameters and domain name. For example, for the WeChat user terminal, the user institution parameter value is "MicroMessenger". In the domain name, the QR code issuing institution classification code (i.e., the issuing institution classification code) and the acquiring institution (i.e., the source of the account selected by the user for payment) identification ID may be included for subsequent generation of redirection address information.

[0045] Next, the user terminal receives the redirection address information generated by the system (step 130) and then generates a second access request to the acquirer according to the redirection address information (step 140). The second access request may be an access request to the acquirer, or may be other types of access requests that can prompt the acquirer to generate an order and send a payment request to the user terminal. In addition to indicating the determined access address (the address for accessing the acquirer), the redirection address information further includes order information corresponding to the transaction order, which at least includes one or more information in the order number and / or order details, and may be included in a certain URL. Subsequently, the order may be processed accordingly based on the information in the order number or order details (e.g., transaction amount, transaction object, transaction time, transaction method, etc.). Depending on the circumstances, the redirection address information may also include other transaction-related information. Thus, the user terminal may access the acquirer according to the redirection address information, and the user may know and further confirm the transaction amount and the name of the payee of the transaction order. For example, the user terminal may access the H5 (HTML5) payment page of the acquirer. Alternatively, the redirection address information may also include the acquirer ID.

[0046] In one embodiment, the redirection of the address is performed through a proxy service. Figure 2 As shown in , a third-party application software (user end or merchant end) sends an address redirection request to a proxy service (S1), and then the proxy service processes the request. Specifically, the proxy service generates redirection address information, and then sends the redirection address information to the acquiring institution (S2). The acquiring institution sends, for example, an H5 payment page to the proxy service (S3), and finally the proxy service sends the page to the third-party application software (S4) for subsequent payment steps.

[0047] Finally, the user terminal performs the corresponding payment operation (step 160) based on the received payment request (step 150). During the payment process, for security reasons, payment is generally completed by calling a secure payment control. In the case of a secure payment control, when the user enters password data such as a password, fingerprint, voiceprint, facial image, dynamic image, etc. during the payment operation, the secure payment control encrypts and protects the user's account and password data, thereby ensuring the security of the user's account and password.

[0048] Reference now Figure 3 , Figure 3 The present invention is a schematic flowchart of an aggregate payment method executed by a system end according to an embodiment of the present invention.

[0049] In step 210, the system receives a first access request corresponding to payment information from the user. Subsequently, based on the received first access request, the system performs step 220 of generating redirection address information.

[0050] In step 220, if Figure 4 As shown in , the system first performs operations of determining the access source (step 2202) and domain name resolution (step 2204). For example, in step 2202, the system determines that the third-party application software is WeChat from the user information included in the first access request, for example, the user institution parameter value "MicroMessenger". The first access request also includes merchant information, code issuing institution classification code and acquiring institution ID.

[0051] In addition, just as an example, the domain name corresponding to the first access request can be, for example, "https: / / qr.95516.com / 00010000 / 0293819283719182", where 0001000 represents the classification code of the issuing agency, and 0293819283719182 represents the acquiring agency ID. Then, in the process of resolving the domain name (step 2204), the system side makes a judgment based on the acquiring agency ID and the classification code of the issuing agency. In one embodiment, if the classification code of the issuing agency is 0001000 or 00010002, it indicates that the QR code is a system-issued code, and the others are self-issued codes by the acquiring agency. In other words, here, the classification code of the issuing agency is used to classify the source of the QR code, which is divided into system-issued codes and self-issued codes by the acquiring agency in the above example. When the QR code is issued by the system, the classification code of the issuing agency is also used to classify the connection between the system end and the merchant end, where 00010000 represents an indirect connection between the system end and the merchant end, and 00010002 represents a direct connection between the system end and the merchant end. The indirect connection means that the system end and the merchant end are connected through an acquiring agency.

[0052] Then, the system end obtains information for generating redirection address information (step 2206), such as a jump target, which is part of the redirection address information, through a table lookup method based on the merchant end information (e.g., merchant number) and the acquirer ID. Specifically, the system end searches and confirms the acquirer from the acquirer ID table. Additionally, the system end further searches for the acquirer code corresponding to the acquirer from the acquirer code table. In addition, the system end determines whether the merchant end is directly connected or indirectly connected to the third-party application software through the business configuration parameters of the merchant end's network access application. An exemplary acquirer ID and code and a code-issuing agency classification code table are shown in Table 1.

[0053] Table 1 Acquirer ID and code and issuing agency classification code table

[0054] Acquirer Acquirer ID Acquirer Code Issuing agency classification code ICBC 0293819283719182 01020000 00010000 China Construction Bank 0293819283719193 01030000 00010002 Agricultural Bank of China 0293819283719104 01040000 01040000

[0055] According to the acquirer ID: 0293819283719182 (or the corresponding acquirer code found based on the acquirer ID: 01020000) and the merchant-side information such as the merchant number, the corresponding jump target can be found from the jump target table. In other embodiments, the acquirer ID can be integrated with the acquirer code to generate an integrated value, thereby reducing the steps of finding the acquirer code from the acquirer ID and further saving signaling overhead. The jump target table can be stored on the system side or on the acquirer. An exemplary jump target table is shown in Table 2 below.

[0056] Table 2 Jump target table

[0057] Acquirer Code Merchant Number Jump target 01020000 310000123456701 https: / / qr.shmetro.com / pay 01040000 310000223456702 https: / / qr.abcchina.com / pay 01020000 * https: / / qr.icbc.com / pay

[0058] Referring to Table 2, in one embodiment, when the acquirer code is required, the merchant code corresponding to the acquirer code 01020000 is 310000123456701, which represents Shanghai Metro, and the jump target is "https: / / qr.shmetro.com / pay". If the merchant code is not determined, the merchant code is represented by "*", and the corresponding jump target is determined according to this item.

[0059] Returning to reference Table 1, in one embodiment, if the code issuing institution classification code is not 0001000 or 00010002, the code issuing institution classification code is the acquiring institution code, and at this time, the merchant number and jump target can be directly searched according to the jump target table.

[0060] After obtaining the jump target, the system executes step 2208 to form redirection address information based on the found jump target and the order information corresponding to the transaction order.

[0061] In one embodiment, the redirect address information takes the form of , where A is the jump target obtained as described above, and B is the payment information data. For example, the corresponding acquiring institution code is "01020000", the merchant number is "310000123456701", the order number is "012056" and the transaction amount information is "1000". In this case, the jump target A is "https: / / qr.shmetro.com / pay", and the payment information data B is "order=012056&amount=1000", which includes the order number (order=012056) and the transaction amount information (amount=1000). The redirect address information thus obtained is " ”.

[0062] Next, the system executes step 230 to return the generated redirection address information to the third-party application software. Figure 5 In the case (1) shown in the figure, when the system end and the merchant end are directly connected and the merchant end and the third-party application software (hereinafter referred to as the third party) are indirectly connected, the system end directly sends the redirection address information to the acquiring institution, and the acquiring institution directly processes it according to the order information in the redirection address information, for example, converting the order information in the redirection address information into a data format suitable for the third party. Then, the acquiring institution sends a payment request (including the order information) to the third party. In this way, since the redirection address information already contains the order information associated with the transaction order, the process of the system end first sending the redirection address information to the acquiring institution, the acquiring institution sending the address to the merchant end, and then the merchant end providing the acquiring institution with payment information such as order information is omitted, thereby saving some signaling overhead between multiple parties.

[0063] In another embodiment, Figure 5 In the case (2) shown in FIG, when the system end and the merchant end are indirectly connected and the merchant end and the third party are directly connected, the system end directly sends the redirection address information to the merchant end (determined by the merchant number). Then, the merchant end processes the order information in the redirection address information. Subsequently, the merchant end sends a payment request to the third party. In this way, the process of the system end first sending the redirection address information to the acquiring institution, the acquiring institution processing the order information according to the received redirection address information, and then sending the order information to the merchant end is omitted, thus saving part of the signaling overhead between multiple parties.

[0064] In yet another embodiment, Figure 5 In the situation (3) shown in the figure, when the system side and the merchant side are directly connected, and the merchant side and the third party are also directly connected, the system side sends the redirection address information to the merchant, and the merchant returns the acquirer redirection address information to the non-system side system APP.

[0065] In yet another embodiment, Figure 5 In the case (4) shown in FIG, when the system and the merchant are connected indirectly, and the merchant and the third party are also connected indirectly, the system sends the redirection address information to the acquiring institution, and the acquiring institution returns the redirection address information to the third party. Since the redirection address information already contains the order information of this transaction, such as the order number and one or more information in the order details, the acquiring institution does not need to request payment information from the merchant after receiving the redirection address information, and waits for the merchant to return the information before sending it to the third party, which saves some signaling overhead between multiple parties.

[0066] In addition, the following method can be used to generate redirection address information. In one embodiment, the acquirer code is "01020000", the merchant number is "*", and the jump target is "https: / / qr.icbc.com / pay". in the form of or In the form of, as mentioned above, A is the jump target, B is the payment information data, and C is the dynamic data containing the QR code. The dynamic data can be the payment information obtained by the third party by scanning the QR code as mentioned above, such as URL (https: / / qr.95516.com / 00010000 / 0293819283719182), that is, https%3a%2f%2fqr.95516.com%2f%3c00010000%3e%2f%3c0293819283719182%3e, which includes the code issuing agency classification code and the acquiring agency ID. Then the third-party application software determines the redirection address information based on the dynamic data.

[0067] In one embodiment, the redirection of the address is performed through a proxy service. Figure 2 As shown in , a third-party application software (user end or merchant end) sends an address redirection request to a proxy service (S1), and then the proxy service processes the request. Specifically, the proxy service generates redirection address information, and then sends the redirection address information to the acquiring institution (S2). The acquiring institution sends, for example, an H5 payment page to the proxy service (S3), and finally the proxy service sends the page to the third-party application software (S4) for subsequent payment steps.

[0068] Figure 6 FIG. 3 is a general timing diagram 300 of the aggregate payment method according to an embodiment of the present invention. Figure 6 The aggregate payment method according to an embodiment of the present invention is described as a whole. First, in step 310, payment information is obtained through a third-party application software (for example, from a QR code provided by the merchant side), and then a corresponding first access request to the system side is generated according to the payment information in step 320. In step 330, the system side generates redirection address information in response to the first access request, and sends it to the third-party application software in step 340. The third-party application software then generates a corresponding second access request to the acquiring institution according to the received redirection address information in step 350. In step 360, the acquiring institution generates a payment request in response to the second access request, and sends it to the third-party application software in step 370. Finally, in step 380, the third-party application software (for example, through a secure payment control) performs a payment operation.

[0069] Figure 7 FIG. 4 is a schematic block diagram of an aggregate payment system 400 according to an embodiment of the present invention. Figure 7 As shown, the system 400 includes a receiving unit 410, a redirection address information generating unit 420 and a sending unit 430. The system 400 communicates directly or indirectly with the user end, the merchant end or the acquiring institution through the receiving unit 410 and the sending unit 430. Figure 7 4 and 5. In the embodiment, the receiving unit 410 and the sending unit 430 are shown as separate receiving units 410 and sending units 430, but it is understood that the functions of the two units can be performed by one unit (e.g., a transceiver unit) or can be incorporated into other units in the system. In one embodiment, the receiving unit 410 is configured to receive a first access request corresponding to payment information from a user terminal.

[0070] Subsequently, based on the received first access request, the redirection address information generating unit 420 generates the redirection address information. The redirection address information generating unit 420 may also include a request source determining unit 4202, a domain name resolving unit 4204, a redirection information determining unit 4206, and a redirection address information forming unit 4208 (in Figure 7 ). The request source determination unit 4202 is configured to determine the source of the access request to the system, that is, the type of the third-party application software that initiates access to the system. In one embodiment, the request source determination unit 4202 can determine that the third-party application software is WeChat from the user terminal information included in the first access request, for example, the user institution parameter value "MicroMessenger". The first access request also includes merchant terminal information, the code issuing institution classification code, and the acquiring institution ID.

[0071] The domain name resolution unit 4204 is configured to resolve the domain name corresponding to the first access request to obtain the payment information therein. As an example only, the domain name corresponding to the first access request may be, for example, "https: / / qr.95516.com / 00010000 / 0293819283719182", where 0001000 represents the code issuing agency classification code, and 0293819283719182 represents the acquirer ID. The domain name resolution unit 4204 determines the identity of the acquirer using the acquirer ID. The domain name resolution unit 4204 may make a judgment based on the acquirer ID and the code issuing agency classification code. In one embodiment, if the code issuing agency classification code is 0001000 or 00010002, the domain name resolution unit 4204 determines that the QR code is a system-issued code, and the others are self-issued codes of the acquirer. That is, here, the code issuing agency classification code is used to classify the source of the QR code, which is classified into system-issued codes and self-issued codes of the acquirer in the above example. When the QR code is issued by the system, the classification code of the issuing agency is also used to classify the connection between the system end and the merchant end, where 00010000 represents an indirect connection between the system end and the merchant end, and 00010002 represents a direct connection between the system end and the merchant end. The indirect connection means that the system end and the merchant end are connected through an acquiring agency.

[0072] Then, the redirection information determination unit 4206 can obtain information for generating redirection address information (step 2206), such as a jump target, which is part of the redirection address information, through a table lookup method based on the merchant-side information (e.g., merchant number) and the acquiring institution ID. Specifically, the redirection information determination unit 4206 can search and confirm the acquiring institution from the acquiring institution ID table. Additionally, the redirection information determination unit 4206 can further search the acquiring institution code corresponding to the acquiring institution from the acquiring institution code table. In addition, the redirection information determination unit 4206 can determine whether the merchant-side is directly connected or indirectly connected to the third-party application software through the business configuration parameters of the merchant-side network access application. Exemplary acquiring institution IDs and codes and the code-issuing institution classification code table are shown in Table 1 above.

[0073] According to the acquirer ID: 0293819283719182 (or the corresponding acquirer code found based on the acquirer ID: 01020000) and the merchant-side information such as the merchant number, the redirection information determination unit 4206 can search for the corresponding jump target from the jump target table. In other embodiments, the acquirer ID can be integrated with the acquirer code to generate an integrated value, thereby reducing the steps of searching the acquirer code from the acquirer ID and further saving signaling overhead. The jump target table can be stored on the system side or on the acquirer. An exemplary jump target table is shown in Table 2 above.

[0074] Referring to Table 2, in one embodiment, when the acquirer code is required, the merchant code corresponding to the acquirer code 01020000 is 310000123456701, which represents Shanghai Metro, and the jump target is "https: / / qr.shmetro.com / pay". If the merchant code is not determined, the merchant code is represented by "*", and the corresponding jump target is determined according to this item.

[0075] Returning to reference Table 1, in one embodiment, if the code issuing institution classification code is not 0001000 or 00010002, the code issuing institution classification code is the acquiring institution code, and at this time, the merchant number and jump target can be directly searched according to the jump target table.

[0076] After obtaining the jump target, the redirect address information forming unit 4208 can be configured to form the redirect address information based on the found jump target and the order information corresponding to the transaction order. The redirect address information forming unit 4208 can also be configured to encapsulate the order information corresponding to the transaction order in the redirect address information.

[0077] In one embodiment, the redirect address information takes the form of , where A is the jump target obtained as described above, and B is the payment information data. For example, the corresponding acquiring institution code is "01020000", the merchant number is "310000123456701", the order number is "012056" and the transaction amount information is "1000". In this case, the jump target A is "https: / / qr.shmetro.com / pay", and the payment information data B is "order=012056&amount=1000", which includes the order number (order=012056) and the transaction amount information (amount=1000). The redirect address information thus obtained is " ”.

[0078] The sending unit 430 is configured to return the generated redirection address information to the third-party application software. Figure 5In the case (1) shown in FIG, when the system end and the merchant end are directly connected and the merchant end and the third-party application software (hereinafter referred to as the third party) are indirectly connected, the sending unit 430 can directly send the redirection address information to the acquiring institution, and the acquiring institution directly processes it according to the order information in the redirection address information, for example, converting the order information in the redirection address information into a data form suitable for the third party. Then, the acquiring institution sends a payment request (including the order information) to the third party. In this way, since the redirection address information already contains the order information associated with the transaction order, the system's sending unit 430 first sends the redirection address information to the acquiring institution, the acquiring institution sends the address to the merchant end, and then the merchant end provides the acquiring institution with payment information such as order information, thereby saving some signaling overhead between multiple parties.

[0079] In another embodiment, Figure 5 In the case (2) shown in FIG. 1 , when the system end and the merchant end are indirectly connected and the merchant end and the third party are directly connected, the sending unit 430 can directly send the redirection address information to the merchant end (determined by the merchant number). Then, the merchant end processes the order information in the redirection address information. Subsequently, the merchant end sends a payment request to the third party. In this way, the process in which the sending unit 430 first sends the redirection address information to the acquiring institution, the acquiring institution processes the order information according to the received redirection address information, and then sends the order information to the merchant end is omitted, thereby saving part of the signaling overhead between multiple parties.

[0080] In yet another embodiment, Figure 5 In the case (3) shown in FIG. 1 , when the system end and the merchant end are directly connected, and the merchant end and the third party are also directly connected, the sending unit 430 can send the redirection address information to the merchant, and the merchant returns the acquirer redirection address information to the non-system end system APP.

[0081] In yet another embodiment, Figure 5 In the case (4) shown in FIG. 1 , when the system end and the merchant end are indirect links, and the merchant end and the third party are also indirect links, the sending unit 430 can send the redirection address information to the acquiring institution, and the acquiring institution returns the redirection address information to the third party. Since the redirection address information already contains the order information of this transaction such as the order number and one or more information in the order details, the acquiring institution does not need to request the payment information from the merchant end after receiving the redirection address information, and waits for the merchant end to return the information before sending it to the third party, thereby saving part of the signaling overhead between multiple parties.

[0082] In addition, the redirection address information forming unit 4208 can also be configured to generate the redirection address information in the following manner. In one embodiment, the acquiring institution code is "01020000", the merchant number is "*", and the jump target is "https: / / qr.icbc.com / pay". in the form of or In the form of, as mentioned above, A is the jump target, B is the payment information data, and C is the dynamic data containing the QR code. The dynamic data can be the payment information obtained by the third party by scanning the QR code as mentioned above, such as URL (https: / / qr.95516.com / 00010000 / 0293819283719182), that is, https%3a%2f%2fqr.95516.com%2f%3c00010000%3e%2f%3c0293819283719182%3e, which includes the code issuing agency classification code and the acquiring agency ID. Then the third-party application software determines the redirection address information based on the dynamic data.

[0083] In one embodiment, the redirection of the address is performed through a proxy service. Figure 2 As shown in , a third-party application software (user end or merchant end) sends an address redirection request to a proxy service (S1), and then the proxy service processes the request. Specifically, the proxy service generates redirection address information, and then sends the redirection address information to the acquiring institution (S2). The acquiring institution sends, for example, an H5 payment page to the proxy service (S3), and finally the proxy service sends the page to the third-party application software (S4) for subsequent payment steps.

[0084] The embodiments and examples set forth herein are provided to best illustrate embodiments according to the present technology and its specific applications, and thereby enable those skilled in the art to make and use the present invention. However, those skilled in the art will appreciate that the above description and examples are provided for ease of illustration and example only. The description set forth is not intended to cover all aspects of the present invention or to limit the invention to the precise form disclosed.

Claims

1. An aggregate payment method, comprising the following steps: Receiving a first access request corresponding to payment information from a user, wherein the user information, the merchant information, the code issuing institution classification code and the acquiring institution ID are obtained by determining the access source and performing domain name resolution on the first access request; generating redirection address information based on the first access request; and Sending the redirection address information to the user terminal; The redirection address information includes the jump target information and the order information corresponding to the paid transaction order. The generating of redirection address information based on the first access request includes: Determine the access source according to the user terminal information; Determine whether the code is issued by the system or by the acquirer according to the code issuing institution classification code; If it is determined that the code is issued by the acquirer, the code issuing agency classification code is the acquirer code, and the corresponding merchant terminal information and jump target information are directly obtained by table lookup method according to the acquirer code; When it is determined that the code is issued by the system, the corresponding acquiring institution code is obtained by table lookup based on the acquiring institution ID, and then the jump target information is obtained by table lookup based on the acquiring institution code and the corresponding merchant terminal information.

2. The aggregate payment method according to claim 1, wherein: The order information includes one or more information of the order number and / or order details.

3. The aggregate payment method according to claim 1, wherein: The redirection address information is generated through a proxy service.

4. The aggregate payment method according to claim 1, wherein: The redirection address information also includes acquiring institution information.

5. The aggregate payment method according to any one of claims 1 to 4, wherein: Sending the redirection address information to the user terminal includes: Sending the redirection address information to the user terminal via the merchant terminal; or The redirection address information is sent to the user terminal via the acquiring institution.

6. An aggregate payment method, comprising the following steps: Get payment information of the order from the merchant; generating a first access request according to the payment information; Receiving redirection address information generated based on the first access request; Generate a second access request according to the redirection address information; receiving a payment request based on the second access request; as well as Make payment according to the payment request; The redirection address information includes the jump target information and the order information corresponding to the paid transaction order. Wherein, generating redirection address information based on the first access request includes: determining the access source according to the user terminal information; According to the classification code of the issuing institution, determine whether the code is issued by the system or by the acquiring institution; If it is determined that the code is issued by the acquirer, the code issuing agency classification code is the acquirer code, and the corresponding merchant terminal information and jump target information are directly obtained by table lookup method according to the acquirer code; When it is determined that the code is issued by the system, the corresponding acquiring institution code is obtained through a table lookup method based on the acquiring institution ID, and then the jump target information is obtained through a table lookup method based on the acquiring institution code and the corresponding merchant-side information.

7. The aggregate payment method according to claim 6, wherein: The order information includes one or more information of the order number and / or order details.

8. The aggregate payment method according to claim 6, wherein: The redirection address information is generated through a proxy service.

9. The aggregate payment method according to claim 6, wherein: The first access request includes user-side information, merchant-side information, code issuing agency classification code and acquiring agency ID.

10. The aggregate payment method according to claim 6, wherein: The redirection address information also includes acquiring institution information.

11. The aggregate payment method according to claim 9, wherein: Obtaining the payment information of the order from the merchant terminal includes: The order information is obtained by obtaining the QR code information.

12. The aggregate payment method according to any one of claims 6 to 11, wherein: Making payment according to the payment request includes: Make payment by calling the payment control.

13. An aggregate payment system, comprising: A receiving unit configured to receive a first access request from a user terminal; a redirection address information generating unit, configured to generate redirection address information based on the first access request; as well as A sending unit, configured to send the redirection address information to the user terminal; The redirection address information generating unit is further configured to encapsulate the jump target information and the order information corresponding to the paid transaction order in the redirection address information. Wherein, the redirection address information generating unit is configured as follows: Determine the access source according to the user terminal information; According to the classification code of the issuing institution, determine whether the code is issued by the system or by the acquiring institution; If it is determined that the code is issued by the acquirer, the code issuing agency classification code is the acquirer code, and the corresponding merchant terminal information and jump target information are directly obtained by table lookup method according to the acquirer code; When it is determined that the code is issued by the system, the corresponding acquiring institution code is obtained through a table lookup method based on the acquiring institution ID, and then the jump target information is obtained through a table lookup method based on the acquiring institution code and the corresponding merchant-side information.

14. The aggregate payment system according to claim 13, wherein: The order information includes one or more information of the order number and / or order details.

15. The aggregate payment system according to claim 13, wherein: The redirection address information generating unit is further configured to generate the redirection address information through a proxy service.

16. The aggregate payment system according to claim 13, wherein: The first access request also includes user-side information, merchant-side information, code issuing agency classification code and acquiring agency identification ID.

17. The aggregate payment system according to claim 13, wherein: The redirection address information also includes acquiring institution information.

18. The aggregate payment system according to claim 16, wherein: The redirection address information generating unit is further configured to: Based on the merchant-side information and the acquiring institution ID, information for generating the redirection address information is obtained through a table lookup method.

19. The aggregate payment system according to any one of claims 13 to 18, wherein: The sending unit is also configured to: Sending the redirection address information to the user terminal via the merchant terminal; or The redirection address information is sent to the user terminal via the acquiring institution.

Images