Mobile payment method

Abstract

To solve the problem in which: consumers download different mobile payment applications onto their mobile devices, apply for corresponding accounts, and then make mobile payments on the corresponding mobile payment platforms; however, currently, there is no mobile payment method or system that can be used across various types of mobile payment platforms.SOLUTION: A mobile payment method of the present invention includes the steps of: starting a universal payment application; acquiring a mobile payment code which is a non-agreed payment code, the non-agreed payment code being generated not correspondingly to the universal payment application, and being non-agreed by the universal payment application; and providing a payment interface by the universal payment application based on the acquired mobile payment code. When the mobile payment code is the non-agreed payment code, the payment interface at least includes a universal payment link and / or a financial transaction trigger link. The present invention discloses a mobile payment system applying the above-mentioned method.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a payment method and system, and more particularly to a mobile payment method and system suitable for mobile payments.

[0002] In recent years, paying for goods through mobile payments has become a mainstream payment method. Generally, any mobile device, such as a mobile phone, tablet, or smartwatch, can be used as a carrier, and can be linked to a credit card, debit card, bank account, charge account, or point exchange to perform an account withdrawal or payment operation.

[0003] For example, when a consumer purchases a product at a store, they scan a barcode or QR code with their mobile device and then make a mobile payment on an appropriate mobile payment platform. Here, the first condition for a smooth mobile payment is that the consumer uses the same mobile payment platform as the store. For example, if the store provides a mobile payment code (e.g., a QR code) from mobile payment platform A, the consumer needs to download the app for mobile payment platform A onto their mobile device, which will allow the mobile payment to be completed smoothly. In other words, if the store only provides a mobile payment code from mobile payment platform A and the consumer does not have the app for mobile payment platform A downloaded onto their mobile device, the mobile payment will not be possible.

[0004] To avoid the above-mentioned mobile payment issues, consumers need to download multiple mobile payment apps to their mobile devices and apply for corresponding accounts, and merchants must also apply for mobile payment codes corresponding to different mobile payment platforms. However, given the popularity of mobile payments, there are currently more than ten mobile payment platforms, including Apple Pay, Google Pay, TW Pay, PayPal, Line Pay, Fami Pay, PXpay, Jiekou Pay, and Quanpay. Applying for accounts corresponding to multiple mobile payment apps or applying for mobile payment codes for different mobile payment platforms is complicated and troublesome for both merchants and consumers, especially for consumers.

[0005] Therefore, providing a mobile payment method and system that can be used on multiple mobile payment platforms is one of the key challenges in the industry today. Summary of the Invention [Problem to be solved by the invention]

[0006] The problem that the present invention aims to solve is that consumers need to download different mobile payment apps to their mobile devices, apply for corresponding accounts, and then make mobile payments on corresponding mobile payment platforms, but currently there is no mobile payment method or system that can be used across multiple mobile payment platforms. [Means for solving the problem]

[0007] In view of the above, the object of the present invention is to provide a mobile payment method and system that can be used with a single payment app across multiple mobile payment platforms, especially those that have not been pre-committed.

[0008] To achieve the above objectives, the mobile payment method of the present invention includes the following steps: launch a universal payment app; obtain a mobile payment code, where the mobile payment code is a non-promised payment code, where the non-promised payment code is generated without corresponding to the universal payment app and is not promised with the universal payment app; the universal payment app provides a payment interface according to the obtained mobile payment code, and if the mobile payment code is a non-promised payment code, the payment interface includes at least a universal payment link and / or a financial transaction trigger link.

[0009] In one embodiment, the mobile payment code is a barcode or a QR code.

[0010] In one embodiment, the step of obtaining the mobile payment code includes obtaining the mobile payment code through an image capturing method or a wireless communication method.

[0011] In one embodiment, the financial transaction trigger links correspond to credit card transactions, debit card transactions, prepaid card transactions, bank transfer transactions, and charge-back transactions.

[0012] In one embodiment, the mobile payment method further includes the following steps: if a universal payment link is selected, the mobile payment is made through a universal payment platform corresponding to the universal payment app; if a financial transaction trigger link is selected, the mobile payment is made through a financial transaction platform corresponding to the financial transaction trigger link, or the mobile payment is made through a universal payment platform.

[0013] In one embodiment, the mobile payment code is a universal payment code, a promised payment code, or a non-promised payment code, where the universal payment code is generated corresponding to a universal payment app, and the promised payment code is generated without corresponding to a universal payment app but is promised to the universal payment app. If the mobile payment code is a universal payment code, the payment interface includes at least a universal payment link; if the mobile payment code is a promised payment code, the payment interface includes at least a promised payment trigger link and / or a universal payment link.

[0014] In one embodiment, the mobile payment method further includes the following steps: if a universal payment link is selected, the mobile payment is made through a universal payment platform corresponding to the universal payment app; if a promise payment trigger link is selected, the mobile payment is made by launching a promise payment app corresponding to the promise payment code, or the mobile payment is made through a universal payment platform; if a financial transaction trigger link is selected, the mobile payment is made through a financial transaction platform corresponding to the financial transaction trigger link, or the mobile payment is made through a universal payment platform.

[0015] To achieve the above objectives, the mobile payment system of the present invention includes a mobile payment code and an electronic mobile device. The mobile payment code is located on a first transaction side, and the mobile payment code is a non-provisional payment code. The electronic mobile device is located on a second transaction side and is installed with a universal payment app. The non-provisional payment code is generated without corresponding to the universal payment app and is not provisioned with the universal payment app. When the electronic mobile device acquires the mobile payment code, the universal payment app provides a payment interface according to the acquired mobile payment code. If the mobile payment code is a non-provisional payment code, the payment interface includes at least a universal payment link and / or a financial transaction trigger link.

[0016] In one embodiment, the mobile payment code is a barcode or a QR code.

[0017] In one embodiment, the electronic mobile device includes an image capturing module, and captures the mobile payment code through an image capturing manner.

[0018] In one embodiment, the electronic mobile device includes a wireless communication module and obtains the mobile payment code through a wireless communication method.

[0019] In one embodiment, the financial transaction trigger links correspond to credit card transactions, debit card transactions, prepaid card transactions, bank transfer transactions, and charge-back transactions.

[0020] In one embodiment, when the universal payment link is selected, the electronic mobile device performs mobile payment through a universal payment platform corresponding to the universal payment app; when the financial transaction trigger link is selected, the electronic mobile device performs mobile payment through a financial transaction platform corresponding to the financial transaction trigger link, or performs mobile payment through a universal payment platform.

[0021] In one embodiment, the mobile payment code is a universal payment code, a promised payment code, or a non-promised payment code. A universal payment code is generated in accordance with a universal payment app, while a promised payment code is generated without corresponding to a universal payment app but is promised to a universal payment app. A non-promised payment code is generated without corresponding to a universal payment app and is not promised to a universal payment app. If the mobile payment code is a universal payment code, the payment interface includes at least a universal payment link. If the mobile payment code is a promised payment code, the payment interface includes at least a promised payment trigger link and / or a universal payment link. If the mobile payment code is a non-promised payment code, the payment interface includes at least a universal payment link and / or a financial transaction trigger link.

[0022] 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 app; when a promise payment trigger link is selected, the electronic mobile device makes a mobile payment by launching a promise payment app corresponding to the promise payment code, or makes a mobile payment through a universal payment platform; 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 a universal payment platform.

[0023] As described above, the mobile payment method of the present invention includes the following steps: acquire a mobile payment code; the mobile payment code is a non-provisional payment code, which is generated without corresponding to a universal payment app and is not procured with a universal payment app; the universal payment app provides a payment interface according to the acquired mobile payment code; if the mobile payment code is a non-provisional payment code, the payment interface includes at least a universal payment link and / or a financial transaction trigger link; and through the above steps, mobile payments can be made using a single payment app (i.e., a universal payment app). Even if the mobile payment code provided during the mobile payment process is a specific payment code (i.e., a universal payment code) generated without corresponding to a specific payment app (i.e., a universal payment app), it can smoothly initiate the next operation in the mobile payment process. Therefore, a single payment app can be used with multiple mobile payment platforms, especially with mobile payment platforms that have not been procured in advance, thereby avoiding the need to download multiple mobile payment apps and apply for corresponding accounts, or the cumbersome process of applying for different mobile payment codes on different mobile payment platforms.

[0024] The mobile payment system of the present invention also includes a mobile payment code and an electronic mobile device. The mobile payment code is located on a first transaction side, and the mobile payment code is a non-provisional payment code. The electronic mobile device is located on a second transaction side and is installed with a universal payment app. The non-provisional payment code is generated without corresponding to a universal payment app and is not procured with a universal payment app. When the mobile payment code is a non-provisional payment code, the payment interface includes at least a universal payment link and / or a financial transaction trigger link. This design allows mobile payments to be made using a single payment app (i.e., a universal payment app). Even if the mobile payment code provided during the mobile payment process is a specific payment code (i.e., a universal payment code) generated without corresponding to a specific payment app (i.e., a universal payment app), it can smoothly initiate the next operation in the mobile payment process. Therefore, a single payment app can be used with multiple mobile payment platforms, especially with mobile payment platforms that have not been procured in advance. This avoids the need to download multiple mobile payment apps and apply for corresponding accounts, or the cumbersome process of applying for multiple mobile payment codes on different mobile payment platforms. [Effects of the Invention]

[0025] The mobile payment method and system of the present invention provides a mobile payment method and system that can be used with a single payment app across multiple mobile payment platforms, especially for mobile payment platforms that have not been agreed upon in advance, thereby avoiding the need to download multiple mobile payment apps and apply for corresponding accounts, or the cumbersome process of applying for different mobile payment codes on different mobile payment platforms. [Brief explanation of the drawings]

[0026] [Figure 1] FIG. 1 is a flow diagram of a mobile payment method according to one embodiment of the present invention. [Figure 2]FIG. 2 is a flow diagram of an embodiment of the mobile payment method shown in FIG. 1. [Figure 3] 1 is a diagram illustrating a mobile payment system according to one embodiment of the present invention. [Figure 4A] 4 is a diagram showing a payment interface displayed on an electronic mobile device in the mobile payment system shown in FIG. 3. [Figure 4B] 4 is a diagram showing a payment interface displayed on an electronic mobile device in the mobile payment system shown in FIG. 3. [Figure 4C] 4 is a diagram showing a payment interface displayed on an electronic mobile device in the mobile payment system shown in FIG. 3. DETAILED DESCRIPTION OF THE INVENTION

[0027] The preferred embodiments of the mobile payment method and system of the present invention will be described below with reference to the accompanying drawings, in which like elements are denoted by like reference numerals.

[0028] FIG. 1 is a flow diagram of a mobile payment method according to one embodiment of the present invention.

[0029] As shown in FIG. 1, the mobile payment method 100 of this embodiment includes the following steps: Launch a universal payment app (step S01). Obtain a mobile payment code, which may be a universal payment code, a promised payment code, or a non-promised payment code. A universal payment code is generated in correspondence with a universal payment app; a promised payment code is generated without corresponding to a universal payment app but is promised to a universal payment app; a non-promised payment code is generated without corresponding to a universal payment app and is not promised to a universal payment app (step S02). The universal payment app provides a payment interface according to the obtained mobile payment code. If the mobile payment code is a universal payment code, the payment interface includes at least a universal payment link; if the mobile payment code is a promised payment code, the payment interface includes at least a promised payment trigger link and / or a universal payment link; if the mobile payment code is a non-universal payment code, the payment interface includes at least a universal payment link and / or a financial transaction trigger link (step S03). If the universal payment link is selected, the mobile payment is made through a universal payment platform corresponding to the universal payment app; if the promise payment trigger link is selected, the mobile payment is made by launching the promise payment app corresponding to the promise payment code, or through a universal payment platform; if the financial transaction trigger link is selected, the mobile payment is made through a financial transaction platform corresponding to the financial transaction trigger link, or through a universal payment platform (step S04).

[0030] In this embodiment, the order of steps S01 and S02 may be different, and this is not a limitation of the present invention. For example, step S01 may be performed first to launch the universal payment app, and then step S02 may be performed to obtain the mobile payment code; or step S02 may be performed first to obtain the mobile payment code, and then step S01 may be performed to launch the universal payment app. Of course, in other embodiments, steps S01 and S02 may be completed simultaneously, and this is not a limitation of the present invention.

[0031] In this embodiment, the mobile payment code can be any applicable code, such as a barcode or a QR code, and the present invention is not limited thereto.

[0032] In addition, in step S02, the operation of acquiring the mobile payment code can be performed by any applicable method, for example, acquiring an image of the mobile payment code by an image acquisition method (e.g., reading the code with a camera lens), or acquiring a signal of the mobile payment code by a wireless communication method (e.g., signal transmission via short-range wireless communication), and the present invention is not limited thereto.

[0033] In this embodiment, the promised payment code is generated without corresponding to a universal payment app, but is promised to a universal payment app. More specifically, the promised payment code may be generated in correspondence with a payment app, such as a platform A payment code corresponding to payment app A of mobile payment platform A, or a platform B payment code corresponding to payment app B of mobile payment platform B. The universal payment platform corresponding to the universal payment app will enter into an agreement (contract) with mobile payment platform A and mobile payment platform B, and the payment code of platform A and the payment code of platform B will be determined as the promised payment code by the universal payment app. It should be noted that when the universal payment platform enters into an agreement (contract) with mobile payment platform A and mobile payment platform B, the payment code identification ability of the universal payment app will be improved, so that the universal payment app can not only identify (or read) the universal payment code, but also identify (or read) the promised payment code (e.g., platform A payment code and platform B payment code).

[0034] In addition, non-promised payment codes are generated without corresponding to a common payment app and are not promised to a common payment app. In detail, non-promised payment codes are generated in correspondence with a payment app, for example, a platform C payment code corresponding to payment app C of mobile payment platform C, a platform D payment code corresponding to payment app D of mobile payment platform D, etc. However, since the common payment platforms corresponding to the common payment apps have not made a contract with mobile payment platform C and mobile payment platform D, the platform C payment code and platform D payment code are determined to be non-promised payment codes by the common payment app.

[0035] In step S04, if a universal payment link is selected, the mobile payment can be made through a universal payment platform. For example, if a universal payment link is selected, the mobile payment code is a universal payment code, which is generated correspondingly by the universal payment platform, so the universal payment platform can directly complete the mobile payment.

[0036] Furthermore, if the promise payment trigger link is selected in step S04, the promise payment app can be launched to make the mobile payment, or the mobile payment can be made through a common payment platform. For example, if the promise payment trigger link is selected, the mobile payment code is a promise payment code (e.g., the payment code of platform A), which is generated by the corresponding mobile payment platform (e.g., mobile payment platform A), so the corresponding promise payment app (e.g., payment app A) is launched, and the mobile payment is completed through the corresponding mobile payment platform (e.g., mobile payment platform A). In addition, even if the obtained mobile payment code is a promise payment code, the mobile payment can be completed through a common payment platform by transacting with other associated mobile payment platforms (e.g., mobile payment platform A or mobile payment platform B).

[0037] Furthermore, if a financial transaction trigger link is selected in step S04, the mobile payment can be made through a financial transaction platform corresponding to the financial transaction trigger link, or through a general payment platform. For example, if a financial transaction trigger link is selected, the mobile payment code may be a non-provisional payment code (e.g., a payment code from platform C), which is generated by the corresponding mobile payment platform (e.g., mobile payment platform C). Therefore, the corresponding payment app (e.g., payment app C) cannot be launched, and the mobile payment cannot be made. In this case, the app of any corresponding applicable financial transaction platform is launched, and the payment is made through the financial transaction platform in a manner such as a credit card transaction, debit card transaction, prepaid card transaction, bank transfer transaction, or recharge transaction. In addition, even if the obtained mobile payment code is a non-provisional payment code, it can be negotiated with any applicable financial transaction platform (e.g., a financial institution such as a bank or credit card center) through a general payment platform, and then this financial transaction platform can negotiate with an unlinked mobile payment platform (e.g., mobile payment platform C or mobile payment platform D) to complete the mobile payment. Of course, financial institutions will complete mobile payments by being able to pay directly to the collector.

[0038] To make this embodiment clearer, the detailed flow of the embodiment of the mobile payment method of this embodiment will be described with reference to FIG.

[0039] As shown in FIG. 2, step S11 is first performed to launch a general payment app, and then step S12 is performed to obtain a 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 performed first to obtain a mobile payment code, and then the corresponding general payment app (step S11) can be directly launched using the obtained mobile payment code. In one embodiment, steps S11 and S12 can be completed simultaneously. For example, an identification process or program can be installed in the firmware of the mobile device's camera module, allowing the camera module to capture an image of the payment code (e.g., a QR code) and simultaneously identify the payment code. When the code is scanned, the image of the payment code and the identification result (e.g., a webpage and payment channel) are simultaneously displayed on the electronic mobile device (e.g., a mobile phone).

[0040] Next, in step S13, it is determined whether the mobile payment code is a universal payment code. If it is determined in step S13 that the mobile payment code is a universal payment code, then step S14 is performed to provide a universal payment link in the payment interface. In this embodiment, the above step S04 can be performed next, that is, the universal payment link can be selected, and mobile payment can be made through the universal payment platform corresponding to the universal payment app. For details, please refer to the above embodiment and will not be described again here.

[0041] If it is determined in step S13 that the mobile payment code is not a universal payment code, then step S15 is executed to determine whether the mobile payment code is a promised payment code. If it is determined in step S15 that the mobile payment code is a promised payment code, then step S16 is executed to provide a linking trigger link and / or a universal payment link in the payment interface. Here, the payment interface provides, for example, a promised payment trigger link and a universal payment link. In this embodiment, the above step S04 is then executed, i.e., the promised payment trigger link or the universal payment link is selected to perform the mobile payment. For a detailed description, please refer to the above embodiment, and it will not be described again here.

[0042] Furthermore, if it is determined in step S15 that the mobile payment code is not a promised payment code, the mobile payment code is considered to be a non-promised payment code, and step S17 is then performed to provide a financial transaction trigger link and / or a universal payment link in the payment interface. Here, the payment interface provides, for example, a financial transaction trigger link and a universal payment link. In this embodiment, step S04 is then performed, i.e., the mobile payment is performed by selecting the financial transaction trigger link or the universal payment link. For a detailed description, please refer to the above embodiment, and will not be described again here.

[0043] To summarize, the mobile payment method of the present invention includes the following steps: obtain a mobile payment code, the mobile payment code being a universal payment code or a promised payment code, the universal payment code being generated corresponding to a universal payment app, the promised payment code being generated without corresponding to a universal payment app but promised to the universal payment app; the universal payment app providing a payment interface according to the obtained mobile payment code, when the mobile payment code is a universal payment code, the payment interface including at least a universal payment link; when the mobile payment code is a promised payment code, the payment interface including at least a promised payment trigger link and / or a universal payment link; through the above steps, mobile payment can be made using a single payment app (i.e., a universal payment app). 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) generated without corresponding to a specific payment app (i.e., a universal payment app), the next operation in the mobile payment can be smoothly initiated. Therefore, a single payment app can be used on multiple mobile payment platforms, especially on mobile payment platforms that have not been agreed upon in advance. This avoids the need to download multiple mobile payment apps and apply for corresponding accounts, or the cumbersome process of applying for different mobile payment codes on different mobile payment platforms.

[0044] 3 is a diagram illustrating a mobile payment system 200 according to an embodiment of the present invention. In this embodiment, the mobile payment system 200 can apply the above-mentioned mobile payment method 100.

[0045] As shown in FIG. 3, the mobile payment system 200 includes a mobile payment code 20 and an electronic mobile device 30.

[0046] In this embodiment, the mobile payment code 20 is located at the first transaction party, such as the collecting party (e.g., a store). The mobile payment code 20 may be, but is not limited to, a universal payment code, a promised payment code, or a non-promised payment code. In this embodiment, the mobile payment code 20 may be, but is not limited to, a barcode or a QR code. In this embodiment, the mobile payment code 20 is exemplified by a QR code. The mobile payment code 20 may be a physical barcode printed on any carrier (e.g., paper, business card, etc.) or a virtual barcode displayed on an electronic display, and the present invention is not limited to this. In this embodiment, the mobile payment code 20 is exemplified by a barcode printed on a business card.

[0047] As shown in Figure 3, the electronic mobile device 30 is located at the second transaction side, for example, the paying side (e.g., the consumer), and is installed with a universal payment app. The universal payment app can correspond to the universal payment code, that is, the universal payment code is generated corresponding to the universal payment app.

[0048] For example, the electronic mobile device 30 may be, but is not limited to, a consumer's mobile phone, a smart watch, etc., and includes at least an image capture module 31 and a display module 32. The image capture module 31 may be, for example, a camera module of a mobile phone, and may capture the mobile payment code 20 using an image capture method. It should be noted that the above description is for illustrative purposes only and is not intended to limit the scope of the present invention. In another embodiment, the electronic mobile device 30 may include a wireless communication module, for example, a near field communication (NFC) module, which receives and captures the mobile payment code 20 using a wireless communication method (e.g., near field communication).

[0049] The display module 32 may be a mobile phone display module, such as an LCD display module or an OLED display module, which displays the payment interface 33 provided by the mobile payment code 20 acquired by the universal payment app. It should be noted that the above description is for illustrative purposes only and is not intended to limit the present invention.

[0050] 2, 3, and 4A to 4C, if the mobile payment code 20 is determined to be a universal payment code in step S13, step S14 is subsequently executed to provide a universal payment link 331 in the payment interface 33 (as shown in FIG. 4A), allowing the consumer to select the universal payment link 331 to make a mobile payment. For details, please refer to the above embodiments, and they will not be described again here. Please note that the above description is for illustrative purposes only and is not intended to limit the present invention.

[0051] Furthermore, if it is determined in step S15 that the mobile payment code 20 is a promised payment code, step S16 is subsequently executed to provide the promised payment trigger link 332 and / or the universal payment link 331 in the payment interface 33. In this embodiment, as shown in FIG. 4B, the promised payment trigger link 332 and the universal payment link 331 are simultaneously provided in the payment interface 33. Therefore, the consumer can select the promised payment trigger link 332 or the universal payment link 331 to make a mobile payment. For a detailed description, please refer to the above embodiment, and it will not be described again here. It should be noted that the above description is for illustrative purposes only and is not intended to limit the present invention.

[0052] Furthermore, if it is determined in step S15 that the mobile payment code 20 is a non-promised payment code, step S17 is subsequently executed to provide the financial transaction trigger link 333 and / or the universal payment link 331 in the payment interface 33. In this embodiment, as shown in FIG. 4C , the financial transaction trigger link 333 and the universal payment link 331 are simultaneously provided in the payment interface 33. Thus, the consumer can select the financial transaction trigger link 333 or the universal payment link 331 to make a mobile payment. For a detailed description, please refer to the above embodiment, and it will not be described again here. It should be noted that the above description is for illustrative purposes only and is not intended to limit the present invention.

[0053] The following describes the application of the mobile payment method and system of this embodiment using a practical example. For example, when a consumer travels to another country and makes a purchase, such as an American consumer traveling to Asia and making a purchase there, the consumer's mobile phone may not have a mobile payment function applicable to the local store, forcing the consumer to pay with cash or a physical credit card. In other words, the consumer wants to pay with mobile payment, and the local store can also use mobile payment, but because the mobile payment platforms of the two parties are different, the two parties cannot use mobile payment. In such a situation (especially when a foreign tourist makes a purchase at a store in another country), the mobile payment method and system of this embodiment can define the mobile payment code provided by the local store as a non-promised payment code of this embodiment, so that the consumer (foreign tourist, second transaction party) can smoothly make a mobile payment at the local store (first transaction party providing the mobile payment code) by following step S17 above.

[0054] To summarize, the mobile payment system of the present invention includes a mobile payment code and an electronic mobile device. The mobile payment code is located on the first transaction side and is a universal payment code or a promised payment code. The electronic mobile device is located on the second transaction side and is installed with a universal payment app. The universal payment code is generated corresponding to the universal payment app, and the promised payment code is generated without corresponding to the universal payment app but is promised to the universal payment app. When the electronic mobile device acquires the mobile payment code, the universal payment app provides a payment interface according to the acquired mobile payment code. If the mobile payment code is a universal payment code, the payment interface includes at least a universal payment link. If the mobile payment code is a promised payment code, the payment interface includes at least a promised payment trigger link and / or a universal payment link. With the above design, mobile payment can be performed using a single payment app (i.e., a universal payment app). 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) generated without corresponding to a specific payment app (i.e., a universal payment app), the next operation in the mobile payment can be smoothly initiated. Therefore, a single payment app can be used on multiple mobile payment platforms, especially on mobile payment platforms that have not been agreed upon in advance. This avoids the need to download multiple mobile payment apps and apply for corresponding accounts, or the cumbersome process of applying for different mobile payment codes on different mobile payment platforms.

[0055] The above are only some of the embodiments of the present invention, and are not intended to limit the present invention. Any modifications or changes made without departing from the spirit and scope of the present invention should fall within the scope of the claims of the present invention. [Industrial Applicability]

[0056] The present invention relates to a mobile payment method and system applicable to mobile payment. [Explanation of symbols]

[0057] 100 Mobile Payment Methods 20 Mobile Payment Code 200 Mobile Payment System 30 Electronic Mobile Devices 31 Image Acquisition Module 32 Display Module 33 Payment Interface 331 Universal Payment Link 332 Promise Settlement Trigger Link 333 Financial Transaction Trigger Link Steps S01-S04, S11-S17

Claims

1. Mobile payment methods include: Steps to launch a general payment app: obtaining a mobile payment code; and and providing a payment interface according to the mobile payment code acquired by the universal payment app; The mobile payment code is a non-promised payment code, which is generated without corresponding to the universal payment app and is not promised with the universal payment app; When the mobile payment code is a non-compatible payment code, the payment interface includes at least a compatible 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 barcode or a QR code.

3. The mobile payment method according to claim 1, wherein the step of acquiring the mobile payment code acquires the mobile payment code by an image acquisition method or a wireless communication method.

4. The mobile payment method according to claim 1, characterized in that, when the universal payment link is selected, the mobile payment is made through a universal payment platform corresponding to the universal payment app, and when the financial transaction trigger link is selected, the mobile payment is made through a financial transaction platform corresponding to the financial transaction trigger link, or the mobile payment is made through the universal payment platform.

5. The mobile payment code is a universal payment code, a promised payment code, or a non-promised payment code, and the universal payment code is generated corresponding to the universal payment app, and the promised payment code is generated without corresponding to the universal payment app but is promised to the universal payment app. When the mobile payment code is the universal payment code, the payment interface includes at least the universal payment link; when the mobile payment code is the promised payment code, the payment interface includes at least the promised payment trigger link and / or the universal payment link; The mobile payment method further comprises: If the universal payment link is selected, making a mobile payment through a universal payment platform corresponding to the universal payment app; When the promise payment trigger link is selected, the promise payment app corresponding to the promise payment code is launched to make the mobile payment, or the mobile payment is made through the universal payment platform; and The mobile payment method according to claim 1, characterized in that, when the financial transaction trigger link is selected, the mobile payment is made through a financial transaction platform corresponding to the financial transaction trigger link, or the mobile payment is made through the general payment platform.

6. The mobile payment system A mobile payment code located on the first transaction side, the mobile payment code being a non-promised payment code; and An electronic mobile device is arranged at a second transaction side and is equipped with a universal payment application, and the non-promised payment code is generated without corresponding to the universal payment application, and the universal payment application is not promised; When the electronic mobile device receives the mobile payment code, the universal payment app provides a payment interface according to the received mobile payment code; If the mobile payment code is the non-promised payment code, the payment interface includes at least a universal 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 barcode or a QR code.

8. The mobile payment system of claim 6, wherein the electronic mobile device includes an image capture module for capturing the mobile payment code by an image capture method, or a wireless communication module for capturing the mobile payment code by a wireless communication method.

9. The mobile payment system of claim 6, characterized in that when the universal payment link is selected, the electronic mobile device makes the mobile payment through a universal payment platform corresponding to the universal payment app, and when the financial transaction trigger link is selected, the mobile payment is made through a financial transaction platform corresponding to the financial transaction trigger link, or the mobile payment is made through the universal payment platform.

10. The mobile payment code is a universal payment code, a promised payment code, or a non-promised payment code, and the universal payment code is generated corresponding to the universal payment app, and the promised payment code is generated without corresponding to the universal payment app but is promised to the universal payment app. When the mobile payment code is the universal payment code, the payment interface includes at least the universal payment link; when the mobile payment code is the promised payment code, the payment interface includes at least the promised payment trigger link and / or the universal payment link; When the universal payment link is selected, the electronic mobile device performs the mobile payment through a universal payment platform corresponding to the universal payment app; When the promise payment trigger link is selected, the electronic mobile device launches a promise payment app corresponding to the promise payment code to make the mobile payment, or makes the mobile payment through the universal payment platform; The mobile payment system of claim 6, characterized in that, when the financial transaction trigger link is selected, the electronic mobile device makes the mobile payment through a financial transaction platform corresponding to the financial transaction trigger link, or makes the mobile payment through the general payment platform.

Images