Mobile payment method and system

Abstract

The invention discloses a mobile payment method. The method comprises the following steps: starting a universal payment application program; a mobile payment code is extracted, the mobile payment code is a non-agreed payment code, and the non-agreed payment code is generated by a non-corresponding universal payment application program and is not agreed with the universal payment application program; and the universal payment application program provides a payment interface according to the extracted mobile payment code, and when the mobile payment code is a non-agreed payment code, the payment interface at least comprises a universal payment link and / or a financial transaction triggering link. The invention further discloses a mobile payment system applying the method.

Description

TECHNICAL FIELD

[0001] The present application relates to a payment method and system, in particular, to a mobile payment method and system suitable for mobile payment. BACKGROUND

[0002] In recent years, using mobile payment to make a purchase has become one of the main payment methods. Generally speaking, as long as a mobile device such as a mobile phone, a tablet computer, a smart watch, etc. is used as a carrier, and further binding methods such as a credit card, a charge card, a bank account, a stored value account, a point discount, etc. are used to deduct or pay, it can be called mobile payment.

[0003] For example, when a consumer makes a purchase in a store, a mobile device can be used to scan a code such as a one-dimensional barcode or a two-dimensional barcode, and then a mobile payment action is performed through a suitable mobile payment platform. At this point, in order to successfully complete the mobile payment action, a prerequisite is that the consumer and the store use the same mobile payment platform, for example, the store provides a mobile payment code (such as a QR code) of the A mobile payment platform, and the consumer's mobile device must install an A mobile payment application of the A mobile payment platform, so that the mobile payment action can be successfully completed. In other words, if the store only provides a mobile payment code of the A mobile payment platform, but the consumer's mobile device does not install the A mobile payment application, the mobile payment action cannot be performed.

[0004] In order to avoid the above situation that the mobile payment action cannot be performed, the consumer's mobile device may need to install multiple mobile payment applications and apply for corresponding accounts at the same time, and the store must apply to different mobile payment platforms to obtain multiple mobile payment codes. However, in the face of the current booming development of mobile payment business, there are dozens of mobile payment platforms on the market, such as Apple Pay, Google Pay, TW Pay, Paypal, Line Pay, FamiPay, PX Pay, Jie Kou Payment, Quan Payment, etc. For both the store and the consumer, especially for the consumer, whether it is to install multiple mobile payment applications and apply for corresponding accounts, or to apply for multiple mobile payment codes of different mobile payment platforms, it is a very complicated and troublesome process.

[0005] Therefore, how to provide a mobile payment method and system that can be used for multiple different mobile payment platforms is one of the important issues in the current industry. SUMMARY

[0006] In view of the above problems, the purpose of the present application is to provide a mobile payment method and system that can be used for multiple different mobile payment platforms with a single payment application, and in particular, can be used for mobile payment platforms without prior agreement.

[0007] To achieve the above object, a mobile payment method according to the present application comprises the steps of: starting a general payment application; extracting a mobile payment code, wherein the mobile payment code is a non-agreed payment code, the non-agreed payment code is generated by a non-corresponding general payment application and is not agreed with the general payment application; and providing a payment interface by the general payment application according to the extracted mobile payment code, wherein when the mobile payment code is the non-agreed payment code, the payment interface at least comprises a general payment link and / or a financial transaction trigger link.

[0008] In one embodiment, the mobile payment code is a one-dimensional barcode or a two-dimensional barcode.

[0009] In one embodiment, the step of extracting the mobile payment code is achieved by using an image extraction method or a wireless communication method.

[0010] In one embodiment, the financial transaction trigger link corresponds to a credit card transaction, a charge card transaction, a stored value card transaction, a bank transfer transaction, or a stored value transaction.

[0011] In one embodiment, the mobile payment method further comprises the steps of: when the general payment link is selected, performing mobile payment through a general payment platform corresponding to the general payment application; and when the financial transaction trigger link is selected, performing mobile payment through a financial transaction platform corresponding to the financial transaction trigger link or through the general payment platform.

[0012] In one embodiment, the mobile payment code is a general payment code, an agreed payment code or a non-agreed payment code, wherein the general payment code is generated by a corresponding general payment application, the agreed payment code is generated by a non-corresponding general payment application but is agreed with the general payment application, wherein when the mobile payment code is the general payment code, the payment interface at least comprises the general payment link, and when the mobile payment code is the agreed payment code, the payment interface at least comprises an agreed payment trigger link and / or the general payment link.

[0013] In one embodiment, the mobile payment method further comprises the steps of: when the general payment link is selected, performing mobile payment through a general payment platform corresponding to the general payment application; when the agreed payment trigger link is selected, starting an agreed payment application corresponding to the agreed payment code to perform mobile payment or performing mobile payment through the general payment platform; and when the financial transaction trigger link is selected, performing mobile payment through a financial transaction platform corresponding to the financial transaction trigger link or performing mobile payment through the general payment platform.

[0014] To achieve the above objectives, a mobile payment system according to the present invention includes a mobile payment code and an electronic mobile device; wherein the mobile payment code is configured on a first transacting party and is a non-contractual payment code; the electronic mobile device is configured on a second transacting party and has a universal payment application installed, wherein the non-contractual payment code is generated by a non-corresponding universal payment application and is not contractually agreed upon with the universal payment application; when the electronic mobile device retrieves the mobile payment code, the universal payment application provides a payment interface based on the retrieved mobile payment code; wherein, when the mobile payment code is a non-contractual payment code, the payment interface includes at least a universal payment link and / or a financial transaction trigger link.

[0015] In one embodiment, the mobile payment code is a one-dimensional barcode or a two-dimensional barcode.

[0016] In one embodiment, the electronic mobile device includes an image extraction module that uses image extraction to obtain a mobile payment code.

[0017] In one embodiment, the electronic mobile device includes a wireless communication module that uses wireless communication to obtain a mobile payment code.

[0018] In one embodiment, the financial transaction trigger link corresponds to a credit card transaction, debit card transaction, prepaid card transaction, bank transfer transaction, or prepaid fund transaction.

[0019] In one embodiment, when a universal payment link is selected, the electronic mobile device makes a mobile payment through the universal payment platform corresponding to the universal payment application; and when a financial transaction trigger link is selected, the mobile payment is made through the financial transaction platform corresponding to the financial transaction trigger link or through the universal payment platform.

[0020] In one embodiment, the mobile payment code is a general payment code, a pre-agreed payment code, or a non-pre-agreed payment code. The general payment code is generated by a corresponding general payment application. The pre-agreed payment code is generated by a non-corresponding general payment application but is agreed upon with the general payment application. The non-pre-agreed payment code is generated by a non-corresponding general payment application and is not agreed upon with the general payment application. When the mobile payment code is a general payment code, the payment interface includes at least a general payment link. When the mobile payment code is a pre-agreed payment code, the payment interface includes at least a pre-agreed payment trigger link and / or a general payment link. When the mobile payment code is a non-pre-agreed payment code, the payment interface includes at least a general payment link and / or a financial transaction trigger link.

[0021] In one embodiment, when a universal payment link is selected, the electronic mobile device makes a mobile payment through a universal payment platform corresponding to the universal payment application; when a pre-selected payment trigger link is selected, the electronic mobile device launches a pre-selected payment application with the corresponding pre-selected payment code to make a mobile payment, or makes a mobile payment through the universal payment platform; and when a financial transaction trigger link is selected, the electronic mobile device makes a mobile payment through a financial transaction platform corresponding to the financial transaction trigger link, or makes a mobile payment through the universal payment platform.

[0022] As described above, the mobile payment method of the present invention includes the following steps: extracting a mobile payment code, wherein the mobile payment code is a non-contractual payment code, which is generated by a non-corresponding general payment application and is not contractually agreed upon with the general payment application; and the general payment application providing a payment interface based on the extracted mobile payment code, wherein when the mobile payment code is a non-contractual payment code, the payment interface includes at least a general payment link and / or a financial transaction triggering link. Through the above steps, when making a mobile payment, a single payment application (i.e., a general payment application) can be used to perform the mobile payment action. At this time, even if the mobile payment code provided during the mobile payment process is a specific payment code (i.e., a general payment code) not generated by a specific payment application (i.e., a corresponding general payment code), the subsequent actions of the mobile payment can still be successfully triggered. A single payment application can be used for multiple different mobile payment platforms, especially for mobile payment platforms that have not been contractually agreed upon in advance. This avoids the complicated process of installing multiple mobile payment applications and applying for corresponding accounts, or applying for multiple mobile payment codes for different mobile payment platforms.

[0023] Furthermore, the mobile payment system of the present invention includes a mobile payment code and an electronic mobile device; wherein the mobile payment code is configured on the first transaction party and is a non-contractual payment code; the electronic mobile device is configured on the second transaction party and has a universal payment application installed, wherein the non-contractual payment code is generated by a non-corresponding universal payment application and is not contractually agreed upon with the universal payment application. When the electronic mobile device retrieves the mobile payment code, the universal payment interface includes at least a universal payment link and / or a financial transaction trigger link. Through the above design, when making a mobile payment, a single payment application (i.e., a universal payment application) can be used to perform the mobile payment action. At this time, even if the mobile payment code provided during the mobile payment process is a specific payment code (i.e., a universal payment code) not generated by a specific payment application (i.e., a corresponding universal payment code), the subsequent actions of the mobile payment can still be successfully triggered. Therefore, a single payment application can be used for multiple different mobile payment platforms, especially for mobile payment platforms that have not been contractually agreed upon in advance, thereby avoiding the complicated process of installing multiple mobile payment applications and applying for corresponding accounts, or applying for multiple mobile payment codes for different mobile payment platforms. Attached Figure Description

[0024] Figure 1 This is a flowchart of a mobile payment method according to an embodiment of the present invention.

[0025] Figure 2 For example Figure 1 The flowchart illustrates one implementation of the mobile payment method.

[0026] Figure 3 This is a schematic diagram of a mobile payment system according to an embodiment of the present invention.

[0027] Figures 4A to 4C For example Figure 3 The diagram shows a payment interface displayed on an electronic mobile device in a mobile payment system. Detailed Implementation

[0028] The preferred embodiments of the mobile payment method and system according to the present invention will be described below with reference to the accompanying drawings, wherein the same elements will be described with the same reference numerals.

[0029] Figure 1 This is a flowchart of a mobile payment method according to an embodiment of the present invention.

[0030] like Figure 1As shown, the mobile payment method 100 of this embodiment includes the following steps: launching a universal payment application (step S01); extracting a mobile payment code, wherein the mobile payment code is a universal payment code, a pre-agreed payment code, or a non-pre-agreed payment code, wherein the universal payment code is generated by the corresponding universal payment application, the pre-agreed payment code is generated by a non-corresponding universal payment application but is agreed upon with the universal payment application, and the non-pre-agreed payment code is generated by a non-corresponding universal payment application and is not agreed upon with the universal payment application (step S02); the universal payment application provides a payment interface based on the extracted mobile payment code, wherein when the mobile payment code is a universal payment code, the payment interface includes at least a universal payment link, and when the mobile payment code is a universal payment code, the payment interface includes at least a universal payment link. When the mobile payment code is a pre-arranged payment code, the payment interface includes at least a pre-arranged payment trigger link and / or a general payment link. When the mobile payment code is a non-pre-arranged payment code, the payment interface includes at least a general payment link and / or a financial transaction trigger link (step S03). When the general payment link is selected, mobile payment is performed through the general payment platform corresponding to the general payment application. When the pre-arranged payment trigger link is selected, the pre-arranged payment application corresponding to the pre-arranged payment code is launched to perform mobile payment, or mobile payment is performed through the general payment platform. When the financial transaction trigger link is selected, mobile payment is performed through the financial transaction platform corresponding to the financial transaction trigger link, or mobile payment is performed through the general payment platform (step S04).

[0031] In this embodiment, the order of steps S01 and S02 may differ, and this invention is not limiting. For example, step S01 can be executed first to launch the universal payment application, and then step S02 can be performed to retrieve the mobile payment code; or step S02 can be executed first to retrieve the mobile payment code, and then step S01 can be performed to launch the universal payment application. Of course, in another embodiment, steps S01 and S02 can also be completed simultaneously, and this invention is not limiting.

[0032] In this embodiment, the mobile payment code can be any applicable barcode, such as a one-dimensional barcode or a two-dimensional barcode, and the present invention does not limit it.

[0033] In addition, in step S02, the action of extracting the mobile payment code can be performed using any applicable method. For example, an image of the mobile payment code can be obtained using an image extraction method (such as scanning the code using a camera lens), or a signal containing the mobile payment code can be obtained using a wireless communication method (such as signal transmission using near-field communication). This invention does not limit the method.

[0034] In this embodiment, the agreed-upon payment code is generated by a non-corresponding general payment application, but is agreed upon with the general payment application. Specifically, the agreed-upon payment code can be generated by any other payment application, such as a payment code for mobile payment platform A (A payment application) or a payment code for mobile payment platform B (B payment application). The general payment platform corresponding to the general payment application can enter into an agreement (contract) with both mobile payment platforms A and B, allowing the general payment application to recognize the payment codes for platforms A and B as agreed-upon payment codes. It should be noted that when the general payment platform can enter into an agreement (contract) with both mobile payment platforms A and B, the payment code recognition capability of the general payment application can be expanded, enabling the general payment application to recognize (or decode) not only general payment codes but also agreed-upon payment codes (such as payment codes for platforms A and B).

[0035] Furthermore, non-contractual payment codes are generated by non-corresponding universal payment applications and are not contractually agreed upon with universal payment applications. In detail, non-contractual payment codes can be generated by any other payment application, such as a C platform payment code corresponding to a C mobile payment application, or a D platform payment code corresponding to a D mobile payment application. Since the universal payment application's universal payment platform has not made any contractual agreement with C mobile payment platform and D mobile payment platform, the C platform payment code and the D platform payment code are judged as non-contractual payment codes by the universal payment application.

[0036] In step S04, when the universal payment link is selected, mobile payment can be made through the universal payment platform. For example, when the universal payment link is selected, it means that the mobile payment code is a universal payment code, which is generated by the universal payment platform. Therefore, the universal payment platform can directly complete the mobile payment action.

[0037] Additionally, in step S04, when the agreed-upon payment trigger link is selected, the agreed-upon payment application can be launched for mobile payment, or mobile payment can be made through a universal payment platform. For example, when the agreed-upon payment trigger link is selected, it indicates that the mobile payment code is an agreed-upon payment code (such as a payment code from platform A), which is generated based on the corresponding mobile payment platform (such as mobile payment platform A). Therefore, the corresponding agreed-upon payment application (such as payment application A) can be launched, and the mobile payment action can be completed through the corresponding mobile payment platform (such as mobile payment platform A). Furthermore, even if the extracted mobile payment code is an agreed-upon payment code, it can still communicate with other agreed-upon mobile payment platforms (such as mobile payment platform A or mobile payment platform B) through the universal payment platform to further complete the mobile payment action.

[0038] Furthermore, in step S04, when a financial transaction trigger link is selected, mobile payment can be made through the financial transaction platform corresponding to the financial transaction trigger link, or through a general payment platform. For example, when a financial transaction trigger link is selected, the mobile payment code may be a non-standard payment code (such as a C platform payment code), which is generated based on the corresponding mobile payment platform (such as C mobile payment platform). Since the corresponding payment application (such as C payment application) cannot be launched to perform the mobile payment action, the application of any applicable financial transaction platform can be launched. For example, the payment action can be performed through the financial transaction platform by means of credit card transaction, debit card transaction, prepaid card transaction, bank transfer transaction, or prepaid fund transaction. Furthermore, even if the extracted mobile payment code is not a pre-agreed payment code, it can still communicate with any applicable financial transaction platform (such as banks, credit card centers, and other financial institutions) through a universal payment platform, and then communicate with the pre-agreed mobile payment platform (such as C mobile payment platform or D mobile payment platform) through this financial transaction platform to further complete the mobile payment action; of course, financial institutions can also directly pay the charging party to complete the mobile payment action.

[0039] To make this embodiment clearer, the following will refer to... Figure 2 This document describes a detailed process for one implementation of the mobile payment method in this embodiment.

[0040] like Figure 2 As shown, first, step S11 is executed to launch the universal payment application, and then step S12 is executed to retrieve the mobile payment code. It should be noted that the above description is merely an example, and the order of steps S11 and S12 is not limited. For example, step S12 can be executed first to retrieve the mobile payment code, and then the corresponding universal payment application can be launched directly based on the retrieved mobile payment code (step S11). Alternatively, in one embodiment, steps S11 and S12 can be completed simultaneously. For example, a recognition program or procedure can be set in the firmware of the camera module of the mobile device. Therefore, when the camera module retrieves the image of the payment code (such as a two-dimensional barcode), the payment code recognition action can be completed simultaneously. At this time, when scanning the code, the electronic mobile device (such as a mobile phone) can simultaneously display the image of the payment code and its recognition result (such as a webpage or payment path).

[0041] Next, step S13 determines whether the mobile payment code is a universal payment code; when step S13 determines that the mobile payment code is a universal payment code, step S14 is then executed to provide a universal payment link in the payment interface. In this embodiment, step S04 can be performed next, that is, the universal payment link can be selected to make a mobile payment through the universal payment platform corresponding to the universal payment application; its detailed description can be found in the foregoing embodiment, and will not be repeated here.

[0042] When step S13 determines that the mobile payment code is not a general payment code, step S15 is then executed to determine whether the mobile payment code is a pre-defined payment code. When step S15 determines that the mobile payment code is a pre-defined payment code, step S16 is then executed to provide a pre-defined payment trigger link and / or a general payment link in the payment interface. Here, the payment interface may provide, for example, a pre-defined payment trigger link and a general payment link. In this embodiment, step S04 can then be performed, i.e., clicking on the pre-defined payment trigger link or the general payment link to perform mobile payment; a detailed explanation can be found in the aforementioned embodiment and will not be repeated here.

[0043] Furthermore, when step S15 determines that the mobile payment code is not a pre-defined payment code, it indicates that the mobile payment code is a non-pre-defined payment code. Therefore, step S17 can be executed next to provide a financial transaction trigger link and / or a general payment link in the payment interface. Here, the payment interface provides, for example, a financial transaction trigger link and a general payment link. In this embodiment, the aforementioned step S04 can then be performed, that is, clicking on the financial transaction trigger link or the general payment link to perform mobile payment; its detailed explanation can be found in the aforementioned embodiment and will not be repeated here.

[0044] In summary, the mobile payment method of the present invention includes the following steps: extracting a mobile payment code, wherein the mobile payment code is a general payment code or a contractual payment code, the general payment code is generated by a corresponding general payment application, and the contractual payment code is generated by a non-corresponding general payment application but is contractually agreed upon with the general payment application; and the general payment application provides a payment interface based on the extracted mobile payment code, wherein when the mobile payment code is a general payment code, the payment interface includes at least a general payment link, and when the mobile payment code is a contractual payment code, the payment interface includes at least a contractual payment trigger link and / or a general payment link. Through the above steps, mobile payments can be made using a single payment application (i.e., a universal payment application). Even if the mobile payment code provided during the mobile payment process is not a specific payment code (i.e., a universal payment code) generated by a different payment application (i.e., a universal payment code), subsequent actions of the mobile payment can still be successfully triggered. Therefore, a single payment application can be used for multiple different mobile payment platforms, especially for mobile payment platforms that have not been agreed upon in advance. This avoids the complicated process of installing multiple mobile payment applications and applying for corresponding accounts, or applying for multiple mobile payment codes for different mobile payment platforms.

[0045] In addition, please refer to Figure 3 The diagram shown is a schematic representation of a mobile payment system 200 according to an embodiment of the present invention. In this embodiment, the mobile payment system 200 can apply the aforementioned mobile payment method 100.

[0046] like Figure 3 As shown, the mobile payment system 200 includes a mobile payment code 20 and an electronic mobile device 30.

[0047] In this embodiment, the mobile payment code 20 is configured on the first transaction party, such as the payment party (e.g., a merchant). The mobile payment code 20 can be, for example, but not limited to, a general payment code, a pre-defined payment code, or a non-pre-defined payment code. In this embodiment, the mobile payment code 20 can be, for example, but not limited to, a one-dimensional barcode or a two-dimensional barcode; specifically, a two-dimensional barcode is used as an example in this embodiment. Furthermore, the mobile payment code 20 can be a physical barcode printed on any medium (e.g., paper, business cards, etc.) or a virtual barcode displayed on an electronic display; this invention does not impose any limitations. Specifically, a mobile payment code printed on a business card is used as an example in this embodiment.

[0048] like Figure 3 As shown, the electronic mobile device 30 is configured on the second transaction party, such as the payer (e.g., a consumer), and is equipped with a universal payment application, wherein the universal payment application corresponds to the aforementioned universal payment code, that is, the universal payment code is generated by the corresponding universal payment application.

[0049] For example, the electronic mobile device 30 may be, for example, but not limited to, a consumer's mobile phone or smartwatch, and includes at least an image extraction module 31 and a display module 32; wherein, the image extraction module 31 may be, for example, a camera module of a mobile phone, used to obtain the mobile payment code 20 by means of image extraction. It should be noted that the above description is only an example and is not intended to limit the invention. In another embodiment, the electronic mobile device 30 may include a wireless communication module, such as a near field communication (NFC) module, which can use wireless communication methods (such as NFC) to sense and obtain the mobile payment code 20.

[0050] Alternatively, the display module 32 can be, for example, a mobile phone display module, such as an LCD display module or an OLED display module, used to display the payment interface 33 provided by the universal payment application based on the extracted mobile payment code 20. It should be noted that the above description is merely illustrative and not intended to limit the invention.

[0051] Please refer to the following at the same time Figure 2 , Figure 3 and Figures 4A to 4C As shown, when step S13 determines that mobile payment code 20 is a universal payment code, step S14 is then executed to provide a universal payment link 331 (e.g., ...) in the payment interface 33. Figure 4A As shown in the diagram, consumers can click on the universal payment link 331 to make a mobile payment; its detailed explanation can be found in the foregoing embodiments, and will not be repeated here. It should be noted that the above description is merely an example and is not intended to limit the invention.

[0052] Additionally, when step S15 determines that the mobile payment code 20 is a pre-defined payment code, step S16 is then executed to provide the pre-defined payment trigger link 332 and / or the general payment link 331 in the payment interface 33; in this embodiment, as Figure 4B As shown, payment interface 33 provides both a pre-arranged payment trigger link 332 and a general payment link 331. Therefore, consumers can choose to click on either the pre-arranged payment trigger link 332 or the general payment link 331 to perform a mobile payment action; detailed descriptions can be found in the foregoing embodiments and will not be repeated here. It should be noted that the above description is merely illustrative and not intended to limit the invention.

[0053] Furthermore, when step S15 determines that the mobile payment code 20 is a non-standard payment code, step S17 can then be executed to provide a financial transaction trigger link 333 and / or a general payment link 331 in the payment interface 33; in this embodiment, as Figure 4CAs shown, payment interface 33 provides both a financial transaction trigger link 333 and a general payment link 331. Therefore, consumers can choose to click on either the financial transaction trigger link 333 or the general payment link 331 to perform a mobile payment action; detailed descriptions can be found in the foregoing embodiments and will not be repeated here. It should be noted that the above description is merely illustrative and not intended to limit the invention.

[0054] The following scenario illustrates the application of the mobile payment method and system of this embodiment. For example, when a consumer travels to another country and makes purchases, such as an American consumer traveling to Asia and making purchases at a local store, the consumer's mobile phone may not have the mobile payment method applicable to the local store. Therefore, the consumer is forced to pay only with cash or a physical credit card. In other words, although the consumer wants to pay using mobile payment and the local store can also accept mobile payment, the different mobile payment platforms prevent the two parties from completing the transaction via mobile payment. In this situation (especially when a foreign tourist makes purchases at a local store in another country), the mobile payment method and system of this embodiment can be applied. The mobile payment code provided by the local store can be defined as the non-conventional payment code in this embodiment. Therefore, through the aforementioned step S17, the consumer (foreign tourist, the second transaction party) can successfully make a mobile payment at the local store (the first transaction party providing the mobile payment code).

[0055] In summary, the mobile payment system of the present invention includes a mobile payment code and an electronic mobile device; wherein the mobile payment code is configured on the first transaction party, and the mobile payment code is a general payment code or a pre-agreed payment code; the electronic mobile device is configured on the second transaction party and has a general payment application installed, wherein the general payment code is generated by the corresponding general payment application, and the pre-agreed payment code is generated by a non-corresponding general payment application but is agreed upon with the general payment application; when the electronic mobile device retrieves the mobile payment code, the general payment application provides a payment interface based on the retrieved mobile payment code; wherein, when the mobile payment code is a general payment code, the payment interface includes at least a general payment link, and when the mobile payment code is a pre-agreed payment code, the payment interface includes at least a pre-agreed payment trigger link and / or a general payment link. With the above design, mobile payments can be made using a single payment application (i.e., a universal payment application). Even if the mobile payment code provided during the mobile payment process is not a specific payment code (i.e., a universal payment code) generated by a different payment application (i.e., a universal payment code), subsequent actions of the mobile payment can still be successfully triggered. Therefore, a single payment application can be used for multiple different mobile payment platforms, especially for mobile payment platforms that have not been agreed upon in advance. This avoids the complicated process of installing multiple mobile payment applications and applying for corresponding accounts, or applying for multiple mobile payment codes for different mobile payment platforms.

[0056] The above description is illustrative only and not restrictive. Any equivalent modifications or alterations made without departing from the spirit and scope of this invention should be included within the scope of the appended claims.

Claims

1. A mobile payment method, comprising: Launch the universal payment application; Extract the mobile payment code, wherein the mobile payment code is a non-contractual payment code, meaning it is not generated by the corresponding general payment application and is not contractually agreed upon with the general payment application; and The general payment application provides a payment interface based on the extracted mobile payment code, wherein: When the mobile payment code is the non-conventional payment code, the payment interface includes at least a general payment link and / or a financial transaction trigger link.

2. The mobile payment method according to claim 1, wherein the mobile payment code is a one-dimensional barcode or a two-dimensional barcode.

3. The mobile payment method according to claim 1, wherein the step of extracting the mobile payment code is to obtain the mobile payment code using an image extraction method or a wireless communication method.

4. The mobile payment method according to claim 1, further comprising: When the universal payment link is selected, mobile payment is made through the universal payment platform corresponding to the universal payment application. as well as When the financial transaction trigger link is selected, the mobile payment is made through the financial transaction platform corresponding to the financial transaction trigger link, or through the general payment platform.

5. The mobile payment method according to claim 1, wherein the mobile payment code is a general payment code, an agreed payment code, or the non-agreed payment code, the general payment code is generated corresponding to the general payment application, and the agreed payment code is not generated corresponding to the general payment application but is agreed upon with the general payment application, wherein when the mobile payment code is the general payment code, the payment interface includes at least the general payment link, and when the mobile payment code is the agreed payment code, the payment interface includes at least an agreed payment trigger link and / or the general payment link; in, The mobile payment method further includes: When the universal payment link is selected, mobile payment is made through the universal payment platform corresponding to the universal payment application. When the agreed payment trigger link is selected, the agreed payment application corresponding to the agreed payment code is launched to perform the mobile payment, or the mobile payment is performed through the general payment platform; and When the financial transaction trigger link is selected, the mobile payment is made through the financial transaction platform corresponding to the financial transaction trigger link, or through the general payment platform.

6. A mobile payment system, comprising: A mobile payment code is configured on the first transacting party, wherein the mobile payment code is a non-conventional payment code; as well as An electronic mobile device is configured with a second transacting party and has a universal payment application installed. The non-contractual payment code is not generated by the universal payment application and is not contractually agreed upon with it. When the electronic mobile device retrieves the mobile payment code, the universal payment application provides a payment interface based on the retrieved mobile payment code, wherein: When the mobile payment code is the non-conventional payment code, the payment interface includes at least a general payment link and / or a financial transaction trigger link.

7. The mobile payment system according to claim 6, wherein the mobile payment code is a one-dimensional barcode or a two-dimensional barcode.

8. The mobile payment system according to claim 6, wherein the electronic mobile device comprises: The image extraction module uses image extraction methods to obtain the mobile payment code; or The wireless communication module uses wireless communication to obtain the mobile payment code.

9. The mobile payment system according to claim 6, wherein: When the universal payment link is selected, the electronic mobile device performs mobile payment through the universal payment platform corresponding to the universal payment application; and When the financial transaction trigger link is selected, the mobile payment is made through the financial transaction platform corresponding to the financial transaction trigger link, or through the general payment platform.

10. The mobile payment system according to claim 6, wherein the mobile payment code is a general payment code, an agreed payment code, or the non-agreed payment code, the general payment code is generated corresponding to the general payment application, and the agreed payment code is not generated corresponding to the general payment application but is agreed upon with the general payment application, wherein when the mobile payment code is the general payment code, the payment interface includes at least the general payment link, and when the mobile payment code is the agreed payment code, the payment interface includes at least an agreed payment trigger link and / or the general payment link; When the universal payment link is selected, the electronic mobile device makes a mobile payment through the universal payment platform corresponding to the universal payment application; When the agreed payment trigger link is selected, the electronic mobile device launches the agreed payment application corresponding to the agreed payment code to perform the mobile payment, or performs the mobile payment through the universal payment platform; and When the financial transaction trigger link is selected, the electronic mobile device performs the mobile payment through the financial transaction platform corresponding to the financial transaction trigger link, or through the general payment platform.

Images