WO2017121283A1 - 支付方法、系统、支付转换方法以及支付转换装置 - Google Patents

支付方法、系统、支付转换方法以及支付转换装置 Download PDF

Info

Publication number
WO2017121283A1
WO2017121283A1 PCT/CN2017/070354 CN2017070354W WO2017121283A1 WO 2017121283 A1 WO2017121283 A1 WO 2017121283A1 CN 2017070354 W CN2017070354 W CN 2017070354W WO 2017121283 A1 WO2017121283 A1 WO 2017121283A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
message
webpage
native
page
Prior art date
Application number
PCT/CN2017/070354
Other languages
English (en)
French (fr)
Inventor
沈军强
李佳佳
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2017121283A1 publication Critical patent/WO2017121283A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/16—Payments settled via telecommunication systems

Definitions

  • the present application relates to the field of data processing technologies, and in particular, to a payment method, a system, a payment conversion method, and a payment conversion device.
  • H5 Hypertext Markup Language HTML 5
  • native native payment method the H5 payment method mainly relies on the payment of the remote H5 web interface
  • the native payment method mainly relies on the payment made by the system's native local interface.
  • the H5 payment method has the following disadvantages: completely relying on the network, slow page rendering, poor user experience, low payment success rate, and the like.
  • moving from the H5 payment method to the Native payment method is not simple, and the human and material costs that are required to be used in the entire transformation process are relatively large.
  • a wireless browser can directly convert the H5 payment method into a native payment method.
  • the wireless browser converts the H5 payment method into a native payment method by using its own proprietary protocol, that is, it can only be applied. In the browser, for example, simply converting the H5 payment link message loaded in the application on the browser, and not converting the H5 payment link message loaded in other applications, resulting in the wireless browser
  • the implementation of the transformation of payment methods is not scalable.
  • the purpose of the present application is to solve at least one of the above technical problems to some extent.
  • the first object of the present application is to propose a payment method.
  • the method realizes that the H5 payment method of the webpage application can be converted into the native payment method in real time, and for the majority of merchants, a large amount of manpower and material cost are saved in the process of switching from the h5 payment method to the native payment method, and Suitable for promotion, with versatility and universality.
  • a second object of the present application is to propose a payment system.
  • a third object of the present application is to propose a payment conversion device.
  • a fourth object of the present application is to propose a payment conversion method.
  • the payment method of the first aspect of the present application includes: intercepting a webpage link message of the webpage application; determining whether the webpage link message is a webpage payment message; if it is determined to be the webpage payment message, Transmitting the webpage payment message into a native payment message; and transmitting the native payment message to a payment server for payment.
  • the payment method of the embodiment of the present application intercepts a webpage link message of the webpage application, and determines whether the webpage link message is a webpage payment message. If it is determined to be a webpage payment message, the webpage payment message is converted into a native payment message, and the native payment is performed. The message is sent to the payment server for payment. Realizing the ability to convert the H5 payment method of the web application into the native payment method in real time, for the majority of merchants, in the process of switching from the h5 payment method to the native payment method, a large amount of manpower and material cost are saved, and The payment performance of the web application provided by the majority of merchants is more stable, the payment success rate of the web application is improved, and the user experience is improved. In addition, since the payment method of the embodiment of the present application can be applied to any web application having a payment function, it is suitable for promotion, and has the characteristics of universality and universality.
  • the payment system of the second aspect of the present application includes a webpage application module, a payment server, and a conversion module, wherein the webpage application module is configured to intercept a webpage link message; Obtaining a webpage link message sent by the webpage application module, and when determining that the webpage link message is a webpage payment message, converting the webpage payment message into a native payment message, and sending the native payment message to the The payment server performs payment; the payment server is configured to perform payment according to the Native payment message and return the payment result.
  • the payment system of the embodiment of the present application acquires a webpage link message sent by the webpage application module through the conversion module, and converts the webpage payment message into a native payment message when the webpage link message is determined to be a webpage payment message, and sends the native payment message To the payment server for payment, the payment server pays according to the Native payment message and returns the payment result.
  • the payment server pays according to the Native payment message and returns the payment result.
  • the payment conversion apparatus of the third aspect of the present application includes: an obtaining module, configured to acquire a webpage link message of a webpage application; and a determining module, configured to determine whether the webpage link message is a webpage support And a conversion module, configured to convert the webpage payment message into a native payment message when the determining module determines that the webpage link message is the webpage payment message.
  • the payment conversion device of the embodiment of the present invention may obtain a webpage link message of the webpage application by the obtaining module, and the determining module determines whether the webpage link message is a webpage payment message, and the conversion module, when the determining module determines that the webpage link message is a webpage payment message, The webpage payment message is converted into a native payment message, and the sending module sends the native payment message to the payment server for payment.
  • a fourth aspect of the embodiments of the present application further provides a payment conversion method, including the steps of: acquiring a webpage link message of a webpage application; determining whether the webpage link message is a webpage payment message; The webpage payment message is converted into a native payment message.
  • the payment conversion method of the embodiment of the present application can convert the H5 payment mode of the webpage application into a native payment mode in real time, and for the majority of merchants, a large amount of manpower is saved in the process of switching from the h5 payment mode to the native payment mode.
  • the material cost and can make the payment performance of the web application provided by the majority of merchants more stable, improve the payment success rate of the web application, and improve the user experience.
  • the payment method of the embodiment of the present application can be applied to any web application having a payment function, it is suitable for promotion, and has the characteristics of universality and universality.
  • FIG. 1 is a flow chart of a payment method in accordance with one embodiment of the present application.
  • FIG. 2 is a flow chart of a payment method according to another embodiment of the present application.
  • FIG. 3 is a flow chart of a payment conversion method according to an embodiment of the present application.
  • FIG. 4 is a structural block diagram of a payment system according to an embodiment of the present application.
  • FIG. 6 is a structural block diagram of a payment conversion apparatus according to an embodiment of the present application.
  • FIG. 7 is a structural block diagram of a payment conversion apparatus according to another embodiment of the present application.
  • FIG. 8 is a structural block diagram of a payment conversion apparatus according to still another embodiment of the present application.
  • the payment method provided by the present application may include: intercepting a webpage link message of the webpage application; determining whether the webpage link message is a webpage payment message; if the webpage payment message is determined, the webpage payment message is Converting to a Native payment message; and transmitting the Native payment message to a payment server for payment.
  • the payment method can be implemented as a stand-alone application, such as an H5 application, or an H5 page program to implement the above payment process, that is, a webpage link message on a webpage program can be intercepted, and can be determined as a payment message according to the link message. It can be converted into a Native payment message for payment processing.
  • the webpage application may be in a browser or in an operating system such as a terminal, that is, the webpage application is installed and runs in an operating system of the mobile terminal or the terminal in a separate program.
  • the web application is an application developed based on HTML (Hypertext Markup Language), for example, based on H5 (5th generation HTML), and the native application (local application) refers to a mobile terminal based Operating systems, such as iOS, Android, WP, etc., and use native programs to write third-party applications that run.
  • the message generated by the web application is a webpage link message
  • the message generated by the native application is a native message.
  • the webpage link of the webpage application can be converted and converted into a native payment message, thereby enabling the webpage application to have the capability of the native application and enhancing the user experience.
  • the payment method may include:
  • the webpage application can determine the input event operation of the user, and perform corresponding operation response according to the judgment result, for example, generating a corresponding webpage.
  • Link message For example, take a web application as an example of a Taobao application when the user is at When a Taobao application wants to make a purchase payment operation for a certain product, the Taobao application generates a corresponding webpage link message according to the user's operation. If a user clicks on the "confirm order" input, the corresponding search may be generated.
  • Web page payment link message for example, when the user wants to know more about a product on the Taobao application, click the details page on the web page where the product is located, and the Taobao application can generate a specific page according to the user's operation.
  • Web page link message may specifically mean that the webpage user program can send the user's input event operation to the corresponding server, and the server processes the operation event and returns a webpage link message, for example, for the above confirmation.
  • a single operation can be sent to the Taobao server by the Taobao application, a payment link message returned by the Taobao server, and so on.
  • the specific implementation may be implemented differently according to specific scenarios.
  • the webpage link message obtained by the webpage application according to the user's operation may be intercepted in real time.
  • the webpage link message may be determined whether the webpage link message has a preset character string, and if it is determined to have a preset character string, the webpage link message is determined to be a webpage payment message.
  • the preset character string can be understood as a character string representing the meaning of the payment message, such as alipay, pay, h5OrderInfo, etc., and the string can be preset according to the webpage payment message. It can be understood that, in actual applications, the webpage payment link provided by the provider to which the different webpage application belongs may be different, and the key string of the webpage payment link provided by the accessed provider may be extracted and stored as Determine whether the link message is the basis for the web page payment message.
  • the webpage link message of the webpage application when intercepted, it can be determined whether the webpage link message has a character string representing the meaning of the payment message as described above, and if it is determined that the webpage link message has such a character string, Then, the webpage link message can be determined to be a webpage payment message.
  • the webpage link message may be processed without any processing, and directly submitted to the webpage application program according to the webpage link message. Processing, for example, the webpage application continues to open the webpage page corresponding to the webpage according to the webpage link message.
  • the webpage payment message is converted into a native payment message.
  • webpage payment message and the native payment message of different payment service providers may be different.
  • the webpage payment message of the WeChat webpage application or the Taobao webpage application is different, so the identifier of the webpage link message needs to be To determine the source of the message, such as from the WeChat web application or Taobao web application, or other web applications.
  • the webpage link message may be acquired.
  • the identifier is determined according to the identifier, and the payment information in the webpage payment message is extracted, and finally, the payment information is added to the conversion template to generate a native payment message.
  • the corresponding conversion template is determined according to the source of the webpage payment message, for example, the US group has the conversion template of the US group, and the first store has the conversion template corresponding to the first store.
  • the webpage link message may be analyzed first.
  • the webpage link message generally includes a URL link, and in this step, the webpage link may be The URL link corresponding to the message is analyzed, such as segmentation, to obtain the identifier of the webpage link message to determine the source of the message, and then the corresponding conversion template may be determined according to the identifier, that is, the different sources of the webpage link message are different.
  • the payment information may be, for example, a payment amount, an order information, a token token (for identity authentication)
  • the payment information is added to the above-mentioned determined conversion template to obtain a Native payment message corresponding to the webpage payment message, that is, the transition from the H5 payment method to the Native payment mode is realized.
  • the emission of the payment information in the webpage payment (ie, H5 payment) link has a clear rule, and therefore, the webpage payment message can be split according to the rule, so that the webpage payment message can be effectively converted into a native payment. Message.
  • the native payment message may be sent to the payment server, so that the payment server completes the payment according to the native payment method.
  • the H5 payment method of the webpage application is converted into the native payment mode, so that the payment performance of the webpage application is more stable, the payment success rate of the webpage application is improved, and the user experience is improved.
  • the execution steps described above may be performed by an execution entity, or may be implemented by different execution entities.
  • the execution entity may refer to a program module or a function module, which may have different definitions according to specific scenarios.
  • the payment method of the embodiment of the present application intercepts a webpage link message of the webpage application, and determines whether the webpage link message is a webpage payment message. If it is determined to be a webpage payment message, the webpage payment message is converted into a native payment message, and the native payment is performed. The message is sent to the payment server for payment. Realizing the ability to convert the H5 payment method of the web application into the native payment method in real time, for the majority of merchants, in the process of switching from the h5 payment method to the native payment method, a large amount of manpower and material cost are saved, and The payment performance of the web application provided by the majority of merchants is more stable, the payment success rate of the web application is improved, and the user experience is improved. In addition, since the payment method of the embodiment of the present application can be applied to any web application having a payment function, it is suitable for promotion, and has the characteristics of universality and universality.
  • FIG. 2 is a flow chart of a payment method in accordance with another embodiment of the present application.
  • the payment method may include:
  • the webpage payment message is converted into a native payment message.
  • the identifier of the webpage link message may be acquired, and the corresponding conversion template is determined according to the identifier, and the payment information in the webpage payment message is extracted, and finally, Payment information is added to the conversion template to generate a Native payment message.
  • a Native Native application can also be invoked to generate a Native payment page, such as calling a local wallet application (Native application) to generate a payment page.
  • S260 Receive a payment password input by the user in the Native payment page, and send the payment password to the payment server for payment.
  • the payment server performs payment according to the payment password and returns the payment result.
  • the payment server completes the payment according to the payment password, and after completing the payment, the corresponding payment result may be fed back, and the payment result may be understood as “payment success” or “payment failure”, and if the payment fails, the payment result is It may also include the relevant failure reason for the payment failure, and the like.
  • the payment method may further include: extracting a payment result page link from the webpage payment message; and when the payment result of the payment server is received, to the webpage application Return to the payment results page and display the payment results on the payment results page.
  • the jump link of the payment result page may be extracted from the webpage payment message, and when receiving the payment result fed back by the payment server, jump to the payment result page according to the jump link of the payment result page, and The payment result fed back by the payment server is loaded into the payment result page.
  • the payment server performs payment according to the Native payment message and returns the payment result, so that the user can easily and intuitively understand the payment result, thereby improving the user experience.
  • a payment conversion method may also be provided. Specifically, it may be an independently developed payment conversion module, such as a payment conversion processing program, and may be integrated into an H5 web application. Alternatively, a separate program may exist independently, so that the payment link module can be processed by the payment conversion module to be converted into a native payment message for payment processing, that is, an H5 link (for example, one) The url) is converted to a native request and sent to the payment server for payment processing.
  • FIG. 3 it is a flowchart of a payment conversion method according to an embodiment of the present application. The method is used to convert a payment message of a web application, thereby enabling the web application to have the capability of a native application to enhance the user experience. The method includes the following steps:
  • the generation of the webpage link message may refer to the description in the related steps above, for example, the webpage link message is sent by the merchant server to the webpage application.
  • the webpage link message may be sent by the webpage application actively, or may be intercepted and obtained by the webpage application, and is not limited.
  • S320 Determine whether the webpage link message is a webpage payment message. Specifically, in the embodiment of the present application, it may be determined whether the webpage link message has a preset character string, and if it is determined to have a preset character string, the webpage link message is determined to be a webpage payment message.
  • the webpage payment message is converted into a native payment message.
  • the identifier of the webpage link message may be acquired, and the corresponding conversion template is determined according to the identifier, and the payment information in the webpage payment message is extracted, and finally, Payment information is added to the conversion template to generate a Native payment message.
  • the payment conversion module or the payment conversion processing program may also return the determination result to the webpage application when determining that the webpage link message is not the payment message, so that the webpage application program normally processes the webpage link message, for example, directly Jumping to the webpage corresponding to the webpage link, etc.; and when determining that the webpage link message is a payment message, the result may be returned to the webpage application, and the payment message may be converted into a native payment when the webpage application initiates the payment conversion request Message.
  • the payment conversion module or the payment conversion program can include two functional units, one can identify the webpage link message to determine whether it is a payment message, and one can be a webpage link message when the payment message is Convert to a Native message, you can also call the corresponding Native payment page, etc.
  • the method further includes transmitting a Native payment message to the payment server for payment, or returning the Native payment message to the web application to be sent to the payment server for payment by the web application. .
  • the present application also proposes a payment system.
  • the payment system may include a webpage application module 100, a payment server 200, and a conversion module 300.
  • the web application module 100 can be used to intercept web page link messages.
  • the web application module 100 can be understood as being located in a web application, such as a browser or the like.
  • the conversion module 300 can be an SDK (software development kit), and the conversion module 300 can be integrated into the web application module 100.
  • the webpage application module 100 can determine the input event operation of the user, and perform corresponding operation response according to the judgment result. For example, if the user performs a shopping operation, the merchant server generates a corresponding webpage link message according to the user's shopping operation, and sends the webpage link message to the webpage application module 100.
  • the web application module 100 intercepts the webpage link message and sends it to the conversion module 300.
  • the conversion module 300 can also directly intercept the webpage link message sent by the merchant server.
  • the conversion module 300 is configured to obtain a webpage link message sent by the webpage application module 100, and convert the webpage payment message into a native payment message when the webpage link message is determined to be a webpage payment message, and send the native payment message to the payment server 200. Pay.
  • the conversion module 300 can acquire the webpage link message generated by the webpage application module 100 in the webpage application according to the operation of the user, and When the webpage link message is obtained, it may be determined whether the webpage link message has a preset character string. If it is determined that the webpage link message has such a character string, the webpage link message may be determined to be a webpage payment message.
  • the preset character string can be understood as a character string representing the meaning of the payment message, such as alipay, pay, h5OrderInfo, etc., and the string can be preset according to the webpage payment message.
  • the webpage payment link provided by the provider to which the different webpage application belongs may be different, and the key string of the webpage payment link provided by the accessed provider may be extracted and stored as Determine whether the link message is the basis for the web page payment message.
  • the conversion module 300 may perform no processing on the webpage link message, and directly submit it to the webpage application module 100 according to the webpage application module 100.
  • the webpage link message is processed accordingly, for example, the webpage application module 100 continues to open the webpage page corresponding to the webpage according to the webpage link message.
  • webpage payment message and the native payment message of different payment service providers may be different.
  • the webpage payment message of the WeChat webpage application or the Taobao webpage application is different, so the identifier of the webpage link message needs to be To determine the source of the message, such as from the WeChat web application or Taobao web application, or other web applications.
  • the conversion module 300 may acquire the identifier of the webpage link message and determine a corresponding conversion template according to the identifier, and extract the payment in the webpage payment message. Information and add payment information to the conversion template to generate a Native payment message.
  • the corresponding conversion template is determined according to the source of the webpage payment message, for example, the US group has the conversion template of the US group, and the first store has the conversion template corresponding to the first store.
  • the conversion module 300 may first analyze the webpage link message when it is determined that the obtained webpage link message is a webpage payment message.
  • the webpage link message generally includes a URL link
  • the webpage link message may be Corresponding URL links are analyzed, such as segmentation, to obtain an identifier of the webpage link message to determine the source of the message, and then the corresponding conversion template may be determined according to the identifier, that is, the different sources of the webpage link message correspond to different ones.
  • Converting the template, and extracting the payment information in the webpage link message (the message is determined to be a webpage payment message at this time), wherein the payment information may be, for example, a payment amount, an order information, a token token (for identity authentication), and the like.
  • the payment information is added to the above-mentioned determined conversion template to obtain a Native payment message corresponding to the webpage payment message, that is, the transition from the H5 payment method to the Native payment method is realized.
  • the conversion module 300 can split the webpage payment message according to the rule, so that the webpage payment message can be effectively converted. Pay for the native message.
  • the conversion module 300 is further configured to acquire a Native payment page, display the Native payment page to the user, and receive a payment password input by the user in the Native payment page, and send the payment password to the payment server 200 for payment.
  • the payment server after receiving the Native payment message, the payment server generates a corresponding Native payment page, and the web application loads the Native payment page and displays the Native payment page to the user.
  • a native Native application can also be invoked to generate a Native payment page, such as calling a local wallet application (Native application) to generate a payment page.
  • the payment server 200 can be configured to make a payment based on the Native payment message and return the payment result. More specifically, the payment server 200 can evoke a native payment when receiving the Native payment message sent by the conversion module 300. And the payment is completed according to the native payment method, and after the payment is completed, the corresponding payment result can be fed back, and the payment result can be understood as “payment success” or “payment failure”, and if the payment fails, the payment result can also include The reason for the failure of the payment failure, etc.
  • the conversion module 300 is further configured to extract a payment result page link from the webpage payment message, and return a payment result page to the webpage application when receiving the payment result of the payment server 200, The payment results are displayed on the payment results page.
  • the conversion module 300 may extract a jump link of the payment result page from the webpage payment message, and when receiving the payment result fed back by the payment server 200, jump to the payment according to the jump link of the payment result page.
  • the result page loads the payment result fed back by the payment server 200 into the payment result page.
  • the payment system of the embodiment of the present application acquires a webpage link message sent by the webpage application module through the conversion module, and converts the webpage payment message into a native payment message when the webpage link message is determined to be a webpage payment message, and sends the native payment message To the payment server for payment, the payment server pays according to the Native payment message and returns the payment result.
  • the payment server pays according to the Native payment message and returns the payment result.
  • the webpage application module 100 in the webpage application can intercept the corresponding webpage link message according to the operation of the user, and send it to the conversion module 300.
  • the conversion module 300 can receive the webpage link message sent by the webpage application module 100, and determine whether the message has a preset character string to determine whether the message is a webpage payment message, and when the webpage link message is determined to be a webpage payment message, the conversion is performed.
  • the module 300 may convert the webpage payment message into a native payment message according to the information contained in the webpage payment message, and send the native payment message to the payment server 200.
  • the payment server 200 can evoke the Native payment, complete the payment according to the Native payment method, and feed back the payment result after completing the payment.
  • the conversion module 300 may also extract a payment result page link from the webpage payment message, and connect Upon receipt of the payment result of the payment server 200, the payment result page is returned to the web application module 100, and the payment result is displayed in the payment result page.
  • the webpage linkup message may be directly processed by the webpage application module 100 according to the webpage link message.
  • the processing for example, the webpage application module 100 continues to open the webpage page corresponding to the webpage according to the webpage link message.
  • FIG. 7 is a structural block diagram of a payment conversion apparatus according to an embodiment of the present application.
  • the payment conversion apparatus may include: an acquisition module 310, a determination module 320, a conversion module 330, and a transmission module 340.
  • the obtaining module 310 can be configured to obtain a webpage link message of the webpage application.
  • the determining module 320 can be configured to determine whether the webpage link message is a webpage payment message. Specifically, in the embodiment of the present application, the determining module 320 determines that the webpage link message is a webpage payment message when determining that the webpage link message has a preset character string.
  • the conversion module 330 can be configured to convert the webpage payment message into a native payment message when the determining module 320 determines that the webpage link message is a webpage payment message.
  • the conversion module 330 may include: a determination sub-module 331, a first extraction sub-module 332, and a generator. Module 333.
  • the determining sub-module 331 can be configured to obtain an identifier of the webpage link message, and determine a corresponding conversion template according to the identifier.
  • the first extraction sub-module 332 can be configured to extract payment information in a webpage payment message.
  • the generation sub-module 333 can be used to add payment information to the conversion template to generate a Native payment message.
  • the sending module 340 can be configured to send a Native payment message to the payment server for payment.
  • the payment conversion apparatus may further include a second extraction module 350 and a result returning module 360.
  • the second extraction module 350 is configured to extract a payment result page link from the webpage payment message.
  • the result return module 360 can be configured to return a payment result page to the web application when the payment result of the payment server is received, and display the payment result in the payment result page.
  • the payment conversion apparatus further includes a receiving module 370, a presentation module 380, and a payment module 390.
  • the receiving module 370 is configured to receive a Native payment page.
  • the presentation module 380 is configured to present the Native payment page to the user.
  • the payment module 390 is configured to receive a payment password input by the user in the Native payment page, and send the payment password to the payment server for payment.
  • the receiving module 370 receives a Native payment page from a payment server.
  • the receiving module 370 can also call a local Native application to generate a Native payment page, such as calling a local wallet application (Native application) to generate a payment page.
  • the payment conversion device of the embodiment of the present invention may obtain a webpage link message of the webpage application by the obtaining module, and the determining module determines whether the webpage link message is a webpage payment message, and the conversion module, when the determining module determines that the webpage link message is a webpage payment message, The webpage payment message is converted into a native payment message, and the sending module sends the native payment message to the payment server for payment.
  • first and second are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated.
  • features defining “first” or “second” may include at least one of the features, either explicitly or implicitly.
  • the meaning of "a plurality” is at least two, such as two, three, etc., unless specifically defined otherwise.
  • Any process or method description in the flowchart or otherwise described herein may be understood to include a Modules, segments or portions of code of one or more executable instructions for implementing steps of a particular logical function or process, and the scope of preferred embodiments of the application includes additional implementations, which may not be as shown or The order of discussion includes performing functions in a substantially simultaneous manner or in the reverse order, depending on the functionality involved, which should be understood by those skilled in the art to which the embodiments of the present application pertain.
  • portions of the application can be implemented in hardware, software, firmware, or a combination thereof.
  • multiple steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system.
  • a suitable instruction execution system For example, if implemented in hardware, as in another embodiment, it can be implemented by any one or combination of the following techniques well known in the art: having logic gates for implementing logic functions on data signals. Discrete logic circuits, application specific integrated circuits with suitable combinational logic gates, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.
  • each functional unit in each embodiment of the present application may be integrated into one processing module, or each unit may exist physically separately, or two or more units may be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the integrated modules, if implemented in the form of software functional modules and sold or used as stand-alone products, may also be stored in a computer readable storage medium.
  • the above mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like. While the embodiments of the present application have been shown and described above, it is understood that the above-described embodiments are illustrative and are not to be construed as limiting the scope of the present application. The embodiments are subject to variations, modifications, substitutions and variations.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种支付方法、系统、支付转换方法以及支付转换装置，其中，该方法包括：拦截网页应用程序的网页链接消息（S110）；判断网页链接消息是否为网页支付消息（S120）；如果判断为网页支付消息，则将网页支付消息转换为Native支付消息（S130）；以及将Native支付消息发送至支付服务器进行支付（S140）。该支付方法实现了能够实时地将网页应用程序的H5支付方式转换为Native支付方式，针对广大商户而言，对于从H5支付方式转向Native支付方式的过程中，节省了大量的人力、物力成本，并适合推广，具有通用性和普遍性等特点。

Description

支付方法、系统、支付转换方法以及支付转换装置
本申请要求2016年01月14日递交的申请号为201610024385.4、发明名称为“支付方法、系统、支付转换方法以及支付转换装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及数据处理技术领域，尤其涉及一种支付方法、系统、支付转换方法以及支付转换装置。
背景技术
目前，常用的无线支付方式主要有两种：一种是H5(超文本标记语言HTML 5)支付方式；另一种是原生Native支付方式。其中，H5支付方式主要依托于远程的H5网页界面进行的支付；Native支付方式主要依托于系统原生的本地界面进行的支付。
相较于Native支付方式，H5支付方式存在以下缺点：完全依赖网络、页面渲染慢、用户体验差、支付成功率低等。然而，从H5支付方式转向Native支付方式，并不简单，在整个转型过程中所需要花费的人力物力成本较大。相关技术中，某无线浏览器能够直接将H5支付方式转换为Native支付方式，但是，该无线浏览器将H5支付方式转换为Native支付方式的实现方式为自身的私有协议，也就是说只能应用于该浏览器中，如，只是单纯的转换在该浏览器上的应用程序中所加载的H5支付链接消息，而并不能转换其他应用程序中所加载的H5支付链接消息，导致该无线浏览器的支付方式转型的实现方式不具备可推广性。
发明内容
本申请的目的旨在至少在一定程度上解决上述的技术问题之一。
为此，本申请的第一个目的在于提出一种支付方法。该方法实现了能够实时地将网页应用程序的H5支付方式转换为Native支付方式，针对广大商户而言，对于从h5支付方式转向native支付方式的过程中，节省了大量的人力、物力成本，并适合推广，具有通用性和普遍性等特点。
本申请的第二个目的在于提出了一种支付系统。
本申请的第三个目的在于提出一种支付转换装置。
本申请的第四个目的在于提出一种支付转换方法。
为达上述目的，本申请第一方面实施例的支付方法，包括：拦截网页应用程序的网页链接消息；判断所述网页链接消息是否为网页支付消息；如果判断为所述网页支付消息，则将所述网页支付消息转换为Native支付消息；以及将所述Native支付消息发送至支付服务器进行支付。
本申请实施例的支付方法，拦截网页应用程序的网页链接消息，并判断网页链接消息是否为网页支付消息，如果判断为网页支付消息，则将网页支付消息转换为Native支付消息，并将Native支付消息发送至支付服务器进行支付。实现了能够实时地将网页应用程序的H5支付方式转换为Native支付方式，针对广大商户而言，对于从h5支付方式转向native支付方式的过程中，节省了大量的人力、物力成本，并且，可以使得广大商户提供的网页应用程序的支付性能更加稳定，提高了网页应用程序的支付成功率，提升了用户体验。另外，由于本申请实施例的支付方法可应用于任意具有支付功能的网页应用程序，所以适合推广，具有通用性和普遍性等特点。
为达上述目的，本申请第二方面实施例的支付系统，包括网页应用程序模块、支付服务器和转换模块，其中，所述网页应用程序模块，用于拦截网页链接消息；所述转换模块，用于获取所述网页应用程序模块发送的网页链接消息，并在判断所述网页链接消息为网页支付消息时，将所述网页支付消息转换为Native支付消息，以及将所述Native支付消息发送至所述支付服务器进行支付；所述支付服务器，用于根据所述Native支付消息进行支付并返回所述支付结果。
本申请实施例的支付系统，通过转换模块获取网页应用程序模块发送的网页链接消息，并在判断网页链接消息为网页支付消息时，将网页支付消息转换为Native支付消息，并将Native支付消息发送至支付服务器进行支付，支付服务器根据Native支付消息进行支付并返回支付结果。实现了能够实时地将网页应用程序的H5支付方式转换为Native支付方式，针对广大商户而言，对于从h5支付方式转向native支付方式的过程中，节省了大量的人力、物力成本，并且，可以使得广大商户提供的网页应用程序的支付性能更加稳定，提高了网页应用程序的支付成功率，提升了用户体验。另外，由于本申请实施例的支付方法可应用于任意具有支付功能的网页应用程序，所以适合推广，具有通用性和普遍性等特点。
为达上述目的，本申请第三方面实施例的支付转换装置，包括：获取模块，用于获取网页应用程序的网页链接消息；判断模块，用于判断所述网页链接消息是否为网页支 付消息；转换模块，用于在所述判断模块判断所述网页链接消息为所述网页支付消息时，将所述网页支付消息转换为Native支付消息。
本申请实施例的支付转换装置，可通过获取模块获取网页应用程序的网页链接消息，判断模块判断网页链接消息是否为网页支付消息，转换模块在判断模块判断网页链接消息为网页支付消息时，将网页支付消息转换为Native支付消息，发送模块将Native支付消息发送至支付服务器进行支付。实现了能够实时地将网页应用程序的H5支付方式转换为Native支付方式，针对广大商户而言，对于从h5支付方式转向native支付方式的过程中，节省了大量的人力、物力成本，并且，可以使得广大商户提供的网页应用程序的支付性能更加稳定，提高了网页应用程序的支付成功率，提升了用户体验。另外，由于本申请实施例的支付方法可应用于任意具有支付功能的网页应用程序，所以适合推广，具有通用性和普遍性等特点。
为达到上述目的，本申请实施例第四方面还提出了一种支付转换方法，包括以下步骤：获取网页应用程序的网页链接消息；判断所述网页链接消息是否为网页支付消息；如果判断为所述网页支付消息，则将所述网页支付消息转换为Native支付消息。
本申请实施例的支付转换方法，能够实时地将网页应用程序的H5支付方式转换为Native支付方式，针对广大商户而言，对于从h5支付方式转向native支付方式的过程中，节省了大量的人力、物力成本，并且，可以使得广大商户提供的网页应用程序的支付性能更加稳定，提高了网页应用程序的支付成功率，提升了用户体验。另外，由于本申请实施例的支付方法可应用于任意具有支付功能的网页应用程序，所以适合推广，具有通用性和普遍性等特点。
本申请附加的方面和优点将在下面的描述中部分给出，部分将从下面的描述中变得明显，或通过本申请的实践了解到。
附图说明
本申请的上述和/或附加的方面和优点从结合下面附图对实施例的描述中将变得明显和容易理解，其中：
图1是根据本申请一个实施例的支付方法的流程图；
图2是根据本申请另一个实施例的支付方法的流程图；
图3是根据本申请一个实施例的支付转换方法的流程图；
图4是根据本申请一个实施例的支付系统的结构框图；
图5是根据本申请一个具体实施例的支付系统的示例图；
图6是根据本申请一个实施例的支付转换装置的结构框图；
图7是根据本申请另一个实施例的支付转换装置的结构框图；
图8是根据本申请又一个实施例的支付转换装置的结构框图。
具体实施方式
下面详细描述本申请的实施例，所述实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的元件或具有相同或类似功能的元件。下面通过参考附图描述的实施例是示例性的，旨在用于解释本申请，而不能理解为对本申请的限制。
本申请提供的支付方法，该支付过程可以包括：拦截网页应用程序的网页链接消息；判断所述网页链接消息是否为网页支付消息；如果判断为所述网页支付消息，则将所述网页支付消息转换为Native支付消息；以及将所述Native支付消息发送至支付服务器进行支付。该支付方法可以作为一个独立的应用，例如H5应用，或者一个H5页面程序来实现上述支付过程，即对于网页程序上的一个网页链接消息可进行拦截，并可根据链接消息确定为支付消息时，可转换成Native支付消息进行支付处理。
图1是根据本申请一个实施例的支付方法的流程图。需要说明的是，本申请实施例的支付方法可应用于任意具有网页支付功能的网页应用程序上。其中，该网页应用程序可以为浏览器上，也可以是承载于例如终端的操作系统中，即网页应用程序以单独的程序方式安装并运行于移动终端或终端的操作系统中。在本申请的实施例中，网页应用程序是基于HTML(超文本标记语言)开发的应用程序，例如基于H5(第5代HTML)，而Native应用程序(本地应用程序)是指基于移动终端的操作系统，例如iOS、Android、WP等，并使用原生程式编写运行的第三方应用程序。在本申请的实施例中，网页应用程序产生的消息为网页链接消息，Native应用程序产生的消息为Native消息。在本申请的实施例中可以将网页应用程序的网页链接进行转换，转换为Native支付消息，从而使得网页应用程序能够具有Native应用程序的能力，增强用户体验。
如图1所示，该支付方法可以包括：
S110，拦截网页应用程序的网页链接消息。
可以理解，用户在使用网页应用程序，并对该网页应用程序进行输入事件操作时，该网页应用程序可判断用户的输入事件操作，并根据判断结果进行相应的操作响应，比如，生成相应的网页链接消息。例如，以网页应用程序为淘宝应用程序为例，当用户在 淘宝应用程序上想对某个产品进行购买支付操作时，淘宝应用程序会根据用户的操作生成对应的网页链接消息，如接收到用户针对“确认下单”输入的点击操作，则可生成对应的网页支付链接消息；又如，当用户在淘宝应用程序上想对某个产品进行进一步了解，可点击该产品所在网页页面上的详情页面，此时淘宝应用程序可根据用户的操作生成针对详情页面的网页链接消息。其中，上述的生成网页链接消息，具体可以是指网页用户程序可以将用户的输入事件操作发送至对应的服务器，由服务器对该操作事件处理并返回一个网页链接消息，例如，对于上述的确认下单操作，可以由淘宝应用程序将其发送给淘宝服务器，由淘宝服务器返回一个支付链接消息，等等。具体实现形式可以根据具体场景有不同实现。
在本步骤中，在用户使用网页应用程序的过程中，可实时拦截网页应用程序根据用户的操作而获取的网页链接消息。
S120，判断网页链接消息是否为网页支付消息。
具体而言，在本申请的实施例中，可判断网页链接消息中是否具有预设字符串，如果判断具有预设字符串，则判断网页链接消息为网页支付消息。其中，该预设字符串可理解为具有代表支付消息意思的字符串，如alipay、pay、h5OrderInfo等，该字符串可以根据网页支付消息进行预先设置。可以理解，在实际应用中，不同的网页应用程序所属的提供商所提供的网页支付链接可能不同，可将已接入的提供商所提供的网页支付链接的关键字符串进行提取并存储以作为判断链接消息是否为网页支付消息的依据。
更具体地，在拦截到网页应用程序的网页链接消息时，可判断该网页链接消息中是否具有如上述等这种代表支付消息意思的字符串，如果判断该网页链接消息具有这种字符串，则可判定该网页链接消息为网页支付消息。
需要说明的是，在本申请的实施例中，如果判断网页链接消息不为网页支付消息，则可对该网页链接消息不做任何处理，直接交由网页应用程序根据该网页链接消息进行相应的处理，如网页应用程序根据该网页链接消息继续打开该消息对应的网页页面。
S130，如果判断为网页支付消息，则将网页支付消息转换为Native支付消息。
可以理解，不同的支付服务提供商所具有的网页支付消息和Native支付消息可能不太一样，例如，微信网页应用程序或淘宝网页应用程序的网页支付消息就不同，因此需要根据网页链接消息的标识来确定该消息的来源，例如来自微信网页应用程序或是淘宝网页应用程序、或是其他网页应用程序等。
具体而言，在本申请的实施例中，当判断为网页支付消息时，可获取网页链接消息 的标识，并根据标识确定对应的转换模板，并提取网页支付消息中的支付信息，最后，将支付信息添加至转换模板以生成Native支付消息。在本申请的实施例中，根据网页支付消息的来源来确定对应的转换模板，例如美团具有美团的转换模板，而一号店具有一号店对应的转换模板。
更具体地，在判断拦截到的网页链接消息为网页支付消息时，可先对该网页链接消息进行分析，可以理解，网页链接消息一般包含一个URL链接，在本步骤中，可对该网页链接消息所对应的URL链接进行如分割等分析，以得到该网页链接消息的标识，以确定该消息的来源，之后，可根据该标识来确定对应的转换模板，即网页链接消息的不同来源对应不同的转换模板，并提取该网页链接消息(此时已判断该消息为网页支付消息)中的支付信息，其中，该支付信息例如可以是支付金额、订单信息、令牌token(用以身份认证)等，最后，将该支付信息添加到上述确定的转换模板中，得到该网页支付消息对应的Native支付消息，即实现了将H5支付方式向Native支付方式的转型。
也就是说，支付信息在网页支付(即H5支付)链接中的排放具有明确的规则，因此，可根据该规则对网页支付消息进行拆分，从而可以有效地将该网页支付消息转换为Native支付消息。
S140，将Native支付消息发送至支付服务器进行支付。
具体地，在将网页支付消息转换为Native支付消息之后，可将该Native支付消息发送到支付服务器，以使支付服务器按照Native支付方式完成支付。由此，实现了将网页应用程序的H5支付方式转换为Native支付方式，使得网页应用程序的支付性能更加稳定，提高了该网页应用程序的支付成功率，提升了用户体验。
上述的各执行步骤可以是由一个执行主体执行，也可以是由不同的执行主体来实现，该执行主体可以是指一个程序模块，或者一个功能模块，根据具体场景可以有不同定义。
本申请实施例的支付方法，拦截网页应用程序的网页链接消息，并判断网页链接消息是否为网页支付消息，如果判断为网页支付消息，则将网页支付消息转换为Native支付消息，并将Native支付消息发送至支付服务器进行支付。实现了能够实时地将网页应用程序的H5支付方式转换为Native支付方式，针对广大商户而言，对于从h5支付方式转向native支付方式的过程中，节省了大量的人力、物力成本，并且，可以使得广大商户提供的网页应用程序的支付性能更加稳定，提高了网页应用程序的支付成功率，提升了用户体验。另外，由于本申请实施例的支付方法可应用于任意具有支付功能的网页应用程序，所以适合推广，具有通用性和普遍性等特点。
图2是根据本申请另一个实施例的支付方法的流程图。
为了提升用户体验，使得用户了解支付结果，在本申请的实施例中，支付服务器根据Native支付消息进行支付之后，可返回相应的支付结果。具体地，如图2所示，该支付方法可以包括：
S210，拦截网页应用程序的网页链接消息。
S220，判断网页链接消息是否为网页支付消息。
具体而言，在本申请的实施例中，可判断网页链接消息中是否具有预设字符串，如果判断具有预设字符串，则判断网页链接消息为网页支付消息。
S230，如果判断为网页支付消息，则将网页支付消息转换为Native支付消息。
具体而言，在本申请的实施例中，当判断为网页支付消息时，可获取网页链接消息的标识，并根据标识确定对应的转换模板，并提取网页支付消息中的支付信息，最后，将支付信息添加至转换模板以生成Native支付消息。
S240，将Native支付消息发送至支付服务器进行支付。
S250，接收支付服务器返回的Native支付页面，并将Native支付页面展示给用户。在本申请的实施例中，支付服务器接收到Native支付消息之后会生成相应的Native支付页面，网页应用程序加载该Native支付页面，并将Native支付页面展示给用户。在本申请的另一个实施例中，还可以调用本地的Native应用程序来生成Native支付页面，例如调用本地的钱包应用程序(Native应用程序)来生成支付页面。
S260，接收用户在所述Native支付页面中输入的支付密码，并将支付密码发送至支付服务器进行支付。
S270，支付服务器根据支付密码进行支付并返回支付结果。
具体地，支付服务器按照支付密码完成支付，并在完成支付之后，可将相应的支付结果进行反馈，该支付结果可理解为“支付成功”或“支付失败”，若支付失败，则该支付结果也可包含该支付失败的相关失败原因等。
在本申请的实施例中，在如图2所示的基础上，该支付方法还可包括：从网页支付消息中提取支付结果页链接；当接收到支付服务器的支付结果时，向网页应用程序返回支付结果页，并在支付结果页中展示支付结果。更具体地，可从网页支付消息中提取出支付结果页的跳转链接，并在接收到支付服务器反馈的支付结果时，根据该支付结果页的跳转链接跳转到该支付结果页，并将支付服务器反馈的支付结果加载到该支付结果页中。由此，用户可以方便且直观地了解到支付结果，同时也保证了在完成Native支付之 后，继续返回到原网页应用程序中。
本申请实施例的支付方法，在将支付密码发送至支付服务器进行支付之后，支付服务器根据Native支付消息进行支付并返回支付结果，可以使得用户方便且直观地了解到支付结果，提升了用户体验。
本申请实施例中，还可提供一种支付转换方法，具体而言，可以是一个独立开发的支付转换模块，例如一个支付转换处理程序，并可将该程序集成在一H5网页应用程序中，或者也可以是单独的一个程序独立存在，这样，可通过该支付转换模块来实现对网页应用程序上的支付链接消息进行处理，转换成Native支付消息进行支付处理，也就是将H5链接(例如一个url)转换成Native请求发送至支付服务器来进行支付处理。如图3所示，为本申请实施例的支付转换方法流程图。该方法用于对网页应用程序的支付消息进行转换，从而使得网页应用程序能够具有Native应用程序的能力，增强用户体验。该方法包括以下步骤：
S310，获取网页应用程序的网页链接消息。
在本申请实施例中，网页链接消息的生成可参考上述相关步骤中的说明，例如该网页链接消息由商家服务器发送至网页应用程序。获取网页链接消息，具体可以是由网页应用程序主动发送过来，或者主动从网页应用程序进行拦截获取等，具体不做限定。
S320，判断所述网页链接消息是否为网页支付消息。具体而言，在本申请的实施例中，可判断网页链接消息中是否具有预设字符串，如果判断具有预设字符串，则判断网页链接消息为网页支付消息。
S330，如果判断为所述网页支付消息，则将所述网页支付消息转换为Native支付消息。具体而言，在本申请的实施例中，当判断为网页支付消息时，可获取网页链接消息的标识，并根据标识确定对应的转换模板，并提取网页支付消息中的支付信息，最后，将支付信息添加至转换模板以生成Native支付消息。
本申请实施例中，支付转换模块或支付转换处理程序也可以在判断网页链接消息不是支付消息时，将判断结果返回给网页应用程序，以便网页应用程序对该网页链接消息进行正常处理，例如直接跳转到该网页链接对应的网页等；且在判断网页链接消息为支付消息时，还可将结果返回给网页应用程序，并可由网页应用程序发起支付转换请求时，将支付消息转换成Native支付消息。可以理解的是，该支付转换模块或者支付转换程序可以包括两个功能单元，一个可以对网页链接消息进行识别，以确定是否为支付消息，一个可以是对网页链接消息为支付消息时，将其转换成Native消息，还可以调用相应的 Native支付页面等。
在本申请的实施例中，该方法还包括将Native支付消息发送至支付服务器进行支付，或者，将Native支付消息返回至网页应用程序，以通过所述网页应用程序发送至所述支付服务器进行支付。
为了实现上述实施例，本申请还提出了一种支付系统。
图4是根据本申请一个实施例的支付系统的结构框图。如图4所示，该支付系统可以包括：网页应用程序模块100、支付服务器200和转换模块300。
具体地，网页应用程序模块100可用于拦截网页链接消息。其中，网页应用程序模块100可理解为位于网页应用程序，例如浏览器等。而转换模块300可为SDK(软件开发包)，该转换模块300可集成在网页应用程序模块100之中。
可以理解，用户在使用网页应用程序，并对该网页应用程序进行输入事件操作时，网页应用程序模块100可判断用户的输入事件操作，并根据判断结果进行相应的操作响应。例如用户进行购物操作，商家服务器会根据该用户的购物操作生成相应的网页链接消息，并发送至网页应用程序模块100。网页应用程序模块100对该网页链接消息进行拦截，并发送至转换模块300。当然在本发明的其他实施例中，转换模块300也可直接进行拦截，对商家服务器发送的网页链接消息进行拦截。
转换模块300可用于获取网页应用程序模块100发送的网页链接消息，并在判断网页链接消息为网页支付消息时，将网页支付消息转换为Native支付消息，以及将Native支付消息发送至支付服务器200进行支付。
具体而言，在申请的实施例中，在用户使用网页应用程序的过程中，转换模块300可实时获取网页应用程序中的网页应用程序模块100根据用户的操作而生成的网页链接消息，并在获取到网页链接消息时，可判断该网页链接消息中是否具有预设字符串，如果判断该网页链接消息具有这种字符串，则可判定该网页链接消息为网页支付消息。其中，该预设字符串可理解为具有代表支付消息意思的字符串，如alipay、pay、h5OrderInfo等，该字符串可以根据网页支付消息进行预先设置。可以理解，在实际应用中，不同的网页应用程序所属的提供商所提供的网页支付链接可能不同，可将已接入的提供商所提供的网页支付链接的关键字符串进行提取并存储以作为判断链接消息是否为网页支付消息的依据。
需要说明的是，在本申请的实施例中，转换模块300在判断网页链接消息不为网页支付消息时，可对该网页链接消息不做任何处理，直接交由网页应用程序模块100根据 该网页链接消息进行相应的处理，如网页应用程序模块100根据该网页链接消息继续打开该消息对应的网页页面。
可以理解，不同的支付服务提供商所具有的网页支付消息和Native支付消息可能不太一样，例如，微信网页应用程序或淘宝网页应用程序的网页支付消息就不同，因此需要根据网页链接消息的标识来确定该消息的来源，例如来自微信网页应用程序或是淘宝网页应用程序、或是其他网页应用程序等。
具体而言，在本申请的实施例中，在判断网页链接消息为网页支付消息时，转换模块300可获取网页链接消息的标识并根据标识确定对应的转换模板，以及提取网页支付消息中的支付信息，并将支付信息添加至该转换模板以生成Native支付消息。在本申请的实施例中，根据网页支付消息的来源来确定对应的转换模板，例如美团具有美团的转换模板，而一号店具有一号店对应的转换模板。
更具体地，转换模块300在判断获取到的网页链接消息为网页支付消息时，可先对该网页链接消息进行分析，可以理解，网页链接消息一般包含一个URL链接，即可对该网页链接消息所对应的URL链接进行如分割等分析，以得到该网页链接消息的标识，以确定该消息的来源，之后，可根据该标识来确定对应的转换模板，即网页链接消息的不同来源对应不同的转换模板，并提取该网页链接消息(此时已判断该消息为网页支付消息)中的支付信息，其中，该支付信息例如可以是支付金额、订单信息、令牌token(用以身份认证)等，最后，将该支付信息添加到上述确定的转换模板中，得到该网页支付消息对应的Native支付消息，即实现了将H5支付方式向Native支付方式的转型。
也就是说，支付信息在网页支付(即H5支付)链接中的排放具有明确的规则，因此，转换模块300可根据该规则对网页支付消息进行拆分，从而可以有效地将该网页支付消息转换为Native支付消息。
转换模块300还用于获取Native支付页面，并将Native支付页面展示给用户，以及接收用户在Native支付页面中输入的支付密码，并将支付密码发送至支付服务器200进行支付。在本申请的实施例中，支付服务器接收到Native支付消息之后会生成相应的Native支付页面，网页应用程序加载该Native支付页面，并将Native支付页面展示给用户。在本申请的另一个实施例中，还可以调用本地的Native应用程序来生成Native支付页面，例如调用本地的钱包应用程序(Native应用程序)来生成支付页面。
支付服务器200可用于根据Native支付消息进行支付并返回支付结果。更具体地，支付服务器200在接收到转换模块300发送的Native支付消息时，可唤起Native支付， 并按照Native支付方式完成支付，并在完成支付之后，可将相应的支付结果进行反馈，该支付结果可理解为“支付成功”或“支付失败”，若支付失败，则该支付结果也可包含该支付失败的相关失败原因等。
进一步地，在本申请的一个实施例中，转换模块300还可用于从网页支付消息中提取支付结果页链接，以及在接收到支付服务器200的支付结果时，向网页应用程序返回支付结果页，并在支付结果页中展示支付结果。
更具体地，转换模块300可从网页支付消息中提取出支付结果页的跳转链接，并在接收到支付服务器200反馈的支付结果时，根据该支付结果页的跳转链接跳转到该支付结果页，并将支付服务器200反馈的支付结果加载到该支付结果页中。由此，使得用户可以方便且直观地了解到支付结果，同时也保证了在完成Native支付之后，继续返回到原网页应用程序中，提升了用户体验。
本申请实施例的支付系统，通过转换模块获取网页应用程序模块发送的网页链接消息，并在判断网页链接消息为网页支付消息时，将网页支付消息转换为Native支付消息，并将Native支付消息发送至支付服务器进行支付，支付服务器根据Native支付消息进行支付并返回支付结果。实现了能够实时地将网页应用程序的H5支付方式转换为Native支付方式，针对广大商户而言，对于从h5支付方式转向native支付方式的过程中，节省了大量的人力、物力成本，并且，可以使得广大商户提供的网页应用程序的支付性能更加稳定，提高了网页应用程序的支付成功率，提升了用户体验。另外，由于本申请实施例的支付方法可应用于任意具有支付功能的网页应用程序，所以适合推广，具有通用性和普遍性等特点。
为了使得本领域的技术人员能够更加清楚地了解本发明，下面可举例说明。
举例而言，如图5所示，在用户使用网页应用程序进行操作时，网页应用程序中的网页应用程序模块100可根据用户的操作拦截相应的网页链接消息，并发送至转换模块300。转换模块300可接收网页应用程序模块100发送的网页链接消息，并判断该消息中是否具有预设字符串以判断该消息是否为网页支付消息，当判断该网页链接消息为网页支付消息时，转换模块300可根据该网页支付消息中所包含的信息，将该网页支付消息转换为Native支付消息，并将该Native支付消息发送到支付服务器200。支付服务器200在接收到该Native支付消息时，可唤起Native支付，并按照Native支付方式完成支付，并在完成支付之后，反馈支付结果。
在本实施例中，转换模块300还可从网页支付消息中提取支付结果页链接，并在接 收到支付服务器200的支付结果时，向网页应用程序模块100返回支付结果页，并在支付结果页中展示支付结果。
可以理解，如图5所示，转换模块300判断网页链接消息不为网页支付消息时，可对该网页链接消息不做任何处理，直接交由网页应用程序模块100根据该网页链接消息进行相应的处理，如网页应用程序模块100根据该网页链接消息继续打开该消息对应的网页页面。
可以理解，上述的各功能模块可以单独存在，并可具有独立的功能实现，本申请实施例不做限制。
与上述几种实施例提供的支付转换方法相对应，本发明的一种实施例还提供一种支付转换装置，由于本发明实施例提供的支付转换装置与上述几种实施例提供的支付转换方法具有相同或相似的技术特征，因此在前述支付转换方法的实施方式也适用于本实施例提供的支付转换装置，在本实施例中不再详细描述。图7是根据本申请一个实施例的支付转换装置的结构框图。如图7所示，该支付转换装置可以包括：获取模块310、判断模块320、转换模块330和发送模块340。
其中，获取模块310可用于获取网页应用程序的网页链接消息。
判断模块320可用于判断网页链接消息是否为网页支付消息。具体而言，在本申请的实施例中，判断模块320在判断网页链接消息中具有预设字符串时，判断网页链接消息为网页支付消息。
转换模块330可用于在判断模320块判断网页链接消息为网页支付消息时，将网页支付消息转换为Native支付消息。
具体而言，在本申请的一个实施例中，在如图6所示的基础上，如图7所示，该转换模块330可以包括：确定子模块331、第一提取子模块332和生成子模块333。
其中，确定子模块331可用于获取网页链接消息的标识，并根据标识确定对应的转换模板。
第一提取子模块332可用于提取网页支付消息中的支付信息。
生成子模块333可用于将支付信息添加至转换模板以生成Native支付消息。
发送模块340可用于将Native支付消息发送至支付服务器进行支付。
进一步地，在本申请的一个实施例中，如图8所示，该支付转换装置还可包括第二提取模块350和结果返回模块360。
其中，第二提取模块350可用于从网页支付消息中提取支付结果页链接。
结果返回模块360可用于当接收到支付服务器的支付结果时，向网页应用程序返回支付结果页，并在支付结果页中展示支付结果。
在本申请的其他实施例中，支付转换装置还包括接收模块370、展示模块380和支付模块390。其中，接收模块370用于接收Native支付页面。展示模块380用于将Native支付页面展示给用户。支付模块390用于接收用户在Native支付页面中输入的支付密码，并将支付密码发送至支付服务器进行支付。在本申请的实施例中，接收模块370从支付服务器接收Native支付页面。在本申请的另一个实施例中，接收模块370还可以调用本地的Native应用程序来生成Native支付页面，例如调用本地的钱包应用程序(Native应用程序)来生成支付页面。
本申请实施例的支付转换装置，可通过获取模块获取网页应用程序的网页链接消息，判断模块判断网页链接消息是否为网页支付消息，转换模块在判断模块判断网页链接消息为网页支付消息时，将网页支付消息转换为Native支付消息，发送模块将Native支付消息发送至支付服务器进行支付。实现了能够实时地将网页应用程序的H5支付方式转换为Native支付方式，针对广大商户而言，对于从h5支付方式转向native支付方式的过程中，节省了大量的人力、物力成本，并且，可以使得广大商户提供的网页应用程序的支付性能更加稳定，提高了网页应用程序的支付成功率，提升了用户体验。另外，由于本申请实施例的支付方法可应用于任意具有支付功能的网页应用程序，所以适合推广，具有通用性和普遍性等特点。
在本申请的描述中，需要理解的是，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括至少一个该特征。在本申请的描述中，“多个”的含义是至少两个，例如两个，三个等，除非另有明确具体的限定。
在本说明书的描述中，参考术语“一个实施例”、“一些实施例”、“示例”、“具体示例”、或“一些示例”等的描述意指结合该实施例或示例描述的具体特征、结构、材料或者特点包含于本申请的至少一个实施例或示例中。在本说明书中，对上述术语的示意性表述不必须针对的是相同的实施例或示例。而且，描述的具体特征、结构、材料或者特点可以在任一个或多个实施例或示例中以合适的方式结合。此外，在不相互矛盾的情况下，本领域的技术人员可以将本说明书中描述的不同实施例或示例以及不同实施例或示例的特征进行结合和组合。
流程图中或在此以其他方式描述的任何过程或方法描述可以被理解为，表示包括一 个或更多个用于实现特定逻辑功能或过程的步骤的可执行指令的代码的模块、片段或部分，并且本申请的优选实施方式的范围包括另外的实现，其中可以不按所示出或讨论的顺序，包括根据所涉及的功能按基本同时的方式或按相反的顺序，来执行功能，这应被本申请的实施例所属技术领域的技术人员所理解。
应当理解，本申请的各部分可以用硬件、软件、固件或它们的组合来实现。在上述实施方式中，多个步骤或方法可以用存储在存储器中且由合适的指令执行系统执行的软件或固件来实现。例如，如果用硬件来实现，和在另一实施方式中一样，可用本领域公知的下列技术中的任一项或他们的组合来实现：具有用于对数据信号实现逻辑功能的逻辑门电路的离散逻辑电路，具有合适的组合逻辑门电路的专用集成电路，可编程门阵列(PGA)，现场可编程门阵列(FPGA)等。
本技术领域的普通技术人员可以理解实现上述实施例方法携带的全部或部分步骤是可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，该程序在执行时，包括方法实施例的步骤之一或其组合。
此外，在本申请各个实施例中的各功能单元可以集成在一个处理模块中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。所述集成的模块如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。
上述提到的存储介质可以是只读存储器，磁盘或光盘等。尽管上面已经示出和描述了本申请的实施例，可以理解的是，上述实施例是示例性的，不能理解为对本申请的限制，本领域的普通技术人员在本申请的范围内可以对上述实施例进行变化、修改、替换和变型。

Claims (25)

  1. 一种支付方法，其特征在于，包括以下步骤：
    拦截网页应用程序的网页链接消息；
    判断所述网页链接消息是否为网页支付消息；
    如果判断为所述网页支付消息，则将所述网页支付消息转换为Native支付消息；以及
    将所述Native支付消息发送至支付服务器进行支付。
  2. 如权利要求1所述的支付方法，其特征在于，所述将所述网页支付消息转换为Native支付消息具体包括：
    获取所述网页链接消息的标识，并根据所述标识确定对应的转换模板；
    提取所述网页支付消息中的支付信息；
    将所述支付信息添加至所述转换模板以生成所述Native支付消息。
  3. 如权利要求1所述的支付方法，其特征在于，还包括：
    所述支付服务器根据所述Native支付消息进行支付并返回所述支付结果。
  4. 如权利要求3所述的支付方法，其特征在于，还包括：
    从所述网页支付消息中提取支付结果页链接；
    当接收到所述支付服务器的所述支付结果时，向所述网页应用程序返回所述支付结果页，并在所述支付结果页中展示所述支付结果。
  5. 如权利要求1所述的支付方法，其特征在于，所述判断所述网页链接消息是否为网页支付消息具体包括：
    判断所述网页链接消息中是否具有预设字符串；
    如果判断具有所述预设字符串，则判断所述网页链接消息为所述网页支付消息。
  6. 如权利要求1所述的支付方法，其特征在于，在所述将所述Native支付消息发送至支付服务器进行支付之后，还包括：
    获取Native支付页面，并将Native支付页面展示给用户；以及
    接收所述用户在所述Native支付页面中输入的支付密码，并将所述支付密码发送至所述支付服务器进行支付。
  7. 如权利要求6所述的支付方法，其特征在于，所述获取Native支付页面具体包括：
    接收所述支付服务器返回的Native支付页面；
    或者调用本地Native应用程序的Native支付页面。
  8. 一种支付系统，其特征在于，包括网页应用程序模块、支付服务器和转换模块，其中，
    所述网页应用程序模块，用于拦截网页链接消息；
    所述转换模块，用于获取所述网页应用程序模块发送的网页链接消息，并在判断所述网页链接消息为网页支付消息时，将所述网页支付消息转换为Native支付消息，以及将所述Native支付消息发送至所述支付服务器进行支付；
    所述支付服务器，用于根据所述Native支付消息进行支付并返回所述支付结果。
  9. 如权利要求8所述的支付系统，其特征在于，所述转换模块获取所述网页链接消息的标识并根据所述标识确定对应的转换模板，以及提取所述网页支付消息中的支付信息，并将所述支付信息添加至所述转换模板以生成所述Native支付消息。
  10. 如权利要求8所述的支付系统，其特征在于，所述转换模块，还用于从所述网页支付消息中提取支付结果页链接，以及当接收到所述支付服务器的所述支付结果时，向所述网页应用程序返回所述支付结果页，并在所述支付结果页中展示所述支付结果。
  11. 如权利要求8所述的支付系统，其特征在于，所述转换模块在判断所述网页链接消息中具有预设字符串时，判断所述网页链接消息为所述网页支付消息。
  12. 如权利要求8所述的支付系统，其特征在于，所述转换模块，还用于获取Native支付页面，并将Native支付页面展示给用户，以及接收所述用户在所述Native支付页面中输入的支付密码，并将所述支付密码发送至所述支付服务器进行支付。
  13. 如权利要求12所述的支付系统，其特征在于，所述转换模块接收所述支付服务器返回的Native支付页面，或者调用本地Native应用程序的Native支付页面。
  14. 一种支付转换方法，其特征在于，包括以下步骤：
    获取网页应用程序的网页链接消息；
    判断所述网页链接消息是否为网页支付消息；
    如果判断为所述网页支付消息，则将所述网页支付消息转换为Native支付消息。
  15. 如权利要求14所述的支付转换方法，其特征在于，还包括：
    将所述Native支付消息发送至支付服务器进行支付；
    或者，将所述Native支付消息返回至所述网页应用程序，以通过所述网页应用程序发送至所述支付服务器进行支付。
  16. 如权利要求14所述的支付转换方法，其特征在于，所述将所述网页支付消息 转换为Native支付消息具体包括：
    获取所述网页链接消息的标识，并根据所述标识确定对应的转换模板；
    提取所述网页支付消息中的支付信息；
    将所述支付信息添加至所述转换模板以生成所述Native支付消息。
  17. 如权利要求14所述的支付转换方法，其特征在于，还包括：
    从所述网页支付消息中提取支付结果页链接；
    当接收到所述支付服务器的所述支付结果时，向所述网页应用程序返回所述支付结果页，并在所述支付结果页中展示所述支付结果。
  18. 如权利要求14所述的支付转换方法，其特征在于，所述判断所述网页链接消息是否为网页支付消息具体包括：
    判断所述网页链接消息中是否具有预设字符串；
    如果判断具有所述预设字符串，则判断所述网页链接消息为所述网页支付消息。
  19. 如权利要求15所述的支付转换方法，其特征在于，在所述将所述Native支付消息发送至支付服务器进行支付之后，还包括：
    获取Native支付页面，并将Native支付页面展示给用户；以及
    接收所述用户在所述Native支付页面中输入的支付密码，并将所述支付密码发送至所述支付服务器进行支付。
  20. 一种支付转换装置，其特征在于，包括：
    获取模块，用于获取网页应用程序的网页链接消息；
    判断模块，用于判断所述网页链接消息是否为网页支付消息；
    转换模块，用于在所述判断模块判断所述网页链接消息为所述网页支付消息时，将所述网页支付消息转换为Native支付消息。
  21. 如权利要求20所述的支付转换装置，其特征在于，还包括：
    发送模块，用于将所述Native支付消息发送至支付服务器进行支付。
  22. 如权利要求20所述的支付转换装置，其特征在于，所述转换模块具体包括：
    确定子模块，用于获取所述网页链接消息的标识，并根据所述标识确定对应的转换模板；
    第一提取子模块，用于提取所述网页支付消息中的支付信息；
    生成子模块，用于将所述支付信息添加至所述转换模板以生成所述Native支付消息。
  23. 如权利要求20所述的支付转换装置，其特征在于，还包括：
    第二提取模块，用于从所述网页支付消息中提取支付结果页链接；
    结果返回模块，用于当接收到所述支付服务器的所述支付结果时，向所述网页应用程序返回所述支付结果页，并在所述支付结果页中展示所述支付结果。
  24. 如权利要求20所述的支付转换装置，其特征在于，所述判断模块在判断所述网页链接消息中具有预设字符串时，判断所述网页链接消息为所述网页支付消息。
  25. 如权利要求20所述的支付转换装置，其特征在于，还包括：
    接收模块，用于接收Native支付页面；
    展示模块，用于将Native支付页面展示给用户；
    支付模块，用于接收所述用户在所述Native支付页面中输入的支付密码，并将所述支付密码发送至所述支付服务器进行支付。
PCT/CN2017/070354 2016-01-14 2017-01-06 支付方法、系统、支付转换方法以及支付转换装置 WO2017121283A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610024385.4A CN106971298A (zh) 2016-01-14 2016-01-14 支付方法、系统、支付转换方法以及支付转换装置
CN201610024385.4 2016-01-14

Publications (1)

Publication Number Publication Date
WO2017121283A1 true WO2017121283A1 (zh) 2017-07-20

Family

ID=59310812

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/070354 WO2017121283A1 (zh) 2016-01-14 2017-01-06 支付方法、系统、支付转换方法以及支付转换装置

Country Status (3)

Country Link
CN (1) CN106971298A (zh)
TW (1) TW201800993A (zh)
WO (1) WO2017121283A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115103320A (zh) * 2022-07-11 2022-09-23 中移互联网有限公司 消息的传输方法、装置、电子设备及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107608798A (zh) * 2017-08-04 2018-01-19 阿里巴巴集团控股有限公司 一种业务处理方法及设备
CN109840998B (zh) * 2017-11-27 2021-10-22 北京聚利科技有限公司 车辆与油枪匹配的方法及第一集线器
CN109120676B (zh) * 2018-07-24 2021-08-17 阿里巴巴集团控股有限公司 提高信息安全的方法及装置和电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120159310A1 (en) * 2010-12-16 2012-06-21 Electronics And Telecommunications Research Institute Method for converting mobile web application into native application and apparatus using the same
CN103106576A (zh) * 2011-11-15 2013-05-15 腾讯科技（深圳）有限公司 基于客户端的支付方法、系统和支付客户端
CN104144207A (zh) * 2014-05-30 2014-11-12 腾讯科技（深圳）有限公司 界面加载方法和系统及装置
CN105138340A (zh) * 2015-09-15 2015-12-09 北京齐尔布莱特科技有限公司 一种Native与Web页面的交互方法和系统
CN105204875A (zh) * 2014-06-11 2015-12-30 腾讯科技（深圳）有限公司 网页调用native功能的方法和系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103051684B (zh) * 2012-12-07 2017-03-15 百度在线网络技术（北京）有限公司 将网站转化为Web App进行展示的方法、系统和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120159310A1 (en) * 2010-12-16 2012-06-21 Electronics And Telecommunications Research Institute Method for converting mobile web application into native application and apparatus using the same
CN103106576A (zh) * 2011-11-15 2013-05-15 腾讯科技（深圳）有限公司 基于客户端的支付方法、系统和支付客户端
CN104144207A (zh) * 2014-05-30 2014-11-12 腾讯科技（深圳）有限公司 界面加载方法和系统及装置
CN105204875A (zh) * 2014-06-11 2015-12-30 腾讯科技（深圳）有限公司 网页调用native功能的方法和系统
CN105138340A (zh) * 2015-09-15 2015-12-09 北京齐尔布莱特科技有限公司 一种Native与Web页面的交互方法和系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115103320A (zh) * 2022-07-11 2022-09-23 中移互联网有限公司 消息的传输方法、装置、电子设备及存储介质
CN115103320B (zh) * 2022-07-11 2023-09-05 中移互联网有限公司 消息的传输方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
TW201800993A (zh) 2018-01-01
CN106971298A (zh) 2017-07-21

Similar Documents

Publication Publication Date Title
US11341478B2 (en) Payment processing method and apparatus, and intelligent device
US10200442B2 (en) Tracking mobile app installations
CN110708346B (zh) 信息处理系统和方法
CN111221739B (zh) 业务测试方法、装置和系统
WO2018223717A1 (zh) 网页前端测试方法、装置、系统、设备及可读存储介质
US11016716B2 (en) Picture interface display method and apparatus according to jump protocol
WO2017121283A1 (zh) 支付方法、系统、支付转换方法以及支付转换装置
US20180131779A1 (en) Recording And Triggering Web And Native Mobile Application Events With Mapped Data Fields
CN108416021B (zh) 一种浏览器网页内容处理方法、装置、电子设备及可读介质
US11935068B1 (en) Methods and apparatus for mobile device messaging-based communications using custom-generated deeplinks and based on the hyper text transfer protocol (HTTP)
WO2014151969A1 (en) Rewarding mobile app installations without a software development kit in the mobile app
US20220215374A1 (en) Payment Method, Apparatus and System, Device, and Storage Medium
JP2022546073A (ja) サードパーティ・クッキーなしにウェブ・パブリッシャー・インベントリをプログラマティック・エクスチェンジに接続すること
WO2017071121A1 (zh) 一种用于建立无线连接的方法与设备
US20150207867A1 (en) Information processing terminal and control method
TW201818317A (zh) 業務實現方法、支付方法、業務實現裝置及支付服務端
TW201621776A (zh) 非結構化消息處理的方法、用戶端、伺服器及平台
CN112015383A (zh) 一种登录方法和装置
US20240177200A1 (en) Business service interaction method and apparatus, device, and storage medium
KR20120076479A (ko) 어플리케이션 제작 시스템 및 방법
CN113472785B (zh) 数据处理方法、装置、电子设备及可读存储介质
CN108471635B (zh) 用于连接无线接入点的方法和设备
CN109756393B (zh) 信息处理方法、系统、介质和计算设备
CN112347382A (zh) 产品页面分享方法、装置及电子设备
CN111597485A (zh) 信息呈现方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17738097

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17738097

Country of ref document: EP

Kind code of ref document: A1