TWM605955U - Mobile payment integration platform - Google Patents

Abstract

The present model provides a mobile payment integration platform, which is an agent payment platform and is provided with a transaction server, so that at least one payer can use a mobile device to scan the payment identification code of at least one payee to perform a payment operation. The transaction server is provided with a transaction page and a payment page, and the transaction page is provided with a plurality of payment tools and a payee information. After the mobile device scans the payment identification code, telecommunications connects to the transaction server and browses the transaction page. When the payer clicks on one of the payment tools, the transaction server telecommunications transmits a channel request to The mobile device enters the payment page after processing the route request, so that the payer can use the payment page to complete the payment operation.

Description

Mobile payment integration platform

This creation is an electronic payment platform, especially a mobile payment integration platform that allows at least one payee to provide multiple payment channels to consumers at one time after registration is completed, so as to achieve the purpose of simplifying the consumption payment model. It has the effect of enhancing the popularity of mobile payment.

Credit card payment is the mainstream online payment method. Since accepting credit cards must be approved by the bank, many individual businesses or small and medium-sized enterprises with insufficient qualifications or capital below the threshold will be limited by the difficulty of their application It is too late to adopt with complexity. Therefore, a few years ago, third-party payment institutions with certain assets and credibility rose to provide a public and reliable intermediary platform for buyers and sellers through the cash flow platform provided by them, while linking banks to handle funds settlement and customers Services and other related work, while connecting a large number of customers and consumers through big data, so that both buyers and sellers can smoothly enter into transactions and solve the problem of C2C (Customer to Customer, person-to-person) transaction choking.

With the widespread use of wireless networks and smart phones, third-party payment platforms have developed a wide range of mobile payment tools such as PayPal, Apple Pay, Alipay, Jiekou, Line Pay, 7-11 Point, etc. to allow the use of After installing a specific business application (APP, Application), you can perform payment transactions by scanning a code. The barcode is often a QR Code (Quick Response Code), a two-dimensional barcode. In the prior art, the QR code cannot be interoperable with various mobile payment tools. That is, one barcode for one merchant only It can be used for a specific industry. In this way, if the merchant wants to provide multiple mobile payment channels to consumers, it will need to apply and review the specific industry from multiple parties, and the application documents, qualifications and review periods required by each specific industry are different, resulting in mobile payment Because of the high burden of promotion, many small businesses such as snack bars, roadside stalls and taxis are unwilling to spend a lot of extra time and energy, resulting in low willingness to adopt or only provide a few mobile payment channels. On the other hand, a consumer must install the corresponding application to make mobile payment through a specific channel. That is to say, even if a merchant provides three mobile payment methods ABC, if the consumer does not install the corresponding ABC three The payment tool also cannot complete payment through mobile payment. The foregoing is also the reason why the current market share of various payment tools is not high, and there are so many types of payment tools, but the penetration rate of electronic wallets in Taiwan has not been able to go further. Furthermore, the more payment channels the merchant provides, the more third-party payment providers need to reconcile and request payments in the future. This not only causes more complicated account management procedures, but also seriously affects operational efficiency and is not conducive to Business strategy.

With this in mind, how to integrate the hard-to-find electronic payment tools on the market so that merchants can achieve diversified business strategies without having to apply for multiple operators repeatedly, and at the same time, support consumers without having to install a large number of mobile devices APP has high consumption flexibility, which is the subject of this creation.

In view of the above problems, the purpose of this creation is to provide a platform for merchants to have diversified payment channels only after registration. At the same time, through the platform, you can manage and withdraw payments from various channels at once. Funds to help businesses realize the effect of improving operating efficiency.

To achieve the above objective, this creation discloses a mobile payment integration platform for at least one payer to use a mobile device to scan at least one of the payee's payment identification code to perform a payment operation, characterized in that: the mobile payment integration The platform is an agency payment and receipt platform, which has a transaction server, a transaction page and a payment page in the transaction server, and the transaction page is equipped with multiple payment tools and a payee information; the mobile device scans After the payment identification code, the telecommunications connects to the transaction server and browses the transaction page. When the payer clicks on one of the payment tools, the transaction server telecommunications transmits a channel request to the mobile device, The mobile device enters the payment page after processing the route request, so that the payer can use the payment page to complete the payment operation.

According to the above platform, each of the payment tools is a credit card payment tool, an electronic wallet, a code generator or a code generator, and the payment page corresponds to the payment tool and is a credit card payment page, an electronic wallet application page, A code generates a page or a code generates a page. When the payer clicks on one of the payment tools, the transaction server sends a wallet read request to search for and read a wallet data in the mobile device, and the wallet data corresponds to the payment tool It is at least one of tool application interface, payment amount, payment object, payment date, mobile phone number, gender, and age. When the transaction server fails to obtain the wallet data after transmitting the wallet read request, it transmits a setting program to the mobile device for the payer to set the wallet data.

Moreover, when the payer uses the payment page to perform the payment operation, the wallet data is formed or updated, and the mobile device feeds back the wallet data to the transaction server for the mobile payment integration platform to record and statistically analyze the wallet data. Obtain behavioral information corresponding to one of the payers. In this way, the mobile payment integration platform not only saves the payee from spending a lot of energy and time in processing mobile payments, but also helps the payee to further understand consumer demand through the collection and analysis of the wallet data And tendencies to improve the business direction.

When the mobile device scans the payment identification code and telecommunications connects to the transaction server, the transaction server sends a wallet search request to search for the e-wallet set in the mobile device to obtain a wallet data, the transaction server The device uses the wallet information to update the payment tools set on the transaction page. The transaction server is telecommunications connected to the server of an external bank. When the payment operation is completed, the bank’s server sends the payment for the payment operation to the transaction server, and the transaction server forms a settlement notice to For the payee to confirm with the payer. The collection identification code is obtained by the payee registering on the mobile payment integration platform, and the payee performs a withdrawal operation on the mobile payment integration platform.

In addition, the second purpose of this creation is to provide a mobile payment integration platform for at least one payer to use a mobile device to scan at least one of the payee's payment identification code, and then drive the server of one of the payers' banks The mobile payment integration platform is characterized in that a transaction server and a data server are provided in the mobile payment integration platform. The data server is telecommunications connected to the transaction server. The transaction server is provided with a transaction page. There are multiple payment tools and a payee information on the page, and the payee identification code is obtained by the payee registering with the data server; the mobile device scans the payee identification code and telecommunications connects to the transaction server to browse On the transaction page, when the payer clicks on one of the payment tools, the transaction server respectively transmits a channel request to the mobile device and a payment request to the bank’s server, the mobile device After feeding back the wallet data corresponding to one of the payment tools to the transaction server, the transaction server forwards the wallet data to the server of the bank to drive the server of the bank to perform the payment operation.

Wherein, each of the payment tools is a credit card payment tool or an electronic wallet. When the payer clicks on one of the payment tools, the transaction server sends a wallet read request to search for and read a wallet data in the mobile device, and the wallet data corresponds to the payment tool It is at least one of tool application interface, payment amount, payment object, payment date, mobile phone number, gender, and age. When the transaction server fails to obtain the wallet data after transmitting the wallet read request, it transmits a setting program to the mobile device for the payer to set the wallet data. When the mobile device receives and processes the channel request, it forms or updates the wallet data, the mobile device feeds back the wallet data to the transaction server, and the data server records and analyzes the wallet data to obtain the corresponding payment One of the behavioral information. When the mobile device scans the payment identification code and telecommunications connects to the transaction server, the transaction server sends a wallet search request to search for the e-wallet set in the mobile device to obtain a wallet data, the transaction server The device uses the wallet information to update the payment tools set on the transaction page. When the payment operation is completed, the bank's server sends the payment for the payment operation to the transaction server, and the transaction server forms a settlement notice and sends it to the mobile device for the payer to confirm, and at the same time, sends the The payment notification is sent to the data server for the recipient to log in to the account to check the payment. When the payee registers the data server and obtains the payee identification code, the data server creates an account corresponding to the payee so that the payee can set at least one bank information for a withdrawal operation .

In summary, through the use of the mobile payment integration platform, the payee can have a diversified third-party payment channel without having to apply to multiple banks or third-party cash flow companies in installments and times. In this way, for small businesses such as food stalls, roadside stalls, or taxis, they can provide various electronic payment channels without spending a lot of time and energy, so they will actively invest in supporting mobile electronic payment services. In addition to increasing payment convenience and stimulating consumption, it is more effective to promote the application penetration rate of e-commerce. In addition, the transaction page and the payment page can be displayed in the form of a web page, so that the mobile device can directly and instantly use the mobile payment integration platform without pre-installing programs. It can be seen that this creation is not only commercial practical, but also effective in promoting the development of the technology industry.

In order to enable those with ordinary knowledge in the field to understand the content of this creation clearly, please refer to the following descriptions and diagrams.

Please refer to Figures 1 and 2, which are respectively the architecture diagram and operation flowchart of a preferred embodiment of the creation. As shown in the figure, the mobile payment integration platform 1 is an agency payment platform that has signed a contract with a statutory financial institution, which provides at least one payee 3, such as roadside stalls, food stalls, taxis, delivery services, restaurants Merchants selling products or services such as grocery stores or beauty salons can provide all kinds of payment channels at one time to facilitate at least one payer 2 to directly use a mobile device 20, such as a mobile phone or tablet A computer or any electronic device with data calculation function scans a payment identification code 30 of the payee 3 to perform a payment operation 200. The mobile payment integration platform 1 is provided with a transaction server 10, and the transaction server 10 is provided with a transaction page 100 and a payment page 101, and both the transaction page 100 and the payment page 101 can be displayed in the form of a web page or an APP screen. The transaction page 100 is provided with a plurality of payment tools 1000 and a payee information 1001. Each of the payment tools 1000 can be a credit card payment tool, an electronic wallet, a code generator, or a code generator. After the payer 2 uses the mobile device 20 to scan the payment identification code 30 in step S10, step S11: the mobile device 20 telecommunications connects to the transaction server 10 to browse the transaction page 100. Step S12, when the payer 2 browses the payment tools 1000 on the transaction page 100, and clicks on one of the payment tools 1000 that meets the requirements, it proceeds to step S13: the transaction server 10 telecommunications A route request 102 is transmitted to the mobile device 20. Next, in step S14, the mobile device 20 enters the payment page 101 after processing the route request 102, so that the payer 2 can use the payment page 101 to complete the payment operation 200. Accordingly, for merchants in the current consumer market, the mobile payment integration platform 1 series can eliminate the inconvenience of applying and registering each independent mobile payment tool one by one, so it can make the consumer transaction market easier and more convenient. The collection and payment model improves the convenience of businesses in business operations and at the same time enhances consumers’ desire to buy. For consumers, they can freely choose the payment method on demand to pay, and they no longer need to be limited by the types of payment provided by the consumer merchants to meet their self-consumption habits and achieve the effect of improving consumer satisfaction.

Please refer to Figures 3 and 4, which are respectively the architecture diagram and the operation flowchart of the second preferred embodiment of the creation. As shown in the figure, another implementation aspect of the mobile payment integration platform 1 created by this invention is provided with a transaction server 10 and a data server 11 for at least one payer 2 to use a mobile device 20 to scan at least one receipt After the payment identification code 30 of the payer 3, the server 4 of the bank of the payer 2 is driven to perform a payment operation 200. The transaction server 10 is telecommunications connected to the data server 11, and a transaction page 100 is provided in the transaction server 11, and the transaction page 100 is provided with a plurality of payment tools 1000 and a payee information 1001. The operation process of the mobile payment integration platform 1 can include the following steps:

In step S20, the payee 3 can use any electronic device to telecommunications connect to the data server 11 and then register to obtain the payee identification code 30. In step S21, after the payer 2 uses the mobile device 20 to scan the payment identification code 30, the mobile device 20 telecommunications connects to the transaction server 10 in step S22 to browse the transaction page 100. Step S23, the payer 2 browses the payment tools 1000 on the transaction page 100, and clicks on one of the payment tools 1000 that meets the requirements, and then proceeds to step S24: the transaction server 10 respectively The telecommunication transmits a route request 102 to the mobile device 20 and a payment request 103 to the server 4 of the bank. Next, in step S25, after the mobile device 20 processes the route request 102, it feeds back a wallet data 201 corresponding to the payment tool 1000 to the transaction server 10, and the transaction server 10 performs step S26: transfer the wallet data 201 to The server 4 of the bank drives the server 4 of the bank to execute the payment operation 200.

Continuing from the content of the first and second embodiments, please refer to Figures 5 to 10, which are the architecture diagram, operation flowchart, and schematic diagrams of the third preferred embodiment of the creation. As shown in the figure, the mobile payment integration platform 1 is an agency payment platform integrating various third-party electronic payment tools known nowadays for at least one payer 2 to scan at least one payee using a mobile device 20 After the payment identification code 30 is one of 3, the server 4 of an external bank is driven to perform a payment operation 200. The mobile payment integration platform 1 may be provided with a transaction server 10, a data server 11, and a service server 12. The transaction server 10 telecommunications connects the data server 11 and the service server 12, and the data server 11 Telecom connects to the service server 12. The transaction server 11 is provided with a transaction page 100 and a payment page 101. The transaction page 100 is provided with a plurality of payment tools 1000, a payee information 1001 and a function form 1002, and each of the payment tools 1000 can be one Credit card payment tool, an electronic wallet, a code generator, a code generator or a ticket payment tool. The payment page 101 corresponds to the payment tool 1000 and can be a credit card payment page, an electronic wallet application page, a code generation page, a code generation page, or a voucher payment page. The service server 12 has a service page 120, and the operation process of the mobile payment integration platform 1 may include the following steps:

First, in step S30, the payee 3 can use any electronic device such as a computer, a tablet, a mobile phone, or a mobile phone to connect to the data server 11 by telecommunications and then register, so that an account 110 is created in the data server 11 and obtained The payment identification code 30. The payment identification code 30 can be a barcode (Barcode); QR Code, PDF417 barcode or two-dimensional bar code such as Hanxin code and other information totems for the recipient 3 to use the electronic device to display and share the payment identification code 30, it can also be printed directly and displayed to the payer through business cards, cardboard or billboards2. In addition, the payee 3 can set personal information, preferences, and bank information 1100 in the account 110. By setting the bank information 1100, the payee 3 can directly pay to the integrated mobile payment platform at any time. 1 Perform withdrawal operations. It can be seen that while the payee 3 provides multiple payment channels to the payer 2 at one time, it can also withdraw money collected from various third-party electronic payment tools at one time, which greatly facilitates the The payee 3 collects accounts and realizes the improvement of the application penetration rate and industrial applicability of electronic payment.

In step S31, after the payer 2 uses the mobile device 20 to scan and calculate the payment identification code 30, the mobile device 20 performs step S32: telecommunication connects to the transaction server 10. In step S320, the transaction server 10 sends a wallet search request 104 to the mobile device 20 to search for the electronic wallet built in the mobile device 20 to obtain a wallet data, and then the transaction server 10 uses the wallet data in step S321 The wallet information updates the payment tools 1000 set on the transaction page 100. For example, if the mobile device 20 is equipped with three wallets such as Jiekou Payment, Alipay, and Apple Pay, the transaction page 100 will only display these three tools, or display these three tools, the credit card payment tool, and the barcode generation Device, the code generator and the ticket payment tool. Next, in step S322, the mobile device 20 reads and browses the transaction page 100 sent by the transaction server 10, so that the payment instruments 1000 on the transaction page 100 can be included in the payer 2 The type and quantity of the electronic wallet installed vary, which simplifies the choice of the payer 2 and improves the payment speed. In addition, this function can be executed by the transaction server 10 forcibly or executed to directly adjust the initial transaction page 100, and can also be executed by a function button set on the transaction page 100, so that the transaction page 100 starts with The fixed payment tools 1000 are presented, but the payer 2 is allowed to adjust itself through the function button. In addition, step S32 can also be directly followed by step S322 without adjusting the payment tools 1000 to the transaction page 100.

And, in step S33, when the payer 2 browses the payment tools 1000 on the transaction page 100 and clicks on one of the payment tools 1000 that meets the requirements, the process proceeds to step S330: telecommunication transmission to a wallet A read request 105 is sent to the mobile device 20 so that the mobile device 20 performs the wallet read request 105 in step S331 and searches for itself whether there is a wallet data 201 corresponding to the payment tool 1000? The wallet data 201 can be at least one of tool application programming interface (API), payment amount, payment object, payment date, mobile phone number, gender, and age. If the mobile device 10 has the wallet data 201, step S332, the wallet data 201 is fed back to the transaction server 10. Conversely, if the corresponding wallet data 201 is not set in the mobile device 20, in step S333, the transaction server 10 sends a setting program to the mobile device 20 for the payer 2 to install the corresponding electronic wallet and After setting the wallet data 201, the wallet data 201 is fed back to the transaction server 10. In this way, even if the mobile device 20 is equipped with the electronic wallet, the mobile device 20 still cannot feed back the corresponding wallet data 201 because the payer 2 has not used, registered or activated the electronic wallet, so the payer 2 The wallet data 201 still needs to be set through the setting procedure. In step S334, the transaction server 10 updates the content of the payment page 101 according to the wallet data 201, and telecommunications transmits a route request 102 to the mobile device 20 and a payment request 103 to the server 4 of the bank.

In step S34, the mobile device 20 enters the payment page 101 after executing the route request 102, so that the payer 2 can fill in the payment amount, authorization information, consumption information, or remarks, and then update the wallet data 201, and the mobile device 20 The updated wallet data 201 is fed back to the transaction server 10 in step S35. In this creation, if the payer 2 chooses to use a supermarket barcode or code for payment, step S33 can skip directly to step S34 to open the barcode generation page for the payer 2 to fill in the information to form the wallet data 201 Of course, steps S330 to S333 can also be performed so that the payer 2 presets some designated consumption information through the setting procedure and then enters the payment page 101 to fill in the payment amount to generate the wallet data 201. In this way, through the execution of the wallet read request 105, no matter what tool the payer 2 chooses to use for payment, the payment page 101 can contain the wallet data 201 so that the payer 2 does not need to fill in a lot of time again. Moreover, as long as the payer 2 has previously set the wallet data 201 corresponding to the payment tool 1000 but has not been deleted from the mobile device 20, even if the mobile device 20 has completed the payment or the electronic wallet has been removed. Those with ordinary knowledge should know that the setup program can include the route request 102 to import the mobile device 20 into the credit card payment page, the barcode generation page, or the code generation page, so that the payer needs to fill in completely twice Only consumer information can make payment.

Step S36, the transaction server 10 forwards the wallet data 201 to the server 4 of the bank corresponding to the payer 2 or the corresponding payment supermarket, so as to use the payment request 103 and the wallet data 201 to drive the server 4 of the bank Perform the payment operation 200. Furthermore, when the payer 2 chooses to use a supermarket barcode or code for payment, the transaction server 10 transmits the payment request 103 and the wallet data 201 to the server 4 of the bank corresponding to the payment supermarket, and The server 4 of the bank of the supermarket executes the payment operation 200 after the payer 2 completes the payment with the barcode or code.

When the payment operation is completed, step S37, the server 4 of the bank sends the payment of the payment operation 200 to the transaction server 10, so that the transaction server 10 forms a payment notification for the payee 3 and the The payer 2 confirms. At the same time, the transaction server 10 stores the payment notice in the data server 11 so that the payee 3 can log in to the account 110 to check the account. In this way, the payee 3 can provide multiple payments at once While channeling to the payer 2, it can also manage the payments received from various third-party electronic payment tools at one time, which is beneficial to the payee 3 for reconciliation.

In step S38, the transaction server 10 records the wallet data 201 and the settlement notice in the data server 11, so that the data server 11 statistically analyzes the wallet data 201 and the settlement notice to obtain the corresponding payer 2 One behavior information and the operating status of the payee 3. It can be seen that through the mobile payment integration platform 1 system, consumer behavior information can be collected to achieve the purpose of integrated analysis, so as to understand the real-time needs and tendencies of the consumer market, which is beneficial to subsequent industrial applications.

It is worth mentioning that in addition to integrating third-party payment tools, the mobile payment integration platform 1 can also integrate functions such as ordering services, reservation services, shopping services, delivery services, purchasing services, and taxi-hailing services. After the payer 2 uses the mobile device 20 to scan the payment identification code 30 to consume a merchant, the payer 2 can also register the data server 10 to record the consumption experience, so that the payer 2 wants to consume the payment again 2 days later At the time of the merchant, the payer 2 can execute the service page 120 through the function form 1002 for consumption. In addition, the payer 2 does not need to register, and can also open the service page 120 through the function form 1002 on the transaction page 100 and search for a merchant for consumption. It can be seen that the mobile payment integration platform 1 of this creation achieves extremely high commercial practicability by integrating various electronic payment tools and integrating various online functions, which is beneficial to the further development and promotion of e-commerce technology.

Among them, the components described in this creation can be realized through hardware or software supplemented by hardware. For example, the definitions of the transaction server 10, the data server 11, and the service server 12 essentially refer to The integration of various hardware devices such as CPU, microprocessor or memory, supplemented by software to realize its technical features. In addition, the transaction server 10, the data server 11 and the service server 12, or even other servers for hosting the mobile payment integration platform 1, all have level specifications that meet the banking requirements for encryption and information security. And efficiency.

However, the above-mentioned are only the preferred embodiments of this creation, and are not used to limit the scope of implementation of this creation; therefore, equal changes and modifications made without departing from the spirit and scope of this creation should be covered in This creation is within the scope of the patent.

1: Mobile payment integration platform 10: Transaction server 100: Transaction page 1000: payment instrument 1001: payee information 1002: function form 101: payment page 102: route request 103: payment request 104: Wallet search request 105: wallet read request 11: Data server 110: Account 1100: Bank Information 12: Service server 120: Service page 2: payer 20: mobile device 200: payment job 201: Wallet data 3: payee 30: Collection identification code 4: The bank's server S10～S38: steps

Figure 1 is a structural diagram of a preferred embodiment of the creation. Figure 2 is a flow chart of the operation of a preferred embodiment of the creation. Figure 3 is a structural diagram of the second preferred embodiment of the creation. Figure 4 is the operation flowchart of the second preferred embodiment of the creation. Figure 5 is a structural diagram of the third preferred embodiment of the creation. Figures 6A, 6B, and 6C are the operation flowcharts of the third preferred embodiment of the creation. Figure 7 is a schematic diagram of the payment identification code of the third preferred embodiment of the creation. Figure 8 is a schematic diagram (1) of the transaction page of the third preferred embodiment of the creation. Figure 9 is a schematic diagram of the transaction page (2) of the third preferred embodiment of the creation. Figure 10 is a schematic diagram of the service page of the third preferred embodiment of creation.

1: Mobile payment integration platform

10: Transaction server

100: Transaction page

101: payment page

1000: payment instrument

1001: payee information

102: route request

2: payer

20: mobile device

200: payment job

3: payee

30: Collection identification code

Claims (16)

A mobile payment integration platform for at least one payer to scan at least one of the payee's payment identification code using a mobile device to perform a payment operation, characterized in that: The mobile payment integration platform is an agency collection and payment platform, which has a transaction server, and the transaction server has a transaction page and a payment page, and the transaction page is equipped with multiple payment tools and a payee information; After the mobile device scans the payment identification code, telecommunications connects to the transaction server and browses the transaction page. When the payer clicks on one of the payment tools, the transaction server telecommunications transmits a channel request to The mobile device enters the payment page after processing the route request, so that the payer can use the payment page to complete the payment operation. For example, the mobile payment integration platform of claim 1, wherein each of the payment tools is a credit card payment tool, an electronic wallet, a code generator or a code generator, and the payment page corresponds to the payment tool and is a credit card payment page, An electronic wallet application page, a code generation page, or a code generation page. For example, the mobile payment integration platform of request 2, wherein when the payer clicks on one of the payment tools, the transaction server sends a wallet read request to search and read the mobile device A wallet data, which corresponds to the payment tool and is at least one of tool application interface, payment amount, payment object, payment date, mobile phone number, gender, and age. For example, in the mobile payment integration platform of request 3, when the transaction server does not obtain the wallet data after sending the wallet read request, it sends a setting program to the mobile device for the payer to set the wallet data. For example, the mobile payment integration platform of claim 4, wherein when the payer uses the payment page to perform the payment operation, the wallet data is formed or updated, and the mobile device feeds back the wallet data to the transaction server for the mobile payment integration The platform records and statistically analyzes the wallet data to obtain behavioral information corresponding to one of the payers. For example, in the mobile payment integration platform of request 5, when the mobile device scans the payment identification code and telecommunications connects to the transaction server, the transaction server sends a wallet search request to search for the electronic device in the mobile device After the wallet obtains a wallet data, the transaction server uses the wallet data to update the payment tools set on the transaction page. For example, the mobile payment integration platform of claim 6, in which the transaction server is connected to a server of an external bank by telecommunications, and when the payment operation is completed, the bank’s server sends the payment for the payment operation to the transaction server, and The transaction server forms a settlement notice for the payee and the payer to confirm. For example, the mobile payment integration platform of claim 7, wherein the collection identification code is obtained by the payee registering with the mobile payment integration platform, and the payee performs a withdrawal operation on the mobile payment integration platform. A mobile payment integration platform for at least one payer to scan at least one of the payee's receiving identification code using a mobile device, and then to drive a server of one of the payees to perform a payment operation, characterized by: The mobile payment integration platform is provided with a transaction server and a data server. The data server is telecommunications connected to the transaction server. The transaction server is provided with a transaction page. The transaction page is equipped with multiple payment tools and a receipt. The payer’s information, and the payee identification code is obtained by the payee registering with the data server; the mobile device scans the payee identification code and telecommunications connects to the transaction server to browse the transaction page. When the payer clicks When one of the payment tools is selected, the transaction server respectively transmits a channel request to the mobile device and a payment request to the server of the bank, and the mobile device feeds back the wallet data corresponding to one of the payment tools. After the transaction server, the transaction server forwards the wallet data to the bank's server to drive the bank's server to perform the payment operation. For example, the mobile payment integration platform of claim 9, wherein each of the payment tools is a credit card payment tool or an electronic wallet. For example, the mobile payment integration platform of claim 10, wherein when the payer clicks on one of the payment tools, the transaction server sends a wallet read request to search and read the mobile device A wallet data, which corresponds to the payment tool and is at least one of tool application interface, payment amount, payment object, payment date, mobile phone number, gender, and age. For example, in the mobile payment integration platform of request 11, when the transaction server does not obtain the wallet data after sending the wallet read request, it sends a setting program to the mobile device for the payer to set the wallet data. For example, the mobile payment integration platform of claim 12, wherein when the mobile device receives and processes the channel request, the wallet data is formed or updated, the mobile device feeds back the wallet data to the transaction server, and the data server records and Statistically analyze the wallet data to obtain behavioral information of one of the payers. For example, the mobile payment integration platform of request 13, wherein when the mobile device scans the payment identification code and telecommunications connects to the transaction server, the transaction server sends a wallet search request to search for the electronic device in the mobile device After the wallet obtains a wallet data, the transaction server uses the wallet data to update the payment tools set on the transaction page. For example, the mobile payment integration platform of request 14, wherein when the payment operation is completed, the bank's server sends the payment of the payment operation to the transaction server, and the transaction server sends a settlement notification to the transaction server The device allows the payer to confirm, and at the same time, sends the settlement notice to the data server for the payee to log in to the account to check the account. For example, the mobile payment integration platform of claim 15, wherein when the payee registers the data server and obtains the payee identification code, the data server creates an account corresponding to the payee for the payee Set up at least one bank profile and perform a withdrawal operation.

Images