Methods for cross-service provider online payment

Abstract

This invention relates to a method for online checkout between a selected issuer's issuer system and an acquirer's acquirer system using mobile payments. The acquirer's online merchant can provide a URL to request payment from a payer of an issuer different from the acquirer. This URL instructs the payer's user device to receive a list of issuers comprising multiple mobile payment service providers, allowing the payer to select one from the list as the issuer for payment. The URL can then instruct the selected issuer to automatically process subsequent steps to deliver funds from the issuer to the acquirer.

Description

Online Payment Method across Service Providers Related Application: This application claims the benefit of U.S. Provisional Application No. 63 / 385,946, filed on December 2, 2023, entitled "A METHOD FOR IMPROVING ONLINE QR CODE PAYMENT", the entire content of which is incorporated herein by reference. The present invention relates to a method for facilitating online payment across service providers, particularly for two mobile payment service providers (MPSPs) with different transaction QR code formats. In recent years, mobile payment has become a popular payment method due to its simplicity of operation and the fact that the payer only needs a mobile device. Among all mobile payment methods, QR code scanning is probably the most widely used method when consumers shop at merchants. In addition to traditional stores, with the development of e-commerce, more and more merchants sell products online. Therefore, the demand for mobile payment in e-commerce is increasing. To request and receive payment, the web page of an online merchant may display a QR code on the checkout page, or it may also redirect the consumer to log in to his / her mobile payment account to continue the payment. Then, the consumer can transfer the payment to the merchant's account, provided that both the consumer's account and the merchant's account belong to the same mobile payment service provider (MPSP). In both of the above cases, online merchants can only receive payments from a limited number of mobile payment service providers (MPSPs). If a consumer does not have an application (App) of any acceptable MPSP installed, he / she may not be able to use mobile payment to purchase goods or services from online merchants. This is especially true in the case where a consumer purchases goods or services from a foreign website, because many MPSPs only provide services locally and do not operate overseas. To solve this problem, some mobile payment service providers may accept cross-MPSP transactions (also known as bridging transactions) by signing bilateral agreements with other service providers and modifying their systems accordingly to be able to accept payments from other service providers. However, even with the above improvements, some problems may still arise. First, signing bilateral agreements with many MPSPs and modifying the system accordingly is cumbersome and time-consuming. A service provider needs to modify its system whenever a new partner joins its payment network. Another problem occurs when a consumer uses a portable device (such as a smartphone) to browse the web page of an online store and check out. The portable device cannot actually scan the QR code on the online checkout page displayed on its screen. For consumers, it is very inconvenient to first take a screenshot and then upload the screenshot of the QR code to another application to "scan" the QR code for payment. If the transaction is a cross-MPSP transaction (a bridging transaction), the situation may be even more complex. Even if the cross-MPSP agreement applies, it is still difficult to conduct cross-MPSP transactions online because the QR code or the link on the checkout page may not direct the consumer to the payment confirmation page of the MPSP they have selected. Therefore, new methods need to be developed to facilitate online payments across MPSPs. This document provides a method for online checkout between an issuer system of a selected issuer and an acquirer system of an acquirer using mobile payment. The method of this application is applicable when a consumer (a payer) wants to purchase goods or services from an online merchant through mobile payment. There may be many available mobile payment service providers (MPSPs) in a payment network, where different MPSPs in the network are linked together through a bridging service provider. The payer can select an MPSP in the network as the issuer to make the payment, and the online merchant can select another MPSP in the network as the acquirer to receive the payment. After the payer decides to check out, the online merchant can provide a checkout URL (which can also be embedded in the merchant's QR code) for the payer to make the payment. Since there may be many MPSPs available as issuers, before processing the payment, the payer's user device can request an issuer list including one or more available issuers for the payer to select. The selected issuer should be different from the acquirer because two members of the same MPSP do not require a bridging service provider. The checkout URL can be used to instruct the user device to generate a delivery request for the payment. Therefore, the delivery request can be generated based on the checkout URL and a delivery transaction can be requested from the acquirer system of the acquirer. In some embodiments, the user device is a portable device, and the checkout URL is set to open the issuer applications of one or more available issuers installed on the portable device. From the perspective of a bridging system of a bridging service provider, the online checkout method includes the following steps: (1) providing a list of issuers including one or more available issuers to a user device of a payor, and (2) receiving a delivery request from the issuer system of the selected issuer, the selected issuer being selected from the one or more available issuers. Before providing the list of issuers including the one or more available issuers, the method may further include the step of receiving a list request from the user device of the payor. The list request can be received from the user device of the payor, or can be redirected by the acquirer system. In the case where the list request is directly received from the user device of the payor, the checkout URL can be used to direct the user device to the bridging system, and the checkout URL can be embedded in a QR code of the bridging service provider. In another case where the list request is redirected by the acquirer system, the checkout URL can be used to direct the user device to the acquirer system, and the checkout URL can be embedded in a QR code of the acquirer. After receiving the delivery request from the issuer system, the online checkout method may further include the following steps to complete the transaction: (1) providing the delivery request to the acquirer system, (2) receiving a payment request from the acquirer system, (3) providing the payment request to the issuer system, (4) receiving a payment confirmation from the issuer system confirming the payment request, and (5) providing the payment confirmation to the acquirer system. From the perspective of the user device of the payor, the online checkout method includes the following steps: (1) receiving a list of issuers including one or more available issuers for the payor to select, and (2) providing a delivery request to the issuer system of the selected issuer, the selected issuer being selected from the one or more available issuers. Before receiving the list of issuers including the one or more available issuers, the method may further include the step of providing a list request by the user device. There are at least three different embodiments for providing and receiving the list of issuers. In the first embodiment, the list request is provided to the bridging system of the bridging service provider, and the list of issuers is also received from the bridging system. In the second embodiment, the list request is provided to the acquirer system of the acquirer, and the list of issuers is also received from the acquirer system. In the third embodiment, the list request is provided to the acquirer system, but the list request is redirected from the acquirer system to the bridging system, so the list of issuers is received from the bridging system. In the case where the list request is provided to the bridging system, the checkout URL can be set to direct the user device to the bridging system, and the checkout URL can be embedded in the QR code of the bridging service provider. In another case where the list request is provided to the acquirer system, the checkout URL can be set to direct the user device to the acquirer system, and the checkout URL can be embedded in the acquirer's QR code. After providing the delivery request to the issuer system, the online checkout method may further include the following steps to complete the transaction: (1) receiving a payment request from the issuer system, and (2) providing a payment confirmation to the issuer system to confirm the payment request. From the perspective of the issuer system of the selected issuer, the online checkout method includes the following steps: (1) receiving a delivery request from a user device of a payor, and (2) transmitting the delivery request to a bridging system of a bridging service provider. Since the checkout URL can be resolved by the bridging system or the acquirer system, the issuer system may not resolve the payment request embedded in the checkout URL. After providing the delivery request to the bridging system, the online checkout method may further include the following steps to complete the transaction: (1) receiving a payment request from the bridging system, (2) providing the payment request to the user device, (3) receiving a payment confirmation from the user device to confirm the payment request, and (4) providing the payment confirmation to the bridging system. From the perspective of the acquirer system of the acquirer, the online checkout method may include a step of directly transmitting an issuer list to the user device after the acquirer system receives the list request, or may also include a step of redirecting the user device to the bridging system after the acquirer system receives the list request. For the first case, the method includes the following steps: (1) receiving a list request from a user device of a payee, (2) providing the user device of the payee with an issuer list including one or more available issuers, and (3) receiving a delivery request from the issuer system of the selected issuer via the bridging system, where the selected issuer is selected from the one or more available issuers. For the second case, the method includes the following steps: (1) receiving a list request from a user device of a payee, (2) redirecting the user device to a bridging system of a bridging service provider such that the bridging system provides the user device with an issuer list including one or more available issuers, and (3) receiving a delivery request from the issuer system of the selected issuer via the bridging system, where the selected issuer is selected from the one or more available issuers. In both cases, the checkout URL may be set to direct the user device to the acquirer system, and the checkout URL may be embedded in the QR code of the acquirer. After receiving the delivery request from the issuer system, the online checkout method may further include the following steps to complete the transaction: (1) providing a payment request to the bridging system, and (2) receiving a payment confirmation from the bridging system confirming the payment request. Other objects, advantages, and novel features of the present invention will become more apparent through the following detailed implementation manners in conjunction with the accompanying drawings.

Brief Description of the Drawings

Claims

1. A method for online checkout between an issuer system of a selected issuer and an acquiring system of an acquiring party, comprising: A bridging system of a bridging service provider receives a listing request from a user device of a payer; The bridging system provides the user device with a list of issuers including one or more available issuers; and the bridging system receives a delivery request from the issuer system of the selected issuer, the selected issuer being chosen by the payer from the one or more available issuers; wherein: the list request is generated by the user device based on a checkout URL having the format of the bridging service provider or the acquirer; the delivery request is generated by the issuer system based on the checkout URL; the delivery request requests a delivery transaction to the acquirer system; and the payment code format of the selected issuer is different from the payment code formats of the bridging service provider and the acquirer, and the issuer system cannot fully parse the checkout URL, requiring payment to the acquirer via the bridging system.

2. The method of request item 1, wherein the manifest request is redirected from the acquiring system before being received by the bridging system.

3. The method of request item 1, wherein the user device is a portable device, and the checkout URL is used to open the publisher application of the one or more available publishers installed on the portable device.

4. The method of request item 1, wherein the checkout URL is used to direct the user device to the bridging system.

5. As in request item 4, wherein the checkout URL is embedded in a QR code of the bridging service provider.

6. The method of request item 2, wherein the checkout URL is used to direct the user device to the acquiring system.

7. As in request item 6, wherein the checkout URL is embedded in a QR code of the acquiring party.

8. The method of request item 1, further comprising, upon receiving the delivery request from the issuer's system: The bridging system provides the delivery request to the acquiring system; The bridging system receives a payment request from the acquiring system; the bridging system provides the payment request to the issuing system; the bridging system receives a payment confirmation from the issuing system confirming the payment request; and the bridging system provides the payment confirmation to the acquiring system.

9. A method for online checkout between an issuer system of a selected issuer and an acquiring system of an acquiring party, comprising: A user device of a payer provides a listing request based on a checkout URL having a format of a bridging service provider or the acquirer; the user device receives an issuer list including one or more available issuers from the acquirer's system or a bridging system of the bridging service provider; and the user device of the payer provides the checkout URL to the issuer system of the selected issuer to generate a delivery request, the selected issuer being chosen from the one or more available issuers; wherein: the delivery request is generated by the issuer system based on the checkout URL; the delivery request requests a delivery transaction to the acquirer's acquirer system; and the payment code format of the selected issuer differs from the payment code formats of the bridging service provider and the acquirer, and the issuer system cannot fully parse the checkout URL, requiring payment to the acquirer via the bridging system.

10. The method of claim 9, wherein the user device is a portable device, and the checkout URL is used to open the publisher application of the one or more available publishers installed on the portable device.

11. The method of request item 9, wherein the list request is provided to the acquiring system.

12. The method of request item 11, wherein the list of issuers is received by the acquiring system.

13. The method of request item 11, wherein the list of issuers is received from the bridging system.

14. The method of request item 9, wherein the list request is provided to the bridging system and the issuer list is received from the bridging system.

15. The method of request item 13, wherein the list request is redirected from the acquiring system to the bridging system.

16. The method of request item 14, wherein the checkout URL is used to direct the user device to the bridging system.

17. The method of request item 16, wherein the checkout URL is embedded in a QR code of the bridging service provider.

18. The method of request item 11, wherein the checkout URL is used to direct the user device to the receiving system.

19. The method of request item 18, wherein the checkout URL is embedded in a QR code of the recipient.

20. The method of request item 9, after providing the delivery request to the issuer's system, further includes: The user device receives a payment request from the issuer's system; And a payment confirmation provided by the user device to the issuing system confirming the payment request.

21. A method for online checkout between an issuer system of a selected issuer and an acquiring system of an acquiring party, comprising: The selected issuer's issuer system receives a checkout URL with a format of either a bridging service provider or the acquirer from a user device of a payer, and generates a delivery request based on the checkout URL; and the selected issuer's issuer system provides the delivery request to a bridging system of the bridging service provider; wherein: the delivery request requests a delivery transaction to the acquirer's acquirer system; and the selected issuer's payment code format differs from the bridging service provider's and the acquirer's payment code formats, and the issuer's system cannot fully parse the checkout URL, requiring payment to the acquirer via the bridging system.

22. The method of request item 21, wherein the issuing system does not parse a payment request embedded in the checkout URL.

23. The method of request item 22, wherein the checkout URL is resolved by the bridging system or the acquiring system.

24. The method of request item 21, further comprising, after providing the delivery request to the bridging system: The issuing system receives a payment request from the bridging system; The payment request is provided to the user device by the issuing system; The issuing system receives a payment confirmation from the user device confirming the payment request; And the issuing system provides the payment confirmation to the bridging system.

25. A method for online checkout between an issuer system of a selected issuer and an acquiring system of an acquiring party, comprising: The acquiring system of the acquiring party receives a list request from a user device of a payer; The acquiring system redirects the user device to a bridging system of a bridging service provider, whereby the bridging system provides the user device with a list of one or more available issuers; and the acquiring system receives a delivery request from the issuer system of the selected issuer, chosen by the payer from the one or more available issuers, via the bridging system; wherein: the list request is generated by the user device based on a checkout URL having the acquiring system's format; the delivery request is generated by the issuer system based on the checkout URL; the delivery request requests a delivery transaction to the acquiring system; and the payment code format of the selected issuer differs from that of the acquiring system, and the issuer system cannot fully parse the checkout URL, requiring payment to the acquiring system via the bridging system.

26. The method of claim 25, wherein the user device is a portable device, and the checkout URL is used to open the publisher application of the one or more available publishers installed on the portable device.

27. The method of request item 25, wherein the checkout URL directs the user device to the acquiring system.

28. The method of request item 27, wherein the checkout URL is embedded in a QR code of the acquiring party.

29. The method of request item 25, further comprising, upon receiving the delivery request from the issuer's system: The acquiring system provides a payment request to the bridging system; And a payment confirmation received by the acquiring system from the bridging system confirming the payment request.

30. A method for online checkout between an issuer system of a selected issuer and an acquiring system of an acquiring party, comprising: The acquiring system of the acquiring party receives a list request from a user device of a payer; The acquiring system provides the payer's user device with a list of one or more available issuers; and the acquiring system receives a delivery request from the issuer system of the selected issuer via a bridging system, the selected issuer being chosen by the payer from the one or more available issuers; wherein: the list request is generated by the user device based on a checkout URL having the acquiring system's format; the delivery request is generated by the issuer system based on the checkout URL; the delivery request requests a delivery transaction to the acquiring system; and the selected issuer's payment code format differs from the acquiring system's payment code format, and the issuer system cannot fully parse the checkout URL, requiring payment to the acquiring system via the bridging system.

31. The method of claim 30, wherein the user device is a portable device, and the checkout URL is used to open the publisher application of the one or more available publishers installed on the portable device.

32. The method of request item 30, wherein the checkout URL directs the user device to the acquiring system.

33. The method of request item 32, wherein the checkout URL is embedded in a QR code of the acquiring party.

34. The method of request item 30, further comprising, upon receiving the delivery request from the issuer's system: The acquiring system provides a payment request to the bridging system; And a payment confirmation received by the acquiring system from the bridging system confirming the payment request.

Images