Payment system, method and device and storage medium
By introducing certificate management end and storage server end in the payment system, flexible call and efficient management of multiple sets of payment certificates is achieved, and complex problems of multi-certificate management in the existing payment system are solved, improving the flexibility and performance of the system.
Patent Information
- Application Number
- CN202411363074.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-27
- Publication Date
- 2024-12-17
AI Technical Summary
The existing payment system only supports the management of one payment certificate, resulting in complex and low flexibility in multi-certificate management in multi-vendor scenarios.
A payment system was designed to query the target certificates in multiple sets of payment certificates through the certificate management end, and use the certificate encryption module and redundant backup module on the storage server to realize flexible call and efficient management of multiple sets of certificates, including certificate management The database sub-end and configuration center sub-end are used to manage interface routing and certificate ID to realize load balancing and certificate hot loading.
It improves the flexibility and performance of the payment system, reduces maintenance costs, adapts to scenarios where certificates are frequently updated, and realizes flexible management of multiple certificates and system scalability and security.
Smart Images
Figure CN119151537A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of payment technology, and in particular to a payment system, method, device and storage medium. Background Art
[0002] The payment system is a system that uses various payment instruments and payment channels to transfer and clear funds between different accounts. The payment system has a wide range of applications in economic activities and can promote the transaction and circulation of goods and services.
[0003] At present, the payment system in the related technology needs to use certificates to achieve secure payment, but the payment system in the related technology only supports the management of one payment certificate. However, with the rapid development of financial technology, a payment system often needs to connect with multiple suppliers, and often needs to load multiple sets of certificates in a payment system. Since the payment system in the related technology only supports the management of one certificate, the management of multiple certificates is more complicated and less flexible. Summary of the invention
[0004] The purpose of the embodiments of the present application is to provide a payment system, method, device and storage medium to achieve flexible management of multiple certificates to improve the flexibility of the payment system.
[0005] In a first aspect, an embodiment of the present application provides a payment system, the system comprising: a payment service end, and a storage service end and a certificate management end respectively communicating with the payment service end, wherein:
[0006] The storage service end is used to store certificate files;
[0007] The certificate management terminal is used to store interface routing information and bucket path information corresponding to each certificate ID; the interface routing information is used to indicate the corresponding relationship between the payment request terminal ID and the interface ID and the certificate ID;
[0008] The payment service end is used to receive a payment request sent by a payment request end; based on the payment request, query the target certificate and its corresponding bucket path information on the certificate management end; based on the bucket path information, call the target certificate file from the storage service end to encrypt the payment request; and send the encrypted payment request to the payment processing end.
[0009] In the process of implementing the above scheme, by setting up a certificate management terminal for managing payment certificates, the payment service end can query the target certificate corresponding to the payment request in multiple sets of payment certificates through the certificate management terminal, so that the above payment system can realize flexible calling of multiple sets of certificates, which is conducive to improving the flexibility of the above payment system.
[0010] In an implementation of the first aspect, the certificate management end includes: a database sub-end and a configuration center sub-end respectively communicating with the payment service end, wherein:
[0011] The database sub-end is used to store interface routing information;
[0012] The configuration center sub-end is used to store each certificate ID and its corresponding storage bucket path information.
[0013] In the process of implementing the above scheme, the database sub-end 121 is used to manage the interface routing information with a lower modification frequency, and the configuration center sub-end 122 is used to manage the certificate ID with a higher modification frequency and its corresponding bucket path information. On the one hand, it is beneficial to improve the performance of the above payment system 100 and the payment response speed; on the other hand, it is beneficial to reduce the maintenance cost of the above payment system 100 and improve the scalability and flexibility of the above payment system 100.
[0014] In an implementation of the first aspect, the configuration center sub-terminal includes:
[0015] The certificate update monitoring module is used to send certificate update information to the storage service end when the stored certificate ID and the corresponding storage bucket path information are updated, so that the storage service end updates the stored certificate file.
[0016] During the implementation of the above scheme, the configuration center sub-end realizes hot loading of certificates by setting up a certificate update monitoring module. On the one hand, it enables the above payment system to be applicable to scenarios where certificates are frequently updated, which is beneficial to improving the adaptability of the above payment system. On the other hand, the hot loading of certificates enables the above payment system to flexibly configure the payment system according to actual conditions, which is beneficial to improving the flexibility of the above payment system.
[0017] In an implementation of the first aspect, the payment service end includes:
[0018] An interface routing selection module is used to select a target interface routing corresponding to the payment request from the interface routing information stored in the certificate management end based on a load balancing weight; wherein the load balancing weight is used to indicate the probability of the interface routing being selected; and the load balancing weight is determined based on certificate performance and / or business traffic of the payment service end.
[0019] In the implementation process of the above solution, the payment server can select the interface route based on the load balancing weight, so as to achieve load balancing between the interface routes, and realize balanced distribution of business traffic through the load balancing weight, which is conducive to improving the system performance and system flexibility of the above payment system.
[0020] In an implementation of the first aspect, the storage service end includes:
[0021] A certificate encryption module, used for encrypting the certificate file;
[0022] And / or, a redundant backup module, used for performing redundant backup of the certificate file.
[0023] In the implementation process of the above scheme, by setting up a certificate encryption module in the storage service end to encrypt the certificate file, it is helpful to improve the security of the above payment system; by setting up a redundant backup module in the storage service end, it is helpful to improve the reliability of the above payment system.
[0024] In a second aspect, an embodiment of the present application provides a payment method, which is applied to a payment service end, and the method includes:
[0025] Receive a payment request sent by a payment request end;
[0026] Based on the payment request, query the target certificate and its corresponding storage bucket path information in the certificate management terminal;
[0027] Pull the target certificate from the storage service end based on the bucket path information to encrypt the payment request;
[0028] The encrypted payment request is sent to the payment processing end.
[0029] In an implementation of the second aspect, querying the target certificate in the certificate management terminal includes:
[0030] Based on the load balancing weight, the target interface route corresponding to the payment request is selected from the interface routing information stored in the certificate management end; wherein the load balancing weight is used to indicate the probability of the interface route being selected; the load balancing weight is determined based on the certificate performance and / or the business flow of the payment service end;
[0031] A target certificate is determined based on the target interface route.
[0032] In a third aspect, an embodiment of the present application provides a payment method, which is applied to a configuration center sub-terminal, and the method includes:
[0033] Monitor whether the stored certificate ID and its corresponding bucket path information are updated;
[0034] When the stored certificate ID and the corresponding storage bucket path information are updated, certificate update information is sent to the storage service client so that the storage service client updates the stored certificate file.
[0035] In a fourth aspect, an embodiment of the present application provides an electronic device, comprising: a processor, a memory, and a communication bus, wherein the processor and the memory communicate with each other through the communication bus; the memory stores computer program instructions that can be executed by the processor, and when the computer program instructions are read and run by the processor, the method provided by the second aspect or any possible implementation of the second aspect or the third aspect or any possible implementation of the third aspect is executed.
[0036] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are read and run by a processor, the method provided by the first aspect or any possible implementation of the first aspect or the third aspect or any possible implementation of the third aspect is executed.
[0037] Other features and advantages of the present application will be described in the following description, and partly become apparent from the description, or be understood by practicing the embodiments of the present application. The purpose and other advantages of the present application can be realized and obtained by the structures specifically pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0039] Figure 1 A schematic diagram of the architecture of the payment system provided in the embodiment of the present application;
[0040] Figure 2 A schematic diagram of the interaction process of various components in a payment system in a certain scenario provided in an embodiment of the present application;
[0041] Figure 3 A schematic diagram of a payment method applied to a payment server provided in an embodiment of the present application;
[0042] Figure 4 A flow chart of a payment method applied to a sub-terminal of a configuration center provided in an embodiment of the present application;
[0043] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0044] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.
[0045] Payment certificates refer to encryption certificates used in payment systems to ensure data security and legitimacy during transactions. Payment certificates are usually associated with payment accounts and used to sign or encrypt payment requests to ensure the integrity and authenticity of transaction information and prevent information from being tampered with or forged. Payment certificates play an important role in payment systems and are one of the important means of ensuring transaction security.
[0046] At present, most payment systems in related technologies only support the management of one certificate. However, with the rapid development of financial technology, a payment system often needs to connect with multiple suppliers, and multiple payment certificates need to be loaded in a payment system. When loading multiple certificates, the payment systems in related technologies have the problem of complex management of multiple certificates and low system flexibility.
[0047] Based on this, an embodiment of the present application provides a payment system, which is provided with a certificate management end for managing payment certificates. After receiving a payment request, the payment service end queries the target certificate storage path in the certificate management end, and then pulls the target certificate from the storage service end based on the target certificate storage path, and then uses the target certificate to encrypt the payment request. The above scheme sets up a certificate management end for managing payment certificates, and the payment service end can query the target certificate corresponding to the payment request in multiple sets of payment certificates through the certificate management end, so that the above payment system can realize flexible calling of multiple sets of certificates, which is conducive to improving the flexibility of the above payment system.
[0048] The following is a detailed description of the above payment systems. Figure 1 The present application embodiment provides a payment system 100, which includes:
[0049] The storage service client 110 is used to store certificate files;
[0050] The certificate management terminal 120 is used to store the interface routing information and the bucket path information corresponding to each certificate ID; the interface routing information is used to indicate the corresponding relationship between the payment request terminal ID and the interface ID and the certificate ID;
[0051] The payment service end 130 is used to receive the payment request sent by the payment request end; query the target certificate and its corresponding bucket path information on the certificate management end based on the payment request; call the target certificate file from the storage service end based on the bucket path information to encrypt the payment request; and send the encrypted payment request to the payment processing end.
[0052] It is understandable that the storage service end 110, the certificate management end 120 and the payment service end 130 can be deployed in the same server or in different servers. Of course, two of the storage service end 110, the certificate management end 120 and the payment service end 130 can also be deployed in the same server, and the other end can be deployed in another server, for example, the storage service end 110 and the certificate management end 120 are deployed in the same server, and the payment service end 120 is deployed in another server.
[0053] The storage service client 110 can implement a file transfer service based on the SFTP protocol and provide a RESTful API interface for other service clients to query and update certificate information.
[0054] The interface routing information stored in the certificate management terminal 120 includes the payment request terminal ID, the interface ID and the certificate ID, wherein the payment request terminal ID is the unique identifier of the payment request terminal, and the interface ID is the unique identifier of a specific interface. The payment request terminal ID and the interface ID can be used to accurately locate the specific interface called by a payment request terminal. In a set of interface routing information stored in the certificate management terminal 120, a pair of payment request terminal ID and interface ID corresponds to a certificate ID. Therefore, the payment service terminal 130 can determine the interface routing according to the payment request terminal ID and interface ID carried in the payment request.
[0055] It is understandable that there may be multiple certificate IDs corresponding to the same pair of payment request end ID and interface ID, that is, for the same payment request end and interface, there may be multiple sets of payment certificates that can be used to process the payment request. In this case, the certificate management end 120 can store multiple sets of interface routing information, and the difference between the multiple sets of interface routing information is that the certificate ID is different. When selecting, the payment service end 130 can randomly select a set from the multiple sets of interface routing information corresponding to the payment request, that is, randomly select a set of certificates to process the payment request.
[0056] In addition, the above interface routing information can be stored in the certificate management end in the form of a table, and the table structure can be designed as: payment request end ID (Primary Key), interface ID (Foreign Key) and certificate ID (Foreign Ke, which can be associated with the certificate storage table in the storage service end).
[0057] In addition, the bucket in the bucket path information stored in the certificate management terminal 120 is a logical unit for organizing and storing data in the object storage service, which is highly configurable and scalable. In the storage service terminal 110, the certificate file can be stored in a bucket.
[0058] It is understandable that the payment request sent by the payment request end may include: user information, payment amount, payment request end ID, interface ID, etc. The payment service end 130 may query the target certificate and its corresponding storage bucket path information in the certificate management end 120 based on the payment request end ID and interface ID in the payment request. Based on the storage bucket path information, the payment service end 120 may pull the certificate file of the target certificate from the storage service end 110 through the SFTP protocol.
[0059] In addition, it is understood that the payment processing end performs transaction processing after receiving the encrypted payment request, and returns the transaction processing result to the payment service end 130. The payment service end 130 can determine how to handle the payment request based on the transaction processing result. For example, if the transaction processing result is a transaction failure, the payment service end 130 can resend the encrypted transaction request to the payment processing end to try to complete the transaction again, or directly feed back the payment failure result to the payment request end, and perform corresponding processing according to the user's choice. In addition, the payment service end 130 can also use a transaction log to record the processing of the payment request.
[0060] See also Figure 1 As an optional implementation of the above payment system, the above certificate management terminal 120 includes: a database sub-terminal 121 and a configuration center sub-terminal 122 that communicate with the payment service terminal 130 respectively, wherein:
[0061] The database sub-terminal 121 is used to store interface routing information;
[0062] The central sub-terminal 122 is configured to store each certificate ID and its corresponding storage bucket path information.
[0063] The above-mentioned database sub-end 121 can realize an efficient query interface and support SQL query language to realize fast retrieval of interface routing information. The above-mentioned configuration center sub-end 122 can use Zookeeper configuration center to manage the certificate ID and its corresponding bucket path information. The configuration center sub-end 122 can also provide transaction management functions to ensure data consistency and integrity.
[0064] It is understandable that the above-mentioned database sub-end 121 and configuration center sub-end 122 can be deployed in the same server or in different servers.
[0065] In addition, it can be understood that the above-mentioned interface routing information is generally information with a low frequency of change, while the certificate ID and its corresponding bucket path information are information with a high frequency of change.
[0066] The above scheme uses the database sub-end to manage the interface routing information with a lower frequency of change, and uses the configuration center sub-end to manage the certificate ID with a higher frequency of change and its corresponding bucket path information. On the one hand, it is conducive to improving the performance of the above payment system and the payment response speed; on the other hand, it is conducive to reducing the maintenance cost of the above payment system and improving the scalability and flexibility of the above payment system.
[0067] As an optional implementation of the above payment system, the configuration center sub-terminal 122 includes:
[0068] The certificate update monitoring module is used to send certificate update information to the storage service end when the stored certificate ID and its corresponding storage bucket path information are updated, so that the storage service end updates the stored certificate file.
[0069] It can be understood that when the above-mentioned configuration center sub-end 122 adopts the Zookeeper configuration center, the Watcher callback mechanism of the Zookeeper configuration center can be used to monitor whether the certificate ID and its corresponding bucket path information are updated. When the certificate ID and / or bucket path information are updated, the event notification mechanism is used to notify the storage service end 110 of the certificate update event, so that the storage service end 110 updates the stored certificate files.
[0070] It is understandable that the certificate update event notification from the configuration center sub-end 122 to the storage service end 110 may include certificate update information, such as new certificates, certificate deletions, certificate updates and other related information. Taking the new certificate as an example, the certificate update information may include the certificate ID of the new certificate and its corresponding bucket path. After receiving the certificate update information, the storage service end 110 may update the stored certificate file according to the certificate update information. Taking the new certificate as an example, the certificate update information received by the storage service end 110 includes the certificate ID of the new certificate and the bucket path of the new certificate. The storage service end 110 pulls the certificate file according to the bucket path of the new certificate and adds the certificate ID of the new certificate to the certificate table.
[0071] In addition, it can be understood that the process of updating the certificate using the Watcher callback mechanism of the configuration center sub-terminal 122 can be performed while the configuration center sub-terminal 122 is in operation without shutting down the configuration center sub-terminal 122, thereby realizing hot loading of the certificate of the above-mentioned payment system 100.
[0072] The configuration center sub-terminal 122 in the above scheme realizes hot loading of certificates by setting up a certificate update monitoring module. On the one hand, it enables the above payment system 100 to be applicable to scenarios where certificates are frequently updated, which is beneficial to improving the adaptability of the above payment system 100; on the other hand, the hot loading method of certificates enables the above payment system 100 to flexibly configure the payment system 100 according to actual conditions, which is beneficial to improving the flexibility of the above payment system 100.
[0073] In the above scheme, it is introduced that for the same pair of payment request end ID and interface ID, the certificate management end 120 may store multiple groups of interface routing information, and at this time a group of interface routing information can be randomly selected to process the payment request. In addition to random selection, the embodiment of the present application also provides the following scheme:
[0074] As an optional implementation of the above payment system, the payment service end 130 includes:
[0075] The interface routing selection module is used to select the target interface routing corresponding to the payment request in the interface routing information stored in the certificate management end based on the load balancing weight; wherein the load balancing weight is used to indicate the probability of the interface routing being selected; the load balancing weight is determined based on the certificate performance and / or the business flow of the payment service end.
[0076] It is understandable that different payment certificates may be used to process payment requests sent by the same payment request end through the same interface, and there are certain performance differences between different types of payment certificates, such as certificate processing speed, resource consumption, encryption strength, stability, etc. In different scenarios, different payment certificates may be used to process payment requests. For example, in a scenario where the business flow of the payment service end 130 is large, a payment certificate with faster processing speed and less resource consumption may be used to process payment requests, while in a scenario where the business flow is small, a payment certificate with high encryption strength and strong stability may be used to process payment requests.
[0077] It can be understood that the above-mentioned interface route selection module can select the interface route corresponding to the payment request based on the load balancing weight, the load balancing weight can be determined based on the certificate performance and / or the business traffic of the payment server, the load balancing weight can pay the probability of each interface route being selected, and the interface route selection module selects the interface route based on the load balancing weight to achieve load balancing between interface routes.
[0078] The payment server 130 in the above scheme can select the interface route based on the load balancing weight, so as to achieve load balancing between the interface routes, and realize balanced distribution of business traffic through the load balancing weight, which is conducive to improving the system performance and system flexibility of the above payment system 100.
[0079] As an optional implementation of the above payment system, the storage service end 110 includes:
[0080] Certificate encryption module, used to encrypt certificate files;
[0081] And / or, a redundant backup module, used for performing redundant backup of certificate files.
[0082] It is understandable that the payment certificate can be used to sign or encrypt the payment request, and the payment certificate itself can also be encrypted. The above-mentioned certificate encryption module can encrypt and package different certificate files of different accounts and store them separately at different addresses, thereby improving the storage security of the payment certificate.
[0083] In addition, the redundant backup module can perform redundant backup of the certificate file, thereby improving the reliability of the certificate file, so that the payment system 100 has the ability to cope with failures.
[0084] In the implementation process of the above scheme, by setting up a certificate encryption module in the storage service end to encrypt the certificate file, it is helpful to improve the security of the above payment system; by setting up a redundant backup module in the storage service end, it is helpful to improve the reliability of the above payment system.
[0085] See also Figure 2 , the following is an introduction to the interaction process of each component in the above payment system:
[0086] Step 1: The payment service end 130 receives the payment request sent by the payment request end;
[0087] Step 2: The payment service end 130 sends an interface routing query request to the database sub-end 121 based on the payment request end ID and the interface ID carried in the payment request;
[0088] Step 3: The database sub-end 121 searches for the interface route corresponding to the payment request according to the payment request end ID and the interface ID, and feeds back the interface route to the payment service end 130;
[0089] Step 4: The payment server 130 determines the target certificate in the interface routing based on the load balancing weight;
[0090] Step 5: The payment service terminal 130 sends a target certificate storage path query request to the configuration center sub-terminal 122;
[0091] Step 6: The configuration center sub-end 122 queries the bucket path information of the target certificate based on the certificate ID of the target certificate, and sends the bucket path information to the payment service end 130;
[0092] Step 7: The payment server 130 calls the API of the storage service client 110 based on the storage bucket path of the target certificate to pull the target certificate file from the storage service client 110;
[0093] Step 8: Use the target certificate file to sign or encrypt the payment request;
[0094] It is understandable that before using the target certificate file to sign or encrypt the payment request, the target certificate may be decrypted first to construct a certificate configuration class, and then the target certificate file may be signed or encrypted using the certificate configuration class.
[0095] Step 9: Send the encrypted payment request to the payment processing end;
[0096] In the above step nine, the encrypted payment request can be sent to the payment processing end by calling the API of the payment processing end.
[0097] The above-mentioned scheme for the payment server 130 to load the certificate configuration information may include:
[0098] Step 1: Initialize an empty Map named certificateMap;
[0099] Step 2: Obtain a list of configuration information of all certificates from the configuration center sub-terminal 122;
[0100] Step 3: For each configuration information in the configuration information list, include:
[0101] a. Extract the certificate ID;
[0102] b. Check if there is already an entry for the certificate ID in certificateMap;
[0103] c. If it does not exist, perform the following steps:
[0104] i. Pull the certificate data stream from the storage server through the SFTP protocol according to the certificate ID;
[0105] ii. Decrypt the certificate data stream;
[0106] iii. Use the decrypted certificate data to build the certificate configuration class;
[0107] iv. Store the certificate ID and certificate configuration class in certificateMap.
[0108] Step 4. Return to certificateMap.
[0109] See also Figure 3Based on the same inventive concept, the embodiment of the present application further provides a payment method, which is applied to the payment service end 130, and the method includes:
[0110] Step S210: receiving a payment request sent by a payment request end;
[0111] Step S220: Based on the payment request, query the target certificate and its corresponding storage bucket path information in the certificate management terminal 120;
[0112] Step S230: Pull the target certificate from the storage service client 110 based on the bucket path information to encrypt the payment request;
[0113] Step S240: Send the encrypted payment request to the payment processing end.
[0114] As an optional implementation of the above-mentioned payment method, the above-mentioned step S210 queries the target certificate in the certificate management terminal 120, including: based on the load balancing weight, selecting the target interface route corresponding to the payment request in the interface routing information stored in the certificate management terminal; wherein the load balancing weight is used to indicate the probability of the interface route being selected; the load balancing weight is determined based on the certificate performance and / or the business traffic of the payment server; and the target certificate is determined based on the target interface route.
[0115] See also Figure 4 Based on the same inventive concept, the embodiment of the present application also provides a payment method, which is applied to the configuration center sub-terminal 122, and the method includes:
[0116] Step S310: monitoring whether the stored certificate ID and its corresponding storage bucket path information are updated;
[0117] Step S320: When the stored certificate ID and the corresponding storage bucket path information are updated, certificate update information is sent to the storage service client 110 so that the storage service client 110 updates the stored certificate file.
[0118] Based on the same inventive concept, the embodiment of the present application further provides a payment device applied to the payment server 130, the device comprising:
[0119] A payment request receiving unit, used to receive a payment request sent by a payment request end;
[0120] A storage path query unit, configured to query the target certificate and its corresponding storage bucket path information in the certificate management terminal based on the payment request;
[0121] A payment request encryption unit, configured to encrypt the payment request by pulling the target certificate from the storage service end based on the bucket path information;
[0122] The encrypted request sending unit is used to send the encrypted payment request to the payment processing end.
[0123] As an optional implementation of the above-mentioned payment device, the above-mentioned storage path query unit queries the target certificate in the certificate management terminal, including:
[0124] Based on the load balancing weight, the target interface route corresponding to the payment request is selected from the interface routing information stored in the certificate management end; wherein the load balancing weight is used to indicate the probability of the interface route being selected; the load balancing weight is determined based on the certificate performance and / or the business flow of the payment service end;
[0125] A target certificate is determined based on the target interface route.
[0126] Based on the same inventive concept, the embodiment of the present application further provides a payment device applied to the configuration center sub-terminal 122, the device comprising:
[0127] An update monitoring unit, used to monitor whether the stored certificate ID and its corresponding storage bucket path information are updated;
[0128] The certificate updating unit is used to send certificate updating information to the storage service client when the stored certificate ID and the corresponding storage bucket path information are updated, so that the storage service client updates the stored certificate file.
[0129] Figure 5 A schematic diagram of an electronic device provided in an embodiment of the present application. Figure 5 The electronic device 400 includes: a processor 410, a memory 420 and a communication interface 430. These components are interconnected and communicate with each other through a communication bus 440 and / or other forms of connection mechanisms (not shown).
[0130] The memory 420 includes one or more (only one is shown in the figure), which may be, but not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), etc. The processor 410 and other possible components may access the memory 420, and read and / or write data therein.
[0131] The processor 410 includes one or more (only one is shown in the figure), which can be an integrated circuit chip with signal processing capabilities. The above-mentioned processor 410 can be a general-purpose processor, including a central processing unit (CPU), a micro control unit (MCU), a network processor (NP) or other conventional processors; it can also be a special-purpose processor, including a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
[0132] The communication interface 430 includes one or more (only one is shown in the figure), which can be used to communicate directly or indirectly with other devices to exchange data. For example, the communication interface 430 can be an Ethernet interface; it can be a mobile communication network interface, such as an interface of a 3G, 4G, or 5G network; or it can be other types of interfaces with data transceiving functions.
[0133] One or more computer program instructions may be stored in the memory 420 , and the processor 410 may read and execute these computer program instructions to implement the payment method and other desired functions provided in the embodiments of the present application.
[0134] Understandably, Figure 5The structure shown is for illustration only. The electronic device 400 may also include Figure 5 More or fewer components as shown, or with Figure 5 Different configurations are shown. Figure 5 Each component shown in the figure can be implemented by hardware, software or a combination thereof. For example, the electronic device 400 can be a single server (or other device with computing processing capabilities), a combination of multiple servers, a cluster of a large number of servers, etc., and can be both a physical device and a virtual device.
[0135] The present application also provides a computer-readable storage medium on which computer program instructions are stored. When the computer program instructions are read and executed by a computer processor, the payment method provided by the present application is executed. For example, the computer-readable storage medium can be implemented as Figure 5 The memory 420 in the electronic device 400.
[0136] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.
[0137] In addition, the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0138] Furthermore, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
[0139] The above description is only an embodiment of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims
1. A payment system, characterized in that: The system comprises: a payment service end, and a storage service end and a certificate management end respectively communicating with the payment service end, wherein: The storage service end is used to store certificate files; The certificate management terminal is used to store interface routing information and bucket path information corresponding to each certificate ID; the interface routing information is used to indicate the corresponding relationship between the payment request terminal ID and the interface ID and the certificate ID; The payment service end is used to receive a payment request sent by a payment request end; based on the payment request, query the target certificate and its corresponding bucket path information on the certificate management end; based on the bucket path information, call the target certificate from the storage service end to encrypt the payment request; and send the encrypted payment request to the payment processing end.
2. The payment system according to claim 1, characterized in that: The certificate management end includes: a database sub-end and a configuration center sub-end respectively communicating with the payment service end, wherein: The database sub-end is used to store interface routing information; The configuration center sub-end is used to store each certificate ID and its corresponding storage bucket path information.
3. The payment system according to claim 2, characterized in that: The configuration center sub-end includes: The certificate update monitoring module is used to send certificate update information to the storage service end when the stored certificate ID and the corresponding storage bucket path information are updated, so that the storage service end updates the stored certificate file.
4. The payment system according to claim 1, characterized in that: The payment service end includes: An interface routing selection module is used to select a target interface routing corresponding to the payment request from the interface routing information stored in the certificate management end based on a load balancing weight; wherein the load balancing weight is used to indicate the probability of the interface routing being selected; and the load balancing weight is determined based on certificate performance and / or business traffic of the payment service end.
5. The payment system according to any one of claims 1 to 4, characterized in that: The storage service end includes: A certificate encryption module, used for encrypting the certificate file; And / or, a redundant backup module, used for performing redundant backup of the certificate file.
6. A payment method, characterized in that: Applied to the payment service end, the method includes: Receive a payment request sent by a payment request end; Based on the payment request, query the target certificate and its corresponding storage bucket path information in the certificate management terminal; Pull the target certificate from the storage service end based on the bucket path information to encrypt the payment request; The encrypted payment request is sent to the payment processing end.
7. The payment method according to claim 6, characterized in that: The querying of the target certificate in the certificate management terminal includes: Based on the load balancing weight, the target interface route corresponding to the payment request is selected from the interface routing information stored in the certificate management end; wherein the load balancing weight is used to indicate the probability of the interface route being selected; the load balancing weight is determined based on the certificate performance and / or the business flow of the payment service end; A target certificate is determined based on the target interface route.
8. A payment method, characterized in that: Applied to the configuration center sub-terminal, the method includes: Monitor whether the stored certificate ID and its corresponding bucket path information are updated; When the stored certificate ID and the corresponding storage bucket path information are updated, certificate update information is sent to the storage service client so that the storage service client updates the stored certificate file.
9. An electronic device, characterized in that: include: A processor, a memory and a communication bus, wherein the processor and the memory communicate with each other via the communication bus; The memory stores program instructions executable by the processor, and the processor can execute the method according to any one of claims 6 to 8 by calling the program instructions.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and when the computer instructions are executed by a computer, the computer is caused to perform the method according to any one of claims 6 to 8.