Payment portal display method, apparatus, device, medium, and product

Abstract

The application discloses a payment entrance display method, device, equipment, medium and product. The payment entrance display method comprises the following steps: receiving a first input of a user for triggering display of a payment interface in a merchant application program; in response to the first input, displaying the payment interface, and scanning an application program in an electronic device according to a target scanning identifier pre-configured in the merchant application program to obtain a scanning result, wherein the target scanning identifier is configured to identify N application programs with a preset payment component; and in the case that it is determined according to the scanning result that any installed application program exists in the N application programs, displaying a payment entrance corresponding to a target application program in the payment interface, wherein the target application program comprises at least one installed application program in the N application programs. According to the embodiment of the application, the payment entrance corresponding to the third-party application program installed in the electronic device can be accurately displayed in the merchant application program, and the operation process of the user is simplified.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of interface interaction, and particularly relates to a payment entry display method and device, equipment, medium and product. BACKGROUND

[0002] With the continuous development of the unified payment platform service, more and more application programs are added to the unified payment platform to realize the payment function of the application program through the payment component service provided by the unified payment platform.

[0003] In the IOS system, the payment entry corresponding to the third-party application program associated with the unified payment platform is generally displayed in the second-level payment interface, and the user needs to click the payment method identifier corresponding to the unified payment platform displayed in the first-level payment interface of the merchant application program to see the payment entry corresponding to each third-party application program associated in the second-level payment interface, which leads to a complicated user operation process. SUMMARY

[0004] The application embodiment provides a payment entry display method, device, equipment, medium and product, which can accurately display the payment entry corresponding to the third-party application program associated with the unified payment platform in the merchant application program, and simplify the user operation process.

[0005] In a first aspect, the application embodiment provides a payment entry display method, which comprises:

[0006] receiving a first input of a user for triggering display of a payment interface in a merchant application program;

[0007] In response to the first input, displaying the payment interface and scanning the application program in the electronic device according to the target scanning identifier pre-configured in the merchant application program to obtain a scanning result, wherein the target scanning identifier is configured to identify N application programs with a preset payment component, and N is an integer greater than 1;

[0008] In the case where it is determined according to the scanning result that there is any installed application program in the N application programs, displaying the payment entry corresponding to the target application program in the payment interface, wherein the target application program includes at least one installed application program in the N application programs.

[0009] In a second aspect, the application embodiment provides a payment entry display device, which comprises:

[0010] a first input module configured to receive a first input of a user for triggering display of a payment interface in a merchant application program;

[0011] The first response module is configured to display the payment interface in response to the first input, and scan an application in the electronic device according to a target scanning identifier pre-configured in the merchant application, to obtain a scanning result, wherein the target scanning identifier is configured to identify N applications having a preset payment component, and N is an integer greater than 1.

[0012] The entry display module is configured to display a payment entry corresponding to a target application in the payment interface, if it is determined according to the scanning result that any installed application exists in the N applications, wherein the target application includes at least one installed application in the N applications.

[0013] In a third aspect, an electronic device is provided, which includes a processor and a memory storing computer program instructions.

[0014] The processor implements the steps of the payment entry display method according to any one of the embodiments of the first aspect when executing the computer program instructions.

[0015] In a fourth aspect, a computer readable storage medium is provided, which stores computer program instructions. The computer program instructions are executed by a processor to implement the steps of the payment entry display method according to any one of the embodiments of the first aspect.

[0016] In a fifth aspect, a computer program product is provided. Instructions in the computer program product are executed by a processor of an electronic device to cause the electronic device to perform the steps of the payment entry display method according to any one of the embodiments of the first aspect.

[0017] The payment entry display method, device, equipment, medium and product in the embodiments of the present application can configure a unified target scanning identifier for a plurality of applications having a preset payment component, scan the applications in the electronic device by using the target scanning identifier when the user triggers to display the payment interface in the merchant application, and display the payment entry corresponding to the at least one installed application in the payment interface if it is determined that at least one installed application exists in the plurality of applications. In this way, since one scanning identifier is configured for a plurality of applications having the same preset payment component, the payment entry corresponding to the installed application in the plurality of applications can be accurately displayed in the merchant application. In addition, since the payment entry corresponding to the scanned application is displayed in the payment interface, i.e. the first-level payment interface, of the merchant application, the user does not need to operate to jump to the second-level payment interface to see and select the payment entry of the corresponding application to complete payment, and thus the user operation process can be simplified. Attached Figure Description

[0018] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a flowchart illustrating a payment entry display method provided in one embodiment of this application;

[0020] Figure 2 This is a schematic diagram of the payment interface corresponding to the merchant application provided in this application;

[0021] Figure 3 This is a schematic diagram of the payment method selection interface provided in this application;

[0022] Figure 4 This is a schematic diagram of a secondary interface corresponding to the payment interface provided in this application;

[0023] Figure 5 This is a schematic diagram of the structure of a payment gateway display device provided in one embodiment of this application;

[0024] Figure 6 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application. Detailed Implementation

[0025] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0026] It is to be understood that the terminology used herein such as first and second, and the like, is only used to distinguish one from another among two or more entities or operations, and does not require or imply that there is any such relationship or order between or among the entities or operations. Moreover, the use of terms such as "including", "containing", or any other variation thereof, is intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element preceded by "comprises" does not, without more constraints, foreclose the existence of additional identical elements in the process, method, article, or apparatus that comprises the stated element.

[0027] At present, in addition to the payment portal corresponding to the self-provided wallet, the payment interface in the merchant application program can also display the payment portal corresponding to other third-party application programs, so as to provide more payment method choices for the user. In consideration of the user's payment experience, the merchant application program will scan the application programs installed in the current electronic device before displaying the payment portal to the user, and the payment portal corresponding to the third-party application program will be displayed on the basis that the third-party application program is installed in the electronic device.

[0028] However, the number of application programs that can be scanned by the same merchant in the IOS system is limited, because the IOS system scans the installed application programs by scanning the identifier (such as scheme), and the upper limit of the number of identifiers that can be configured in the same merchant application program for scanning is 50. For the plurality of application programs corresponding to the unified payment platform and having the same preset payment component, the number of scanning identifier resources is required more, so only part of the application programs can be selected from the plurality of application programs, and different scanning identifiers are configured for them respectively. This may cause that the application program installed in the electronic device is not configured with a scanning identifier in the merchant application program, and the application program not installed in the electronic device is configured with a scanning identifier in the merchant application program, so that the payment portal corresponding to the third-party application program installed in the electronic device cannot be accurately displayed in the merchant application program. For example, the application program configured for scanning in the merchant application program is A, and the application program installed in the electronic device is B, so the payment portal of the application program B cannot be normally displayed in the merchant application program, but in fact the user can pay through the payment portal corresponding to the application program B.

[0029] In addition, there are many payment levels. Since the payment entry provided by the plurality of applications corresponding to the unified payment platform is usually displayed in the merchant application, the payment mode identifier of the unified payment platform is first displayed in the payment interface of the merchant application, and after the user clicks the payment mode identifier, the payment entry of the corresponding application is displayed in the second-level payment interface, thereby causing the user operation process to be relatively cumbersome.

[0030] To solve the problems in the prior art, embodiments of the present application provide a payment entry display method, device, equipment, medium and product. The payment entry display method can be applied to a scenario of displaying a payment entry. First, the payment entry display method provided by the embodiments of the present application is introduced.

[0031] Figure 1 FIG. 1 is a flowchart of a payment entry display method provided by an embodiment of the present application. As shown in FIG. 1, the payment entry display method can specifically include the following steps: Figure 1

[0032] S110, receiving a first input of a user for triggering display of a payment interface in a merchant application;

[0033] S120, in response to the first input, displaying the payment interface, and scanning an application in an electronic device according to a target scanning identifier pre-configured in the merchant application to obtain a scanning result, wherein the target scanning identifier is configured to identify N applications having a preset payment component, and N is an integer greater than 1;

[0034] S130, in a case where it is determined according to the scanning result that there is at least one installed application in the N applications, displaying a payment entry corresponding to a target application in the payment interface, wherein the target application includes at least one installed application in the N applications.

[0035] ​Thus, by configuring one unified target scan identifier for the plurality of applications having the preset payment component, the application in the electronic device is scanned by the target scan identifier when the user triggers the display of the payment interface in the merchant application, and in the case where it is determined that there is at least one installed application in the plurality of applications, the payment portal corresponding to the at least one installed application can be displayed in the payment interface. In this way, since one scan identifier is configured for the plurality of applications having the same preset payment component, the limitation of the number of scan identifiers can be broken through, and thus the payment portal corresponding to the installed application in the electronic device in the plurality of applications can be accurately displayed in the merchant application. In addition, since the payment portal corresponding to the scanned application is displayed in the payment interface, i.e., the first-level payment interface, of the merchant application, the user does not need to operate to jump to the second-level payment interface to see and select the payment portal of the corresponding application to complete payment, and thus the user operation process can be simplified.

[0036] The specific implementation of each of the above steps will be described below.

[0037] In some embodiments, in S110, the first input may, for example, be an input of the user clicking a payment button in the merchant application for an order.

[0038] For example, after the user selects the items to be purchased in the merchant application, the user can trigger the generation of an order, and then click a payment button in the order page to trigger the display of the payment interface of the merchant application.

[0039] In some embodiments, in S120, different scan identifiers can be configured in different merchant applications, and the number of scan identifiers that can be configured in each merchant application is limited. The merchant application can scan the installed applications in the electronic device by one or more scan identifiers configured in advance, and determine whether there is an application corresponding to the pre-configured scan identifier. The N applications having the preset payment component can be applications corresponding to a unified payment platform providing the preset payment component.

[0040] In the embodiments of the present application, one unified identifier can be set for the N applications having the preset payment component in the merchant application, and the unified identifier can be configured as a scan identifier for scanning applications, i.e., a target scan identifier.

[0041] In addition, in the IOS system, the scan identifier may, for example, be a scheme for scanning.

[0042] Based on this, in some specific examples, when displaying the payment interface of the merchant application, the installed applications in the electronic device can be scanned according to the unified scheme pre-configured in the merchant application, to determine whether one or more of the N applications corresponding to the unified scheme exist in the scanned results. The scanned results can include the number of installed applications in the N applications, and can also include the identification or payment portal of the installed applications in the N applications.

[0043] In some embodiments, in S130, if the number of installed applications in the scanned results is greater than 0, or there is an identification or payment portal of any application, it can be determined that at least one installed application exists in the N applications, and then the payment portal corresponding to the target application can be displayed in the payment interface of the currently displayed merchant application. The target application can include one or more installed applications in the N applications.

[0044] In some embodiments, S130 can specifically include:

[0045] The payment portal corresponding to the target application is displayed as a payment option of the target payment method, and the identification corresponding to the target payment method is displayed in the payment interface.

[0046] Here, the target payment method is a payment method corresponding to a preset payment component, that is, a payment method corresponding to a unified payment platform.

[0047] For example, in addition to displaying the payment portal corresponding to the target application, the payment method identification corresponding to the unified payment platform, that is, the identification corresponding to the target payment method, can also be displayed in the payment interface of the merchant application.

[0048] For example, as shown in Figure 2 The finally displayed payment interface of the merchant application can include the payment method identification 21 corresponding to the unified payment platform, the payment portal 22 corresponding to the application A associated with the unified payment platform and installed in the current electronic device, and the payment portal 23 corresponding to the application B, and the payment portal corresponding to the scanned other third-party application. In the payment interface, the user can quickly initiate the application A for payment by selecting the payment portal 22, so that, compared with the method of displaying the payment portal corresponding to each application in the second-level payment interface in the prior art, the payment method identification 21 and the corresponding payment option can be displayed in the first-level payment interface for the user to select without jumping to the second-level payment interface.

[0049] In some embodiments, the number of target application programs can be fixed, for example, can be fixedly set as M, M is an integer, and 2≤M≤N; different target application programs correspond to different payment portals.

[0050] Based on this, in some embodiments, before S130, the payment portal display method provided by the embodiments of the present application can further include:

[0051] In the case that the number L of installed application programs in the N application programs is greater than M, then M application programs are determined from the installed application programs as target application programs;

[0052] In the case that the number L of installed application programs in the N application programs is equal to M, the installed application programs are determined as target application programs;

[0053] In the case that the number L of installed application programs in the N application programs is less than M, (M-L) application programs are determined from the uninstalled application programs in the N application programs, and (M-L) application programs and the installed application programs are determined as target application programs, wherein L is a positive integer, and L≤N.

[0054] Here, the target application programs can be all installed application programs in the N application programs in the current electronic device, can be part of the installed application programs in the N application programs in the current electronic device, or can be a combination between all installed application programs and part of uninstalled application programs in the N application programs in the current electronic device, which is not limited here.

[0055] Exemplarily, according to the size relationship between the number L of installed application programs in the N application programs and the number M of target application programs that need to be displayed, it can be determined which application programs in the N application programs are target application programs.

[0056] In some specific examples, if the number L of installed application programs in the N application programs is 3, and the number M of application program payment portals that can be displayed is 2, then two application programs that are most likely to be selected by the user can be selected from the three installed application programs as target application programs according to a preset selection rule, so as to display the payment portals corresponding to the two target application programs in the payment interface of the merchant application program.

[0057] In another specific example, if the number L of installed application programs in the N application programs is 2, and the number M of application program payment portals that can be displayed is 2, then the two application programs are directly selected as target application programs, so as to display the payment portals corresponding to the two target application programs in the payment interface of the merchant application program.

[0058] In some embodiments, if the number of installed applications L among the N applications is 1 and the number of fixed displayable application payment portals M is 2, in addition to the installed application as one of the target applications, the other target application can be selected from the other (N-1) uninstalled applications according to a preset selection rule as the one most likely to be selected by the user, so as to display the payment portals corresponding to the two target applications in the payment interface of the merchant application.

[0059] In this way, by using different display schemes for different situations, the limited display positions in the payment interface can be fully utilized, and the payment portals corresponding to all or part of the installed applications or the applications that are not installed but are likely to be selected by the user can be effectively displayed, thereby improving the payment portal display efficiency.

[0060] Based on this, in order to improve the probability of the user selecting the payment portal corresponding to the target application, in some embodiments, the step of determining M applications from the installed applications as target applications can specifically include:

[0061] Obtaining payment preferential information corresponding to each of the installed applications;

[0062] According to the payment preferential information, determining the preferential strength corresponding to each of the installed applications, respectively;

[0063] Based on the preferential strength, determining M applications with the largest preferential strength from the installed applications as target applications.

[0064] Here, the preset selection rule can be to select the application to be displayed according to the size of the preferential strength of each installed application. The preferential strength can be determined by the preferential amount and / or the use threshold.

[0065] Exemplarily, when the number of installed applications L among the N applications is greater than the number of fixed displayable application payment portals M, the merchant application can send a preferential information query request to the unified payment platform or the server corresponding to each installed application through the background, so that the unified payment platform or the server corresponding to each application returns the payment preferential information corresponding to each application. In this way, the merchant application can determine the M applications with the largest preferential strength among the N applications as the target applications to be displayed according to the preferential strength of each installed application.

[0066] Similarly, in some embodiments, the step of determining (M-L) applications from the (N-M) applications that are not installed, can specifically include:

[0067] obtaining payment discount information corresponding to each of the (N-M) applications that are not installed;

[0068] determining, according to the payment discount information, a discount intensity corresponding to each of the (N-M) applications that are not installed, respectively;

[0069] determining, based on the discount intensity, (M-L) applications that have the largest discount intensity from the (N-M) applications that are not installed as the target applications.

[0070] Here, the way of selecting (M-L) applications from the (N-M) applications that are not installed can also be performed according to the size of the discount intensity, which is the same as the above selection method, and for the sake of brevity of the table, it will not be repeated here.

[0071] Based on this, in some embodiments, the S130 can specifically include:

[0072] determining, based on a preset priority rule, an arrangement order corresponding to the target applications, wherein the preset priority rule includes at least one of an installed application priority display and a large discount intensity application priority display, and the display priority of the installed application is higher than the display priority of the large discount intensity application;

[0073] displaying, in the payment interface, payment entrances corresponding to the target applications according to the arrangement order.

[0074] Exemplarily, when displaying the payment entrances corresponding to the target applications, the target applications can be first sorted according to a preset priority rule, wherein the preset priority rule can include an installed application priority display, followed by a large discount intensity application priority display, and in addition, a default arrangement order set by the unified payment platform according to the access time of the applications. Of course, the arrangement order of the target applications can also be customized by the user according to the needs, which is not limited here.

[0075] In this way, the payment entrances corresponding to the target applications can be arranged and displayed in the payment interface of the merchant application according to the determined arrangement order, so as to further improve the probability of the user selecting the target application for payment.

[0076] In addition, when the payment entrances corresponding to the target application programs are displayed in the payment interface, the payment discount information of the corresponding application program can be displayed at the position corresponding to each payment entrance to attract the user to select the payment method for payment. For the target application program for which the payment discount information is not queried or the query fails, the corresponding payment discount information can not be displayed.

[0077] In addition, in order to enable the merchant application program to normally jump to the target payment interface corresponding to the target application program through the payment entrance of the target application program selected by the user, in some embodiments, different jump identifiers are configured in the merchant application program for different application programs in the N application programs.

[0078] Correspondingly, the payment entrance display method provided by the embodiments of the present application can further include:

[0079] receiving a second input of the user on the payment entrance;

[0080] In the case that the target application program is an installed application program, in response to the second input, the target payment interface corresponding to the target application program is jumped to according to the target jump identifier corresponding to the target application program;

[0081] In the case that the target application program is an uninstalled application program, in response to the second input, the target application program is downloaded and installed in the electronic device.

[0082] Here, the second input can be, for example, a click input of the user on the payment entrance.

[0083] Exemplarily, the embodiments of the present application can further set one jump identifier for each of the N application programs in the merchant application program, and the jump identifiers corresponding to different application programs are different, wherein the jump identifier and the scanning identifier are identifiers of different use types, and the jump identifier can be used to indicate that the merchant application program jumps from its own interface to the interface corresponding to other application programs. The number of jump identifiers that can be configured for each merchant application program is not limited. In the IOS system, the jump identifier can be, for example, a scheme used for application program jumping.

[0084] Based on this, in some specific examples, as Figure 2 As shown in the figure, in the case that the application program A is an installed application program in the current electronic device and the application program B is an uninstalled application program in the current device, if the user clicks the payment entrance 22 corresponding to the application program A, the payment interface corresponding to the application program A can be jumped to according to the jump identifier corresponding to the application program A. If the user clicks the payment entrance 23 corresponding to the application program B, the application program B can be triggered to be downloaded and installed so that the user can use the application program B to complete the payment.

[0085] Additionally, in some embodiments, the step of downloading and installing the target application in response to the second input when the target application is not installed may specifically include:

[0086] If the target application is not installed, in response to the second input, a payment method selection interface is displayed, and the payment entry corresponding to each of the N applications is displayed in the payment method selection interface;

[0087] Receive a third input from the user for the first payment entry point, where the first payment entry point is the payment entry point corresponding to the first application among N applications;

[0088] If the first application is an installed application, in response to the third input, the user is redirected to the first payment interface corresponding to the first application.

[0089] If the first application is not installed, in response to the third input, the first application is downloaded and installed on the electronic device.

[0090] Here, the payment method selection interface can be a drop-down page, meaning it can be displayed when the user selects an uninstalled application. For example... Figure 3 As shown, the payment method selection interface displays the payment entry points for all applications associated with the unified payment platform. Users can continue to select the payment entry point for a previously chosen but not yet installed application, or select payment entry points for other installed or uninstalled applications, thus increasing user flexibility. In other words, the first application can be the user's selected target application, or it can be any of the N applications other than the user's selected target application.

[0091] In some specific examples, if the user is in such Figure 2 If the payment interface shown selects payment entry 23 corresponding to application B, and application B is not installed on the current electronic device, or the user has not logged in or authorized application B, then the system will redirect to display the following: Figure 3 The payment method selection interface is shown. If the user selects payment entry 24 corresponding to application C in this payment method selection interface, and application C is not installed, the electronic device will be triggered to download and install application C; if the user selects payment entry 22 corresponding to application A in this payment method selection interface, and application A is an installed application, the electronic device will be triggered to jump to the payment interface corresponding to application A, so that the user can use the payment function of application A to complete the payment operation.

[0092] Based on this, in order to distinguish between displaying installed applications and uninstalled applications, in some embodiments, the above step of displaying N application payment portals in the payment method selection interface can specifically include:

[0093] Displaying the payment portals corresponding to the installed applications in the N applications in the first area of the payment method selection interface, and displaying the payment portals corresponding to the uninstalled applications in the N applications in the second area of the payment method selection interface.

[0094] For example, as shown in the payment method selection interface, Figure 3 the installed applications and the uninstalled applications can be displayed in different areas of the interface respectively, wherein the payment portal 21 corresponding to the installed application A can be displayed in the first area 31, and the payment portal 23 corresponding to the uninstalled application B and the payment portal 24 corresponding to the application C can be displayed in the second area 32.

[0095] In this way, by distinguishing between displaying the payment portals corresponding to the installed and uninstalled applications in different areas, the user can be facilitated to make a selection.

[0096] In addition, it should be noted that the payment portals corresponding to the applications in the above payment method selection interface can also be arranged and displayed according to the arrangement order of the applications, and the specific application sorting manner is the same as above, which will not be described here.

[0097] In addition, the payment interface of the merchant application can also be provided with a target component, which can be used to trigger the display of the full-amount application secondary page with the preset payment component. For example, as shown in the payment interface, Figure 2 the user can trigger the display of the secondary page as shown in the payment interface, Figure 4 by clicking the target component 25 displayed in the payment interface, wherein the payment portals corresponding to all applications with the preset payment component can be fully displayed in the secondary page, and the arrangement order of the applications can be determined by the unified payment platform, and the display manner and logic support can be configured in advance in the unified payment platform according to the merchant dimension.

[0098] In addition, if the user selects an application that has been installed in the electronic device but has not logged in or has not opened the unified payment service in the payment interface of the merchant application or the payment method selection interface, the user can be guided to log in or open the unified payment service. If the user cancels the login or the payment fails, the above secondary page can be returned.

[0099] It should be noted that the application scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the emergence of new application scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0100] Based on the same inventive concept, the present application also provides a payment entry display device. Specifically, the payment entry display device is described in detail in combination with Figure 5

[0101] Figure 5 FIG. 1 is a structural schematic diagram of a payment entry display device provided by an embodiment of the present application.

[0102] As shown in Figure 5 , the payment entry display device 500 can include:

[0103] a first input module 501 configured to receive a first input of a user for triggering display of a payment interface in a merchant application;

[0104] a first response module 502 configured to, in response to the first input, display the payment interface and scan an application in an electronic device according to a target scanning identifier pre-configured in the merchant application to obtain a scanning result, wherein the target scanning identifier is configured to identify N applications having a preset payment component, and N is an integer greater than 1;

[0105] an entry display module 503 configured to, in a case where it is determined according to the scanning result that there is at least one installed application in the N applications, display a payment entry corresponding to a target application in the payment interface, wherein the target application includes at least one installed application in the N applications.

[0106] The payment entry display device 500 is described in detail as follows.

[0107] In some embodiments, the entry display module 503 can specifically include:

[0108] a common display sub-module configured to display the payment entry corresponding to the target application as a payment option of a target payment method and an identifier corresponding to the target payment method in the payment interface, wherein the target payment method is a payment method corresponding to the preset payment component.

[0109] In some embodiments, the number of target applications is fixedly set to M, M is an integer, and 2≤M≤N; different target applications correspond to different payment entries. ​

[0110] In some embodiments, the payment portal display apparatus 500 further comprises:

[0111] A first determination module, configured to, before displaying the payment portal corresponding to the target application program in the payment interface, if the number L of installed application programs in the N application programs is greater than M, then determine M application programs from the installed application programs as the target application programs;

[0112] A second determination module, configured to, if the number L of installed application programs in the N application programs is equal to M, determine the installed application programs as the target application programs;

[0113] A third determination module, configured to, if the number L of installed application programs in the N application programs is less than M, determine (M-L) application programs from the uninstalled application programs in the N application programs, and determine the (M-L) application programs and the installed application programs as the target application programs, wherein L is a positive integer and L≤N.

[0114] In some embodiments, the first determination module comprises:

[0115] A first acquisition sub-module, configured to acquire payment preferential information corresponding to each of the installed application programs;

[0116] A first determination sub-module, configured to determine preferential strength corresponding to each of the installed application programs according to the payment preferential information;

[0117] A second determination sub-module, configured to determine M application programs with the greatest preferential strength from the installed application programs as the target application programs based on the preferential strength.

[0118] In some embodiments, the third determination module comprises:

[0119] A second acquisition sub-module, configured to acquire payment preferential information corresponding to each of the uninstalled application programs;

[0120] A third determination sub-module, configured to determine preferential strength corresponding to each of the uninstalled application programs according to the payment preferential information;

[0121] A fourth determination sub-module, configured to determine (M-L) application programs with the greatest preferential strength from the uninstalled application programs as the target application programs based on the preferential strength.

[0122] In some embodiments, the portal display module 503 comprises:

[0123] a sequence determination module, configured to determine a sequence of arrangement corresponding to the target application program based on a preset priority rule, wherein the preset priority rule comprises at least one of an installed application program priority display and a large-benefit-intensity application program priority display, and a display priority corresponding to the installed application program is higher than a display priority corresponding to the large-benefit-intensity application program;

[0124] an arrangement display module, configured to display a payment portal corresponding to the target application program in the payment interface according to the sequence of arrangement.

[0125] In some embodiments, different jump identifiers are configured in the merchant application for different application programs in the N application programs;

[0126] The payment portal display apparatus 500 further includes:

[0127] a second input module, configured to receive a second input of the payment portal by a user;

[0128] In a case where the target application program is an installed application program, in response to the second input, a target payment interface corresponding to the target application program is jumped to according to a target jump identifier corresponding to the target application program;

[0129] a second response module, configured to, in a case where the target application program is an uninstalled application program, in response to the second input, download and install the target application program in the electronic device.

[0130] In some embodiments, the second response module includes:

[0131] a display sub-module, configured to, in a case where the target application program is an uninstalled application program, in response to the second input, display a payment method selection interface, and display payment portals corresponding to the N application programs respectively in the payment method selection interface;

[0132] a receiving sub-module, configured to receive a third input of a first payment portal by a user, wherein the first payment portal is a payment portal corresponding to a first application program in the N application programs;

[0133] a jump sub-module, configured to, in a case where the first application program is an installed application program, in response to the third input, jump to a first payment interface corresponding to the first application program;

[0134] an installation sub-module, configured to, in a case where the first application program is an uninstalled application program, in response to the third input, download and install the first application program in the electronic device.

[0135] In some embodiments, the display sub-module comprises:

[0136] The partition display unit is configured to display, in a first area of the payment method selection interface, payment portals corresponding to installed applications among the N applications, and display, in a second area of the payment method selection interface, payment portals corresponding to uninstalled applications among the N applications.

[0137] Thus, by configuring a unified target scanning identifier for a plurality of applications having a preset payment component, the target scanning identifier is used to scan applications in the electronic device when a user triggers display of a payment interface in a merchant application, and in a case where at least one installed application exists among the plurality of applications, the payment portal corresponding to the installed at least one application can be displayed in the payment interface. In this way, since a scanning identifier is configured for a plurality of applications having the same preset payment component, the limitation on the number of scanning identifiers can be broken through, and thus the payment portal corresponding to the installed application among the plurality of applications in the electronic device can be accurately displayed in the merchant application. In addition, since the scanned payment portal corresponding to the application is displayed in the payment interface of the merchant application, i.e., the first-level payment interface, the user does not need to operate to jump to the second-level payment interface to see and select the payment portal of the corresponding application to complete payment, and thus the user operation process can be simplified.

[0138] Figure 6 FIG. 1 is a structural schematic diagram of an electronic device according to an embodiment of the present application.

[0139] The electronic device 600 can include a processor 601 and a memory 602 storing computer program instructions.

[0140] Specifically, the processor 601 can include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or can be configured as one or more integrated circuits implementing an embodiment of the present application.

[0141] The memory 602 can include mass storage for data or instructions. As an example and not by way of limitation, the memory 602 can include a hard disk drive (HDD), a floppy disk drive, flash memory, an optical disc (e.g., a compact disc (CD) or a digital versatile disc (DVD)), a solid-state drive (SSD), a USB drive, or a combination of two or more of these. Where appropriate, the memory 602 can include removable or non-removable (or fixed) media, where appropriate. The memory 602 can be internal or external to the integrated gateway disaster recovery appliance. In particular embodiments, the memory 602 is non-volatile, solid-state memory.

[0142] In particular embodiments, a memory can include read-only memory (ROM), random access memory (RAM), a magnetic disk storage medium, an optical storage medium, a flash memory device, electrical, optical, or other physical / tangible memory storage device. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software that, when executed (by one or more processors), is operable to

[0143] The processor 601 implements any of the payment portal display methods in the above embodiments by reading and executing computer program instructions stored in the memory 602.

[0144] In some examples, the electronic device 600 can also include a communication interface 603 and a bus 610. As shown, the processor 601, the memory 602, and the communication interface 603 are connected by the bus 610 and complete communication among each other. Figure 6

[0145] The communication interface 603 is mainly used to realize the communication between the modules, devices, units and / or equipment in the embodiments of the present application.

[0146] ​The bus 610 includes hardware, software, or both, and couples the components of the online data flow meter charging device to each other. By way of example and not limitation, the bus 610 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a memory bus, a MicroChannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses or a combination of two or more of these. Where appropriate, the bus 610 may include one or more buses. Although the embodiments of the present application describe and illustrate specific buses, the present application contemplates any suitable bus or interconnect.

[0147] Exemplarily, the electronic device 600 may be a mobile phone, a tablet computer, a laptop computer, a palmtop computer, an in-vehicle electronic device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), etc.

[0148] The electronic device 600 can execute the payment entrance display method in the embodiments of the present application, so as to implement the combination Figure 1 and Figure 5 the payment entrance display method and device described.

[0149] In addition, in combination with the payment entrance display method in the above embodiments, the embodiments of the present application can be implemented by providing a computer-readable storage medium. Computer program instructions are stored on the computer-readable storage medium; when the computer program instructions are executed by a processor, any one of the payment entrance display methods in the above embodiments is implemented. Examples of the computer-readable storage medium include non-transitory computer-readable storage media, such as a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, etc.

[0150] It is to be understood that the application is not limited to particular configurations and processes described herein and shown in the drawings. The detailed description is not to be taken as limiting the application. In the above embodiments, several specific steps are described and illustrated in order to provide a thorough understanding of the application. However, the application can be practiced with fewer or additional steps, and in a different order. The application is not limited to the described and illustrated embodiments.

[0151] The functions of the elements of described above, illustrated in the block diagrams, can be implemented as hardware, software, firmware or any combination thereof. When implemented as hardware, for example, they can be implemented as electronic circuits, application specific integrated circuits (ASICs), suitable firmware, plug-ins, function cards, etc. When implemented as software, the elements of the application are program or code segments that are used to perform the required tasks. The program or code segments can be stored in a machine-readable medium or transmitted through a data signal carried in a carrier wave over a transmission medium or communication link. A "machine-readable medium" includes any medium that can store or transfer information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. The code segments can be downloaded via computer networks such as the Internet, intranet, etc.

[0152] It is also to be understood that the example embodiments described herein are based on a series of steps or apparatuses to describe some methods or systems. However, the application is not limited to the order of the steps described above, that is, the steps can be performed in the order mentioned in the embodiments, or in an order different from the embodiments, or several steps can be performed simultaneously.

[0153] The computer program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other processing devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other processing devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. Such processes can be realized by a hardware component or components operating together, such as a processing device that is missing, a special purpose computer, an application specific integrated circuit or combinations of others known or contemplated.

[0154] The above merely describes a specific implementation of the present application. Those skilled in the art can clearly understand the specific working processes of the system, modules and units described above for the convenience and brevity of description, and the corresponding processes in the foregoing method embodiments can be referred to, which will not be described herein again. It should be understood that the protection scope of the present application is not limited in this way, and any person skilled in the art can easily think of various equivalent modifications or replacements within the technical range disclosed in the present application, and these modifications or replacements should be covered in the protection scope of the present application.

Claims

1. A payment gateway display method characterized by comprising: The method comprises: receiving a first input of a user for triggering display of a payment interface in a merchant application program; in response to the first input, displaying the payment interface and scanning an application program in an electronic device according to a pre-configured target scanning identifier in the merchant application program to obtain a scanning result, wherein the target scanning identifier is configured to identify N application programs having a preset payment component, and N is an integer greater than 1; in a case where it is determined according to the scanning result that there is at least one installed application program in the N application programs, displaying a payment portal corresponding to a target application program in the payment interface, wherein the target application program comprises at least one installed application program in the N application programs; the N application programs are a plurality of application programs corresponding to a unified payment platform and having the same preset payment component; the number of target application programs is fixedly set as M, M is an integer, and 2≤M≤N; different target application programs correspond to different payment portals; before displaying the payment portal corresponding to the target application program in the payment interface, the method further comprises: in a case where the number L of installed application programs in the N application programs is less than M, determining (M-L) application programs from the N application programs that are not installed, and determining the (M-L) application programs and the installed application programs as the target application programs, wherein L is a positive integer, and L≤N.

2. The method of claim 1, wherein, the displaying of the payment portal corresponding to the target application program in the payment interface comprises: displaying the payment portal corresponding to the target application program and an identifier corresponding to a target payment method as payment options of the target payment method in the payment interface, wherein the target payment method is a payment method corresponding to the preset payment component.

3. The method of claim 1, wherein, before displaying the payment portal corresponding to the target application program in the payment interface, the method further comprises: in a case where the number L of installed application programs in the N application programs is greater than M, determining M application programs from the installed application programs as the target application programs; in a case where the number L of installed application programs in the N application programs is equal to M, determining the installed application programs as the target application programs.

4. The method of claim 3, wherein, the determining of the M application programs from the installed application programs as the target application programs comprises: obtaining payment discount information corresponding to each of the installed application programs; determining the discount intensity corresponding to each installed application program according to the payment discount information; based on the discount intensity, determining M application programs with the greatest discount intensity from the installed application programs as the target application programs.

5. The method of claim 3, wherein, the determining of the (M-L) application programs from the N application programs that are not installed comprises: obtaining payment discount information corresponding to each of the installed application programs; determining the discount intensity corresponding to each installed application program according to the payment discount information; based on the discount intensity, determining M application programs with the greatest discount intensity from the installed application programs as the target application programs. Determine, based on the discount strength, M-L application programs with the maximum discount strength from the uninstalled application programs as the target application programs.

6. The method according to any one of claims 1 to 5, characterized in that, The payment interface includes: Determine, based on a preset priority rule, an arrangement order corresponding to the target application programs, wherein the preset priority rule includes at least one of a priority display of an installed application program and a priority display of an application program with a large discount strength, and a display priority corresponding to the installed application program is higher than a display priority corresponding to the application program with the large discount strength; Display, in the payment interface, the payment entrances corresponding to the target application programs according to the arrangement order.

7. The method of claim 1, wherein, The merchant application program is configured with different jump identifiers for different application programs in the N application programs. The method further includes: Receive a second input of the user on the payment entrance; In a case where the target application program is an installed application program, jump, in response to the second input, to a target payment interface corresponding to the target application program according to a target jump identifier corresponding to the target application program; In a case where the target application program is an uninstalled application program, download and install the target application program in the electronic device in response to the second input.

8. The method of claim 7, wherein, The downloading and installing of the target application program in the electronic device in response to the second input in a case where the target application program is an uninstalled application program includes: In a case where the target application program is an uninstalled application program, display, in response to the second input, a payment method selection interface, and display, in the payment method selection interface, payment entrances corresponding to the N application programs respectively; Receive a third input of the user on a first payment entrance, wherein the first payment entrance is a payment entrance corresponding to a first application program in the N application programs; In a case where the first application program is an installed application program, jump, in response to the third input, to a first payment interface corresponding to the first application program; In a case where the first application program is an uninstalled application program, download and install the first application program in the electronic device in response to the third input.

9. The method of claim 8, wherein, The displaying of the payment entrances corresponding to the N application programs in the payment method selection interface includes: Display, in a first region in the payment method selection interface, payment entrances corresponding to installed application programs in the N application programs, and display, in a second region in the payment method selection interface, payment entrances corresponding to uninstalled application programs in the N application programs.

10. A payment gateway display device, characterized by, The apparatus includes: A first input module configured to receive a first input of the user for triggering display of a payment interface in a merchant application program; The first response module is configured to display the payment interface in response to the first input, and scan an application in the electronic device according to a target scanning identifier pre-configured in the merchant application to obtain a scanning result, wherein the target scanning identifier is configured to identify N applications having a preset payment component, and N is an integer greater than 1. The entry display module is configured to display a payment entry corresponding to a target application in the payment interface when it is determined according to the scanning result that there is at least one installed application in the N applications, wherein the target application includes at least one installed application in the N applications. The N applications are a plurality of applications corresponding to a unified payment platform and having the same preset payment component. The number of the target applications is fixedly set as M, M is an integer, and 2≤M≤N; and different target applications correspond to different payment entries. The payment entry display device further includes: The third determination module is configured to determine (M-L) applications from the N applications that are not installed when the number L of the installed applications in the N applications is less than M, and determine the (M-L) applications and the installed applications as the target applications, wherein L is a positive integer, and L≤N.

11. An electronic device, comprising: The device includes a processor and a memory storing computer program instructions; The processor executes the computer program instructions to implement the steps of the payment entry display method according to any one of claims 1-9.

12. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer program instructions, and the computer program instructions are executed by the processor to implement the steps of the payment entry display method according to any one of claims 1-9.

13. A computer program product, characterised in that, The instructions in the computer program product are executed by the processor of the electronic device to enable the electronic device to perform the steps of the payment entry display method according to any one of claims 1-9.

Images