A transfer method, system and transfer platform connecting a payment platform and a non-tax bill system

Abstract

The present invention relates to the field of data processing technology, and in particular to a transfer method, system and transfer platform for connecting a payment platform and a non-tax bill system. The transfer method for connecting a payment platform and a non-tax bill system is to set up a non-tax bill transfer platform to adapt to the payment platform and the non-tax bill system respectively; the non-tax bill transfer platform adapts to all functions of the non-tax bill system; when the payment platform initiates a request to the non-tax bill transfer platform, the non-tax bill transfer platform directly responds to the payment platform. This allows the payment platform to obtain the capabilities of the non-tax bill system without having to connect to the non-tax bill system one by one, which will greatly reduce workload and reduce R&D costs. From the non-tax bill system side, the risks brought by multi-system access are reduced. The non-tax bill system only needs to open one interface to the non-tax bill transfer platform, without opening multiple interfaces. From the system security level, it is safer and more convenient.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a transfer method, system and transfer platform for connecting a payment platform and a non-tax bill system. Background Art

[0002] The current payment process for fiscal non-tax funds requires the existing unified payment platform to be integrated with the non-tax billing system. However, there is more than one non-tax billing system; there are provincial and municipal non-tax billing systems, and these systems are further categorized into 1.0, 2.0, and 3.0 billing systems. When developing a provincial unified payment platform for non-tax payment services, it needs to integrate with each of these systems, creating a large and complex integration workload. If the unified payment platform were deployed separately in each city, each payment platform would need to integrate with a different non-tax billing system, exponentially increasing the workload.

[0003] The current implementation method of non-tax payment is complex and cumbersome. From the perspective of the payment platform, there are many systems that need to be connected.

[0004] Connecting with the non-tax bill system involves more than just the payment process. There are also multiple links such as payment slip issuance, payment slip inquiry, payment slip confirmation, payment slip statement upload, electronic invoice issuance and inquiry. For each link, each payment platform needs to be connected with different non-tax and bill systems, and the workload is growing exponentially.

[0005] For each different non-tax invoice system, the docking standards are different, which makes it impossible to quickly implement the payment platform, prolongs the online time, and brings unnecessary cumbersome development.

[0006] The configured backend needs to be deployed on each payment platform, and configuration is required every time a non-tax invoice system is connected, which increases the workload of operation and maintenance personnel. Summary of the Invention

[0007] To this end, a transfer method connecting the payment platform and the non-tax bill system is needed to solve the problems of the payment platform needing to connect with different non-tax and bill systems, which requires different configurations and development for each system, resulting in a large workload and cumbersome development. The specific technical solution is as follows:

[0008] A transfer method for connecting a payment platform and a non-tax bill system, comprising the steps of:

[0009] The non-tax bill transfer platform is adapted to the payment platform and non-tax bill system respectively;

[0010] The non-tax bill transfer platform is adapted to all functions of the non-tax bill system;

[0011] The payment platform initiates a request to the non-tax bill transfer platform, and the non-tax bill transfer platform directly responds to the payment platform.

[0012] Furthermore, the "non-tax bill transfer platform is adapted to the payment platform and the non-tax bill system respectively" specifically includes the following steps:

[0013] The non-tax bill transfer platform generates different interface layers corresponding to the non-tax bill system by defining different system macros;

[0014] Connecting with each non-tax bill system through the different interface layers, and then the non-tax bill transfer platform uniformly encapsulates an interface;

[0015] The payment platform is connected to the non-tax bill transfer platform through an interface encapsulated in a unified manner.

[0016] Furthermore, the "non-tax bill transfer platform is adapted to all functions of the non-tax bill system" specifically includes the following steps:

[0017] The non-tax invoice transfer platform accesses documents according to the standards of the non-tax invoice system and obtains data information from the non-tax invoice system.

[0018] Furthermore, the “payment platform initiates a request to the non-tax bill transfer platform, and the non-tax bill transfer platform directly responds to the payment platform” specifically includes the following steps:

[0019] The content of the request includes an object identifier. The non-tax invoice transfer platform initiates a request to the corresponding non-tax invoice system according to the object identifier and returns the data information required by the payment platform.

[0020] Furthermore, before the payment platform initiates a request to the non-tax bill transfer platform, the following steps are also included:

[0021] Configure the correspondence between the payment platform and the non-tax invoice system through the background.

[0022] In order to solve the above technical problems, a transfer system connecting the payment platform and the non-tax bill system is also provided. The specific technical solution is as follows:

[0023] A transfer system connecting the payment platform and the non-tax bill system, wherein the transfer system is adapted to the payment platform and the non-tax bill system respectively;

[0024] The transfer system is adapted to all functions of the non-tax bill system;

[0025] The transfer system receives the initiation request from the payment platform and responds to it.

[0026] Furthermore, the transit system generates different interface layers corresponding to the non-tax bill system by defining different system macros;

[0027] Connecting with each non-tax bill system through the different interface layers, and then the transfer system encapsulates an interface;

[0028] The transfer system is connected to the payment platform through the unified encapsulated interface.

[0029] Furthermore, the transit system accesses documents according to the standards of the non-tax invoice system and obtains data information from the non-tax invoice system.

[0030] Furthermore, the content of the request includes an object identifier, and the transit system initiates a request to the corresponding non-tax invoice system according to the object identifier, and returns the data information required by the payment platform.

[0031] In order to solve the above technical problems, a transfer platform is also provided. The specific technical solutions are as follows:

[0032] A transfer platform, including: a non-tax bill transfer platform, a payment platform and a non-tax bill system;

[0033] The non-tax bill transfer platform is adapted to the payment platform and non-tax bill system respectively;

[0034] The non-tax bill transfer platform is adapted to all functions of the non-tax bill system;

[0035] The payment platform initiates a request to the non-tax bill transfer platform, and the non-tax bill transfer platform directly responds to the payment platform.

[0036] The beneficial effects of the present invention are: by setting up a non-tax bill transfer platform to adapt to the payment platform and the non-tax bill system respectively; the non-tax bill transfer platform adapts to all functions of the non-tax bill system; when the payment platform initiates a request to the non-tax bill transfer platform, the non-tax bill transfer platform directly responds to the payment platform. This allows the payment platform to obtain the capabilities of the non-tax bill system without having to connect to the non-tax bill system one by one, which will greatly reduce the workload and reduce R&D costs. From the perspective of the non-tax bill system, the risks brought by the access of multiple systems are reduced. The non-tax bill system only needs to open one interface to the non-tax bill transfer platform, without opening multiple interfaces. From the perspective of system security, it is safer and more convenient.

[0037] The non-tax bill transfer platform realizes the empowerment of non-tax and bill capabilities by connecting with multiple sets of non-tax bill systems respectively, and directly outputs this capability to each payment platform, so that the payment platform can quickly implement it by connecting with the set of non-tax bill systems during the implementation process.

[0038] By integrating the non-tax bill transfer platform with the non-tax bill system, all non-tax and bill-related operations and data are retained on the non-tax bill transfer platform. During the integration process, payment platforms can be directly reused, reducing duplication of construction.

[0039] Through the configuration of the visual management page of the non-tax invoice transfer platform, the problem of one-to-one matching between industry non-tax and payment units has been solved. The landing account of the payment unit only needs to be configured once, and the platform merchants of the payment platform can be connected with the landing account of the payment unit, avoiding the increased probability of errors caused by multiple configurations and ensuring that the payment funds can fall into the correct account.

[0040] When designing this non-tax bill transfer platform, comprehensive consideration was given to the non-tax models of different payment platforms. It can be perfectly connected to third-party payment platforms as an independent system, with better compatibility and convenience. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 A flowchart of a transfer method for connecting a payment platform and a non-tax bill system according to a specific embodiment;

[0042] Figure 2 This is a schematic diagram of an application system for a transfer method connecting a payment platform and a non-tax bill system according to a specific embodiment;

[0043] Figure 3 This is a schematic diagram of the application architecture of a transfer method for connecting a payment platform and a non-tax bill system according to a specific embodiment;

[0044] Figure 4 This is a schematic diagram of the platform application architecture described in the specific implementation method;

[0045] Figure 5 This is a schematic diagram of the deployment structure design described in the specific implementation method;

[0046] Figure 6 A business diagram of a transfer method for connecting a payment platform and a non-tax bill system according to a specific embodiment;

[0047] Figure 7 This is a module diagram of a transfer system connecting a payment platform and a non-tax bill system according to a specific embodiment;

[0048] Figure 8 This is a module schematic diagram of a transfer platform described in a specific implementation method.

[0049] Description of reference numerals:

[0050] 700, transfer system,

[0051] 800. A transfer platform,

[0052] 801. Non-tax bill transfer platform,

[0053] 802. Payment platform,

[0054] 803. Non-tax invoice system. DETAILED DESCRIPTION

[0055] In order to explain the technical content, structural features, achieved objectives and effects of the technical solution in detail, the following is a detailed description in conjunction with specific embodiments and accompanying drawings.

[0056] See also Figures 1 to 6 In this embodiment, a transit method connecting a payment platform and a non-tax bill system can be applied to a transit system connecting a payment platform and a non-tax bill system. The transit system connecting a payment platform and a non-tax bill system includes: a non-tax bill transit platform.

[0057] Specifically, Figure 2 As shown:

[0058] Payment platform side:

[0059] 1) Output payment capabilities, with deployment modes divided into provincial unified payment platforms and municipal payment platforms;

[0060] 2) If non-tax payment business is required, it is also necessary to connect to the non-tax bill system to obtain non-tax capabilities.

[0061] Non-tax bill system:

[0062] 1) Provide non-tax bill support capabilities to the payment platform, such as payment receipt issuance, payment receipt inquiry, payment receipt confirmation, bill acquisition, etc.

[0063] 2) There are provincial non-tax bill systems and municipal non-tax bill systems, and the bill systems are divided into new and old versions. The current mainstream ones are version 2.0 and version 3.0.

[0064] Non-tax bill transfer platform:

[0065] Provide adaptation services for a non-tax system and a bill system, and provide access services for multiple payment platforms.

[0066] The core technical idea of ​​this application is: the non-tax invoice transfer platform, which provides adaptation services to the non-tax system and the invoice system, and provides docking services for multiple payment platforms. It is only necessary to connect to different non-tax systems and invoice systems once through the non-tax invoice transfer platform, and the subsequent payment platforms can directly connect to the non-tax invoice transfer platform. Only one docking is required to complete the implementation of services in each link. The configuration background only needs to deploy one set on the non-tax invoice transfer platform side, and there is no need to deploy it on each payment platform. Configure the accessed non-tax invoice system related data and the accessed payment platform related data on the non-tax invoice system side to associate the two.

[0067] Step S101: The non-tax bill transfer platform is adapted to the payment platform and the non-tax bill system respectively. It specifically also includes the following steps: the non-tax bill transfer platform generates different interface layers corresponding to the non-tax bill system by defining different system macros; it connects with each non-tax bill system respectively through the different interface layers, and then the non-tax bill transfer platform uniformly encapsulates an interface; the payment platform connects with the non-tax bill transfer platform through the uniformly encapsulated interface. That is: the non-tax bill transfer platform defines different system macros, and this header file becomes the interface layer of the corresponding non-tax bill system after expansion. It connects with each non-tax bill system respectively through different interface layers, and then the transfer platform uniformly encapsulates an interface. In the subsequent process of connecting the payment platform, it only needs to call this one interface to obtain the implementation files corresponding to different systems. Please describe the application architecture of the platform as follows Figure 4 As shown, the deployment structure design is as follows Figure 5 shown.

[0068] During the deployment of the transit platform, the CentOS Linux 7.4 (64-bit) operating system was used, deployed on the government cloud to ensure data security and stability. Internally deployed support components such as Redis, logging services, and full-path tracking support upper-layer non-tax invoice services, basic information services, reconciliation services, non-tax adaptation services, and invoice adaptation services. Furthermore, by deploying an OpenAPI gateway system and establishing an operations configuration management webpage and an operations supervision service webpage, login accounts are provided for payment platform operators to meet configuration requirements.

[0069] Step S102: The non-tax bill transfer platform adapts to all functions of the non-tax bill system. Specifically, it also includes the following steps:

[0070] The non-tax bill transfer platform accesses documents according to the standards of the non-tax bill system and obtains data information from the non-tax bill system. Figure 3As shown, the non-tax bill transfer platform, through integration with the non-tax bill system, provides capabilities such as payment receipt query, payment receipt issuance, payment receipt confirmation, non-tax adaptation services, bill query, bill issuance, bill download, bill adaptation services, transaction flow download, and fund statement download. By connecting to the non-tax bill transfer platform, electronic payment platforms can obtain these capabilities, including non-tax-related capabilities, without having to connect to each non-tax bill system individually.

[0071] Step S103: The payment platform initiates a request to the non-tax bill transfer platform, and the non-tax bill transfer platform directly responds to the payment platform. Specifically, the following steps are included:

[0072] The content of the request includes an object identifier. The non-tax invoice transfer platform initiates a request to the corresponding non-tax invoice system according to the object identifier and returns the data information required by the payment platform.

[0073] Furthermore, in this application, being compatible with multiple sets of non-tax and bill systems and multiple payment platforms at the same time is a technical difficulty. It is necessary to clarify which system the payment platform is targeting during the payment process, and which version of the bill system the bill is issued from. During the implementation process, in terms of data docking and request, the interface docking is used. The non-tax bill transfer platform provides a standard interface docking method for the payment platform, and accesses it according to the standard documents of the non-tax bill system to obtain data information on the non-tax bill side. In the implementation of how to achieve a one-to-one correspondence between the payment platform and the non-tax bill system, a background configuration method is adopted. The payment object of the payment platform is paired with the non-tax bill system. When the payment platform requests the non-tax bill transfer platform, the object identifier is included. The non-tax bill transfer platform requests the corresponding non-tax or bill system based on the identifier, thereby returning the data information required by the payment platform.

[0074] Its overall business process is as follows Figure 6 As shown, further, in the data access and transmission process of each process, this application adopts technologies such as digital certificates, attribute certificates and XML encryption to make the authentication process more secure and the permission management more convenient. At the same time, it also ensures the security of data during network transmission and the flexibility of encryption, and realizes secure access to remote databases and secure data transmission.

[0075] By setting up a non-tax bill transfer platform to adapt to the payment platform and non-tax bill system respectively; the non-tax bill transfer platform adapts to all functions of the non-tax bill system; when the payment platform initiates a request to the non-tax bill transfer platform, the non-tax bill transfer platform directly responds to the payment platform. This allows the payment platform to obtain the capabilities of the non-tax bill system without having to connect to the non-tax bill system one by one, which will greatly reduce the workload and reduce R&D costs. From the perspective of the non-tax bill system, the risks brought by the access of multiple systems are reduced. The non-tax bill system only needs to open one interface to the non-tax bill transfer platform, without opening multiple interfaces. From the perspective of system security, it is safer and more convenient.

[0076] The non-tax bill transfer platform realizes the empowerment of non-tax and bill capabilities by connecting with multiple sets of non-tax bill systems respectively, and directly outputs this capability to each payment platform, so that the payment platform can quickly implement it by connecting with the set of non-tax bill systems during the implementation process.

[0077] By integrating the non-tax bill transfer platform with the non-tax bill system, all non-tax and bill-related operations and data are retained on the non-tax bill transfer platform. During the integration process, payment platforms can be directly reused, reducing duplication of construction.

[0078] Through the configuration of the visual management page of the non-tax invoice transfer platform, the problem of one-to-one matching between industry non-tax and payment units has been solved. The landing account of the payment unit only needs to be configured once, and the platform merchants of the payment platform can be connected with the landing account of the payment unit, avoiding the increased probability of errors caused by multiple configurations and ensuring that the payment funds can fall into the correct account.

[0079] When designing this non-tax bill transfer platform, comprehensive consideration was given to the non-tax models of different payment platforms. It can be perfectly connected to third-party payment platforms as an independent system, with better compatibility and convenience.

[0080] See also Figures 3 to 7 In this embodiment, a specific implementation of a transfer system connecting the payment platform and the non-tax bill system is as follows:

[0081] like Figure 7As shown, a transit system 700 is connected to the payment platform and the non-tax bill system, and the transit system 700 is adapted to the payment platform and the non-tax bill system respectively. Specifically, it can be as follows: the transit system 700 generates different interface layers corresponding to the non-tax bill system by defining different system macros; it connects with each non-tax bill system respectively through the different interface layers, and then the transit system 700 uniformly encapsulates an interface; the payment platform connects with the transit system 700 through the uniformly encapsulated interface. That is: the transit system 700 defines different system macros, and this header file becomes the interface layer of the corresponding non-tax bill system after expansion. It connects with each non-tax bill system respectively through different interface layers, and then the transit platform uniformly encapsulates an interface. In the subsequent process of connecting the payment platform, it only needs to call this one interface to obtain the implementation files corresponding to different systems. Please refer to the application architecture of the platform as shown below. Figure 4 As shown, the deployment structure design is as follows Figure 5 shown.

[0082] During the deployment of the transit platform, the CentOS Linux 7.4 (64-bit) operating system was used, deployed on the government cloud to ensure data security and stability. Internally deployed support components such as Redis, logging services, and full-path tracking support upper-layer non-tax invoice services, basic information services, reconciliation services, non-tax adaptation services, and invoice adaptation services. Furthermore, by deploying an OpenAPI gateway system and establishing an operations configuration management webpage and an operations supervision service webpage, login accounts are provided for payment platform operators to meet configuration requirements.

[0083] The transfer system 700 is adapted to all functions of the non-tax bill system. Specifically, the transfer system 700 performs document access according to the standards of the non-tax bill system and obtains data information from the non-tax bill system. Figure 3 As shown, by adapting to the non-tax bill system, transit system 700 provides capabilities such as payment receipt query, payment receipt issuance, payment receipt confirmation, non-tax adaptation services, bill query, bill issuance, bill download, bill adaptation services, transaction flow download, and fund statement download. By connecting to transit system 700, electronic payment platforms can access these capabilities, eliminating the need to connect to individual non-tax bill systems.

[0084] The transfer system 700 receives the initiation request from the payment platform and responds to it. The details are as follows:

[0085] The content of the request includes an object identifier. The transfer system 700 initiates a request to the corresponding non-tax invoice system according to the object identifier and returns the data information required by the payment platform.

[0086] Furthermore, in this application, being compatible with multiple sets of non-tax and bill systems and multiple payment platforms at the same time is a technical difficulty. It is necessary to clarify which system the payment platform is targeting during the payment process and which version of the bill system the bill is issued from. During the implementation process, the interface is used for data docking and request. The transit system 700 provides a standard interface docking method for the payment platform, and accesses it according to the standard documents of the non-tax bill system to obtain data information on the non-tax bill side. In the implementation of how to achieve a one-to-one correspondence between the payment platform and the non-tax bill system, a background configuration method is adopted. The payment object of the payment platform is paired with the non-tax bill system. When the payment platform requests the transit system 700, it carries the object identifier. The transit system 700 requests the corresponding non-tax or bill system based on the identifier, thereby returning the data information required by the payment platform.

[0087] Its overall business process is as follows Figure 6 As shown, further, in the data access and transmission process of each process, this application adopts technologies such as digital certificates, attribute certificates and XML encryption to make the authentication process more secure and the permission management more convenient. At the same time, it also ensures the security of data during network transmission and the flexibility of encryption, and realizes secure access to remote databases and secure data transmission.

[0088] By setting up a self-configured transfer system 700 to adapt to the payment platform and non-tax invoice system respectively; transfer system 700 adapts to all functions of the non-tax invoice system; when the payment platform initiates a request to transfer system 700, transfer system 700 directly responds to the payment platform. This allows the payment platform to obtain the capabilities of the non-tax invoice system without having to connect to each non-tax invoice system one by one, which will greatly reduce workload and R&D costs. From the perspective of the non-tax invoice system, this reduces the risks associated with multiple system access. The non-tax invoice system only needs to open a single interface to transfer system 700, eliminating the need for multiple interfaces. From a system security perspective, this is more secure and convenient.

[0089] The transit system 700 realizes the non-tax and bill capability empowerment by connecting with multiple non-tax bill systems respectively, and directly outputs this capability to each payment platform, so that the payment platform can quickly implement it by connecting with the non-tax bill system during the implementation process.

[0090] By adapting the transfer system 700 to the non-tax bill system, all non-tax and bill-related operations and data are retained in the transfer system 700. During the docking process, the payment platform can be directly reused, reducing duplication of construction.

[0091] Through the configuration of the 700 visual management page of the transfer system, the problem of one-to-one matching between industry non-tax and payment units is solved, and the landing account of the payment unit only needs to be configured once, and the platform merchant of the payment platform and the landing account of the payment unit can be connected in series, avoiding the increased probability of errors caused by multiple configurations, and ensuring that the payment funds can fall into the correct account.

[0092] The transfer system 700 was designed with comprehensive consideration of the non-tax modes of different payment platforms. It can be perfectly connected to third-party payment platforms as an independent system, with better compatibility and convenience.

[0093] See also Figures 2 to 6 ,and Figure 8 In this embodiment, a specific implementation of the transfer platform 800 is as follows:

[0094] The specific ones can be as follows Figure 2 As shown:

[0095] Payment platform 802 side:

[0096] 1) Output payment capabilities, with deployment modes divided into provincial unified payment platform 802 and municipal payment platform 802;

[0097] 2) If non-tax payment services are required, it is also necessary to connect to the non-tax bill system 803 to obtain non-tax capabilities.

[0098] Non-tax bill system 803:

[0099] 1) Provide non-tax bill support capabilities to the payment platform 802, such as payment receipt issuance, payment receipt query, payment receipt confirmation, bill acquisition, etc.

[0100] 2) There are provincial non-tax bill system 803 and municipal non-tax bill system 803, and the bill system is divided into new and old versions. The current mainstream ones are version 2.0 and version 3.0.

[0101] Non-tax bill transfer platform 801:

[0102] Provides adaptation services for a non-tax system and a bill system, and provides access services for multiple payment platforms 802.

[0103] The following is a detailed description of each module:

[0104] The non-tax bill transfer platform 801 is adapted to the payment platform 802 and the non-tax bill system 803 respectively. Specifically, it can be as follows: the non-tax bill transfer platform 801 generates different interface layers corresponding to the non-tax bill system 803 by defining different system macros; it connects with each non-tax bill system 803 through the different interface layers, and then the non-tax bill transfer platform 801 uniformly encapsulates an interface; the payment platform 802 connects with the non-tax bill transfer platform 801 through the uniformly encapsulated interface. That is: the non-tax bill transfer platform 801 defines different system macros, and this header file becomes the interface layer of the corresponding non-tax bill system 803 after expansion. It connects with each non-tax bill system 803 through different interface layers, and then the transfer platform uniformly encapsulates an interface. In the subsequent process of connecting the payment platform 802, it only needs to call this one interface to obtain the implementation files corresponding to different systems. Please refer to the application architecture of the platform as follows Figure 4 As shown, the deployment structure design is as follows Figure 5 shown.

[0105] During the deployment of the transit platform, the CentOS Linux 7.4 (64-bit) operating system was used, deployed on the government cloud to ensure data security and stability. Internally deployed support components such as Redis, logging services, and full-path tracking support upper-layer non-tax invoice services, basic information services, reconciliation services, non-tax adaptation services, and invoice adaptation services. Furthermore, by deploying an OpenAPI gateway system and establishing an operations configuration management webpage and an operations supervision service webpage, login accounts were provided to the payment platform's 802 operators to meet configuration requirements.

[0106] The non-tax bill transfer platform 801 adapts to all functions of the non-tax bill system 803. Specifically, the non-tax bill transfer platform 801 accesses documents according to the standards of the non-tax bill system 803 and obtains data information from the non-tax bill system 803. Figure 3 As shown, non-tax bill transfer platform 801, by adapting to non-tax bill system 803, obtains capabilities such as payment receipt query, payment receipt issuance, payment receipt confirmation, non-tax adaptation services, bill query, bill issuance, bill download, bill adaptation services, transaction flow download, and fund statement download. Electronic payment platform 802, by connecting to non-tax bill transfer platform 801, can obtain these capabilities and non-tax-related capabilities without having to connect to non-tax bill system 803 one by one.

[0107] The payment platform 802 initiates a request to the non-tax bill transfer platform 801, and the non-tax bill transfer platform 801 directly responds to the payment platform 802. Specifically, the request includes an object identifier. The non-tax bill transfer platform 801 initiates a request to the corresponding non-tax bill system 803 based on the object identifier and returns the required data information to the payment platform 802.

[0108] Furthermore, in this application, compatibility with multiple sets of non-tax and bill systems and multiple payment platforms 802 at the same time is a technical difficulty. It is necessary to clarify which system the payment platform 802 is targeting during the payment process and which version of the bill system the bill is issued from. During the implementation process, in terms of data docking and request, the interface is connected. The non-tax bill transfer platform 801 provides a standard interface docking method for the payment platform 802, and accesses it according to the standard documents of the non-tax bill system 803 to obtain non-tax bill side data information. In the implementation of how to achieve a one-to-one correspondence between the payment platform 802 and the non-tax bill system 803, a background configuration method is adopted. The payment object of the payment platform 802 is paired with the non-tax bill system 803. When the payment platform 802 requests the non-tax bill transfer platform 801, it carries the object identifier. The non-tax bill transfer platform 801 requests the corresponding non-tax or bill system based on the identifier, thereby returning the data information required by the payment platform 802.

[0109] Its overall business process is as follows Figure 6 As shown, further, in the data access and transmission process of each process, this application adopts technologies such as digital certificates, attribute certificates and XML encryption to make the authentication process more secure and the permission management more convenient. At the same time, it also ensures the security of data during network transmission and the flexibility of encryption, and realizes secure access to remote databases and secure data transmission.

[0110] By setting up a non-tax bill transfer platform 801 to adapt to the payment platform 802 and the non-tax bill system 803, the non-tax bill transfer platform 801 adapts to all functions of the non-tax bill system 803. When the payment platform 802 initiates a request to the non-tax bill transfer platform 801, the non-tax bill transfer platform 801 directly responds to the payment platform 802. This allows the payment platform 802 to access the capabilities of the non-tax bill system 803 without having to connect to each system individually, significantly reducing workload and R&D costs. From the perspective of the non-tax bill system 803, this reduces the risks associated with multiple system accesses. The non-tax bill system 803 only needs to open a single interface to the non-tax bill transfer platform 801, eliminating the need for multiple interfaces. This makes the system more secure and convenient.

[0111] The non-tax bill transfer platform 801 realizes the non-tax and bill capability empowerment by connecting with multiple sets of non-tax bill systems 803 respectively, and directly outputs this capability to each payment platform 802, so that the payment platform 802 can connect with the non-tax bill system 803 during the implementation process and quickly implement the implementation.

[0112] By adapting the non-tax bill transfer platform 801 to the non-tax bill system 803, all non-tax and bill-related operations and data are retained in the non-tax bill transfer platform 801. During the docking process, the payment platform 802 can be directly reused, reducing duplication of construction.

[0113] Through the configuration of the visual management page of the non-tax bill transfer platform 801, the problem of one-to-one matching between industry non-tax and payment units is solved, and the landing account of the payment unit only needs to be configured once, and the platform merchant of the payment platform 802 can be connected in series with the landing account of the payment unit, avoiding the increased probability of errors caused by multiple configurations and ensuring that the payment funds can fall into the correct account.

[0114] The non-tax bill transfer platform 801 was designed with comprehensive consideration of the non-tax modes of different payment platforms 802. It can be perfectly connected to the third-party payment platform 802 as an independent system, with better compatibility and convenience.

[0115] It should be noted that although the above embodiments have been described herein, this does not limit the scope of patent protection of the present invention. Therefore, based on the innovative concept of the present invention, changes and modifications to the embodiments described herein, or equivalent structural or equivalent process transformations made using the contents of the present invention's specification and drawings, and direct or indirect application of the above technical solutions to other related technical fields, are all included in the scope of patent protection of the present invention.

Claims

1. A transfer method connecting a payment platform and a non-tax bill system, characterized in that: Including steps: The non-tax bill transfer platform is adapted to the payment platform and non-tax bill system respectively; The non-tax bill transfer platform is adapted to all functions of the non-tax bill system; The payment platform initiates a request to the non-tax bill transfer platform, and the non-tax bill transfer platform directly responds to the payment platform; The non-tax bill transfer platform is adapted to the payment platform and the non-tax bill system respectively, and specifically includes the following steps: the non-tax bill transfer platform generates different interface layers corresponding to the non-tax bill systems by defining different system macros; the non-tax bill transfer platform connects with each non-tax bill system through the different interface layers, and then the non-tax bill transfer platform uniformly encapsulates an interface; the payment platform connects with the non-tax bill transfer platform through the uniformly encapsulated interface; The non-tax bill transfer platform is adapted to all functions of the non-tax bill system, and specifically includes the following steps: the non-tax bill transfer platform accesses documents according to the standards of the non-tax bill system and obtains data information from the non-tax bill system; The payment platform initiates a request to the non-tax bill transfer platform, and the non-tax bill transfer platform directly responds to the payment platform, specifically including the steps of: the content of the request includes an object identifier, the non-tax bill transfer platform initiates a request to the corresponding non-tax bill system according to the object identifier, and returns the data information required by the payment platform; Before the payment platform initiates a request to the non-tax bill transfer platform, the following steps are also included: Configure the correspondence between the payment platform and the non-tax invoice system through the background.

2. A transfer system connecting the payment platform and the non-tax bill system, characterized in that: The transfer system is adapted to the payment platform and the non-tax bill system respectively; The transfer system is adapted to all functions of the non-tax bill system; The transfer system receives the initiation request from the payment platform and responds to it; The transit system generates different interface layers corresponding to the non-tax bill system by defining different system macros; The transfer system is connected to each non-tax bill system through the different interface layers, and then the transfer system is uniformly encapsulated into an interface; The transfer system is connected to the payment platform through the unified encapsulated interface; The transfer system accesses documents according to the standards of the non-tax invoice system and obtains data information from the non-tax invoice system; The content of the request includes an object identifier. The transit system initiates a request to the corresponding non-tax invoice system based on the object identifier and returns the data information required by the payment platform. Configure the correspondence between the payment platform and the non-tax invoice system through the background.

3. A transfer platform, characterized in that: include: Non-tax bill transfer platform, payment platform and non-tax bill system; The non-tax bill transfer platform is adapted to the payment platform and non-tax bill system respectively; The non-tax bill transfer platform is adapted to all functions of the non-tax bill system; The payment platform initiates a request to the non-tax bill transfer platform, and the non-tax bill transfer platform directly responds to the payment platform; The non-tax bill transfer platform generates different interface layers corresponding to the non-tax bill systems by defining different system macros; the platform interfaces with each non-tax bill system through the different interface layers, and then the non-tax bill transfer platform uniformly encapsulates a single interface; the payment platform interfaces with the non-tax bill transfer platform through the uniformly encapsulated interface; The non-tax bill transfer platform accesses documents according to the standards of the non-tax bill system and obtains data information from the non-tax bill system; The content of the request includes an object identifier. The non-tax invoice transfer platform initiates a request to the corresponding non-tax invoice system based on the object identifier and returns the data information required by the payment platform. Configure the correspondence between the payment platform and the non-tax invoice system through the background.

Images