Payment processing method, device, electronic device and storage medium

Abstract

The present application relates to a payment processing method, device, electronic device and storage medium, the method comprising: obtaining business system information corresponding to a payment platform; matching at least one candidate payment component from a component library according to the business system information; according to a selection instruction for the candidate payment component, using the selected candidate payment method component as a target payment component; and loading the target payment component into the payment platform framework to obtain a payment platform corresponding to the business system. The technical solution simplifies the development and maintenance of the payment platform, improves development efficiency, and reduces the manpower and time costs required for development and maintenance.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a payment processing method, device, electronic device and storage medium. Background Art

[0002] The payment platform is a system used to connect the business system and banks or third-party payment gateways, providing the business system with acquiring capabilities, meeting the payment-related needs of the business system and providing support for related systems such as finance, clearing and settlement, risk control, and marketing.

[0003] The payment platform is usually a payment module in a large business system, which needs to be modified and customized according to the needs of the business system to meet the needs of the business system. In the case of various business needs, it usually takes a lot of manpower and time to maintain the payment platforms of multiple business systems, and the maintenance cost of the payment platform is high. Summary of the invention

[0004] In order to solve the above technical problems or at least partially solve the above technical problems, the embodiments of the present application provide a payment processing method, device, electronic device and storage medium.

[0005] According to one aspect of an embodiment of the present application, a payment processing method is provided, including:

[0006] Obtain the business system information corresponding to the payment platform;

[0007] Matching at least one candidate payment component from a component library according to the business system information;

[0008] According to the selection instruction of the candidate payment component, the selected candidate payment method component is used as the target payment component;

[0009] The target payment component is loaded into the payment platform framework to obtain the payment platform corresponding to the business system.

[0010] Optionally, the step of loading the target payment component into the payment platform framework to obtain a payment platform corresponding to the business system includes:

[0011] Generate a system configuration file corresponding to the business system information;

[0012] Determine a configuration file identifier corresponding to the system configuration file;

[0013] The system configuration file is defined in a project configuration file corresponding to the payment platform, so that the operation of the system configuration file is controlled by an operation command including the configuration file identifier.

[0014] Optionally, the business system information includes a system security level of the business system;

[0015] The matching at least one candidate payment component according to the business system information includes:

[0016] Obtaining payment security levels corresponding to each candidate payment component in the component library;

[0017] The candidate payment components whose payment security level matches the system security level are screened.

[0018] Optionally, the method further includes:

[0019] receiving a component adding instruction, wherein the component adding instruction is used to add a new payment component that does not belong to the component library to the payment platform;

[0020] Get the newly uploaded payment component;

[0021] Loading the newly added payment component on the payment platform;

[0022] Add the newly added payment component to the component library.

[0023] Optionally, the method further includes:

[0024] Obtaining the priority corresponding to the target payment component;

[0025] The target payment components are sorted on the payment platform according to the priority.

[0026] Optionally, the method further includes:

[0027] Receiving a component adjustment instruction, wherein the component adjustment instruction includes a component identifier of a target payment component to be adjusted and adjusted attribute information;

[0028] The payment platform adjusts the target payment component corresponding to the component identifier according to the adjusted attribute information.

[0029] Optionally, the method further includes:

[0030] Obtain the gateway corresponding to the target payment component;

[0031] A connection relationship between the payment platform and the gateway is established.

[0032] According to another aspect of an embodiment of the present application, a payment processing device is provided, including:

[0033] The acquisition module is used to obtain the business system information corresponding to the payment platform;

[0034] A matching module, used to match at least one candidate payment component from a component library according to the business system information;

[0035] A selection module, configured to select the selected candidate payment method component as a target payment component according to a selection instruction for the candidate payment component;

[0036] A loading module is used to load the target payment component into the payment platform framework to obtain the payment platform corresponding to the business system.

[0037] According to another aspect of an embodiment of the present application, a storage medium is further provided, which includes a stored program, and the above steps are executed when the program is run.

[0038] According to another aspect of the embodiment of the present application, there is provided an electronic device, comprising: a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0039] The memory is used to store computer programs;

[0040] The processor is used to implement the above method steps when executing a computer program.

[0041] According to another aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the above method steps are implemented.

[0042] The above technical solution provided by the embodiment of the present application has the following advantages compared with the prior art:

[0043] By abstracting various payment methods into payment components in advance, when developing a payment platform, the required payment components are selected according to the needs of the business system, and these payment components are loaded into the payment platform framework to generate a payment platform corresponding to the business system. In this way, the development and maintenance of the payment platform are simple, customization is reduced, development efficiency is improved, the manpower and time costs required for development and maintenance are reduced, and unified maintenance and flexible deployment are achieved while meeting business needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0045] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0046] Figure 1 A flow chart of a payment processing method provided in an embodiment of the present application;

[0047] Figure 2 A flow chart of a payment processing method provided in another embodiment of the present application;

[0048] Figure 3 A flow chart of a payment processing method provided in another embodiment of the present application;

[0049] Figure 4 A flow chart of a payment processing method provided in another embodiment of the present application;

[0050] Figure 5 A flow chart of a payment processing method provided in another embodiment of the present application;

[0051] Figure 6 A flow chart of a payment processing method provided in another embodiment of the present application;

[0052] Figure 7 A block diagram of a payment processing device provided in an embodiment of the present application;

[0053] Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0055] The embodiment of the present application provides a set of unified standard payment interfaces by abstracting the parameters and processes of different payment methods, and uses each abstracted payment method as a loadable component (Jar file), so that the required payment methods can be dynamically loaded according to business needs in different deployment environments, avoiding unnecessary development and maintenance work and reducing customization.

[0056] In this embodiment, Maven can be used to create corresponding Profile configuration files for different deployment environments and manage the required payment method Jar libraries.

[0057] Among them, in the software field, JAR file (Java Archive, English: Java Archive) is a software package file format, which is usually used to aggregate a large number of Java class files, related metadata and resource (text, pictures, etc.) files into one file to develop Java platform application software or libraries.

[0058] Maven is an open source project developed in pure Java under Apache. Based on the concept of Project Object Model (abbreviation: POM), Maven uses a central information fragment to manage the steps of building, reporting and documentation of a project. Maven is a project management tool that can build and manage dependencies for Java projects.

[0059] At present, commonly used payment methods include but are not limited to the following: quick payment, authentication payment, gateway payment, offline payment, installment payment, etc. Each payment method can have multiple payment components based on the different banks or third-party channels that provide payment.

[0060] Among them, quick payment is suitable for scenarios such as face-scanning payment. Users have bound and authorized the payment method in advance, and can make payments without any perception, without the need for selection and verification.

[0061] Verified payment requires users to select a payment account at the checkout counter of the payment system and perform simple verification, such as a payment password, SMS verification code, etc.

[0062] Gateway payment requires users to jump out to the bank\third-party gateway website\APP to perform relevant verification operations, and redirect to the current payment system after completing the payment.

[0063] Offline payment is a popular payment method in some countries and regions in Southeast Asia. The payment system needs to connect to the corresponding bank\third-party gateway to obtain the corresponding payment code and complete the payment at the relevant online business locations.

[0064] Installment payment is mainly used for some consumer finance products, such as Bai Tiao installment. Users need to open corresponding consumer finance product accounts, and the payment system connects to the relevant consumer finance product gateway to complete the payment.

[0065] The following first introduces a payment processing method provided by an embodiment of the present invention.

[0066] Figure 1 A flow chart of a payment processing method provided in an embodiment of the present application. Figure 1As shown, the method comprises the following steps:

[0067] Step S11, obtaining the business system information corresponding to the payment platform.

[0068] Among them, the business system needs to deploy a payment platform including the required payment methods according to the environment to meet the payment needs of the business system.

[0069] The payment platform in this embodiment is a framework that carries different payment method processing modules. In different deployment environments, the payment platform can load different payment methods and develop new payment methods based on special business needs to meet the necessary customization and flexibility. However, the payment platform itself remains unchanged, achieving unified maintenance and unified deployment.

[0070] Step S12: matching at least one candidate payment component from the component library according to the business system information.

[0071] Among them, the corresponding payment methods are different based on the different environments in which the business systems are deployed. For example, for the business system of unmanned supermarkets, the candidate payment components matched to it may include: quick payment components; for the business system of overseas e-commerce, the candidate payment components matched to it may include: quick payment components, authentication payment components, gateway payment components, offline payment components, installment payment components, etc.; for the business system of electronic wallets, the candidate payment components matched to it may include: quick payment components, authentication payment components, gateway payment components, offline payment components, etc.

[0072] Optionally, based on the country or region where the business system is deployed, the candidate payment components corresponding to the country or region can be matched. In addition, the payment methods included in the payment platform of the business system in different fields are also different.

[0073] Step S13: according to the selection instruction of the candidate payment component, the selected candidate payment method component is used as the target payment component.

[0074] Optionally, the development interface of the payment platform may display options corresponding to the candidate payment components, and the developer may select the required payment component from the candidate payment components as the target payment component to be loaded into the payment platform as needed. Optionally, the development interface also provides an option to "select all" all the candidate payment components.

[0075] When the candidate payment components do not include the required payment component, you can also click the "Add" option to select the required payment component from the payment component library.

[0076] Step S14, loading the target payment component into the payment platform framework to obtain the payment platform corresponding to the business system.

[0077] In this embodiment, various payment methods are abstracted into payment components in advance. When developing a payment platform, the required payment components are selected according to the needs of the business system, and these payment components are loaded into the payment platform framework, thereby generating a payment platform corresponding to the business system. In this way, the development and maintenance of the payment platform are simple, customization is reduced, development efficiency is improved, the manpower cost and time cost required for development and maintenance are reduced, and unified maintenance and flexible deployment are achieved on the premise of meeting business needs.

[0078] Figure 2 A flow chart of a payment processing method provided in another embodiment of the present application. Figure 2 As shown, the above step S14 includes the following steps:

[0079] Step S21, generating a system configuration file corresponding to the business system information;

[0080] Step S22, determining the configuration file identifier corresponding to the system configuration file;

[0081] Step S23, defining the system configuration file in the project configuration file corresponding to the payment platform, so that the operation of the system configuration file is controlled by the operation command including the configuration file identifier.

[0082] In this embodiment, Maven can be used to create a corresponding system configuration file Profile for the business system. The Profile in Maven is a set of optional configurations that can be used to set or override configuration default values. Profile can be used to customize builds for different environments. Profile can be configured in the project configuration file pom.xml, and a configuration file identification ID is set for Profile. In this way, the command line including the ID used when running Maven controls Maven to run the goals in the corresponding Profile. Each Profile manages each payment component (Jar package) in the corresponding payment platform, thereby achieving flexible deployment and unified maintenance of the payment platform in different deployment environments.

[0083] In an optional embodiment, the business system information includes the system security level of the business system. Business systems with different security levels have different payment components that can be loaded in their payment platforms. Figure 3 A flow chart of a payment processing method provided in another embodiment of the present application. Figure 3 As shown, the above step S12 includes the following steps:

[0084] Step S31, obtaining the payment security level corresponding to each candidate payment component in the component library;

[0085] Step S32, screening candidate payment components whose payment security levels match the system security level.

[0086] For example, for business systems with relatively high security requirements, such as financial and wealth management business systems, payment components with relatively high security levels are provided, such as authentication payment, gateway payment, installment payment or offline payment, etc. For business systems with relatively low security levels, such as unmanned supermarkets, payment components with relatively low security levels, such as quick payment, etc., can be provided.

[0087] In this way, in the process of generating a payment platform, the payment security of the business system is improved by selecting payment components according to the security payment level.

[0088] Optionally, developers can input a security level, and the system will select a payment component that meets this security level from the component library. For multiple payment components under the same payment method, the security level of the payment component can also be determined based on the security level of the bank or third party providing the payment.

[0089] In another optional embodiment, when the component library does not include the required payment component, a new payment component may be imported and stored in the component library. Figure 4 A flow chart of a payment processing method provided in another embodiment of the present application. Figure 4 As shown, the method also includes:

[0090] Step S41, receiving a component adding instruction, where the component adding instruction is used to add a new payment component that does not belong to the component library to the payment platform;

[0091] Step S42, obtaining the uploaded newly added payment component;

[0092] Step S43, loading a new payment component on the payment platform;

[0093] Step S44, adding the new payment component to the component library.

[0094] In this embodiment, developers can package the parameters, processes, etc. of the newly added payment method, as well as the payment interface of the specified payment method, into a loadable payment component Jar package according to the configuration rules, load it into the payment platform, and add it to the component library for subsequent use.

[0095] Optionally, different payment components are set with different priorities, ie, payment methods recommended in the business system. Figure 5 A flow chart of a payment processing method provided in another embodiment of the present application. Figure 5 As shown, the method also includes:

[0096] Step S51, obtaining the priority corresponding to the target payment component;

[0097] Step S52: sorting the target payment components according to priority on the payment platform.

[0098] Optionally, the priority can be set as a default for each payment component, and developers can also adjust the priority of each payment component according to business system requirements.

[0099] For example, the payment method priority is ranked from high to low as follows: quick payment, gateway payment, authentication payment, installment payment, offline payment. Each payment component under each payment method can be set with a priority, such as arranging each payment component according to the priority corresponding to the bank under authentication payment.

[0100] In another optional embodiment, for a business system that has been launched or developed, developers can adjust various payment methods in the payment platform as needed. Figure 6 A flow chart of a payment processing method provided in another embodiment of the present application. Figure 6 As shown, the method also includes:

[0101] Step S61, receiving a component adjustment instruction, the component adjustment instruction including a component identifier of a target payment component to be adjusted and adjusted attribute information;

[0102] Step S62: The payment platform adjusts the target payment component corresponding to the component identifier according to the adjusted attribute information.

[0103] Among them, the existing payment components on the payment platform can be deleted, modified, or new payment components can be added.

[0104] In an optional embodiment, the method further includes: obtaining a gateway corresponding to the target payment component; and establishing a connection relationship between the payment platform and the gateway.

[0105] In this embodiment, different payment components are connected to corresponding banks or third-party gateways through their own payment interfaces, and the transaction is connected to the bank or third-party gateway through the payment interface encapsulated by the payment component.

[0106] The following are device embodiments of the present application, which can be used to execute method embodiments of the present application.

[0107] Figure 7 This is a block diagram of a payment processing device provided in an embodiment of the present application. The device can be implemented as part or all of an electronic device through software, hardware, or a combination of both. Figure 7 As shown, the payment processing device includes:

[0108] Acquisition module 701, used to acquire business system information corresponding to the payment platform;

[0109] A matching module 702, configured to match at least one candidate payment component from a component library according to the business system information;

[0110] A selection module 703, for selecting a selected candidate payment method component as a target payment component according to a selection instruction for a candidate payment component;

[0111] The loading module 704 is used to load the target payment component into the payment platform framework to obtain the payment platform corresponding to the business system.

[0112] Optionally, the loading module 704 includes:

[0113] A generation submodule, used to generate a system configuration file corresponding to the business system information;

[0114] A determination submodule, used to determine a configuration file identifier corresponding to the system configuration file;

[0115] The configuration submodule is used to define the system configuration file in the project configuration file corresponding to the payment platform, so that the operation of the system configuration file is controlled by an operation command including the configuration file identifier.

[0116] Optionally, the business system information includes a system security level of the business system; the matching module 702 includes:

[0117] An acquisition submodule, used to acquire the payment security level corresponding to each candidate payment component in the component library;

[0118] The screening submodule is used to screen candidate payment components whose payment security level matches the system security level.

[0119] Optionally, the device further includes: a receiving module 705 , a component acquiring module 706 and an adding module 707 .

[0120] A receiving module 705, configured to receive a component adding instruction, wherein the component adding instruction is configured to add a new payment component that does not belong to the component library to the payment platform;

[0121] The component acquisition module 706 is used to acquire the uploaded newly added payment component;

[0122] The loading module 704 is used to load the newly added payment component on the payment platform;

[0123] The adding module 707 is used to add the newly added payment component to the component library.

[0124] Optionally, the device further includes: a priority acquisition module 708 and a sorting module 709 .

[0125] A priority acquisition module 708, used to acquire the priority corresponding to the target payment component;

[0126] The sorting module 709 is used to sort the target payment components according to the priority on the payment platform.

[0127] Optionally, the device further includes: an adjustment module 710 .

[0128] A receiving module 705 is used to receive a component adjustment instruction, wherein the component adjustment instruction includes a component identifier of a target payment component to be adjusted and adjusted attribute information;

[0129] The adjustment module 710 is used to adjust the target payment component corresponding to the component identifier on the payment platform according to the adjusted attribute information.

[0130] Optionally, the device further comprises:

[0131] A gateway acquisition module 711 is used to acquire the gateway corresponding to the target payment component;

[0132] The connection establishment module 712 is used to establish a connection relationship between the payment platform and the gateway.

[0133] The present application also provides an electronic device, such as Figure 8 As shown, the electronic device may include: a processor 1501 , a communication interface 1502 , a memory 1503 and a communication bus 1504 , wherein the processor 1501 , the communication interface 1502 , and the memory 1503 communicate with each other via the communication bus 1504 .

[0134] Memory 1503, used for storing computer programs;

[0135] The processor 1501 is used to implement the steps of the above method embodiment when executing the computer program stored in the memory 1503.

[0136] The communication bus mentioned in the above electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0137] The communication interface is used for communication between the above electronic device and other devices.

[0138] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0139] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0140] The present application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the following method embodiment:

[0141] Obtain the business system information corresponding to the payment platform;

[0142] Matching at least one candidate payment component from a component library according to the business system information;

[0143] According to the selection instruction of the candidate payment component, the selected candidate payment method component is used as the target payment component;

[0144] The target payment component is loaded into the payment platform framework to obtain the payment platform corresponding to the business system.

[0145] Optionally, the step of loading the target payment component into the payment platform framework to obtain a payment platform corresponding to the business system includes:

[0146] Generate a system configuration file corresponding to the business system information;

[0147] Determine a configuration file identifier corresponding to the system configuration file;

[0148] The system configuration file is defined in a project configuration file corresponding to the payment platform, so that the operation of the system configuration file is controlled by an operation command including the configuration file identifier.

[0149] Optionally, the business system information includes a system security level of the business system;

[0150] The matching at least one candidate payment component according to the business system information includes:

[0151] Obtaining payment security levels corresponding to each candidate payment component in the component library;

[0152] The candidate payment components whose payment security level matches the system security level are screened.

[0153] Optionally, the method further includes:

[0154] receiving a component adding instruction, wherein the component adding instruction is used to add a new payment component that does not belong to the component library to the payment platform;

[0155] Get the newly uploaded payment component;

[0156] Loading the newly added payment component on the payment platform;

[0157] Add the newly added payment component to the component library.

[0158] Optionally, the method further includes:

[0159] Obtaining the priority corresponding to the target payment component;

[0160] The target payment components are sorted on the payment platform according to the priority.

[0161] Optionally, the method further includes:

[0162] Receiving a component adjustment instruction, wherein the component adjustment instruction includes a component identifier of a target payment component to be adjusted and adjusted attribute information;

[0163] The payment platform adjusts the target payment component corresponding to the component identifier according to the adjusted attribute information.

[0164] Optionally, the method further includes:

[0165] Obtain the gateway corresponding to the target payment component;

[0166] A connection relationship between the payment platform and the gateway is established.

[0167] It should be noted that, for the above-mentioned device, electronic device and computer-readable storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0168] It should be further noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0169] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A payment processing method, characterized in that: include: Obtain the business system information corresponding to the payment platform; Matching at least one candidate payment component from a component library according to the business system information; wherein the candidate payment component includes packaging parameters, processes, and a payment interface of a specified payment method into a loadable component according to configuration rules; According to the selection instruction of the candidate payment component, the selected candidate payment method component is used as the target payment component; Load the target payment component into the payment platform framework to obtain the payment platform corresponding to the business system; The step of loading the target payment component into the payment platform framework to obtain a payment platform corresponding to the business system includes: Generate a system configuration file corresponding to the business system information; Determine a configuration file identifier corresponding to the system configuration file; The system configuration file is defined in a project configuration file corresponding to the payment platform, so that the operation of the system configuration file is controlled by an operation command including the configuration file identifier.

2. The method according to claim 1, characterized in that The business system information includes the system security level of the business system; The matching at least one candidate payment component according to the business system information includes: Obtaining payment security levels corresponding to each candidate payment component in the component library; The candidate payment components whose payment security level matches the system security level are screened.

3. The method according to claim 1, characterized in that: The method further comprises: receiving a component adding instruction, wherein the component adding instruction is used to add a new payment component that does not belong to the component library to the payment platform; Get the newly uploaded payment component; Loading the newly added payment component on the payment platform; Add the newly added payment component to the component library.

4. The method according to claim 1, characterized in that: The method further comprises: Obtaining the priority corresponding to the target payment component; The target payment components are sorted on the payment platform according to the priority.

5. The method according to claim 1, characterized in that: The method further comprises: Receiving a component adjustment instruction, wherein the component adjustment instruction includes a component identifier of a target payment component to be adjusted and adjusted attribute information; The payment platform adjusts the target payment component corresponding to the component identifier according to the adjusted attribute information.

6. The method according to claim 1, characterized in that The method further comprises: Obtain the gateway corresponding to the target payment component; A connection relationship between the payment platform and the gateway is established.

7. A payment processing device, characterized in that: include: The acquisition module is used to obtain the business system information corresponding to the payment platform; A matching module, used to match at least one candidate payment component from a component library according to the business system information; wherein the candidate payment component includes packaging the parameters and process of the payment method and the payment interface of the specified payment method into a loadable component according to the configuration rules; A selection module, configured to select the selected candidate payment method component as a target payment component according to a selection instruction for the candidate payment component; A loading module, used to load the target payment component into the payment platform framework to obtain the payment platform corresponding to the business system; The loading module is used to generate a system configuration file corresponding to the business system information; determine a configuration file identifier corresponding to the system configuration file; define the system configuration file in a project configuration file corresponding to the payment platform, so that the operation of the system configuration file is controlled by an operation command including the configuration file identifier.

8. An electronic device, characterized in that: include: A processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; The memory is used to store computer programs; The processor is used to implement the method steps described in any one of claims 1-6 when executing the computer program.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method steps described in any one of claims 1 to 6 are implemented.

Images